VP-X Flaps with a red X

[carlmeek]

I can't get my flap widget to work with the VP-X. It's actually working perfectly - showing the degree, and the position, but it's got a red X through it.

Flaps are calibrated inside the VP-X Configurator, and on the Dynon - when i go to hardware calibration, it shows the values and states it's already calibrated.

I just need the red X to go! Any ideas?

 

[dynonsupport]

Check that you don't have the non-VPX flaps widget also displayed. You might have both on, and are seeing the other one right on top or under it.

A screen shot would help greatly as well, as the way it's drawn can give us a lot of hints.

 

[carlmeek]

I only have a single flap widget showing.  If i select it and move it, the widget moves complete with the red X.

Excuse the messy screen, i've not even started to lay it out properly yet!

Screenshots attached.

 

[Dynon]

Still stumped here. I'm noticing this note in our installation guide, although I admit I'm not sure whether what you're seeing is the expected symptom:

"Though the VP-X’s trim and flaps calibrations are not used by SkyView, leaving any of the VP-X trim or flaps end points or neutral positions to “0” in the VP-X Configuration program will cause SkyView’s trim or flaps indications to not display properly. To avoid this, set all of the trim and flaps end points and neutral points to “1” in the VP-X Configurator."

 

[Dynon]

Also check that SETUP MENU > VP-X SETUP > FLAP POSITION is set to VP-X.

 

[carlmeek]

Yes, that's set to VP-X.
I can also confirm that my flap start point is set to '1' in the VP-X Configurator, not zero. However it originally WAS zero, but i changed it - this did not affect the red X.

It IS working correctly, it just has a red cross as well.

 

[carlmeek]

OK - I've Fixed it! It's very odd....

I went into the configuration to assign sensors to pins, and i assigned a spare one to Flap Position. Red cross disappeared!

I then went back in, and removed this - leaving nothing assigned to flap position... and Red cross still gone!

So it's fixed - but i have no idea why this did it.