Issue on Skyview system. Need help

[FlyRV8]

Hello Dynon support,

I am actually building a Van’s RV8 and I installed and ran a skyview system in it few months ago and everything worked well.

After two monts of inactivity, I decided today to check that everything was still working good before sendind the plane to the paint shop but it did not work well anymore.

Here is the configuration :
Dual SV-D1000 (S/N 2847 and 2860)
Dual ADAHRS ( 200 and 201) plug on 2860 screen
EMS-220 (S/N 2776) plug on 2847 screen
VP-X sport (S/N 978 on serial port 1)
Dynon 261 transponder (serial port 2)
GPS-250 (serial port 5)

I got the ADAHRS red cross on both screens, the EMS red cross on the S/N2860 screen.
As in the manual I use the detect function on the screens but it doesn’t detect the ADAHRS on both screens and the EMS on the S/N2860 screen.
On the S/N2860 when there is a message that is written on the screen :
« THERE WAS A PROBLEM CONFIGURING YOUR SYSTEM :
NETWORK ERROR :0 –NO ERROR
FOR HELP{…} »
I also see that I can’t enter the setup menu on both screens at the same time ( if I recall correct it was not possible before). As the both screens don’t detect the other one I am thinking of a communicating problem between them.
Moreover the D sub connectors and Ethernet cable are pluged in so instead of a cable failure (which won’t explain why the ADAHRS are not detected by any of the two screens) I don’t see what I can do to make the system working again.

Both screen are occasionnaly at boot up doing green stripes with dynon logo behind but I also see this phenomem on others screens (is it an issue ?)

I read the manual twice to see what could be the reason of the failure but did not find the answer.

I need some help

Thanks

 

[MurphyElite]

It sounds like you didn't change anything so this is a long shot, but check to make sure both screens are running the same firmware version

 

[FlyRV8]

Hi KP,
Both screens are running on the same firmware version.
It is amazing to see that everything worked good, come back a month later and it fails.

It also shows (at least in my system) a failure in the redundancy I believed I had with dual screen and dual ADAHRS as I can't have PFD information on either screen.

I'm sure there is something wrong but I can't find what

 

[dynonsupport]

So first, let's try getting the displays detecting the modules. Try the following:

-Unplug the two SkyView Network cables from both displays (you can leave serial devices connected. They're not involved with or can affect this process)
-Make sure the tail numbers are the same on both displays.
-Do a network configuration on both displays, independently. Exit setup on both.
-Shut down both displays
-Plug the SkyView Network cables into ONLY one of the displays, turn only it on, do a Network Configuration.
-Shut everything down.
-Connect the other display and its modules back up.
-Turn everything on, do a network configuration.
-Fixed?

Then, if that fixes everything, make sure you're running the latest firmware, which is 3.3.2 as of now. If they're not running that, you'll want to update both displays.

 

[FlyRV8]

Thank you for your quick answer but it stills fail.

I unpluged the 4 DB9 connectors ( the EMS, the ADAHRS and the network cable between the two screens) but let the two DB37 connectors plugged to both screens.
I pressed the detect button on both screens (I did it when both screens were running at the same time and also one at time). The 2860 detect itself and the 2847 also detect itself which I believe is normal.
Both screens have the same tail number « F PVRB »

Then I pluged the network cables (ADAHRS and EMS ) to one screen (but letting the D37 plugged to the two screen) I ran only one screen at time (on the backup battery), pressed the detect button but it only detect itself. Try on the other but it only detect itself too.
All the module have a red led flashing which I believe means that they are powered up.
All the system was running on 3.3.2
Looking for an other option.

( The only difference between today on two months ago on the system is that I pull the electronic ignition modules from LightSpeedEngineering off the plane.

 

[dynonsupport]

First, are the LEDs on all 3 of the modules flashing slowly when plugged in? Or are any of them flashing fast are on solid or are not on at all?

I'm wondering if there is something going on in one of your SkyView Network cables. With just one display (either of them), try connecting just one module at a time, then detect, then try the other module by itself, detect, etc, to try to narrow down which harness or module is the source of the issue.

 

[FlyRV8]

I try using the test network cables which comes with every Skyview and it worked. I try using again the cables of the plane and it worked....
Am I missing something??
To have the failure I had, I believe it means that I should have 3 network cables failure at the same time (ADAHRS, EMS and connection between the screens) which is very improbable.
Could it be a software problem?

If I was in flight I would have lost all PFD and EMS informations and it would have been uncomfortable.

I really like the skyview system on all points but I'd like to get some informations about the redundancy of my system (dual screen, dual ADAHRS).
Do you think the failure I had is an architecture problem or a software's?

Thanks for your support

 

[dynonsupport]

This doesn't imply a triple cable failure. It implies one of two things:
-Some sort of non-obvious software-based SkyView Network configuration problem. Usually this happens when network configurations are done in a very atypical way, or when displays or modules are replaced, etc, or when a software update hasn't gone perfectly. Having a system behave this way randomly one day is very uncommon (you may be the first case). When an odd configuration is suspected, what we try to have you do is completely reset the network via the above procedure, or something similar. If that doesn't work, then...

-The other thing it could be is a cable or module failure of some sort that somehow caused SkyView Network to become completely inoperative. This is also extremely rare and almost always is discovered during installation due to a wiring issue. All that said, SkyView redundancy is about to receive improvements that make better use of the network's full capability to both detect and work around data faults via a redundant data bus. See http://dynonavionics.com/cgi-bin/yabb2/YaBB.pl?num=1339250731/1#1 for more details on this.

Back to your issue. Are you saying it's working now?

 

[FlyRV8]

Thank you very much for your answers and for the explanations.
The system is now working as well it was before the "failure" without doing anything more than waiting for a day before coming back to the plane.

I'll keep you in touch if I have the same problem again.

 

[dbuds2]

I just experienced the same thing. Single 10 Skyview, turned it on yesterday evening all fine. Powered up again this morning to check some of the EMS gauge settings (Green/Yellow/Red) and got big ADAHRS and EMS red X's. Did a detect and only thing found was the 10" Display. Previously the ADAHRS, EMS, both servos were 'talking' to the network.

I did a reboot, re-detect and nothing. EMS has a slow blinking light, all buss cables are installed tight.

Scary, I haven't flow yet,learning the systems and this happens.

Help Dynon.

 

[jakej]

A hypothetical ? question--

If you lose a display ie 'lights out' on a single display set up, is there any way to get the settings etc out from the system ?

Jake J

 

[dynonsupport]

For the end customer: no.

For us once it's here: it depends on the failure.

 

[jeffa]

A hypothetical ? question--

If you lose a display ie 'lights out' on a single display set up, is there any way to get the settings etc out from the system ?

Jake J

For the end customer: no.

For us once it's here: it depends on the failure.

That's why anytime I make a settings or EMS change, I export them immediately to my USB.

 

[dbuds2]

:-?Couple days have passed since my posting, re-read the advice given to FlyRV8 above and talked to a doubting Dynon support on Monday.  Remember, to the best of my knowledge, I didn't do anything physical or software wise to get this problem other than turn everything off.

Went to the airport last night expecting to have to disconnect all the network cables and reconfigure. Turned master on and then Skyview on, still no connection to the ADAHRS, EMS and AP listed under status. Re-ran the detect routine and now everything was found and communicating.
1. Why would it loose communication from Saturday to Sunday?
2. Why running detect several times on Sunday didn't find the other network units.

Feeling brave I uploaded V4.0 software and everything is still working fine.

 

[ttreat]

I'm having some random issues similar to dbuds2. Single 10 inch and all factory cables. Since the 4.0 upgrade I have seem random brief issues. Once a couple of gauges red x then pop on a few seconds later. Don't remember which... Once the GPS total failure, then back on during taxi. Once the screen froze during a screen capture.

I have a gut feeling that there's a bug in the software. I am also guessing that it has to do with the network checking code.

It's not stopping me from flying.

 

[dynonsupport]

So that might mean an intermittent connection somewhere. Or a number of other things. 4.0 changes the way modules communicate DRAMATICALLY for the better. SkyView Network will now tell you when a data line is glitching, and it can even tell you which wire(s) are not connected. So if you see the X'ing now, something is seriously wrong (because there's a full backup data bus that everything can fall down to if the primary gets corrupted somehow). More likely, you'll see a STANDBY NETWORK ERROR if there is a persistent problem that needs to be addressed. If you see that, go into the Network Status page and it will then tell you where the problem lies in the network.

 

[dbuds2]

  :-? :-?Well I'm back with another episode of no communication on the SV network.

As you may remember from a posting above, everything is fine with both my EMS and ADAHRS talking to SV one day and not the next and then couple days later communicating again.

Latest problem: As far as I know all systems up and talking. Had to trouble shoot my electric trim wiring so panel off and all SV plugs disconnected. Fixed the trim problem put it all back together and now SV and ADAHRS not communicating.

Did multiple "network status" and "network configure detects" with no change. Red light power light was on ADAHRS. OK, must be the data connection, so removed all connectors again, switched the 2 DB9 connectors, making sure all well inserted. No Change. On the last "configure detect" routine, got this message: "Network Configuration, There was a problem configuring your system. Network Error: 0 No Error".

So this morning i was all set to take apart my ADAHRS DB9 connector and find a problem, but, first I did another "Detect" and, you guessed it all is OK again (with absolutely nothing changed/moved/wiggled/etc. )

DYNON I'm anxiously worried and I know this sounds like the mysterious car noise that the dealer can never find.

 

[dynonsupport]

  :-? :-?Well I'm back with another episode of no communication on the SV network.

As you may remember from a posting above, everything is fine with both my EMS and ADAHRS talking to SV one day and not the next and then couple days later communicating again.

Latest problem: As far as I know all systems up and talking. Had to trouble shoot my electric trim wiring so panel off and all SV plugs disconnected. Fixed the trim problem put it all back together and now SV and ADAHRS not communicating.

Did multiple "network status" and "network configure detects" with no change. Red light power light was on ADAHRS. OK, must be the data connection, so removed all connectors again, switched the 2 DB9 connectors, making sure all well inserted. No Change. On the last "configure detect" routine, got this message: "Network Configuration, There was a problem configuring your system. Network Error: 0 No Error".

So this morning i was all set to take apart my ADAHRS DB9 connector and find a problem, but, first I did another "Detect" and, you guessed it all is OK again (with absolutely nothing changed/moved/wiggled/etc. )

DYNON I'm anxiously worried and I know this sounds like the mysterious car noise that the dealer can never find.

This sounds like an issue that's more appropriate for the 1:1 communication available through Tech Support than the forum. Give them a call - 425-402-0433 or email - support@dynonavionics.com.

 

[dbuds2]

It's been a while since having any issues. Dynon brought my unit back for a check up, all good.

Prepared for a early Sunday morning flight so connected my Odyssey battery charger to my Odyssey battery saturday evening. For a while I began to think charging might have been when big red ADAHRS X occurred, but it hasn't appeared or recent charging sessions, until this weekend. I powered down the SV, turned it back on and the x was gone.

Don't know if Dynon has a theory on this or if anyone else has seen it???