Skyview 17.4 bug?

[PaulSS]

Sorry the photo is not so clear but taken off a video.

On this occasion the route was transferred from SkyDemon, via the SkyView WIFI, to the HDX flight plan. Once airborne, NAV was engaged and the autopilot followed the route but there was no annunciation of the next waypoint in either of the red 'circled' areas.

 

[kurtfly]

Just loaded 17.5. Did not fix the missing next waypoint.

Kurt

 

[swatson999]

You need to provide more data. What type of waypoint, for example? VOR? APT? User?

 

[PhilzSkyHdx]

Just loaded 17.5. Did not fix the missing next waypoint.

Kurt

Update: on my last flight I switched from GPS to Skyview for navigation and the Next waypoint displayed normally, so yeah, it is a problem with transferring flight plans via airinc 429 to the Skyview HDX panel. (ver. 17.6)


Dammit! I was hoping for that feature to get fixed.
Skyview HDX v. 17.5
More Info: I uploaded my flight plan from Foreflight (ipad) into my GPS175, using the AIRINC 429 link to my Skyview HDX 1100. I believe
the intermediate waypoints I used for that flight were uncrontrolled airports. I'll try some RNAV waypoint fixes next time.

 

[Biggiesauls]

Not happy to hear that but in looking over the issues fixed it only had 2 listed which seemed rather slim considering it’s been 6 months since 17.4 came out.

I was really hoping the dual comm feature was in this update also since it was announced at Sun&Fun. Sales mentioned 2-4 weeks at that time for release.

 

[kurtfly]

You need to provide more data. What type of waypoint, for example? VOR? APT? User?

Yes. All next waypoints is missing on the hsi and on the customizable list if you have NEXT WPT in the list.

so, to see what you are navigating to you must either hit the FPL to view flight plan or go to your navigator and view the flight plan.

 

[Blimpguy]

Yes. All next waypoints is missing on the hsi and on the customizable list if you have NEXT WPT in the list.View attachment 7132so, to see what you are navigating to you must either hit the FPL to view flight plan or go to your navigator and view the flight plan.

We are still working on running this one down, it's a weird bug and not all GTN/IFD customers are seeing it. Some have reverted back to an earlier version (17.1.0 and it seemed to resolve it for some, but not for all). We have diagnostic data from some customers that has been useful to the software team who is working on diagnosing and fixing it, if you haven't, please submit data after a flight via the link below to help us squash this one.

Early indications have pointed into garbage data coming over the ARINC stream from the NAV database that the external navigators are sending. Either a corrupted waypoint ID or simply a label that we deem as invalid (and maybe it isn't invalid). We're working on solving it though, I know it's frustrating..

Diagnostic File Upload Link

 

[Blimpguy]

Not happy to hear that but in looking over the issues fixed it only had 2 listed which seemed rather slim considering it’s been 6 months since 17.4 came out.

I was really hoping the dual comm feature was in this update also since it was announced at Sun&Fun. Sales mentioned 2-4 weeks at that time for release.

17.6.0 which includes the items shown off at SnF is targeted to be out by the end of the month. It's currently in the software test phase in-house, one of the last steps to releasing it into the wild.

 

[kurtfly]

I reverted back to version 17.1. This restored the “NEXT WPT” being displayed.

But now with about 5 flights i have had one occasion where my tablet will not stay connected to wifi. Another issue on shutdown i got a “system event 3”.

All issues that were improved after 17.1…..

I think i will live with the 17.1 bugs for now.

Kurt

 

[DBRV10]

So has anyone tried 17.1 yet to see if this is solved? I have a few customers here suffering and would like to know before getting their hopes up.

 

[PhilzSkyHdx]

So has anyone tried 17.1 yet to see if this is solved? I have a few customers here suffering and would like to know before getting their hopes up.

You mean 17.6 ?

also: For me, the missing "Next Waypoint" problem is from my Garmin GPS 175 when linked and displayed on my HDX 1100 panel. If I use the GPS 2020 (Dynon) Nav flight plan, the next waypoint displays properly. I'm running the Skyview HDX 17.5 software. Other than the "Next Waypoint" problem, v.17.5 seems to be error free for me, so I'll continue to use it until I get v.17.6 installed.

 

[Rhino]

So has anyone tried 17.1 yet to see if this is solved? I have a few customers here suffering and would like to know before getting their hopes up.

If you mean 17.6, no.

New Aug 2026 software question

Does the new software fix the next waypoint problem?

forum.flydynon.com

 

[kurtfly]

So has anyone tried 17.1 yet to see if this is solved? I have a few customers here suffering and would like to know before getting their hopes up.

I reverted back to 17.1 and the "NEXT WPT" is fixed. I will stay at 17.1 until it is fixed. I can live with the intermittent WiFi issues and System Event 3 errors on shutdown. Do not need any new features. You do have to pay attention on shutdown. If an error does pop up it will not shut down. It will exhaust your SV Battery.

Kurt

 

[DBRV10]

Yes, I did mean 17.6......I must have had 17.1 on my mind from those reverting.

I see no mention of it on the update so maybe not.

 

[Solana]

Sadly, not fixed. Hopefully everyone with the problem has uploaded a file through Blimpguy’s Diagnostic File Upload Link (posted May 18 on this thread). Maybe more data will help Dynon.

Rick

 

[steve m]

I did not have this issue of missing "Next Waypoint" until I installed 17.6...now I have this problem. I am not sure what version I updated from though..

Are there any instructions out there detailing how to go back a version of software? For IFR flying, I really like having the next waypoint displayed on an approach, very helpful and reassuring to know where the autopilot is navigating to. I am running Garmin 175 as the IFR navigator

 

[ve0kog]

Could @Dynon address what is happening in general on the software development side?

Just a few years ago we had a state of the art EFIS and now it is slowly falling behind competition. Simple features and fixes become a heavy lift with many months of effort. I'm hesitant to update anything until there is some clarity.

I would not mind a reasonable recurring support fee if that will move things along. There are so many improvement requests on this forum and most are just never adressed. Anything we can do to change that?

 

[PhilzSkyHdx]

I did not have this issue of missing "Next Waypoint" until I installed 17.6...now I have this problem. I am not sure what version I updated from though..
Are there any instructions out there detailing how to go back a version of software? For IFR flying, I really like having the next waypoint displayed on an approach, very helpful and reassuring to know...

I also use a Garmin GPS 175 for primary nav on approaches. And I use Foreflight displayed on my 11-in iPad which is connected to the Garmin via Bluetooth and to the Skyview HDX via Wi-Fi. It displays a lot of information on approaches, charts, weather, airports, Notams, traffic, etc. On approaches, you can bring up a side panel that shows all the step down fixes with altitudes and distances. I can quickly send a flight plan to the Garmin from Foreflight, and I can also easily upload changes I made in the Garmin to update the current flight plan displayed in Foreflight. I wouldn't fly IFR without it.
Note: Obviously this does nothing to fix the missing waypoint bug. I just wanted to share how I use Foreflight to enhance the nav system in general, improve situational awareness and it's a good workaround for the missing next waypoint issue.

 

[Marc_J._Zeitlin]

I also use a Garmin GPS 175 for primary nav on approaches...

As do I.

And I use Foreflight displayed on my 11-in iPad which is connected to the Garmin via Bluetooth and to the Skyview HDX via Wi-Fi.

As I do not.

But in any case, while there are some workarounds for the obvious bug in Dynon's software that's now been there for years and is a large issue and COULD be a safety issue, what does any of what you wrote have to do with that bug, which is what's being discussed?

Also, @ve0kog 's question is a valid one - while I really like my HDX system, they are NOT fixing bugs or adding features that have been suggested and they ARE falling further behind Garmin. They do not have an official bug reporting system for customers, nor an outward facing bug list indicating what they're working on and when they expect a resolution. For safety critical equipment, this is not acceptable, even though the idea to do this was suggested to them MANY years ago. I quite understand not having outward facing enhancement lists, but not indicating when bugs will be fixed, and which bugs they're going to ignore, is unacceptable.

I have not updated from 17.1 for the reasons indicated here and above. I do not trust 17.4 or 17.6 to be acceptable for IFR usage.

 

[PhilzSkyHdx]

As do I.

As I do not.

But in any case, while there are some workarounds for the obvious bug in Dynon's software that's now been there for years and is a large issue and COULD be a safety issue, what does any of what you wrote have to do with that bug, which is what's being discussed?

Also, @ve0kog 's question is a valid one - while I really like my HDX system, they are NOT fixing bugs or adding features that have been suggested and they ARE falling further behind Garmin. They do not have an official bug reporting system for customers, nor an outward facing bug list indicating what they're working on and when they expect a resolution. For safety critical equipment, this is not acceptable, even though the idea to do this was suggested to them MANY years ago. I quite understand not having outward facing enhancement lists, but not indicating when bugs will be fixed, and which bugs they're going to ignore, is unacceptable.

I have not updated from 17.1 for the reasons indicated here and above. I do not trust 17.4 or 17.6 to be acceptable for IFR usage.

My information on Foreflight has nothing to do with the problem other than it does allow you to see these missing waypoints that people are complaining about. Disregard it if it doesn't interest you.