Updating dual SkyView

[bbaggerman]

I have a dual Dynon D1000 EFIS setup in my RV-12. The left one is a SkyView Touch (SV-D1000T) and the right one is a SkyView Classic (SV-D1000). I recdently updated from software 15.3.2 to 16.4.0 that I download from Vans website. Now the left screen has the RV-12 / Dynon logo. Following the detailed procedure from Vans the right screen has only the older Dynon logo. That kind of annoys me and I was wondering if that is normal.

Here is what I think happens.

I just got my left screen back from repair from Dynon (rainbow of death, among other things). As part of the process they update the software before returning it. Everything in my plane had been at 15.3.2. The returned screen was at 16.x. So it was necessary to get everything to the same software rev. Vans has a "blessed" version of Dynon software (version 16.4.0) along with configuration files tested and known to work well with the -12. They also have a nice writeup document explaining the software and configuration loading procedure.

I downloaded everything and followed the procedure for loading software and configurations. The software (SkyView-16.4.0.9609-dynon_update_Classic.dup) and sensor file (sensor_68996.sfg) is loaded on both screens. But the upgrade procedure specifically says only load the big master configuration file (12_Rotax_912ULS_SkyView_Settings_v16.4.0_09-16-22.dfg) in the left display. After loading the master config file as well as a few smaller ancillary config files, the configuration is transferred to the right hand display.

The big master config file has a couple of lines that read...

check_bios_v8=1
bios_splash=RV12

This big master config file never gets loaded directly onto the right hand display and so I am guessing that it never got commanded to check its bios version level or update the splash screen to the RV-12 logo. I noticed on the left hand display the bios was definitely updated as part of the overall update procedure but not on the right hand display.

Anybody else done a software update on a dual Dynon SkyView cockpit? Do you see the updated logo on both displays or only on the left hand display? Vans specifically says don't load configuration files on the right hand display but the Dynon update instructions say to repeat everything you did on the first display on the second display.

 

[Rhino]

This big master config file never gets loaded directly onto the right hand display....

Looks like it does in Step 7. It's the engine settings in Step 10 that don't get loaded on the second display.

 

[Dynon]

If you take JUST the bios line, put it in a .dfg file by itself, load it to the screen that isn't showing the RV12 logo, and then reboot after the load, it should fix it. Note that that first reboot will take extra time. That's normal. Don't interrupt/turn off/etc during that long boot because it's loading the splash screen into the bios.

 

[Rhino]

Vans also noted that it may take several reboots for the logo to appear.

 

[bbaggerman]

Looks like it does in Step 7. It's the engine settings in Step 10 that don't get loaded on the second display.

Step 7 has you load the software and sensor configuration file into the second display. The Step 7 sensor configuration file does not contain the line that updates the BIOS and changes the logo. That is done via the big configuration file loaded into the primary display only in Step 10.

 

[bbaggerman]

If you take JUST the bios line, put it in a .dfg file by itself, load it to the screen that isn't showing the RV12 logo, and then reboot after the load, it should fix it. Note that that first reboot will take extra time. That's normal. Don't interrupt/turn off/etc during that long boot because it's loading the splash screen into the bios.

I suspected that might be the case but it is good to hear it from Dynon directly!

Thanks for the info. I'll give it a try!

 

[Rhino]

Step 7 has you load the software and sensor configuration file into the second display. The Step 7 sensor configuration file does not contain the line that updates the BIOS and changes the logo. That is done via the big configuration file loaded into the primary display only in Step 10.

Okay. To me, the system software (dup) IS the big master configuration file, and I didn't see your .dfg reference.

 

[bbaggerman]

If you take JUST the bios line, put it in a .dfg file by itself, load it to the screen that isn't showing the RV12 logo, and then reboot after the load, it should fix it. Note that that first reboot will take extra time. That's normal. Don't interrupt/turn off/etc during that long boot because it's loading the splash screen into the bios.

I made a .dfg with just...

check_bios_v8=1
bios_splash=RV12

and loaded it. Now I've got updated BIOS and updated RV-12 logos on both screens. The screens have slightly different logos. The Dynon logo portion is different. That is a bit of a mystery because I loaded the same software on both. But at least now I am confident all the software / firmware components have been updated to the most recent rev.

 

[Rhino]

...Now I've got updated BIOS and updated RV-12 logos on both screens. The screens have slightly different logos. The Dynon logo portion is different. That is a bit of a mystery because I loaded the same software on both....

It's fairly common to get different logos when a display gets sent to Dynon for repair. They likely just changed it from the version they previously coordinated with Vans. If I understand it correctly, the logo is in the firmware, not the configuration files. The files just tell it to use the logo or not.

 

[Dynon]

There's a complicated combination of internal changes to hardware we've made over time that can yield different splash screens.