GoFlight programming and the Bendix/King KAP 140
Posted: Wed May 30, 2018 10:29 pm
I've been trying to program my GoFlight MPCPro using GoFlight Interface Tool (GIT) and I've had partial success with the exception of the HDG and NAV operation.
I see the KAP140_ Lvars and the "regular" events that get triggered when pushing the HDG or NAV button, but when I emulate those Lvars and events using GIT I get nothing ... ROL will change "HDG" in the display but the aircraft will not respond to the set heading (HEADING_BUG_SET value from AUTOPILOT_HEADING_LOCK_DIR).
Is there any that just NOT exposed that is needed to make this work? I don't mind if there is hidden logic, as I'll stop trying to make it work if that's the case. I can sorta make it work but I have to set NAV ARM and then going in/out of HDR/ROL works, but I shouldn't really need to set NAV Arm?
I was able to get AP On/Off, BARO (that was a little tricky as I need to get current Alt and then round up to nearest 100ft), ARM, Alt/VS, Alt Selection (100/1000 inc), but HDG and NAV are proving problematic.
So any Lvars/Event usage and/or logic implementation hints would be most grateful.
On a side note I'm using the F1 750/650 also but not sure if that is relevant. I've also got EVERY other button/knob mapped and working with GoFlight modules including WX and even "options" (like pitot cover, chocks, pilot, etc.) and even included mapping of the correct sound event and add sound events where none were before.
Cheers, Rob.
I see the KAP140_ Lvars and the "regular" events that get triggered when pushing the HDG or NAV button, but when I emulate those Lvars and events using GIT I get nothing ... ROL will change "HDG" in the display but the aircraft will not respond to the set heading (HEADING_BUG_SET value from AUTOPILOT_HEADING_LOCK_DIR).
Is there any that just NOT exposed that is needed to make this work? I don't mind if there is hidden logic, as I'll stop trying to make it work if that's the case. I can sorta make it work but I have to set NAV ARM and then going in/out of HDR/ROL works, but I shouldn't really need to set NAV Arm?
I was able to get AP On/Off, BARO (that was a little tricky as I need to get current Alt and then round up to nearest 100ft), ARM, Alt/VS, Alt Selection (100/1000 inc), but HDG and NAV are proving problematic.
So any Lvars/Event usage and/or logic implementation hints would be most grateful.
On a side note I'm using the F1 750/650 also but not sure if that is relevant. I've also got EVERY other button/knob mapped and working with GoFlight modules including WX and even "options" (like pitot cover, chocks, pilot, etc.) and even included mapping of the correct sound event and add sound events where none were before.
Cheers, Rob.