Trim widget indicates CFG? on boot

[jbeaver]

Recently, when first booting the system, the trim widget displays a large X and the CFG? label. If I turn off the engine page and then turn if right back on, the trim widget displays properly. I'm running 3.3.2.

Any ideas why this might be happening?

 

[dynonsupport]

What's is it actually connected to? A Ray Allen sensor or a VP-X? When you see that behvior, go into the EMS Setup > Sensor Debug Data. What are the values for those pins? Are you saying that a simple double press of Engine Page fixes it?

 

[jbeaver]

It's connected to a VP-X.  This is what I see when I go into the EMS Setup > Sensor Debug Data:

Here's what I see when I first boot the system.  I didn't realize yesterday that the flaps widget (which should appear just below the trim widget) isn't there at all.

After a simple double press of the Engine page button, this is what I see:

 

[dynonsupport]

Using the VP-X configurator, make sure that none of the endpoints/neutral points/other points that define their cal (which we ignore, except for there's a small bug in that "ignoring") aren't set to 0. Good chance that's it.

 

[jbeaver]

I checked that and there were indeed some endpoints and neutral points set to 0. I changed them to 1 and restarted the VP-X and SkyView systems, but the problem still persists. Interestingly, I also turned on the engine page on the other screen, and it works right from first boot. Here's how the system comes up. Notice that the trim and flaps are visible on the left screen and there is a big X over the trim widget on the right screen and the flaps are just gone.

 

[dynonsupport]

Ah - also, make sure you have the latest sensor config file loaded. If you haven't made any custom mods yourself, just grab the latest version from our website. Load it to BOTH screens (but particularly the one with problems).

 

[jbeaver]

I had previously installed the latest sensor config file (5/2/12) on both displays, but I reinstalled it on both and doubled checked that both displays were completely up to date (software version, databases, etc.).  The problem still happens.  Any other thoughts?

 

[dynonsupport]

A couple other things to double check: both displays are getting serial data individually from the VP-X, and both have a serial port set up in setup as VP-X. Also, try turning on just one display at a time. Does the right one always do it in this case?

 

[jbeaver]

Both displays are configured identically and both are receiving data from the VP-X correctly. Regardless of the order I turn on the displays, the right display always exhibits this issue and the left one works fine.

 

[jbeaver]

Support, any additional thoughts on this?

 

[dynonsupport]

Support, any additional thoughts on this?

Have you verified that the serial port wiring from the VP-X is wired (both TX and RX wires) to BOTH displays?

 

[dynonsupport]

A couple other things:

Are both displays' tail numbers the same? If yes, try doing a network configuration from the good display. If not, that's going to cause issues with settings properly synchronizing, period.
Next, check all the items under the VP-X settings. Are they the same on each display? Does the non-working display have anything different in the pin mapping section of the EMS setup? None of the above should be different, because all settings not in the local display setup should be synced, but, we're searching for something that's either a bug or a nonobvious configuration issue.

 

[jbeaver]

All serial port TX & RX lines are connected to both displays.

The tail numbers are the same. Rerunning the network configuration didn't make a difference.

All of the items under the VP-X settings are identical on each display.

All pin mapping is identical on each display.

The right display (with the problem) has a much earlier serial number than the left display. Any chance that's related?

 

[dynonsupport]

The age of the display should not make any difference. We contacted you by email, to request that you export and send us your settings files. That may help us shed some light on the problem.

-Dynon Support

 

[dynonsupport]

Just to close this out - Jason found a corner case that occurs if you replace a display, and then don't re-enter the VP-X license code on the replacement. We've tweaked both the way we process RMAs, and our license procedures,to prevent this from happening in the future.

 

[jbeaver]

Sorry, I should have followed up. Thanks so much to the Dynon tech support guys; they never gave up and eventually helped me figure this out. You guys rock!