Search results

Thanks for the info Airguy!

So I flew yesterday and the problem did go away airborne, so maybe Dynon was right in my case. I do get the "ADS-B Partial" and/or "No Signal" message on the ground at my local Troutdale, OR (TTD, a few miles W. of PDX) airport however.

I gotta get that book!

Ah, crikey mate!

Oz? okay I don't get the joke. is it a joke? Seattle center maybe?

re: ADS-B No Signal Nav Unit: Skyview SV-HDX1100, ver. 17.4.0.23677 ADSB: SV-ADSB-472 Pt No: 102985-000, Firm. ver. 2.4.58 I've submitted this error to Dynon support and they are reviewing my diagnostic file that I uploaded. This is the error I've had starting about a month ago. Anyone...

I have a similar issue with my Skyview HDX and the latest software update of 17.4.0.2367. I didn't have this error initially after the software update, but the last couple of times I flew (over a month ago) the error was there, so I don't know if this is exactly the same software issue.

That helps a lot. I have a Garmin 175 (using Arinc 429) so that's good to know!

I have to admit I was a little hasty in my critique of Dynon on this issue. I haven't flown small private aircraft in over 35 years so I'm "new" to this type of flying (lol). I come from a professional background (30 yrs) using pro-level avionics which very seldom had an issue. If they did, the...

I just assumed Dynon was aware of the problem earlier, maybe I was wrong. I'm sure they'll address the problem. But, it's pretty hard to believe that the Dynon software developers don't notice a post with "Skyview System Software Bug" in the title, so I think they've known about this for a while.

Yeah you're right. We should all be perfectly satisfied with Dynan's silence on this software problem. Also, I'm not "paranoid" about anything. I was just curious as to why Dynon was taking so long to address this issue. I'm giving them a pass on this due to the holidays and this not being...

You're full of crap rhino. I like Dynon and I like the Skyview system that I purchased, but I also like corporate responsibility. You apparently don't give a damn about that.

My guess is they do not want to admit there's a screw up in their software for fear of litigation, in case there was an accident and someone blamed them because of this bug. Although this is a pretty minor bug, you'd still think they would admit it and notify users, which you could argue would...

nope. just irresponsible non-response in dealing with this issue. after this much time since these events they can't at least say they are looking into this?

Right. they probably imagine that we imagine they are looking into it. 😆

Crickets from Dynon on this issue. Hmmm...

Good question. Is your next waypoint the destination? Maybe it doesn't show that if there's not another intermediate waypoint?

Default is 68000. Increasing the value will Reduce reported fuel flow, Decreasing the value will Increase the reported fuel flow. Example: If you believe your reported fuel flow is 5% Low (remaining calculated fuel 5% higher than actual) then use 64,600 (.95 x 68000). Personally, I would use 7%...

Your memory does not serve you well (lol). Default is 68000. Increasing the value will Reduce reported fuel flow, Decreasing the value will Increase the reported fuel flow. Example: If you believe your reported fuel flow is 5% Low (remaining calculated fuel 5% higher than actual) then use...