SV-D1000 Data Connection Fault - Data 2 Pair (pins 4 and 8)

[jsalak]

Went to fly today and got a CAUTION message for a secondary network fault. Checking the network status page shows the D1000 display has the fault listed. Troubleshooting steps:
1. swapped D1000 DB-9 cable to other D1000 network port. Error still shows.
2. swapped D1000 DB-9 cable to two other network ports on the SV-HUB. Error still shows.
3. pulled the cable and tested all DB-9 cable sockets end-to-end and cross pins for shorts, 100% good, no sockets are pushed in. Cable has nylon abrasion sleeve, so no jacket shorts to anything. Reinstalled cable, error still shows.

Anyone have any other troubleshooting hints I should try?

 

[Rhino]

Did you check the pins on the D1000 itself?

 

[jsalak]

Did you check the pins on the D1000 itself?

Just visually. It would be nice if there was a loopback test from the primary network to the secondary network on the DB-9 connector to verify the problem is not internal to the D1000.

 

[owenssonex]

Had this issue with my friends' RV-12. The secondary network cable pinouts were backwards. The white with blue stripe, and the white with green stripe wires were in the incorrect pins at the vertical power box. Swap it and problem solved. The secondary network error would randomly appear. The wires were always wrong.

 

[airguy]

Had this issue with my friends' RV-12. The secondary network cable pinouts were backwards. The white with blue stripe, and the white with green stripe wires were in the incorrect pins at the vertical power box. Swap it and problem solved. The secondary network error would randomly appear. The wires were always wrong.

Was that a Dynon-produced cable or owner-built?

 

[owenssonex]

It was a harness from a well known supplier

 

[jsalak]

Quick update after 3 additional flights with a secondary network error cautions. Looking at the alert data log for each flight the secondary network caution showed at 14 minutes after D1000 startup on 2 flights and 12 minutes on the third. That pattern is typically associated with a heat failure of an electronic component. The last flight included an EMS Fail that lasted 1 second (flashed the red X on the EMS display) and recorded 3 instances of KNOB PANEL OFFLINE alerts that lasted for 1 second each. That is the first time I have ever seen a Knob Panel Offline alert in the log.

 

[airguy]

Those two pieces of data point to a loose cable connection, as things warm up some pins stop making contact.

 

[jsalak]

Just wanted to close out this thread with the final resolution for the secondary network error Caution I was getting on my SV-D1000.

Working with Dynon tech support, extensive configuration testing was completed using both a newly fabricated EMS cable and a Dynon supplied test cable. Getting the system configuration down to just the D1000 and only one other SV device at a time, like the EMS, the D1000 always showed the secondary network fault. The configuration changes included testing with a new SV Hub and wiring the EMS directly to the second D1000 SV Network port (SV hub was on the other port). I also upgraded to software ver 16.7.4 as a final troubleshooting step. After several additional flights, including one where both the primary and secondary network failed (no EMS data or ADAHRS data), the D1000 and EMS were returned to Dynon for repair.

One note about the inflight primary and secondary network failure, after flying several minutes with no EMS and no PFD it was apparent the D1000 was not locked up, so I did a Button 1 power down and restart. Upon rebooting the D1000 was operating normally (still had the secondary network error) until I landed about 45 minutes later. I did get a SE21 on a previous flight where the D1000 had auto-rebooted during flight and ran fine for another hour after that before landing.

One month and $1,100 later, the D1000 has been repaired and returned. I asked what was repaired and did not receive a response other than “mechanical/electrical component failure”. The EMS-220 only received a “functional test”, which I presume means it was working with no issues observed or repairs required.