FBW A32NX AP heading update via offset 07CC

[quintinm]

Hello,

 

it's seems working ! thank you !

do you know what simvar is for the autopilot vertical speed ? because I didn't see which could be

thanks

Michel 

[John Dowson]

9 hours ago, quintinm said:

do you know what simvar is for the autopilot vertical speed ?

Similar to the heading, 0x07F2 holds the AUTOPILOT VERTICAL HOLD VAR and 0x07EC the AUTOPILOT VERTICAL HOLD, so try them. There is also the custom events for the VS:

    A32NX.FCU_VS_INC
    A32NX.FCU_VS_DEC
    A32NX.FCU_VS_SET
    A32NX.FCU_VS_PUSH
    A32NX.FCU_VS_PULL

so if writing to offset 0x07F2, you will have to do the same as you did for the heading - add the simvar to a spare FSUIPC offset and use a lua script to call A32NX.FCU_VS_SET when changed.

John

 

 

 

 

[quintinm]

Here included my .log

When I scroll the VS nothing updated

 

I have added this to .ini :

3=Lua FBW-Vs

I have added this to myoffsets.txt :

0x2744, 2, AUTOPILOT VERTICAL HOLD VAR, F64, Feet per minute

I have created this file FBW-Vs.lua

function FBWVsUpdate(offset, value)

    ipc.log("Vertical speed updated: " .. value)

    ipc.execCalcCode(value .. " (>K:A32NX.FCU_VS_SET)")

end

 

event.offset(0x2744, "UW","FBWVsUpdate")

 

 

FSUIPC7.log

[John Dowson]

It looks like the VS uses the lvar L:A32NX_AUTOPILOT_VS_SELECTED. Try listing the lvars to see if that holds the correct value, and if so add that to a free FSUIPC7 offset. See the section Adding Lvars to Offsets in the Advanced User guide (P46) on how to do this. I don't know if writing to that lvar is working to update the VS, but you can also try that by writing to the offset that holds the lvar, and FSUIPC will try to update the lvar value.

Note that the MF presets for the VS in/dec use the following calculator code:

 inc: (L:A32NX_TRK_FPA_MODE_ACTIVE, bool) 1 == if{ (>H:A320_Neo_FCU_AP_INC_FPA) } els{ 3 (>K:AP_VS_VAR_INC)  (>H:A320_Neo_FCU_VS_INC) }
 dec: (L:A32NX_TRK_FPA_MODE_ACTIVE, bool) 1 == if{ (>H:A320_Neo_FCU_AP_DEC_FPA) } els{ 3 (>K:AP_VS_VAR_DEC) (>H:A320_Neo_FCU_VS_DEC) }

So it looks like updating this depends on the track FPA mode - whatever that is...

Later: there is also the lvar L:A320_Neo_FCU_VS_SET_DATA that may also be worth adding and checking....    
    - checked this and this doesn't hp;f the set value, but the lvar L:A32NX_AUTOPILOT_VS_SELECTED does, but haven't checked if it can be updated...

Edited July 11, 2023 by John Dowson
Later added

[John Dowson]

48 minutes ago, John Dowson said:

It looks like the VS uses the lvar L:A32NX_AUTOPILOT_VS_SELECTED. Try listing the lvars to see if that holds the correct value, and if so add that to a free FSUIPC7 offset. See the section Adding Lvars to Offsets in the Advanced User guide (P46) on how to do this. I don't know if writing to that lvar is working to update the VS, but you can also try that by writing to the offset that holds the lvar, and FSUIPC will try to update the lvar value.

The lvar holds the correct value but writing to this does not update it. The MF in/dec presets work, but I don't know what can be used to set a specific value.