Devices offline and software mismatch????

DBRV10

Active Member
Joined
Jun 15, 2008
Messages
926
Location
Brisbane, Qld. Australia
I have updated to 11.1 recently and I am experiencing SOFTWARE MISMATCH and at times the SV KNOB PANEL and or ARINC 429 module offline warnings.

The catch is, this only appears on the D1000 and never on the two x D700 screens. The knob panel works fine, as is the ARINC 429 working with the rest of the system.

The D1000 is never the master, however if I turn off the master D700 (usually the same one) the D1000 becomes the master, and all of a sudden everything is fine.

All the devices have the 11.1 software, all screens have the same databases, maps etc. This did not occur with 10 or 11.0 software. I have force loaded the software from D700 and D1000 screens and nothing changes.

I can't seem to reload the 11.1 in case there is a bug as it refuses to reload over the same version. Has anyone else seen this before?

photo_zps7402657b.jpg

photo2_zpse58765ca.jpg


Also I have seen the CRS setting fluctuate violently from its set point to a number 60-70 degrees apart while not touching the knob. The first time this was on one D700 so I suspected a knob issue, so I reassigned the CRS to another knob on another screen. It does the same thing, randomly. Anyone else seen this? I can only imagine what a VOR or ILS approach would be like with this behaviour  :eek:
 

dynonsupport

Dynon Technical Support
Staff member
Joined
Mar 23, 2005
Messages
13,226
David,
We can think about this more on Monday, but one suggestion- have you re-run a network config from the screen that is acting weird?

When you see the CRS change on you, is this on the GPS or NAV side of the GTN?
 

DBRV10

Active Member
Joined
Jun 15, 2008
Messages
926
Location
Brisbane, Qld. Australia
I will go try that this morning and let you know. I have tried several things and having three screens….the options are almost limitless :)

With the CRS fluctuation, it is on the sky views as well as on the GTN, the CRS setting gets passed back over the ARINC. Another thing I noticed is the data is slow to respond, in other words move 3 clicks of the knob, and the degrees change on the CRS with a delay…maybe 0.5-1.0 seconds. This indicates a comms timing error perhaps?

Could this be related to the bug?

Data file uploaded, I will talk by phone Monday afternoon your time.

I posted this here in the hope that anyone else with an observed bug like this may come forward with extra info. I can't be the only one ;)
 

Carl_Froehlich

Active Member
Joined
Aug 22, 2007
Messages
324
I had the same software mismatch on one of the two displays after loading 11.1. It happened only twice - but not right after loading 11.1. All was fine for several flights before this first popped up. No rhyme or reason. The first time I did a display restart and it went away. The second time I looked to see what was wrong - it listed the autopilot servos as needing an update. I pushed the network configuration and the problem has not returned.
 

DBRV10

Active Member
Joined
Jun 15, 2008
Messages
926
Location
Brisbane, Qld. Australia
Yep! That seems to have fixed it. With three screens I could have needed to do it on all of them so they all played nicely together!

The only bug remaining now is the CRS randomly swinging around. I have sent a video and diagnostic file to Dynon, so if anyone else has seen this they might like to hear from you.

I am not sure which employee answered this thread on a Sunday, but I am mighty impressed. As usual. :)
 

Carl_Froehlich

Active Member
Joined
Aug 22, 2007
Messages
324
The software mismatch problem returned twice today, again on the right display. The mismatch is again on both the roll and pitch servos (software version listed as 0.0 or such - and "needs update"). I did a restart of the right display and the problem went away. On the flight home the problem again came back shortly after startup - and again a right display restart fixed it. After landing I checked the network configuration and both roll and pitch servos listed the correct software version. I did not repeat the network configure push as I did last time.

The left display has not had this issue.

Any ideas?
 

dynonsupport

Dynon Technical Support
Staff member
Joined
Mar 23, 2005
Messages
13,226
Carl:

This is sufficiently complex that we think we should work with you directly via email instead of the Forum. Please email support@dynonavionics.com, mention this post, and we'll continue with you via email.

The software mismatch problem returned twice today, again on the right display.  The mismatch is again on both the roll and pitch servos (software version listed as 0.0 or such - and "needs update").  I did a restart of the right display and the problem went away.  On the flight home the problem again came back shortly after startup - and again a right display restart fixed it.  After landing I checked the network configuration and both roll and pitch servos listed the correct software version.  I did not repeat the network configure push as I did last time.

The left display has not had this issue.

Any ideas?
 

DBRV10

Active Member
Joined
Jun 15, 2008
Messages
926
Location
Brisbane, Qld. Australia
Just to add some further info, if I do a network discovery on either of the D700's which are normally powered up first, and one D700 is always the master, then I get the software mismatch.

If I do a network discovery on the D1000 even though it never becomes the master, it does not show this error.
 

dynonsupport

Dynon Technical Support
Staff member
Joined
Mar 23, 2005
Messages
13,226
David:

As with Carl, this is sufficiently complex that we think we should work with you directly via email instead of the Forum. Please email support@dynonavionics.com, mention this post, and we'll continue with you via email.

Just to add some further info, if I do a network discovery on either of the D700's which are normally powered up first, and one D700 is always the master, then I get the software mismatch.

If I do a network discovery on the D1000 even though it never becomes the master, it does not show this error.
 
Top