John Dowson

When you have overloaded (i.e. multiple) assignments to a key or button, only one assignment is shown in the UI and it will be greyed-out and you cannot edit or change it. You can only modify such assignments by directly editing the ini file. The issue with these assignments: is that both will always be sent. You can add an offset condition as I already outlined, or possibly define a new toggle preset, that looks at the value of A:FUEL TANK SELECTOR:1 and then triggers the correct event. So, rather than: use something like: DA62s_LH_Fuel_Control_Toggle#(A:FUEL TANK SELECTOR:1, enum) 0 == if{ (>K:FUEL_SELECTOR_LEFT_MAIN) } els{ (>K:FUEL_SELECTOR_OFF) } Not 100% sure that is correct as I don't know the range of values for A:FUEL TANK SELECTOR:1 or what they mean without checking, but that preset code just assumes 0 is off and any other value is on. Using that, you only need the one assignment. The preset for the right fuel control toggle would be similar but use the appropriate A:vars and K:events.

A compound key press would be a key press that is dependent on another key being pressed. I think what you are talking about is overloading your assignments, i.e. having multiple assignments to the same button. To do this, you need to comment out the first assignment, make the second assignment, and then uncomment the first. See this post: You can also do the same to overload buttons. You can also do compound key and button assignments. Compound button assignments are described in the Advanced User guide. For compound key assignments, you would have to use a spare FSUIPC offset. As well as the two assignment lines for the key press, you add a third assignment on the key you want to use to compound with, and assign this to set an offset value to 1 on press and 0 on release. You then add an offset condition on your original key press assignments, so that one is used when the offset holds 1 (indicating the compounding key is pressed) and the other when the offset holds 0. You can do something similar to have alternating assignments on a key press. You would need 3 assignments to the same key press, the two you want to alternate, and a third one that toggles the first bit in a (spare) FSUIPC offset. The two alternating key presses would then have an offset condition on the state of this offset. So when you press the assigned key(s), this would send one control, depending on the state of the offset, and then change/toggle the value in the offset. The next time you pressed the key(s), the second assignment would be sent (as the offset now holds a different value), and then the offset would be toggled again to go back to its original value. Try setting this up yourself, otherwise I can take a look but not until next week now. I have already spent a lot of time helping you - I really need to get onto other things for a few days. No, because as I keep telling you, the C510 is mainly using Input Events, and you cannot use input events via calculator code/presets. I can share my assignments to the input events - I will add these to the other thread when I get time.

Yes - see John

PMDG 737: I have assigned using Send to FS as normal axis to Axis Throttle1 Set (X-axis) and Axis Throttle2 Set (R-axis). No calibration - make sure you are using a profile calibration section and reset the throttle calibration on page 3 of the calibration screen. However, you sill still need to reverse the axis by scaling, i.e. add ,*-1 to the axis assignment line, e.g. 5=BX,256,F,66420,0,0,0,*-1 -{ TO SIM: AXIS_THROTTLE1_SET }- 6=BR,256,F,66423,0,0,0,*-1 -{ TO SIM: AXIS_THROTTLE2_SET }- You can probably also do this via calibration if you prefer. For the CRJ, you need to assign with 'Send to FS as normal axis' and use the Throttle1 Axis Set Ex1 and Throttle2 Axis Set Ex1 controls/events. You should then go to the calibration tab, check the Profile Specific checkbox, and then re-calibrate the throttles on page 3 (you will need to reverse). Once that is done, you should be able to calibrate further in the EFB, Make sure you are using Throttle Type set to use Dual Axis, and if using reverser axes, make sure you re doing the same in FSUIPC calibration - but probably better to not use reversers on an axis for this aircraft with the Bravo, as it doesn't have a proper reverser axis. The ATR is similar to the PMDG (i.e. it uses the *_EX1 controls/events). Once configured in FSUIPC, configure in the EFB. For the Fenix (which I don't have), I think you also need to use the *_EX1 controls, or presets). See You will need to reverse, either via scaling or calibration. Also see: The BAE 146 also uses the *_EX1 controls - s Nothing is simple in MSFS! John

Try these presets (add to your myevents.txt file): Dividing your axis value by 218.45 should change the range from -16384 to +16283 to -75 to +75 which looks to be the range for the lvar. John

Have you tried assigned using the Steering Tiller axis (with Send direct to FSUIPC calibration) or Steering Set / Axis Steering Set (with Send to FS as normal axis)? Otherwise, there are two potentiometer Presets for the Fenix A320 steering tiller: FNX320 Misc Tiller Capt Steering Set and FNX320 Misc Tiller FO Steering Set (see https://hubhop.mobiflight.com/presets/). As these are Input (potentiometer) presets, they will not appear in the MF events.txt file. However, you can copy the preset definitions and add them to your myevents.txt file and then assign to them directly. You probably need to calibrate the preset for your axis values - most MF presets assume a potentiometer range of 0 - 1024, rather than a standard axis range of -16384 to + 16383, so you need to change the calibration of the axis input value (represented by @ in the preset definitions) to work on a standard axis range. I can help with this if not familiar with RPN. Looking at those presets, they seem to use AXIS_STEERING_SET to control the tiller, but also lvars L:N_FC_CAPT_TILLER or L:N_FC_FO_TILLER, probably to control the visuals, so looks like a preset is needed rather than simple direct assignments to the axis control. John

Can you please attach your FSUIPC7.ini, FSUIPC7.log and FSUIPC7.JoyScan.csv files please and I will take a look. Are your assignments still working, or do you have to edit/change the ini or re-assign when your devices are detected and given a different letter? This really shouldn't happen, unless windows is generating a new GUID for your devices. I will know more when I can see your full files. John

I have the Bravo and have no issues. I can check for some of your aircraft (ATR, CRJ, PMDG 737) but not for the ones I don't have (Fenix A320 or the Justflight BAE 146). This will be nothing to do with Honeycomb, and will be due to the way you have assigned. Well, do this when you get a chance and report back. John

I cannot tell what is happening as you have not activated logging for Buttons & Keys. Please do this, also set logging for Events, and remove all other logging, and then show me the FSUIPC7.log file showing your issue. If you open the logging console (Log->Open Console), you should be able to see what is happening in real-time and this might give you some insight, Otherwise, attach your log here and I will take a look. Also please check and remove any key press assignments in MSFS for any key combination assigned in FSUIPC7. You can do this if there is something that holds the state of the fuel control (i.e. on or off). This may be an lvar or a simvar. You would need to add this to a spare FSUIPC7 offset, if not already available, then overload your key press assignment (i.e. assign both to the same key press) and then add an offset condition on each assignment, so only one is executed. Alternatively, you can define the presets so they only actually do anything if the state is correct, and overload your assignments to send both presets. Then only one should actually do anything. You also seem to be duplicating MF presets (available in the events.txt file) in your myevents.txt file. Why are you doing this? Better to just use the MF presets, but if you want to use your own then you should at least give them a unique name. As you are using the same preset names as MF, I do not know which preset definition will be executed - it could be either. John

Yes That looks ok and should work, so I don't know why it isn't. Just checked that here and it reverses the axis here. In the calibration page, do you see the in/out values move when you move the throttle lever (you need to have the aircraft loaded and ready-to-fly)? You should see the difference in the in/out values between when the rev box is checked and when not. You can also reverse an axis using an axis scaling value of -1 - this is described on page 41 of the Advanced User guide, section Additional parameters to scale input axis values. You are confusing reversing the axis with reversers ON an axis - they are two different things. You have also calibrated in the sim/EFB with a reverser axis, but have calibrated in FSUIPC7 with no reverse zone. This will invariably cause issues. If you are using a reverser axis, you need to uncheck the No reverse zone checkbox in the FSUIPC7 calibration page and then calibrate with a reverser axis. Othewise, you need to switch the calibration on the EFB to 'Throttle hardware has no reverser axis'. As the CRJ uses the *_EX1 controls for throttle, you have to use Send to FS as normal axis. You cannot use these axes controls with Send direct to FSUIPC calibration, as doing that would use the standard axes controls which do not work in the CRJ. Take off axis control logging for the time being and your log files will be a lot smaller. I will ask you to activate logging if/when needed. You are not using profiles-in-separate-files, so I only need one ini, your FSUIPC7.ini. Try calibrating with a reverse zone. Otherwise switch to Send to FS as normal axis and try with the Axis Throttlen Set controls If you cannot get this to work, activate logging for axes controls, load the aircraft and then: 1. Move the throttle in the VC through its full range, to max throtle and back to min/idle. 2. Move your assigned axis through to full throttle and then back again Then exit FSUIPC7, and show me your FSUIPC7.log and FSUIPC7.ini files. John

The controls/events listed when Select for FS control is checked ARE the sim events - I just replace the underscores with spaces and only capitalize the first letter to make it more readable and look better. All FS events/controls are also listed in a text document in your FSUIPC7 documents folder, both in alphabetical order and control number order. This is a question for MSFS - nothing to do with FSUIPC7. I cannot do anything about this. Of course, and I have told you this many times - just check Select for Input Event. You can assign buttons and keys to input events, as well as to entering/leaving an axis range. You cannot directly assign to an axis - you need lua for that. It does recognise the tab key as an additional modifier, but not the windows key. I removed this as it invariably causes issues. See page 25 of the Advanced User guide for a list of the available modifiers (or shifts) : Not sure what you mean here. Presumably by output keypresses, you mean when FSUIPC7 sends keys, such as on a button press, and input keypresses are assignments to key presses in FSUIPC7? All modifier keys are available in both (although different shift values are used, as documented). You can also add offset conditions to key press assignments, as you can for button assignments. As I keep saying, you can assign directly to Input Events. However, you cannot use input events in calculator code, so you cannot use them (i.e. B:vars) in presets. This is due to MSFS, not FSUIPC7. If you want to access B:vars / Input Events, there is a hack you can do (i.e. via changing the aircraft xml files) which I have explained in several posts, but I would not recommend this (it works by adding your own l:var to control the b:var, and then use the lvar). John

Note that you can now use Input Events (or lvars) for most controls. However, I am still having issues finding out how to assign to the fuel cut-off triggers, below the throttles. These trigger the events TOGGLE_FUEL_VALVE_ENG1 and TOGGLE_FUEL_VALVE_ENG2, but sending these (or the SET_FUEL_VALVE_ENG1/2 controls) doesn't seem to do anything. There are also no Input Events or lvars for these triggers (that I can see). Further info in this topic: John

For the pitot static/off switch, you can use the lvar C510_Pitot_Switch_Position. John

Ok. Not sure why - battery, avionics, starter all work easily via Input Events. The only difficulty I am having at the moment is for the fuel cut-off triggers and the pitot heat/static switch which don't seem straight-forward - I will look into these further tomorrow. You can also use FSUIPC logging - events and Input Events, and open the logging console (Log->Open Console) to see the messages in real-time. Of course - just check Select for Input Event in the assignments panels. You can choose between Standard FS controls (including PM controls), Presets or Input Events for assignments. Thats strange, and I do not see that here. Windows normally uses the windows (or CMD) key, not the alt key, which is why it is recommended not to use this as a modifier (and I think I removed this in FSUIPC7). Yes, that seems to be the key combination for the nav log. No idea where this is defined - it isn't listed under the keyboard controls. Modifier keys just allow for more distinct assignments. Using them will not prevent anything else that is also using and receiving them. Yes. This is for receiving keys. Normally FSUIPC receives key press/release events from MSFS via SimConnect. However, for some button-controllers (i.e. controllers that send configurable key press combinations on a button press) the key presses will not be received. For such controllers, you can set this and FSUIPC7 will install a global keyboard hook and receive all key presses directly from windows and not from MSFS via SimConnect. You only need to set this option if you are using a button-controller that sends key presses that are not seen by FSUIPC7. FSUIPC7 cannot control how other programs respond to your key presses. Choose a combination that doesn't trigger other actions - there are many possible combinations. John

In FSUIPC... It certainly is - see, for example, the image on page 36 of the User guide - notice the Rev checkbox. This is for reversing an axis, and will be in each calibration panel for axes that can be reversed. No idea what this means, sorry... zip/compress them if too large to attach directly. Your upload limit will increase the more you post. It is usually much better to assign with Send direct to FSUIPC calibration and calibrate, and assign using Send to FS as normal axis only if the aircraft is having issues with FSUIPC calibration. If you assign using Send to FS as normal axis then this will also be calibrated in FSUIPC, but AFTER values have been sent to the FS and received back, which can also create issues with certain aircraft. If assigning in this way and you do not want FSUIPC to calibrate, then you must create a profile-specific calibration section (or else the general calibration section will be used) and disable any calibration settings you have there (i.e. click Reset in each of the calibration tabs). I am not going to look at your files yet - I have no idea what I am looking for! As I said, lets do one aircraft/issue at a time. If I can show you how to do that, it may become clear to you. So please let me know what aircraft you are using, what issue you are having, and show me/attach your ini and log files for this. I don't understand the issues you are having - if you had everything working with the saitek controller, it should be relatively straightforward to switch to using the Bravo. John

You are also using a very old beta version of FSUIPC7, 7.3.26g: Please update to the latest and only supported version, 7.4.11. You need a later version to assign to Input Events correctly.

I have just looked at the ini and log files you posted, and they report no devices acquired for use by FSUIPC7: So your devices are not being controlled by FSUIPC7. No idea why this is. Are your devices working and recognised by FSUIPC or not? And this is nothing to do with the aircraft you are using...If your devices are not recognised, we need to look into this first rather than assignments for a specific aircraft,,, You have raised quite a few support requests on this so I presume your devices were recognised. What has changed? John

Well, they should provide information on how to control the aircraft, whether this be standard events, lvars/hvars or input events. However, it is not difficult to detemine how any switch works, by either using FSUIPC logging (which will log events and input events. when selected) or using the facilities provided by MSFS (devel functionality, mainly behaviors console). I wouldn't expect developers to provide presets or Spad.Next snippets. These are both community-driven efforts. And as the C510 seems to mainly use Input Events, you cannot use presets/calculator code for most functions of this aircraft. And you must see the difficulty here. Your Alpha/Bravo controllers are nothing like the actual instruments in the C510, and so some mapping is necessary, and people will want to map these controls differently. For example, the Alpha uses a magneto to start the aircraft (i.e. it is for GS aircraft). There is no sensible mapping of this to engine L/R start buttons - you have to decide how you want to do this. But once you have decoded which controls/buttons to use. it should be relatively straightforward to implement/assign. I got these working using my saitek X55 controllers within a few minutes, assigned to the appropriate Input Events. I will look into assigning these on my alpha/bravo. What would you like to use, for example, for the engine start buttons on the alpha/bravo?

First, you posted in the wrong sub-forum - I have moved your post to the correct place, the sub-forum for FSUIPC7. This issue is documented in the README.txt file that comes in the zip file you downloaded (as well as in many other support requests in this forum): John

The C510 does have these input events, although I think the standard controls might also work, or at least some. Will take a look when I have time, but also need to familiarise myself with the start-up procedure first.

You may as well aslo remove these entries if you no longer use these devices: John

Note that you have no general assignments and you are not using substrings for your profiles. Therefore if you load an aircraft that does not exactly match a profile entry, you will have no assignments in FSUIPC7. Revise your profile strings - they all look a bit strange. For example, change this: to this: and this: to this: etc. Do this for all your profile aircraft, i.e. use substrings to match all variants.

You can reverse in the calibration page. But what am I looking at? You have reported so many issues. Lets do one issue at a time please. Load an aircraft you are having issues with. Activate appropriate logging for your issue (i.e. if it is with an axis, activate logging for an axis). Then reproduce your issue, exit FSUIPC7 and then attach both your FSUIPC7.ini and FSUIPC7.log files and I will take a look.

This is not a 'FSUIPC thing'... An axis is just an axis, it depends how it is configured. Configuring an axis for throttle on the Bravo is EXACTLY the same as configuring an axis on a saitek device. There is no difference as far as FSUIPC is concerned, it is just another axis on a controller. So it all depends on how it is configured. Did you re-configure you assignments for the Bravo? Did you disable the bravo in MSFS, or at least remove the default assignments? You are assigning to the wrong controls. For the CRJ, you need to assign to the _EX1 controls (i.e. THROTTLE1_AXIS_SET_EX1 & THROTTLE2_AXIS_SET_EX1, or THROTTLE_AXIS_SET_EX1). If your throttle was working on your saitek controller, then you must have been using this axis control. For each aircraft. you need to check how your axes were assigned with the Saitek and then redo your assignments with the bravo. I don't understand how you would expect it to work without doing this. Please do this., Any further issues, please at least attach your FSUIPC7.ini file so that I can see your assignments. John

Also, have you read the documentation for the C510, especially the start-up procedures? You have to open the fuel cut-off levers under each throttle - see page 27. Are you doing this before trying to start the engines?