Problem loading 6.0

[RV9APlane]

Hi, I tried to load 6.0 today.  I am upgrading from 3.3.2 and used Method 2 as directed.  Everything seemed to be going fine until the "Starting Network Manager..." as seen in the attached picture. Just prior to the "Network Update Status" dialog box with "Loader Disconnecting" as shown it said "Enumerating Network" and was stuck on 0% until the box came up as shown.  I let it sit this way for 15 minutes and then tried to recycle power but when I shut off the power it wouldn't power down until I disconnected the backup battery.  I turned the power on again and the same result even though let it try for about an hour until I turned the power off again.  What do I need to do?  I have dual SV1000 displays but did not attempt on the other one. I should mention that I am not flying yet and this week is the first power up and configuration of my Dynon system. Prior to trying to update to 6.0 I configured per the install manual which went fine. I did not try to configure the ADS-B 470 or my SV 261 Transponder. My system recognized the EMS and the network fine.

 

[RV9APlane]

Update Re: Problem loading 6.0

Hi,
Today I went out and powered up the system and the PFD came up.  Initially it showed the PFD screen but then changed to this view:

[/URL][/img]

I was able to enter the setup menu and looked at the network status and saw this:

[/URL][/img]

Here is what the MFD shows:

[/URL][/img]

Here's the good news I think, I was able to export a diagnostic file to the thumbdrive if you can tell me how to get it to you.  Here's what the screen looks like as I was exporting:

[/URL][/img]

 

[Dynon]

It looks like one of your displays has new firmware and the other old. Though it shouldn't make a difference, there's a possibility that for some reason this configuration is making your system behave the way it is. You might try upgrading the other display and see if that unsticks things.

 

[RV9APlane]

Would not the diagnostic file offer any insight to this problem if I sent it to you? I'm concerned obviously that trying to upgrade the other display will only leave me with two problems.

 

[Dynon]

The diagnostic file tells us a lot about history of events, readings, sensors, and other things that are logged continuously, but with upgrade issues it's not as useful.

 

[RV9APlane]

Well, as I feared, I now have both displays doing exactly the same thing...the second display shows the same thing as my picture in post #1.

What do you suggest now?

 

[RV9APlane]

Mike called me this morning to discuss and gave me some instructions to work on over the next few days to try to isolate the problem. I will call him back later in the week to discuss my findings. Thanks.

 

[Dynon]

One thing to try, if you haven't already, is to disconnect both of the SkyView Network cables from the display. These are the 9 pin connectors on the back of the display. Does that make a difference?

 

[RV9APlane]

We tried that this morning as I was talking with Mike. Prior to doing that one display has been booting up but the other was stuck at the screen posted below. After disconnecting the network and also the ethernet connection, both display booted up but only show the map and the red X over the EMS. After connecting back up the ethernet cable, neither display could recognize the other. So the plan is for me to connect one network module at a time to see what happens so that we might isolate it to a single module on the network. Mike said that he had seen something like my problem before but ultimately the displays had to be shipped in for repair. I am not able to work on this until tomorrow night so will post my findings later that evening.

 

[Dynon]

So if you still have it, that diagnostics file might be useful after all. I'll PM you details on how to get it to us.

 

[RV9APlane]

Re: Problem loading 6.0---Solved!

I have solved the problem I had by using the instructions Mike gave me to take everything off the network and add them back one at a time to try and isolate the problem.  I began to do that tonight and as I added them back everything began to work. I started with the EMS, the two ADAHRS one at a time, and although not technically part of the network, the transponder, ADS-B, and backup batteries.  I saved the pitch servo for last and there it was...everything went haywire on the network.  I first looked at the network hub connectors and everything checked out fine there, but when I opened up the connectors at the servo I discover a mismatch of the pins...the wht/grn and wht/blu were reversed as were the solid blue and green. Once I put everyting in the proper place everything worked.  So in the end it was my own boneheaded mistake even though I thought I had double and triple checked everything.  Thanks to Mike and the other good Dynon folks for their patience with me as I tried to figure this out.