Help with settings for AP Engage Vertical Speed and ALTITUDE (AP Managed and Selected) in A320 FBW

[MarcoM1973]

Sorry.... first of all... Sorry....

I'm being crazy to find a solution to configure my hotas switches for engage vertical speed (once selected) and for engage the altitude i want set the aircraft with AP (a cruize altitude for example)....but i can't... i got use mouse every time... it's frustating.... 

I bought FSUIPC 7.... i'm trying to set switches throught it but i think not correctly.... i'm not a programmer so i'm in difficult to operate changes in file .ini or in file .log (.log... I can't even find it...:-(((((((.....quite desperate...i'm sorry...)

I use Logitech Hotas x56 Throttle and Stick, Msfs 2020 (all updated) i tried to follow some youtube's tutorials but none specifically talk about it...

Please someone help me.... please.....

Marco

[John Dowson]

53 minutes ago, MarcoM1973 said:

I'm being crazy to find a solution to configure my hotas switches for engage vertical speed (once selected) and for engage the altitude i want set the aircraft with AP (a cruize altitude for example)....but i can't... i got use mouse every time... it's frustating.... 

I bought FSUIPC 7.... i'm trying to set switches throught it but i think not correctly.... i'm not a programmer so i'm in difficult to operate changes in file .ini or in file .log (.log... I can't even find it...:-(((((((.....quite desperate...i'm sorry...)

First, your log file is in the same location of your FSUIPC7.ini file. in the FSUIPC7 installation folder. This is the location you selected or accepted during the installation process. If you don't know where this is, you can use the File -> Open Installation Folder... menu option. If you can't see the FSUIPC7.log file there, you probably have windows explorer et to hide known file types. If this is the case, see the Addendum in the Installation and Registration guide (Identifying Files in Windows Explorer).

And you should not need to edit the FSUIPC7.ini file except for some more advanced uses. You can assign most things via the UI.

Which aircraft are you using? Try activating logging for Events (Log -> Events), then open the console (Log -> Open Console). Then operate the functions you want to assign in the UI, and you will see what event the loaded aircraft is using (it can be different for different aircraft). Then, knowing what events are logged, you can then assign to those to controls via your devices.

For further help, please let me know what aircraft you are using and what you want to control/assign. Also, please see the provided documentation, and for further help please attach your FSUIPC7.log and .ini files and let me know what you have tried and what your issues are.

 

[MarcoM1973]

THANK YOU SO MUCH!!!!!!!!!!!

I USE A320XN FlyByWire! I want to control activation of Alitude Knob (i like have a switch to engage it) and activation of Vertical Speed Knob (i like have a switch to engage it)

So... I start my MSFS 2020 throught FSUIPC, and start a custom flight...

First of all when I open LOG Window on FSUIPC and than I OPEN CONSOLE,  appears this situation in the Log File:

___________________________________________________________________________________________________________________________________________________________________________________

Console Started ...

********* FSUIPC7, Version 7.1.0 (9th May 2021) by John Dowson *********
Checking for FS path in 'C:\Users\marco\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt'
FS path found = C:\Users\marco\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\
WebSocket server found: C:\FSUIPC7\\Utils\FSUIPCWebSocketServer.exe
Windows 10 Pro 64 Bit reported as Build 19042, Release ID: 2009 (OS 10.0)
Reading options from "C:\FSUIPC7\FSUIPC7.ini"
Checking the Registrations now ...
User Name="Marco Mazzari"
User Addr="marco_mazzari@libero.it"
FSUIPC7 Key is provided
WIDEFS7 not user registered, or expired
       94 System time = 25/05/2021 15:56:40
      109 FLT path = "C:\Users\marco\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\"
      141 -------------------------------------------------------------------
      172 Registered HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1)
      203 FS path = "C:\Users\marco\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\"
      203 ---------------------- Joystick Device Scan -----------------------
      203 Product= Saitek Pro Flight X-56 Rhino Throttle
      203    Manufacturer= Mad Catz
      203    Serial Number= ko092871
      203    Vendor=0738, Product=A221 (Version 1.0)
      219    GUIDs returned for product: VID_0738&PID_A221:
      219       GUID= {61E63730-B648-11EB-8001-444553540000}
      219       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0
      219 Product= Saitek Pro Flight X-56 Rhino Stick
      219    Manufacturer= Mad Catz
      219    Serial Number= k0345497
      219    Vendor=0738, Product=2221 (Version 1.0)
      219    GUIDs returned for product: VID_0738&PID_2221:
      219       GUID= {4FDA2F30-B650-11EB-8001-444553540000}
      219       Details: Btns=17, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R4095,U255,V255,X65535,Y65535,Z0
      219 -------------------------------------------------------------------
      219    WARNING: Joystick ID 1 is duplicated in Registry
      234 Device acquired for use:
      234    Joystick ID = 1 (Registry okay)
      234    1=Saitek Pro Flight X-56 Rhino Throttle
      234    1.GUID={61E65E40-B648-11EB-8002-444553540000}
      234 Device acquired for use:
      234    Joystick ID = 0 (Registry okay)
      234    0=Saitek Pro Flight X-56 Rhino Stick
      234    0.GUID={4FDA2F30-B650-11EB-8001-444553540000}
      234 -------------------------------------------------------------------
      266 LogOptions=00000000 00000001
     3172 Simulator detected
    21234 SimConnect_Open succeeded
    21234 Running in "KittyHawk", Version: 11.0.282174.999 (SimConnect: 11.0.62651.3)
    21234 MSFS version = 11.0.282174.999
    21234 Initialising SimConnect data requests now
    28797 C:\Users\marco\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community\flybywire-aircraft-a320-neo\SimObjects\Airplanes\FlyByWire_A320_NEO\aircraft.CFG
    29516 Aircraft loaded: running normally now ...
    30234 User Aircraft ID not supplied -- trying default
    32266 System time = 25/05/2021 15:57:12, Simulator time = 12:57:09 (13:57Z)
    32281 Aircraft="Airbus A320 Neo Alitalia 8K (A32NX Converted)"
    44297 -------------------- Starting everything now ----------------------
   105031 Sim stopped: average frame rate for last 75 secs = 61.1 fps
   105031    Max AI traffic was 0 aircraft
   105031 -------------------------------------------------------------------
   110500 C:\Users\marco\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\MISSIONS\Custom\CustomFlight\CustomFlight.FLT

___________________________________________________________________________________________________________________________________________________________________________________

Then when I click on EVENTS in Log Window, this happens (without I touch anything...):

___________________________________________________________________________________________________________________________________________________________________________________

  255516 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   255656 *** EVENT: Cntrl= 67042 (0x000105e2), Param= 0 (0x00000000) LIGHT_POTENTIOMETER_24_SET
   256078 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   256656 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   256688 *** EVENT: Cntrl= 67042 (0x000105e2), Param= 0 (0x00000000) LIGHT_POTENTIOMETER_24_SET
   257234 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   257688 *** EVENT: Cntrl= 67042 (0x000105e2), Param= 0 (0x00000000) LIGHT_POTENTIOMETER_24_SET
   257734 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   258266 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   258719 *** EVENT: Cntrl= 67042 (0x000105e2), Param= 0 (0x00000000) LIGHT_POTENTIOMETER_24_SET
   258797 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   259313 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   259719 *** EVENT: Cntrl= 67042 (0x000105e2), Param= 0 (0x00000000) LIGHT_POTENTIOMETER_24_SET
   259844 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   260422 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   260750 *** EVENT: Cntrl= 67042 (0x000105e2), Param= 0 (0x00000000) LIGHT_POTENTIOMETER_24_SET
   260953 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   261453 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   261766 *** EVENT: Cntrl= 67042 (0x000105e2), Param= 0 (0x00000000) LIGHT_POTENTIOMETER_24_SET
   261969 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   262484 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   262797 *** EVENT: Cntrl= 67042 (0x000105e2), Param= 0 (0x00000000) LIGHT_POTENTIOMETER_24_SET
   262984 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   263500 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   263828 *** EVENT: Cntrl= 67042 (0x000105e2), Param= 0 (0x00000000) LIGHT_POTENTIOMETER_24_SET
   264000 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   264531 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   264859 *** EVENT: Cntrl= 67042 (0x000105e2), Param= 0 (0x00000000) LIGHT_POTENTIOMETER_24_SET
   265063 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   265609 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   265859 *** EVENT: Cntrl= 67042 (0x000105e2), Param= 0 (0x00000000) LIGHT_POTENTIOMETER_24_SET
   266141 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   266656 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   266875 *** EVENT: Cntrl= 67042 (0x000105e2), Param= 0 (0x00000000) LIGHT_POTENTIOMETER_24_SET
   267156 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   267734 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   267891 *** EVENT: Cntrl= 67042 (0x000105e2), Param= 0 (0x00000000) LIGHT_POTENTIOMETER_24_SET
   268250 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   268813 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   268938 *** EVENT: Cntrl= 67042 (0x000105e2), Param= 0 (0x00000000) LIGHT_POTENTIOMETER_24_SET
   269359 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   269922 *** EVENT: Cntrl= 67042 (0x000105e2), Param= 0 (0x00000000) LIGHT_POTENTIOMETER_24_SET
   269938 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   270453 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   270938 *** EVENT: Cntrl= 67042 (0x000105e2), Param= 0 (0x00000000) LIGHT_POTENTIOMETER_24_SET
   270953 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   271469 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   271984 *** EVENT: Cntrl= 67042 (0x000105e2), Param= 0 (0x00000000) LIGHT_POTENTIOMETER_24_SET
   271984 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   272516 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   272984 *** EVENT: Cntrl= 67042 (0x000105e2), Param= 0 (0x00000000) LIGHT_POTENTIOMETER_24_SET
   273016 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   273578 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   273969 *** EVENT: Cntrl= 67042 (0x000105e2), Param= 0 (0x00000000) LIGHT_POTENTIOMETER_24_SET
   274094 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   274609 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   274984 *** EVENT: Cntrl= 67042 (0x000105e2), Param= 0 (0x00000000) LIGHT_POTENTIOMETER_24_SET
   275141 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   275641 *** EVENT: Cntrl= 65891 (0x00010163), Param= 1 (0x00000001) AP_PANEL_SPEED_HOLD
   276016 *** EVENT: Cntrl= 67042 (0x000105e2), Param= 0 (0x00000000) LIGHT_POTENTIOMETER_24_SET

___________________________________________________________________________________________________________________________________________________________________________________

Those two commands continues scrolling only when i select "EVENTS on LOG window od FSUIPC7. When I deselect "EVENTS" it stops to scroll....

... is that right? If not...how can I stop these events? Could they create some kind of contrasts for my failed assignements?

Then, this is my file.ini after I closed the custom flight.....

___________________________________________________________________________________________________________________________________________________________________________________

[General]
InvokeFSUIPCOptionsKey=70,12
AxesWrongRange=No
TCASid=Flight
TCASrange=40,3
AxisCalibration=No
DirectAxesToCalibs=No
AxisIntercepts=No
DontResetAxes=No
ThreadAffinityMask=x0
LuaAffinityMask=x0
LogOptionProtect=Yes
AutoConnectToSim=Yes
AutoExitWithSim=Yes
TimeForLuaClosing=2
TrafficStallTime=2
InitialStallTime=120
NormalStallTime=2
LuaRerunDelay=66
ComReadLoopTime=20
ControlsListBuild=999
Window=1061,294,1561,394
Console=Yes
ConsoleWindowTopMost=No
ConsoleWindow=67,110,979,627
UseSystemTime=No
JoystickTimeout=20
DisconnTrimForAP=No
ZeroElevForAPAlt=No
ThrottleSyncAll=No
EnableExtraButtons=Yes
ShowPMcontrols=No
SpoilerIncrement=512
MagicBattery=No
RudderSpikeRemoval=No
ElevatorSpikeRemoval=No
AileronSpikeRemoval=No
ReversedElevatorTrim=No
ClockSync=No
ClockSyncMins=5
ClearWeatherDynamics=No
PauseAfterCrash=No
BrakeReleaseThreshold=75
SaveDataWithFlights=No
UseProfiles=Yes
WideLuaGlobals=Yes
FSVersionUsed="KittyHawk",11.0.282174.999
SimConnectUsed=11.0.62651.3

[WideServer]
WideFSenabled=Yes

[Sounds]
Device1=Driver audio principale
Device2=Altoparlanti (High Definition Audio Device)
Device3=BenQ PD2700U (NVIDIA High Definition Audio)
Device4=Digital Audio (S/PDIF) (High Definition Audio Device)

[JoyNames]
0=Saitek Pro Flight X-56 Rhino Stick
0.GUID={4FDA2F30-B650-11EB-8001-444553540000}
1=Saitek Pro Flight X-56 Rhino Throttle
1.GUID={61E65E40-B648-11EB-8002-444553540000}
A=Saitek Pro Flight X-56 Rhino Stick
A.GUID={4FDA2F30-B650-11EB-8001-444553540000}
B=Saitek Pro Flight X-56 Rhino Throttle
B.GUID={61E65E40-B648-11EB-8002-444553540000}

[JoystickCalibration]
RudderBlendLowest=1

[Axes]
PollInterval=10
RangeRepeatRate=10

[Buttons]
PollInterval=25
ButtonRepeat=20,10

[AutoSave]
Next=1
Interval=60
Files=10
SaveOnGround=No
AutoSaveEnabled=No

[GPSout]
GPSoutEnabled=No

[GPSout2]
GPSoutEnabled=No

[Profile.A320NX]
1=Airbus A320 Neo Alitalia 8K (A32NX Converted)

[Axes.A320NX]
RangeRepeatRate=10
[Buttons.A320NX]
0=PB,17,C68067,2     -{ALTITUDE_SLOT_INDEX_SET}-
___________________________________________________________________________________________________________________________________________________________________________________

...as you can see in the final, I tried to configure switch number 17 to activate altitude selected through the ALT KNOB but nothing.... 

Surely I do something wrong.... can anything be done? I'm just feel a little bit unable....

Thank you....

[John Dowson]

1 hour ago, MarcoM1973 said:

... is that right? If not...how can I stop these events?

Yes, that is correct. Many aircraft continually emit certain events, with the events being different depending on the aircraft. You can such events using the DontLogThese ini parameter. Best to use in a profile. See the Advanced User Guide for details.

1 hour ago, MarcoM1973 said:

Could they create some kind of contrasts for my failed assignements?

No.

1 hour ago, MarcoM1973 said:

...as you can see in the final, I tried to configure switch number 17 to activate altitude selected through the ALT KNOB but nothing.... 

But you have only assigned to the ALTITUDE_SLOT_INDEX_SET control. That should just switch to 'Managed' mode (as parameter=2). Doesn't it do that?

Have you tried changing the altitude using the AUTOPILOT ALTITUDE LOCK VAR (offset 0x07D4)?
And what does AUTOPILOT ALTITUDE LOCK VAR:3 hold (offset 0x0818)?

Maybe try logging those offsets (using Log->Offsets... facility)  and also try setting the lock VAR (LOCK VAR:3 is read-only).

You can maybe also try using hvars to pull/push the VS knob - best to initially try using the WASM->Execute Calculator Code functionality.  You can try with the following:
    to pull: (>H:A320_Neo_FCU_VS_PULL)
    to push: (>A320_Neo_FCU_VS_PUSH)

They are the hvars in the current A320.hvar file. However, not sure if thats up to date - if they don't work, you can try the following:
    (>H:A320_Neo_FCU_VS_HOLD)
    (>H:A320_Neo_FCU_VS_PUSH)

 

[MarcoM1973]

Nothing.......... Nothing...... Nothing......😪 

I can't customize my Hotas....  I just try all, I'm sure I wrong something........ It seems impossible to me...... 

It doesn't matter....... I surrender..... I'll contunue to use mouse for that AP controls......

Thany you so much anyway........ 

Marco

[John Dowson]

12 hours ago, MarcoM1973 said:

Nothing.......... Nothing...... Nothing......😪 

I can't customize my Hotas....  I just try all, I'm sure I wrong something........ It seems impossible to me...... 

What do you mean by "nothing"? Do the lvars/hvar work when using them directly, but not via assignments? Or do they just not work?
What have you tried? 

[MarcoM1973]

John.... I begin to think Im not able to do it ...

...I don't know how to change Ivars/hvar... assigne them to joystick (and then answer to your question).... and how to verify if they work or not....

Help me just a little bit.... i'm quite complitely ignorant about these procedures....

...sometimes I think I'm so near the solution but then I let myself be taken by despair...😔... SORRY.....

[MarcoM1973]

....oh and I forgot to tell you that I can't try also with the Offset procedure..... I'm not able even with that...

[John Dowson]

But what have you actually tried? What do you mean by 'Offset procedure'? Do you mean the new facility to add lvars to offsets? If so, that is only available in the latest 7.2.0a beta release - have you tried that?

It is difficult for me to help you  when you are not explaining what you have tried. Just saying 'nothing...' and 'I can't customize' doesn't help me. I need to know what you have tried, and what you see, and also see your logs and ini files (attached preferably, not selected contents pasted). And as I said, if using lvars/hvars, test them first using the facilities provided. Did you do that?

 

[MarcoM1973]

John... you are perfectly right... 

So...

....we can say that, since now, I just tried only to set the standard ALTITUDE_SLOT_INDEX_SET control, through FSUIPC>Assignments>Buttons & Switches, and I just tried with both parameters (1 to pull, 2 to push), but joystick switches don't give signs of life during flight. I just tried with other preset controls AP_PANEL_ALT... - AP_ALT_HOLD - ..._LEVEL and others with ALT term... but same result....

___________________________________________________________________________________________________________________________________________________________________________________

Then You said: 

""Have you tried changing the altitude using the AUTOPILOT ALTITUDE LOCK VAR (offset 0x07D4)?
And what does AUTOPILOT ALTITUDE LOCK VAR:3 hold (offset 0x0818)?

Maybe try logging those offsets (using Log->Offsets... facility)  and also try setting the lock VAR (LOCK VAR:3 is read-only)"". 

___________________________________________________________________________________________________________________________________________________________________________________

So.... I opened FSUIPC>Log>Offsets... but I blocked there 😭 cause i don't know what to write in the Offset Logging window... and then what to do next... 

___________________________________________________________________________________________________________________________________________________________________________________

Than you said:

""You can maybe also try using hvars to pull/push the VS knob - best to initially try using the WASM->Execute Calculator Code functionality.  You can try with the following:
    to pull: (>H:A320_Neo_FCU_VS_PULL)
    to push: (>A320_Neo_FCU_VS_PUSH)

They are the hvars in the current A320.hvar file. However, not sure if thats up to date - if they don't work, you can try the following:
    (>H:A320_Neo_FCU_VS_HOLD)
    (>H:A320_Neo_FCU_VS_PUSH)""

___________________________________________________________________________________________________________________________________________________________________________________

So.... I just found A320.hvar file in the modules folder (in Community/fsuipc-Ivar-modules)... I opened file with Block Notes and found these already: 
H:A320_Neo_FCU_VS_PULL
H:A320_Neo_FCU_VS_PUSH

I don't understand what I got to do....😭 replace strings? And then? 

I know it's probably an impossible request but can you explane me step by step how to apply these your solutions, Offsets and .hvar (as possibly as you can... according to your patience).....

THANK YOU ANYWAY!!!!!!! 

 

[John Dowson]

I'll take a look at the A320 FBW to see what works for these and let you know...may take me a day or so to get around to this though as I've a few issues to sort out first.

[MarcoM1973]

OBVIOUSLY NO PROBLEM......🙏 I'LL WAIT YOU ANXIOUSLY!!!😁

In the meantime I attached my last file .ini, file .log and file .hvar.

THANK YOU SO MUCH

FSUIPC7_prev.log FSUIPC7.ini A320.hvar

[John Dowson]

First, sorry for the delay.

For the VS speed knob, you can try the following:
  For increment/decrement (rotating the knob), try assigning to
     AP_VS_VAR_INC
     AP_VS_VAR_DEC
  both with a parameter of 3.
 For the Pull, assign to
    AP_PANEL_VS_ON with a parameter of 1 on press, and AP_PANEL_SPEED_HOLD with a parameter of 1 on release
For the Push, assign to
    VS_SLOT_INDEX_SET with a parameter of 1 on press, and AP_PANEL_SPEED_HOLD with a parameter of 1 on release
They seem to have the same affect as push/pulling the knob, but I'm not 100% sure on this, and there is no animation of the knob when sending these.

The Altitude knob seems more complicated. The inner knob, which changes the inc/dec values between 100 and 1000 can be assigned by using the lvar XMLVAR_Autopilot_Altitude_Increment with a value of 100 and 1000 respectively.

The inc/dec controls use the AP_ALT_VAR_SET_ENGLISH control, but this doesn't seem to have any affect when I assign to this. This actually changes the AUTOPILOT ALTITUDE LOCK VAR:3 which is held in offset 0818, so you could try adjusting this directly. I haven't tried this. However, changing this does not seem to have any affect either.

Pulling the altitude knob sends a ALTITUDE_SLOT_INDEX_SET control with parameter 1, and pushing the same control with a parameter of 2.
You could try assigning to those.

Note that there are the following additional events provided by FBW for their A320:
  VSpeed:
    A32NX.FCU_VS_PUSH  - (>K:A32NX.FCU_VS_PUSH)
    A32NX.FCU_VS_PULL  - (>K:A32NX.FCU_VS_PULL)
    A32NX.FCU_VS_INC   - (>K:A32NX.FCU_VS_INC)
    A32NX.FCU_VS_DEC   - (>K:A32NX.FCU_VS_DEC)
    A32NX.FCU_VS_SET   - ?
  Altitude:
    A32NX.FCU_ALT_PUSH - (>K:A32NX.FCU_ALT_PUSH)
    A32NX.FCU_ALT_PULL - (>K:A32NX.FCU_ALT_PULL)
    A32NX.FCU_ALT_INC  - (>K:A32NX.FCU_ALT_INC)
    A32NX.FCU_ALT_DEC  - (>K:A32NX.FCU_ALT_DEC)
    A32NX.FCU_ALT_SET  - ?
I've also tried these but without much luck. I've attached the FBW FSUIPC event file for the additional events, in case you haven't got it - just drop it into your FSUIPC7 installation folder and it will be picked-up the next time you run FSUIPC7, and the additional events will be available for assignment. But, as I say, I haven't had much luck with those - you may want to ask about them on the FBW support or discord channel.

There are also various additional MobiFlight events for the control of the FCU VS and ALT. Generally the MF events just set lvars or activate lvars, bur they can also contain more complicated code, which you can also use in FSUIPC via the ipc.execCalcCode lua function. However, it may be easier to try the MF events directly, but to use these you will need the MF WASM module installed, and make the events you want to use known to FSUIPC7 via adding an event file (like the FBW one, but for MF events).

Sorry  I can't be of more help. I'm not that familiar with the A320 (any version), so you may be better off asking directly on the FBW forums/discord channel for further information, especially why the events they provide don't seem to be working. Here's the event file: flybywire-aircraft-a320-neo.evt
(thats from https://github.com/flybywiresim/a32nx/tree/master/docs, where you may find more info).

Please report back if you find out anything more. I will also take another look at the altitude inc/dec via offsets when I get time, but not being familiar with the A320 I'm not sure about the managed/selected modes and the slot index variables, etc. I think that there is also another simvar like this, AUTOPILOT VS SLOT INDEX, bit this isn't currently requested or available in the FSUIPC offsets. I could add this if useful.

John

Edited June 1, 2021 by John Dowson
Checked adjusting offset 0818

[John Dowson]

18 hours ago, John Dowson said:

The inc/dec controls use the AP_ALT_VAR_SET_ENGLISH control, but this doesn't seem to have any affect when I assign to this. This actually changes the AUTOPILOT ALTITUDE LOCK VAR:3 which is held in offset 0818, so you could try adjusting this directly. I haven't tried this. However, changing this does not seem to have any affect either.

Sorry, this is wrong. Using the AP_ALT_VAR_SET_ENGLISH control does work and updates the displayed value and changes the AUTOPILOT ALTITUDE LOCK VAR:3 variable with the provided parameter. Offset 0818 is currently read-only, so updating the offset directly won't work (although I will look into updating so that writing to the offset triggers the AP_ALT_VAR_SET_ENGLISH  control).
The problem will be how to determine the correct parameter value to send with the AP_ALT_VAR_SET_ENGLISH control. the parameter is the value to be displayed (in feet), so you would need to read the displayed value, which is in offset 0818 but in metres, so you would need to convert this to feet, and add/subtract the appropriate increment/decrement and then set the value. You could do this in a lua script but it may be easier if I do this by enabling writes to offset 0818. I will look into both.

[John Dowson]

2 hours ago, John Dowson said:

You could do this in a lua script but it may be easier if I do this by enabling writes to offset 0818. I will look into both.

I think its best to allow offset 0818 to be written to in feet, as this can then be used directly with the AP_ALT_VAR_SET_ENGLISH  control. I have updated FSUIPC7 for this and will release in the next few days, when I release v7.2.0. O will release this as v7.2.0d (beta) today via the 7.2.0 beta announcement page.

With this implemented, you can write a lua script to inc/dec the selected altitude. To do this, you should use the lua event.button function to assign the button, rather than the UI. The handling functions should:
    - read the current setting from offset 0x0818. This will be in meters*65536.
    - convert the value read to feet by dividing by dividing by 65536 (to get metres) then multiply by 3.280839895 to convert to feet
    - then adjust the value by the increment/decrement amount (in feet), taken from lvar L:XMLVAR_Autopilot_Altitude_Increment 
    - write the resulting value back to offset 0x0818

I can provide such a script if you like. I can look into this after I have released the pending changes in both FSUIPC6 and FSUIIPC7, probably next week.

John

[MarcoM1973]

Hi John....

... step by step I managed to associate joystick button to inc/dec altitude and inc/dec vertical speed....

...but I can't activate them..... even following your instructions I can't associate joystick switches to do it.... it seems impossible to pull or to push that damned knobs except with the mouse......

...I'm going crazy.... I can inc/dec altitude and VS with joystick but I got to activate and engage them with mouse cursor on heading panel....

I thought I could make you a short video... to explain better the problem...what do u think about it???

Best regards, Marco

[John Dowson]

2 minutes ago, MarcoM1973 said:

... step by step I managed to associate joystick button to inc/dec altitude and inc/dec vertical speed....

Ok, thats good. What did you assign to for these?

3 minutes ago, MarcoM1973 said:

...but I can't activate them..... even following your instructions I can't associate joystick switches to do it.... it seems impossible to pull or to push that damned knobs except with the mouse......

Did you try what I suggested:

On 6/1/2021 at 5:58 PM, John Dowson said:

For the Pull, assign to
    AP_PANEL_VS_ON with a parameter of 1 on press, and AP_PANEL_SPEED_HOLD with a parameter of 1 on release
For the Push, assign to
    VS_SLOT_INDEX_SET with a parameter of 1 on press, and AP_PANEL_SPEED_HOLD with a parameter of 1 on release
They seem to have the same affect as push/pulling the knob, but I'm not 100% sure on this, and there is no animation of the knob when sending these.

 

On 6/1/2021 at 5:58 PM, John Dowson said:

Pulling the altitude knob sends a ALTITUDE_SLOT_INDEX_SET control with parameter 1, and pushing the same control with a parameter of 2.
You could try assigning to those.

?
That won't animate the knob, but should hopefully activate what you have set.

5 minutes ago, MarcoM1973 said:

I thought I could make you a short video... to explain better the problem...what do u think about it???

Not much point at the moment - an explanation and your ini and log files is usually more informative than a video. How are you assigning to push/pull the knobs?

[MarcoM1973]

In screen 1 and screen 2 I used your settings for VS knob (B-15 Switch and B-16 switch) but it doesn't work.... Is that correct haw I did it???

[John Dowson]

I can't read those images. Please show me your FSUIPC7.ini file.

[MarcoM1973]

Ok!!!!! Sorry!!!!

Here it is!!!!  B15 & B16 for VS   and    B17 & B18 For alitude.... but they don't work.

FSUIPC7.ini

[John Dowson]

What aircraft are you using? Your A320NX profile is only set-up to be used with the following aircraft:
    Airbus A320 Neo Alitalia 8K (A32NX Converted)
Is this the old FBW A320 that replaced/augmented the stock one? If so, its vety old now. The latest FBW A320 is installed as a distinct A320 to the stock one, and is called:
    Airbus A320 Neo FlyByWire
So, first can you check that you are up-to-date with the latest FBW release.
Also, in your FSUIPC7.ini, you should change this:

Quote

[Profile.A320NX]
1=Airbus A320 Neo Alitalia 8K (A32NX Converted)
 

to this:

Quote

[Profile.A320NX]
1=A320

to pick-up all variants (including the stock A320). If you don't want to include the stock A320 in your profile, you can adjust so that the name you enter is a substring match to only the FBW A320 (e.g. 1=FlyByWire).

19 hours ago, MarcoM1973 said:

... step by step I managed to associate joystick button to inc/dec altitude and inc/dec vertical speed....

How have you assigned this? I see nothing in the ini you attached that does this...

Once you have checked you are using the latest FBW A320, please try again. You can also open the console window (Log -> Open Console) to see which events are being sent when you pull/push the knobs in the UI, then try your assignment to these functions to see if they emit the same controls. You can attach your .log file (and updated .ini) with this logging if still not working.

 

[John Dowson]

Also, just checked again, and it looks like those controls for the VS pull/push don't work, but the altitude ones seem ok, but please test.
I'll keep looking for the VS pull/push....

[John Dowson]

Just checked the MobiFlight spreadsheet to determine the state if the FBW events, and the FCU VS/ALT pull/push events are all documented as:
    dev version, soon on experimental
(see https://docs.google.com/spreadsheets/d/1jTXlcHaJWx0B7TB63Pmma7bKwpxsxXJO6EJ3ECt7zpc/edit#gid=172455454)

So these aren't working yet on the stable - and also not in the experimental. So, it sounds like you need the dev version for these to work at the moment, or maybe wait until it has been moved to the stable.