Getting NO HI-RES TERRAIN message while in flight

[jmurtagh13]

I've noticed that I get a voice "caution" several times an hour and the screen flashes at the same time but there is no message in the message box. So on this last trip I logged the time for about 10 occurrences, in all cases the ALERT DATA shows NO HI-RES TERRAIN message along with the SYS-CAUTION message.

So my question is this a concern? It is a little unnerving for my passengers.

I have 2 SykView touches connected to a Gramin 650

Thank you

John

 

[Dynon]

Hmm - that's a little odd. What do you see for high res terrain under SETUP MENU > LOCAL DISPLAY SETUP > INSTALLED DATABASES under the terrain heading? What's the EXACT string there? Do you see any synthetic vision on the PFD?

 

[jmurtagh13]

I do see the synthetic vision on the PFD. I'll check the installed databases this weekend unless that info is in the logs some where which I have here now.

 

[dynonsupport]

I bet if you look in the datalogs before that alert, it shows your GPS position somewhere outside of the USA for one update. We'll throw that alert if you're in a place where you don't have terrain data.

If it is doing this, you should probably pull a Dynon Diagnostic log so we can see what we are getting from the 650 and see what is up.

 

[jmurtagh13]

That's it, in every case 3 erroneous Latitude's are in the ALERT Data.

11.2512 -83.65282 3687 122.1 230.4 1.9 16:02:10 TEXT SHOW NO HI-RES TERRAIN
11.2512 -83.65282 3687 122.1 230.4 1.9 16:02:10 AUDIO PLAY SYS_CAUTION
11.2512 -83.65282 3687 122.1 230.4 1.9 16:02:10 AUDIO PLAY SYS_CAUTION

I do have the Diagnostic_Data what is the best way to get that to you?

Thank you

John

 

[jmurtagh13]

Attached is my Diagnostic Data

 

[dynonsupport]

John,
Thanks for the data logs.

In the data log it shows that the data we get over ARINC does show large jumps in LAT or LONG to other places in the world. This generally only happens for about 0.2 seconds. We believe this is in the data we get right from the 650 based on what we can see right now.

We've looked at our own 650, and it does the same thing. It's never come up before since almost everyone with a 650 also uses the SV-GPS-250, which is a better GPS source in general. This means SkyView ignores the 650's position, so when the data glitches, no warning is triggered.

We'll look into this further and let you know what we find.

 

[jmurtagh13]

Dynon,

Thank you for your very quick response and help.  What do you recommend I do next, should I report this issue to Garmin?  And if so what is the best way to do that?

John

 

[dynonsupport]

John,
Let us look into it a bit further and see what we can find. As we say, our own airplane with a 650 in it does it too, so we can do some more engineering and make sure it's not an issue on our end.

 

[jmurtagh13]

Sounds good.

Thank you

 

[jmurtagh13]

Dynon,

It's been a few years and I still have this issue with increased frequency. I was hoping that your software updates would have fixed this but they have not. I fly a lot of IFR and though it recovers quickly it's very disconcerting when flying an approach, each time it happens it cancels the autopilot. Please let me know if you need additional information I would really like to get this issue resolved.

Thank you

John

 

[CGameProgrammer]

They probably don't care because in two years you will need the SV-GPS-2020 and the issue does not occur with it. They said it only occurs when using the 650 as your GPS source.

 

[Dynon]

Actually, the 650 is a valid position device for ADS-B purposes, so those with a 650 don't necessarily need an SV-GPS-2020.

We did make changes to try to address this issue, but evidently, there are still some customers like yourself having issues. One thing we might want to try (if we haven't already) is a different ARINC module, because we do know that this isn't a universal issue (IE, lots of 650 customers but only isolated reports). I'm guessing you're running the latest 650 software too, so we can probably rule that out as an issue. Give our support team an email or call at 425-402-0433 or support at dynonavionics dot com, and mention that you're experiencing the issue described in case 200271

 

[jmurtagh13]

Dynon,

I've replaced my ARINC with the new one you sent me, thank you for getting the replacement to me. But it did not resolve the issue. Within the first 15 minutes of startup I got the warning and then again about 30 minutes later. I've attached the data log that contains the first event at the end of the log(I did the dump right after it happened - 12:13 EST). One other thing I noticed the serial number of the replacement ARINC is 16xx, while the one it replaced is 2141. So it seems like I replaced with an older unit but maybe the 16xx unit has been upgraded.

Thank you

John

 

[jmurtagh13]

Dynon,

Attached is the data dump for the 2nd occurrence of the warning message. The event happened at 12:46 EST about 15 minutes from the end of the file.

Thank you
John

 

[Dynon]

Hi John. Thanks for the update here. For more help with this issue, I'll have our support team reach out to you. We'd prefer to communicate with you personally instead of on the forum, as it is more integrated with our tech support services.