Jump to content
The simFlight Network Forums

MCDU Button Press


samsee23

Recommended Posts

Hi All,

 

I have made a button box for my A320 mcdu module and I am trying to figure out how to assign the relevent physical buttons to the simulator ones. The buttons don't appear to be in the dropdown list and i cant get mouse macros to work.

 

Any help would be appreciated

Edited by samsee23
Link to comment
Share on other sites

20 minutes ago, samsee23 said:

The buttons don't appear to be in the dropdown list and i cant get mouse macros to work.

No mouse macros yet in FSUIPC7. If there are no controls in the dropdown, it means that there aren't any provided by MSFS.

You can check to see if MobiFlight provide additional events for this, and if so you can install the MobiFlight WASM module and add the events to FSUIPC using event files. See 

 

and

 

 

Link to comment
Share on other sites

There are a bunch of hvars exposed by MobiFlight to control the CDU in the A320Neo:

    "(>H:A320_Neo_CDU_1_BTN_0)",
    "(>H:A320_Neo_CDU_1_BTN_1)",
    "(>H:A320_Neo_CDU_1_BTN_2)",
    "(>H:A320_Neo_CDU_1_BTN_3)",
    "(>H:A320_Neo_CDU_1_BTN_4)",
    "(>H:A320_Neo_CDU_1_BTN_5)",
    "(>H:A320_Neo_CDU_1_BTN_6)",
    "(>H:A320_Neo_CDU_1_BTN_7)",
    "(>H:A320_Neo_CDU_1_BTN_8)",
    "(>H:A320_Neo_CDU_1_BTN_9)",
    "(>H:A320_Neo_CDU_1_BTN_A)",
    "(>H:A320_Neo_CDU_1_BTN_B)",
    "(>H:A320_Neo_CDU_1_BTN_C)",
    "(>H:A320_Neo_CDU_1_BTN_D)",
    "(>H:A320_Neo_CDU_1_BTN_E)",
    "(>H:A320_Neo_CDU_1_BTN_F)",
    "(>H:A320_Neo_CDU_1_BTN_G)",
    "(>H:A320_Neo_CDU_1_BTN_H)",
    "(>H:A320_Neo_CDU_1_BTN_I)",
    "(>H:A320_Neo_CDU_1_BTN_J)",
    "(>H:A320_Neo_CDU_1_BTN_K)",
    "(>H:A320_Neo_CDU_1_BTN_L)",
    "(>H:A320_Neo_CDU_1_BTN_M)",
    "(>H:A320_Neo_CDU_1_BTN_N)",
    "(>H:A320_Neo_CDU_1_BTN_O)",
    "(>H:A320_Neo_CDU_1_BTN_P)",
    "(>H:A320_Neo_CDU_1_BTN_Q)",
    "(>H:A320_Neo_CDU_1_BTN_R)",
    "(>H:A320_Neo_CDU_1_BTN_S)",
    "(>H:A320_Neo_CDU_1_BTN_T)",
    "(>H:A320_Neo_CDU_1_BTN_U)",
    "(>H:A320_Neo_CDU_1_BTN_V)",
    "(>H:A320_Neo_CDU_1_BTN_W)",
    "(>H:A320_Neo_CDU_1_BTN_X)",
    "(>H:A320_Neo_CDU_1_BTN_Y)",
    "(>H:A320_Neo_CDU_1_BTN_Z)",
    "(>H:A320_Neo_CDU_1_BTN_DIR)",
    "(>H:A320_Neo_CDU_1_BTN_PROG)",
    "(>H:A320_Neo_CDU_1_BTN_PERF)",
    "(>H:A320_Neo_CDU_1_BTN_INIT)",
    "(>H:A320_Neo_CDU_1_BTN_DATA)",
    "(>H:A320_Neo_CDU_1_BTN_FPLN)",
    "(>H:A320_Neo_CDU_1_BTN_NAVRAD)",
    "(>H:A320_Neo_CDU_1_BTN_FUEL)",
    "(>H:A320_Neo_CDU_1_BTN_SEC)",
    "(>H:A320_Neo_CDU_1_BTN_ATC)",
    "(>H:A320_Neo_CDU_1_BTN_MENU)",
    "(>H:A320_Neo_CDU_1_BTN_AIRPORT)",
    "(>H:A320_Neo_CDU_1_BTN_UP)",
    "(>H:A320_Neo_CDU_1_BTN_DOWN)",
    "(>H:A320_Neo_CDU_1_BTN_PREVPAGE)",
    "(>H:A320_Neo_CDU_1_BTN_NEXTPAGE)",
    "(>H:A320_Neo_CDU_1_BTN_L1)",
    "(>H:A320_Neo_CDU_1_BTN_L2)",
    "(>H:A320_Neo_CDU_1_BTN_L3)",
    "(>H:A320_Neo_CDU_1_BTN_L4)",
    "(>H:A320_Neo_CDU_1_BTN_L5)",
    "(>H:A320_Neo_CDU_1_BTN_L6)",
    "(>H:A320_Neo_CDU_1_BTN_R1)",
    "(>H:A320_Neo_CDU_1_BTN_R2)",
    "(>H:A320_Neo_CDU_1_BTN_R3)",
    "(>H:A320_Neo_CDU_1_BTN_R4)",
    "(>H:A320_Neo_CDU_1_BTN_R5)",
    "(>H:A320_Neo_CDU_1_BTN_R6)",
    "(>H:A320_Neo_CDU_1_BTN_PLUSMINUS)",
    "(>H:A320_Neo_CDU_1_BTN_SP)",
    "(>H:A320_Neo_CDU_1_BTN_DIV)",
    "(>H:A320_Neo_CDU_1_BTN_OVFY)",
    "(>H:A320_Neo_CDU_1_BTN_CLR)",
    "(>H:A320_Neo_CDU_1_BTN_BRT_S1)", // Experimental brightness increase (INOP)
    "(>H:A320_Neo_CDU_1_BTN_DIM_S2)", // Experimental brightness decrease (INOP).
    "(>H:A320_Neo_CDU_1_BTN_DOT)",

However, I don't think its possible to use these yet. I am currently working on a WASM module for FSUIPC7 that should be able to handle these (and also lvars), but this is still a few weeks away.

John

Link to comment
Share on other sites

3 minutes ago, John Dowson said:

There are a bunch of hvars exposed by MobiFlight to control the CDU in the A320Neo:

    "(>H:A320_Neo_CDU_1_BTN_0)",
    "(>H:A320_Neo_CDU_1_BTN_1)",
    "(>H:A320_Neo_CDU_1_BTN_2)",
    "(>H:A320_Neo_CDU_1_BTN_3)",
    "(>H:A320_Neo_CDU_1_BTN_4)",
    "(>H:A320_Neo_CDU_1_BTN_5)",
    "(>H:A320_Neo_CDU_1_BTN_6)",
    "(>H:A320_Neo_CDU_1_BTN_7)",
    "(>H:A320_Neo_CDU_1_BTN_8)",
    "(>H:A320_Neo_CDU_1_BTN_9)",
    "(>H:A320_Neo_CDU_1_BTN_A)",
    "(>H:A320_Neo_CDU_1_BTN_B)",
    "(>H:A320_Neo_CDU_1_BTN_C)",
    "(>H:A320_Neo_CDU_1_BTN_D)",
    "(>H:A320_Neo_CDU_1_BTN_E)",
    "(>H:A320_Neo_CDU_1_BTN_F)",
    "(>H:A320_Neo_CDU_1_BTN_G)",
    "(>H:A320_Neo_CDU_1_BTN_H)",
    "(>H:A320_Neo_CDU_1_BTN_I)",
    "(>H:A320_Neo_CDU_1_BTN_J)",
    "(>H:A320_Neo_CDU_1_BTN_K)",
    "(>H:A320_Neo_CDU_1_BTN_L)",
    "(>H:A320_Neo_CDU_1_BTN_M)",
    "(>H:A320_Neo_CDU_1_BTN_N)",
    "(>H:A320_Neo_CDU_1_BTN_O)",
    "(>H:A320_Neo_CDU_1_BTN_P)",
    "(>H:A320_Neo_CDU_1_BTN_Q)",
    "(>H:A320_Neo_CDU_1_BTN_R)",
    "(>H:A320_Neo_CDU_1_BTN_S)",
    "(>H:A320_Neo_CDU_1_BTN_T)",
    "(>H:A320_Neo_CDU_1_BTN_U)",
    "(>H:A320_Neo_CDU_1_BTN_V)",
    "(>H:A320_Neo_CDU_1_BTN_W)",
    "(>H:A320_Neo_CDU_1_BTN_X)",
    "(>H:A320_Neo_CDU_1_BTN_Y)",
    "(>H:A320_Neo_CDU_1_BTN_Z)",
    "(>H:A320_Neo_CDU_1_BTN_DIR)",
    "(>H:A320_Neo_CDU_1_BTN_PROG)",
    "(>H:A320_Neo_CDU_1_BTN_PERF)",
    "(>H:A320_Neo_CDU_1_BTN_INIT)",
    "(>H:A320_Neo_CDU_1_BTN_DATA)",
    "(>H:A320_Neo_CDU_1_BTN_FPLN)",
    "(>H:A320_Neo_CDU_1_BTN_NAVRAD)",
    "(>H:A320_Neo_CDU_1_BTN_FUEL)",
    "(>H:A320_Neo_CDU_1_BTN_SEC)",
    "(>H:A320_Neo_CDU_1_BTN_ATC)",
    "(>H:A320_Neo_CDU_1_BTN_MENU)",
    "(>H:A320_Neo_CDU_1_BTN_AIRPORT)",
    "(>H:A320_Neo_CDU_1_BTN_UP)",
    "(>H:A320_Neo_CDU_1_BTN_DOWN)",
    "(>H:A320_Neo_CDU_1_BTN_PREVPAGE)",
    "(>H:A320_Neo_CDU_1_BTN_NEXTPAGE)",
    "(>H:A320_Neo_CDU_1_BTN_L1)",
    "(>H:A320_Neo_CDU_1_BTN_L2)",
    "(>H:A320_Neo_CDU_1_BTN_L3)",
    "(>H:A320_Neo_CDU_1_BTN_L4)",
    "(>H:A320_Neo_CDU_1_BTN_L5)",
    "(>H:A320_Neo_CDU_1_BTN_L6)",
    "(>H:A320_Neo_CDU_1_BTN_R1)",
    "(>H:A320_Neo_CDU_1_BTN_R2)",
    "(>H:A320_Neo_CDU_1_BTN_R3)",
    "(>H:A320_Neo_CDU_1_BTN_R4)",
    "(>H:A320_Neo_CDU_1_BTN_R5)",
    "(>H:A320_Neo_CDU_1_BTN_R6)",
    "(>H:A320_Neo_CDU_1_BTN_PLUSMINUS)",
    "(>H:A320_Neo_CDU_1_BTN_SP)",
    "(>H:A320_Neo_CDU_1_BTN_DIV)",
    "(>H:A320_Neo_CDU_1_BTN_OVFY)",
    "(>H:A320_Neo_CDU_1_BTN_CLR)",
    "(>H:A320_Neo_CDU_1_BTN_BRT_S1)", // Experimental brightness increase (INOP)
    "(>H:A320_Neo_CDU_1_BTN_DIM_S2)", // Experimental brightness decrease (INOP).
    "(>H:A320_Neo_CDU_1_BTN_DOT)",

However, I don't think its possible to use these yet. I am currently working on a WASM module for FSUIPC7 that should be able to handle these (and also lvars), but this is still a few weeks away.

John

thanks for this john. ill have a look to see what they can do... i need to learn how to use WASM first lol

Link to comment
Share on other sites

1 minute ago, samsee23 said:

thanks for this john. ill have a look to see what they can do... i need to learn how to use WASM first lol

As  I said, you can't use them (i.e. hvars) yet (as far as I am aware). You can use the MobiFlight events though - check them to see if there is anything there that you can use.

Installing the MobiFlight WASM is pretty straightforward. You have to download the MobiFlight connector app and install from there. There are instructions somewhere over on the Asobo forums. Once you have installed the WASM module (into your MSFS Community folder), you will need to download the MobiFlight event files and add them to your FSUIPC7 installation folder. Note that there is currently a bug in the released version of FSUIPC7, v7.0.4, where only one event file is recognised. There is a beta version in the thread I posted where this is fixed - you need to download and use that if using more than one event file.

John

Link to comment
Share on other sites

8 minutes ago, John Dowson said:

As  I said, you can't use them (i.e. hvars) yet (as far as I am aware). You can use the MobiFlight events though - check them to see if there is anything there that you can use.

Installing the MobiFlight WASM is pretty straightforward. You have to download the MobiFlight connector app and install from there. There are instructions somewhere over on the Asobo forums. Once you have installed the WASM module (into your MSFS Community folder), you will need to download the MobiFlight event files and add them to your FSUIPC7 installation folder. Note that there is currently a bug in the released version of FSUIPC7, v7.0.4, where only one event file is recognised. There is a beta version in the thread I posted where this is fixed - you need to download and use that if using more than one event file.

John

any idea when these might be implemented or mouse macro?

Link to comment
Share on other sites

8 minutes ago, samsee23 said:

any idea when these might be implemented or mouse macro?

I am working on a WASM module for lvar and hvar access at the moment. I'm hoping to have a beta out in a couple of weeks, but it depends on how much time I have free to work on this. Support is currently taking up a lot of time, which doesn't leave me much time for new development...

No idea about mouse macros at the moment. I'm not sure if the facilities are available yet, but I'll start looking at this one the lvar/hvar functionality has been released.

John

Link to comment
Share on other sites

2 minutes ago, John Dowson said:

I am working on a WASM module for lvar and hvar access at the moment. I'm hoping to have a beta out in a couple of weeks, but it depends on how much time I have free to work on this. Support is currently taking up a lot of time, which doesn't leave me much time for new development...

No idea about mouse macros at the moment. I'm not sure if the facilities are available yet, but I'll start looking at this one the lvar/hvar functionality has been released.

John

ok cool...one last question and ill leave you alone... how do i install hte beta and not lose my licence? i just tried it and it dfaulted me back to the free version

 

Link to comment
Share on other sites

15 minutes ago, samsee23 said:

ok cool...one last question and ill leave you alone... how do i install hte beta and not lose my licence? i just tried it and it dfaulted me back to the free version

Just replace your current FSUIPC7.exe withthe new one, and it will pick-up the same FSUIPC7.key file that the previous version used. If you are running it from a different folder, then you need to copy across your FSUIPC7.key and FSUIPC7.ini file (+ any other files you may use) to the new installation folder (i.e. where you run FSUIPC7 from).

Its easier just to replace your existing FSUIPC7.exe with the new one downloaded.

Link to comment
Share on other sites

36 minutes ago, John Dowson said:

Just replace your current FSUIPC7.exe withthe new one, and it will pick-up the same FSUIPC7.key file that the previous version used. If you are running it from a different folder, then you need to copy across your FSUIPC7.key and FSUIPC7.ini file (+ any other files you may use) to the new installation folder (i.e. where you run FSUIPC7 from).

Its easier just to replace your existing FSUIPC7.exe with the new one downloaded.

do i need a plugin to use my arduino leonardo with fsuipc. it doesnt seem to be picking up button presses 

Link to comment
Share on other sites

44 minutes ago, samsee23 said:

do i need a plugin to use my arduino leonardo with fsuipc.

FSUIPC only recognises HID joystick type devices. If its another HID type device, you will need to use lua. There is a demo script provided in the lua axamples zip called HidDemo.lua. You can try that - you need to edit it to provide the VID and PID of your arduino, place it in you FSUIPC installation folder and have it auto-started from your ini's [Auto] section.

Link to comment
Share on other sites

34 minutes ago, John Dowson said:

FSUIPC only recognises HID joystick type devices. If its another HID type device, you will need to use lua. There is a demo script provided in the lua axamples zip called HidDemo.lua. You can try that - you need to edit it to provide the VID and PID of your arduino, place it in you FSUIPC installation folder and have it auto-started from your ini's [Auto] section.

ok im getting somewhere with this but i can't get fsuipc to show the mobiflight a320 like yours

Link to comment
Share on other sites

3 minutes ago, samsee23 said:

in the control sent when button is pressed drop down, the A320 isnt listed there.

Why should it be? That just lust the controls available. Did you add the MobiFlight events by dropping the event files into your FSUIPC7 installation folder?
Once you do that, you should see the MobiFlight events at the top of the controls drop-down menu.

Currently you can only use the MobiFlight events, not the hvars, as I said.

Link to comment
Share on other sites

Just now, John Dowson said:

Why should it be? That just lust the controls available. Did you add the MobiFlight events by dropping the event files into your FSUIPC7 installation folder?
Once you do that, you should see the MobiFlight events at the top of the controls drop-down menu.

Not to worry... I had a little play around and i have managed to get the MCDU to work though button presses now. Thank you so much for your help today. It has been very much appreciated!

 

Link to comment
Share on other sites

23 minutes ago, samsee23 said:

I had a little play around and i have managed to get the MCDU to work though button presses now.

Ok, but it would be useful if you could explain how to help others who may have the same issue.

23 minutes ago, samsee23 said:

Thank you so much for your help today. It has been very much appreciated!

No problem!

Link to comment
Share on other sites

Can I ask what devices have you been successful in getting the buttons programmed to work using the MobiFlight events and FSUIPC? 

I'm trying to use GoFlight and TM MFD Cougar devises and have not been successful.  FSUIPC seems to be sending the event, as it shows up in the log, but so far the sim is not responding.

I don't know how or if you can configure these devices in MobiFlight.

Thanks in advance for any insight you can provide!

 

Link to comment
Share on other sites

13 hours ago, GPan099 said:

FSUIPC seems to be sending the event, as it shows up in the log, but so far the sim is not responding.

If the events are being sent then you should be ok. Have you installed the MobiFlight WASM module into your Community folder? That's the module that handles the events on the FS side.

Link to comment
Share on other sites

  • 2 months later...

Hi all....
Don´t know if anyone asked this but I need some help.
(New to all of the MobiFlight, Linda and all of the new stuff out there).... I´ve got myself one of the good things in life, A320 Throttle that I´m, trying to get it to work with no luck at all so far. It works ok within XP, but wen it comes to MSFS2020 it´s completely dead to the world, and I can´t for the love of anything make it work.
So, please anyone with a bit of patience that can land me a hand and guide me into "light"....!
Thank you
Paul

This is the link for what I have.

Throttle & Engine start panel — FSCOCKPIT.EU

Link to comment
Share on other sites

11 hours ago, PSantos said:

Don´t know if anyone asked this but I need some help.
(New to all of the MobiFlight, Linda and all of the new stuff out there).... I´ve got myself one of the good things in life, A320 Throttle that I´m, trying to get it to work with no luck at all so far. It works ok within XP, but wen it comes to MSFS2020 it´s completely dead to the world, and I can´t for the love of anything make it work.
So, please anyone with a bit of patience that can land me a hand and guide me into "light"....!

You have hijacked a completely unrelated thread. Please do not do this -raise a new support topic, giving it an appropriate title. Also, if using FSUIPC, please provide more information.

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.