I have the same problem. The VP-X screen is fully functional, meaning I can still activate the components by touch through the VP-X screen, but the rotary knob will not move the 'active' knob anywhere other than to the bottom of the screen. Scrolling through with a finger swipe works fine.
Software Update v16
- Thread starter yadmas
- Start date
swatson999
Well-Known Member
- Joined
- Oct 6, 2010
- Messages
- 1,534
I'm puzzled by something. The new software shows this as an improvement:
Just wondering...
However, I think that's backwards...NEXRAD usually (always?) shows *bright* green (or "light" green) for light precip, and *dark* green for moderate. Why is this backwards for Dynon? Is it because they're using luminance as more of a key to precip levels, rather than hue? (Incidentally, that's not a wrong approach...most color scales for data use rather poorly-designed schemes, e.g., red indicating "higher", rather than white/yellow, which has higher luminance value).
Just wondering...
Stevec
Member
- Joined
- Jun 24, 2020
- Messages
- 125
After installing the v16 update on both of my classic 7" and 10" screens I now find if they are turned on with the master switch the Knob panel does not come online. My work around is to power up the D1000 on backup battery and once its up and running turning on the master switch.
Dynon any ideas how this can be improved
Steve
Dynon any ideas how this can be improved
Steve
Raymo
I love aviation!
Maybe confirm the knob panel is seen/detected by both screens?
Stevec
Member
- Joined
- Jun 24, 2020
- Messages
- 125
Checked and knob panel missing from both screens which I probably would have expected as it is all on the same network. The knob panel is last in the list of network devices and is highlighted red and offline. As I mentioned the single device start up seems to pick it up OK.
pacecapt
Member
I just installed the Knob panel (one day before V16 was released) it took a couple of reboots but it was recognized. Works great with V16. Try resetting you pin connectors, I have found that has been an issue with other connections
Stevec
Member
- Joined
- Jun 24, 2020
- Messages
- 125
As I mentioned its only on a dual startup that it fails single start up is fine and when it's all up and running there are no problems and I have just done 3.5 hours flying with no problem. If there was a wiring issue I would expect random errors while it was working. I will try re establishing the network again and see if that has any effect.
TrevorMills
Member
- Joined
- Jan 9, 2020
- Messages
- 35
Flight Plan Altitudes?
Is there any way to add altitudes for each waypoint in an approach on the FLT PLN page? (I know the picture has airports in them but if it was a list of your approach waypoints, it would be nice if the altitudes were out to the side for quick reference.) Also, on some Flight displays while...
Ron Mortellito
New Member
I have the same issue. In my case, It's at the bottom of the VPX list, the knob does not scroll thru the list and touching, dragging, etc the scroll bar on the side DOES NOT respond. Interestingly, if I blindly turn the knob and find a device off the top of the items that show (such as Trim or Flaps) I can activate those devices by pressing the knob. Weird. I'm hoping this is something that came with last update.
EDIT: Correction. I CAN scroll up and down the VPX device list by dragging the whole list with my finger (not the side scroll bar). It is only the KNOB that will not scroll the list.
Last edited:
pacecapt
Member
Maybe the difference is that I have a 10 and 7" HDX not Classic...
Update: Digging deeper on this, I don't think there is a bug in the UDP streaming. What I did was make a bad assumption about Dynon's implementation. Dynon packs all three packets into one packet, whereas my partial packet picking protocol picks a packet from a pack of packets. I talked to Peter Piper who packs the picked packets and comfirmed that my packet picking wasn't perfect.
Said another way: The three Dynon sentences (ADAHRS, SYSTEM, EMS) are packed into one UDP packet, rather than three individual UDP packets that I was expecting. This means a significant code rewrite for my devices, particularly since I have to keep backwards compatibility with my existing UDP streaming device that plugs into the Dynon serial port. No sweat, it's just typing. A lot of typing.
V
Last edited:
Son of a gun.... just finished the upgrade and I too have this message. I have 2 10”HDX and only one has this warning. I rebooted etc but did not clear this. I have all the Dynon goodies - autopilot panel etc.
and then I read up the string a little and lmao about packet picking packers. We might need a separate thread for this trim warning.
and then I read up the string a little and lmao about packet picking packers. We might need a separate thread for this trim warning.
Colin Pazdzior
New Member
- Joined
- Oct 14, 2020
- Messages
- 22
So... I have no direct experience with these Dynon systems so far, but have been reading a fair bit of documentation in preparation for an install. I'm sure Dynon Support will chime in soon with a better answer, but one thing I note in v16 is support for the SV-AP-TRIMAMP (per a post on here, to be released on certified product with A36 STC expansion).
One of the details of this installation appears to be trim running detection and annunciation, via a dedicated wire from the trim amp to display pin 14 (contact input 3). See twin engine wiring diagram: https://www.dynoncertified.com/down...View_HDX_Wiring_Diagram_Twin_Engine_Rev_A.pdf
I don't see any reference to the "Trim Feedback Stuck" error in the documentation, but I wonder if the logic that monitors that input now also catches faults, like short to ground?
So, absent anything else from Dynon, I'd be curious about what's connected to pin 14 in your 37 pin main display connectors.... is pin 14 open, or grounded, or something else?
One of the details of this installation appears to be trim running detection and annunciation, via a dedicated wire from the trim amp to display pin 14 (contact input 3). See twin engine wiring diagram: https://www.dynoncertified.com/down...View_HDX_Wiring_Diagram_Twin_Engine_Rev_A.pdf
I don't see any reference to the "Trim Feedback Stuck" error in the documentation, but I wonder if the logic that monitors that input now also catches faults, like short to ground?
So, absent anything else from Dynon, I'd be curious about what's connected to pin 14 in your 37 pin main display connectors.... is pin 14 open, or grounded, or something else?
DBRV10
Active Member
So far so good. No bugs as suggested above. Have updated SV classics, HDX1100 and 800's so far....
I hope this stays true
I hope this stays true
Flew my two 7" HDX today, no squawks noted so far. Knob panel lights properly, no trim stuck issues. Flew an ILS approach in terribly gusty conditions, did fine (but it did drop below the glideslope pretty bad as I pulled power some power back). May have to do some more autopilot tuning.
Same problem. I had no problem without the engine running, but with the engine running, I had to reboot to get out of video mode.
New issue: reported to Dynon.
I get a Trim Feedback Stuck message, even though I am not using Dynon's trim controller and the trim sensor is directly wired to the EMS. My on-screen display is very slow to respond, but my trim tab works normally. The SV has no knowledge of trim position other than the voltage on the EMS input, so how can it determine 'feedback'?
I get a Trim Feedback Stuck message, even though I am not using Dynon's trim controller and the trim sensor is directly wired to the EMS. My on-screen display is very slow to respond, but my trim tab works normally. The SV has no knowledge of trim position other than the voltage on the EMS input, so how can it determine 'feedback'?
Hi Dave My two classics upgraded without any issues as well. Hoping no issues arise.So far so good. No bugs as suggested above. Have updated SV classics, HDX1100 and 800's so far....
I hope this stays true