Jump to content
The simFlight Network Forums

AP ALT offset for A320 is not correct


Karl_Yoghurt

Recommended Posts

Hello

I try to control AP altitude in a320 MsFS2020 and I'm a little confused.

offset  0x07D4 work perfect on Boeing but didn't on Airbus

events for AP Altitude value is different

Please tell me the correct offset for AP_ALT_VAR_SET_ENGLISH event

Many thanks.

A320 events log
433531 *** EVENT: Cntrl= 66124 (0x0001024c), Param= 4000 (0x00000fa0) AP_ALT_VAR_SET_ENGLISH
434125 *** EVENT: Cntrl= 66124 (0x0001024c), Param= 3000 (0x00000bb8) AP_ALT_VAR_SET_ENGLISH
434594 *** EVENT: Cntrl= 66124 (0x0001024c), Param= 2000 (0x000007d0) AP_ALT_VAR_SET_ENGLISH
435125 *** EVENT: Cntrl= 66124 (0x0001024c), Param= 1000 (0x000003e8) AP_ALT_VAR_SET_ENGLISH
435703 *** EVENT: Cntrl= 66124 (0x0001024c), Param= 0 (0x00000000) AP_ALT_VAR_SET_ENGLISH
436734 *** EVENT: Cntrl= 66124 (0x0001024c), Param= -1000 (0xfffffc18) AP_ALT_VAR_SET_ENGLISH
437406 *** EVENT: Cntrl= 66124 (0x0001024c), Param= 0 (0x00000000) AP_ALT_VAR_SET_ENGLISH
437484 *** EVENT: Cntrl= 66124 (0x0001024c), Param= 1000 (0x000003e8) AP_ALT_VAR_SET_ENGLISH
437578 *** EVENT: Cntrl= 66124 (0x0001024c), Param= 2000 (0x000007d0) AP_ALT_VAR_SET_ENGLISH
437984 *** EVENT: Cntrl= 66124 (0x0001024c), Param= 3000 (0x00000bb8) AP_ALT_VAR_SET_ENGLISH
438016 *** EVENT: Cntrl= 66124 (0x0001024c), Param= 4000 (0x00000fa0) AP_ALT_VAR_SET_ENGLISH
438078 *** EVENT: Cntrl= 66124 (0x0001024c), Param= 5000 (0x00001388) AP_ALT_VAR_SET_ENGLISH
438156 *** EVENT: Cntrl= 66124 (0x0001024c), Param= 6000 (0x00001770) AP_ALT_VAR_SET_ENGLISH
438344 *** EVENT: Cntrl= 66124 (0x0001024c), Param= 7000 (0x00001b58) AP_ALT_VAR_SET_ENGLISH
439187 *** EVENT: Cntrl= 66124 (0x0001024c), Param= 8000 (0x00001f40) AP_ALT_VAR_SET_ENGLISH
439766 *** EVENT: Cntrl= 66124 (0x0001024c), Param= 9000 (0x00002328) AP_ALT_VAR_SET_ENGLISH
440359 *** EVENT: Cntrl= 66124 (0x0001024c), Param= 10000 (0x00002710) AP_ALT_VAR_SET_ENGLISH

 

Boeing 747 events log
609516 *** EVENT: Cntrl= 65893 (0x00010165), Param= 0 (0x00000000) AP_ALT_VAR_DEC
609797 *** EVENT: Cntrl= 65893 (0x00010165), Param= 0 (0x00000000) AP_ALT_VAR_DEC
610078 *** EVENT: Cntrl= 65893 (0x00010165), Param= 0 (0x00000000) AP_ALT_VAR_DEC
610328 *** EVENT: Cntrl= 65893 (0x00010165), Param= 0 (0x00000000) AP_ALT_VAR_DEC
610734 *** EVENT: Cntrl= 65893 (0x00010165), Param= 0 (0x00000000) AP_ALT_VAR_DEC
610922 *** EVENT: Cntrl= 65893 (0x00010165), Param= 0 (0x00000000) AP_ALT_VAR_DEC
611000 *** EVENT: Cntrl= 65893 (0x00010165), Param= 0 (0x00000000) AP_ALT_VAR_DEC
611109 *** EVENT: Cntrl= 65893 (0x00010165), Param= 0 (0x00000000) AP_ALT_VAR_DEC
611203 *** EVENT: Cntrl= 65893 (0x00010165), Param= 0 (0x00000000) AP_ALT_VAR_DEC
611625 *** EVENT: Cntrl= 65893 (0x00010165), Param= 0 (0x00000000) AP_ALT_VAR_DEC
611766 *** EVENT: Cntrl= 65893 (0x00010165), Param= 0 (0x00000000) AP_ALT_VAR_DEC
612281 *** EVENT: Cntrl= 65893 (0x00010165), Param= 0 (0x00000000) AP_ALT_VAR_DEC
612391 *** EVENT: Cntrl= 65893 (0x00010165), Param= 0 (0x00000000) AP_ALT_VAR_DEC
612453 *** EVENT: Cntrl= 65893 (0x00010165), Param= 0 (0x00000000) AP_ALT_VAR_DEC
612562 *** EVENT: Cntrl= 65893 (0x00010165), Param= 0 (0x00000000) AP_ALT_VAR_DEC
613094 *** EVENT: Cntrl= 65893 (0x00010165), Param= 0 (0x00000000) AP_ALT_VAR_DEC
613812 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC
613859 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC
613906 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC
614016 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC
614359 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC
614391 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC
614422 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC
614484 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC
614875 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC
614922 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC
614953 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC
615031 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC
615297 *** EVENT: Cntrl= 65892 (0x00010164), Param= 0 (0x00000000) AP_ALT_VAR_INC
616000 *** EVENT: Cntrl= 65893 (0x00010165), Param= 0 (0x00000000) AP_ALT_VAR_DEC
616562 *** EVENT: Cntrl= 65893 (0x00010165), Param= 0 (0x00000000) AP_ALT_VAR_DEC

 

 

Link to comment
Share on other sites

18 minutes ago, John Dowson said:

If it works on the Boeing but not on the Airbus, it sounds like an issue with the Airbus model. I'll take a look and see if this needs reporting to Asobo, but I don't think this is an issue with FSUIPC7. I'll report back once I've investigated.

Thanks for the report.

Thanks for answer

0x07D4 it work like on a320:

AP ALT set 5000 0x07D4 = 5000

AP ALT encoder turn to alt 3000 AP disp in game show 3000 in but offset 0x07D4 = 5000

push confirm AP Alt button AP set 3000, 0x07D4 = 3000 😞

 

is it possible to know offset for AP_ALT_VAR_SET_ENGLISH event ?

THANks

Edited by Karl_Yoghurt
Link to comment
Share on other sites

5 minutes ago, Karl_Yoghurt said:

is it possible to know offset for AP_ALT_VAR_SET_ENGLISH event ?

It is 0x07D4. I'm not sure I understand the log snippets you posted. How did you generate them? The A320 log (which you say isn't working) is using the AP_ALT_VAR_SET_ENGLISH event - is this via offset 0x07D4? The Boeing log only shows inc and dec controls,.

Link to comment
Share on other sites

29 minutes ago, Karl_Yoghurt said:

0x07D4 it work like on a320:

AP ALT set 5000 0x07D4 = 5000

AP ALT encoder turn to alt 3000 AP disp in game show 3000 in but offset 0x07D4 = 5000

push confirm AP Alt button AP set 3000, 0x07D4 = 3000 😞

But this is correct, no? The offset only changes when the AP Alt is set....

I'm a bit confused now.... let me check this....

Link to comment
Share on other sites

Btw, how are you sending the alt/dec controls? Is this using FSUIPC, or are you operating it in the UI?

If the latter, can you activate event logging in FSUIPC, and see what events are being sent when you do this. I suspect that FSUIPC may not be seeing the alt/dec events in the Airbus,, but are in the Boeing.

Link to comment
Share on other sites

Sorry, but you log doesn't tell me much as its a 'continuation' log -  I can't even tell what aircraft you were using. Anyway, it doesn't matter, I think I know what the issue is, but need to look into this a bit further. I'll get back to you, but I suspect that the airbus is not updating the AUTOPILOT ALTITUDE LOCK VAR simulator variable correctly.

Link to comment
Share on other sites

On 9/8/2020 at 1:35 PM, John Dowson said:

Sorry, but you log doesn't tell me much as its a 'continuation' log -  I can't even tell what aircraft you were using. Anyway, it doesn't matter, I think I know what the issue is, but need to look into this a bit further. I'll get back to you, but I suspect that the airbus is not updating the AUTOPILOT ALTITUDE LOCK VAR simulator variable correctly.

UPDATE

ap ALT change by 65893 and 65892 events

but i cant confirm alt set by events (also i can find button in game controls)

i try look in log events - nothing

problem only in a320  

Link to comment
Share on other sites

  • 2 months later...

@Karl_Yoghurt The latest release of FSUIPC7, v7.0.2, contains AUTOPILOT ALTITUDE LOCK VAR:3 at offset  0x0818 - this may contain the value you are after (the altitude displayed on the FCU in the A320). See https://forums.flightsimulator.com/t/a320-fcu-variable-autopilot-altitude-lock-var-vs-displayed-altitude/307093/3

John 

Link to comment
Share on other sites

For AP issues with the A320, please note the following post from Asobo:

Quote

We are aware of the AP issues with the A320 and the team is working hard on a fix to resolve this with the next update.

In the meantime from FlyByWire:

Screenshot 2020-11-30 140135

The Direct Link: https://github.com/flybywiresim/a32nx/releases/download/vmaster/A32NX-master.zip

Thank you for your patience.

Best regards,

Royal

John

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.