John Dowson

Your scan shows 8 HID devices (4 distinct, with 2 Button Box Interface and 2 Virtual joystick). Disconnect these: Button Box Interface (both) Button Box Interface BBI-64 Virtual joystick (both) BU0836 Interface The script I attached removes the registry setting for these devices. If you look at your JoyScan.csv file, you will see a discrepancy between the HID scanning (first section) and the Registry scanning (second section). These two sections are then matched/merged with your current user settings (third section) to produce thee matched/decided settings (fourth section). The incorrect entries are these in bold: The .reg script removes all the entries for these 6 devices (4 distinct types). Hopefully, when these entries are removed and your devices reconnected, it will add the correct entries. John

I only provide this file. It is generated from the community-driven effort led by MobiFlight, and the source is here: https://hubhop.mobiflight.com/presets/ Note that if/when defining your own presets, you should do this using the myevents.txt file. Otherwise you will lose your changes as the events.txt file will get updated/overwritten each time you install/update FSUIPC7. If any events in the events.txt file, provided by MobiFlight, are not correct, then you should submit changes/updates on the HubHop website. This is the community driven resource for these events/presets. John

Can you please attach your FSUIPC7.ini file complete and in its original format. This is because there is an error in your assignments. If you look at them, they are all like this: 433=38,8,P,0 -{Up: Press=Preset Control }- i,e, assigned to a preset but no preset was selected. An assignment to a preset should look like this: 239=83,8,PParking_Brake_Set,0 -{S: Press=Preset Control }- i.e. with the name of the preset after the P. How are you adding these assignments? For key assignments, you need to Confirm before clicking Ok - are you doing this? Otherwise, please let me know how you are generating assignments to presets with no preset specified. Also, please check what version of FSUIPC7 you are using., If it is not 7.4.5, please update.

From http://fsuipc.com/ Can you please switch to using joyletters: change the following in the [JoyNames] section of your FSUIPC5.ini file: AutoAssignLetters=Yes Then run P3D/FSUIPC5 and exit. This will switch to using JoyLetters. Your JoyScan file shows some confusion in your registry and needs to be cleaned. First, run regedit and take a back-up of your registry. Then, disconnect your devices, and download and run (i.e. double-click) the attached file - this will remove registry entries for 4 of your devices. Reboot and reconnect your devices. Then run P3D/FSUIPC5 and exit, then show me/attach your ini, log and JoyScan.csv files again. removeDevices.reg

Try logging offset 0B63 (as U8 in Hex) to see if this offset is being used. Does it update correctly when using the PMDG->Vehicles->Failure Menu? If you also log events, what events do you see? When your lua script sets/clears the bits in this offset, do you see the same values and events? As you are using a PMDG aircraft (which one?), it may not be responding to standard FS controls. Again, use logging. If you are sending the same control in an event callback that is handling the control, then you will get into an infinite recursive loop. Maybe check the event parameter - is this different between a toggle on and a toggle off (some toggle controls do use a parameter)? If so, you can use that to distinguish between toggle on and toggle off, and only send the control for one parameter. Otherwise, try using event.offset instead, and again only send the required control when needed. What events do you see when you use the menu to toggle failures on and off? Check if a parameter is needed. If you need further help, please show me your lua script, and your ini and log files, the latter with logging for Events activated as well as logging for offset 0B63, and maybe also lua plugin logging. One log file should show you toggling and clearing the brake failure via the PMDG menu (without your lua running), and another log file showing what you are trying to achieve with your lua script running.

@Marcolinno Does your parking brake work with 7.4.4?

Yes, of course - please see the lua library documentation: I have moved your post to the FSUIPC7 / MSFS sub-forum. John

Can you please attach your FSUIPC5.JoyScan.csv file please, as well as your FSUIPC5.ini file. Note that you are also using an old and unsupported version of FSUIPC5, 5.131 - please update to the latest and only supported version, 5.157. John

Not sure what you mean by this - each time you run FSUIPC7. it starts afresh...obviously I would have thought... You can use offset 0x3400 to set/clear most logging options, but not all (e.g. no bit yet assigned to Input Event logging or to Lua Plugin logging), and use the offset controls for assignment. Don't forget you need to set LogOptionsProtect =No before you can change logging options on-the-fly. See the Offset Status document on how to use this offset.. John

There are issues when assigning flaps to an axis and calibrating in FSUIPC - some users have reported that this can reduces the climb rate - see and also Better to switch to using the presets instead - see the first link above. Depending upon when FSUIPC is started and the aircraft used, it can take up to a minute or more for everything to be loaded and started. It is better to just wait for everything to be started before you do anything. It is also not possible to read the position of an axis - data is only sent when an axis is moved, so it is not possible to sync the software position with the hardware position at start-up. You just need to move the hardware lever to its initial position before starting MSFS/FSUIPC. John

Can you please provide more information, and attach both your FSUIPC7.ini and FSUIPC7.log files, the latter with appropriate logging activated. What version of FSUIPC were you previously using? Which switches no longer work? Activate logging for Buttons & Keys and Events and generate a log file showing your issue, i.e. load an aircraft and activate a few buttons/switches that don't work, then exit FSUIPC7 and attach both your .log and .ini files.

To assign the flaps in the PMDG 737, use the button presets PMDG B737 Set Flaps n presets (where n is 1,2,5,10,15,25,30,40 or Up - 9 discrete positions) and assign using the right-hand side of the axes assignment panel. See the User guide from page 34 for details on setting up sending presets on axis ranges. John

I think your issue lies elsewhere. but attached below is 7.4.4 for you to try. FSUIPC7.exe

But that is the current/latest version - are you saying it is now working? If not, what was the version previously installed that WAS working? Your log file shows no issues, but shows that you did not add the testoptions logging, as asked for, and you also attached the log file when FSUIPC7 was still running. Please ALWAYS exit FSUIPC7 before attaching log files. As I have no idea how your parking brake is assigned, I need to know the version you previously used when this was working, and then to look at any changes between that and the current/latest version to see what has changed that could possibly affect this. John

As I said, I don't have it and cannot build this (FSUIPC4 was only added to source control at version 4.976), and if I did then I'm pretty sure it still won't work. The issue is with the build tools used to build the version, not the version itself. Maybe someone has an old copy of 4.971 built with the tools at the time and can attach it for you... John

What was the previous version of FSUIPC that you were using? There are very few changes between 7.4.5 and 7.4.4, and nothing that could affect this. And I know nothing about the CFY driver - does this use FSUIPC? If not, your issue lies elsewhere... Can you please answer my questions and follow the advice in my previous post. And its John, not Pete...Pete retired 5 years ago now.... John

👍

Older versions of FSUIPC are not available, and it is not possible for me to build a version of FSUIPC4 that old, and if I could, it would probably not be compatible with XP. No version of FSUIPC4 is supported on any version of Windows before Windows 7.

First, you have no assignments whatsoever in FSUIPC7 - neither axes or button assignments. How is your parking brake assigned? Your log file does show issues - did you manually disconnect and reconnect, or was this automatic? Those entries show FSUIPC7 stopping after 20 seconds, connecting again then stopping after 3 seconds, then connecting again. Do you know why? Can you add the following to the [General] section of your FSUIPC7.ini file: TestOptions=x800 and activate logging for Events and generate another log file. Just load your aircraft, wait a minute or so, then test your parking brake assignment, then exit FSUIPC7 before attaching your log file. Please also explain how your parking brake is assigned. If using an FSUIPC offset, you should add logging for that offset (maybe offset 0x0BC8 as U16).

Than download it from the very first comment in this topic/thread. John

That preset doesn't work - not sure why. I took a look at this and you should assign to the Input Event FUEL_1_Condition_Lever on your axis ranges using a parameter of 2 for cut-off, 1 low idle and 2 for High Idle. I have done this for you in the attached ini file if you would like to try it. John FSUIPC7.ini

All registration/license details for products purchased via SimMarket can be found in your SimMarkeeeeey account. No. You have to click the Register button, which will validate the license details entered and generates the key file. If that is successful, you are good-to-go. If you have a key file, then you either clicked that button or copied it across from your old installation. John

By the way. '//' are NOT the characters that you use to define a comment. Use a semicolon ;. To keep comments in their place, if they are not the first comments in a section, you need to put the semicolon after the index number.

For the Asobo C208 Caravan condition lever, you have to assign to the presets not the FS event. There are two ways to do this: 1. Assign your axis to the button presets Fuel Condition Lever Cutoff, Fuel Condition Lever Low Idle & Fuel Condition Lever High Idle to specific ranges of your axes using the right-hand side of the axes assignment panel. 2. Define an axes preset for the condition lever in your myevents.txt file (create this file if it doesn't exist). Add the following: Restart FSUIPC7 and then assign your axis to this preset (C208 Fuel Condition Lever Set) using the left-hand side of the axes assignment panel. There may also be an Input Event that you can use, but to do this you would have to use an offset and a lua script, so try the preset first.

Please do NOT attach screenshots - attach your FSUIPC7.log and FSUIPC7.ini files. Depending on which aircraft you are using, you may need to assign to something else (e.g. a preset or Input Event). Your FSUIPC7.log file will tell me what aircrfaft you are using, so please show me/attach that. John