John Dowson Posted November 21, 2022 Report Posted November 21, 2022 43 minutes ago, Sandy R said: Success!!! Great! 44 minutes ago, Sandy R said: I am however concerned as to why my brake lever was reversed in the first place. I hadn't really questioned it before when all I had to do was tick the 'reversed' box in the dialog before binding the control. However, I now suspect that I may have reversed the polarity of one of the magnets when I was assembling the Hall Sensor units. This means that if I were to share the script on the Authentikit forum, it's only going to work for people who've made the same stupid mistake as I when building their control columns. I think I will go back and redo this fix 'mechanically'* (ie reverse the magnet), and then verify that the original script works ok. It is not an issue if an axis is/needs reversing - many axes work in this manner. To handle this nicely in the script, you can add add two boolean variables - rudderAxisReversed, brakeAxisReversed, and then use those to determine whether to reverse or not. Then it is a simple matter of setting those to true or false. If you can attach the script you are using, I can make those changes for you. John
John Dowson Posted November 21, 2022 Report Posted November 21, 2022 Also, note other users may have an issue with the axis range, not just the reversing. As I said, the script expects each axis to be in the -16383 - +16383 range. Quite a few axes, especially those home-made using potentiometers, can have a different range. If this is the case, you would also need to calibrate the pot's range input to the script to -16383 - +16383. John
Sandy R Posted November 22, 2022 Author Report Posted November 22, 2022 John, I have reversed the polarity of the magnet in the hall effect sensor arrangement on which the Brake Lever relies. This 'Un-reversed' the brake control and enabled me to test your original script and prove it worked perfectly 'straight out of the box'. Also, I was able to check that I had built it as designed first time round so the likelihood is that anyone who's built the Authentikit Spitfire Control Column will have the brake control axis reversed same as I did! Nice to know that I'm not a complete idiot! I am returning the two LUA scripts here should you wish to make the axis independent script you suggested. Thank you so much for this, you wouldn't believe how much joy* this has brought me. Regards Sandy *and frustration - if you thought the Spit's ground handling was challenging, try adding differential braking to the mix spitfireBrake.lua spitfireBrakeRev.lua
John Dowson Posted November 22, 2022 Report Posted November 22, 2022 Simple update - see attached (untested!). Glad this is working for you! Regards, John spitfireBrake.lua
Sandy R Posted November 22, 2022 Author Report Posted November 22, 2022 Thank you so much (again). I shall test this out then post it on the Authentikit forum. I hope you get flooded with FSUIPC sales from them as a result! Reading through your script, it looks like I really over complicated things when I tried to reverse the axis! I console myself with the fact that at least it worked! Best Regards Sandy
Hazzer111 Posted Tuesday at 05:47 PM Report Posted Tuesday at 05:47 PM Good afternoon, Apologies as I am resurrecting this thread a little. I was very happy to discover this solution for making it possible to use differential braking with one axis in msfs. The Avro Lancaster (amongst others) also used this single lever for differential braking. I have been trying to make it work in my sim, however I have reached a dead end. Presently: Pulling the lever applies both brakes - excellent! When I add left rudder the left brake comes on, and the right reduces, visa versa - great, apart from it does this without input from the brake lever. When the brake lever is applied and rudder is input, the brakes just come on as if there was no differential braking. I apologies as this is beyond my basic understanding of the FSUIPC world, so any help would be appreciated. I have searched around and attempted to change numerous settings with no joy. Many thanks, Hazzer spitfireBrake.rar
Hazzer111 Posted Tuesday at 05:48 PM Report Posted Tuesday at 05:48 PM (edited) 1 minute ago, Hazzer111 said: Good afternoon, Apologies as I am resurrecting this thread a little. I was very happy to discover this solution for making it possible to use differential braking with one axis in msfs. The Avro Lancaster (amongst others) also used this single lever for differential braking. I have been trying to make it work in my sim, however I have reached a dead end. Presently: Pulling the lever applies both brakes - excellent! When I add left rudder the left brake comes on, and the right reduces, visa versa - great, apart from it does this without input from the brake lever. When the brake lever is applied and rudder is input, the brakes just come on as if there was no differential braking. I apologies as this is beyond my basic understanding of the FSUIPC world, so any help would be appreciated. I have searched around and attempted to change numerous settings with no joy. Many thanks, Hazzer Please see log as well - seems it wont let me submit more than one thing at a time due to file limits ********* FSUIPC7, Version 7.5.4 (13th July 2025) by John Dowson ********* WebSocket server found: D:\FSUIPC\\Utils\FSUIPCWebSocketServer.exe Windows 11 detected - setting DisableMSFSMonitor to 'Enum' Windows 10 Home 64 Bit reported as Build 22631, Release ID: 2009 (OS 10.0) FSUIPC is running with standard privileges Reading options from "D:\FSUIPC\FSUIPC7.ini" Checking the Registrations now ... User Name="harry smith" User Addr="smithy-harry@hotmail.co.uk" FSUIPC7 Key is provided WIDEFS7 not user registered, or expired 47 System time = 05/08/2025 18:38:35 47 Allowing calibration when not assigned with 'Send direct to FSUIPC Calibration' 63 ------------------------------------------------------------------- 63 *** Preset name 'Cirrus_SF50_Vision_Jet__MSFS2024_-_Toggle_VNV_Button_in_Autopilot_On_and_OFF' exceeds max allowed length of 63 characters - ignoring 219 *** Preset name 'NAV_GPS_SWAP__NAV__button_on_EFIS_Control_Panel__LEFT_SIDE__CAPTAIN_' exceeds max allowed length of 63 characters - ignoring 219 *** Preset name 'NAV_GPS_SWAP__NAV__button_on_EFIS_Control_Panel__RIGHT__SIDE__FIRST_OFFICER_' exceeds max allowed length of 63 characters - ignoring 235 *** Preset name 'Main_instrument_panel_standby_attitude_indicator_cage_button_release' exceeds max allowed length of 63 characters - ignoring 235 Preset file 'D:\FSUIPC\myevents.txt' not found [info only] 235 19666 Calculator Code presets have been loaded and are available for use 266 Registered HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1) 266 FS path = "" 281 ---------------------- Joystick Device Scan ----------------------- 281 Product= Controller (Xbox One For Windows) 281 Vendor=045E, Product=02FF (Version 0.0) 344 GUIDs returned for product: VID_045E&PID_02FF: 344 GUID= {0CE66430-7160-11F0-8001-444553540000} 344 Details: Btns=16, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U65535,V65535,X65535,Y65535,Z65535 344 Product= Rhino FFB Joystick 344 Manufacturer= VPforce 344 Serial Number= 3359534E0100004C52006600 344 Vendor=FFFF, Product=2055 (Version 2.8) 344 GUIDs returned for product: VID_FFFF&PID_2055: 344 GUID= {A8C007E0-1192-11F0-800C-444553540000} 344 Details: Btns=64, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U255,V255,X4096,Y4096,Z4096 344 Product= MFG Crosswind V2 344 Manufacturer= MFG 344 Serial Number= MFG500002 344 Vendor=16D0, Product=0A38 (Version 33.1) 344 GUIDs returned for product: VID_16D0&PID_0A38: 344 GUID= {1ECE9D80-1192-11F0-8009-444553540000} 344 Details: Btns=2, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R4096,U0,V0,X4096,Y4096,Z0 344 Product= L-VPC Throttle MT-50 344 Manufacturer= VIRPIL Controls/20210102 344 Vendor=3344, Product=8191 (Version 0.1) 344 GUIDs returned for product: VID_3344&PID_8191: 344 GUID= {564B53C0-1192-11F0-800A-444553540000} 344 Details: Btns=84, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R16384,U16384,V16384,X0,Y0,Z16384 360 Product= Bravo Throttle Quadrant 360 Manufacturer= Honeycomb Aeronautical 360 Serial Number= 6F7B2E091F1A3B00 360 Vendor=294B, Product=1901 (Version 1.5) 360 GUIDs returned for product: VID_294B&PID_1901: 360 GUID= {966C4330-10C3-11F0-8001-444553540000} 360 Details: Btns=48, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U1023,V1023,X1023,Y1023,Z1023 360 ------------------------------------------------------------------- 360 Device acquired for use: 360 Joystick ID = 4 (Registry okay) 360 4=Controller (Xbox One For Windows) 360 4.GUID={0CE66430-7160-11F0-8001-444553540000} 360 Device acquired for use: 360 Joystick ID = 3 (Registry okay) 360 3=VPforce Rhino FFB Joystick 360 3.GUID={A8C007E0-1192-11F0-800C-444553540000} 360 Device acquired for use: 360 Joystick ID = 1 (Registry okay) 360 1=MFG Crosswind V2 360 1.GUID={1ECE9D80-1192-11F0-8009-444553540000} 360 Device acquired for use: 360 Joystick ID = 2 (Registry okay) 360 2=L-VPC Throttle MT-50 360 2.GUID={564B53C0-1192-11F0-800A-444553540000} 360 Device acquired for use: 360 Joystick ID = 0 (Registry okay) 360 0=Bravo Throttle Quadrant 360 0.GUID={966C4330-10C3-11F0-8001-444553540000} 360 ------------------------------------------------------------------- 375 LogOptions=00000000 00000001 375 Manually started with DetectToConnectDelay=1, InitialStallTime=15 3266 Simulator detected 4266 Trying to connect... 4266 SimConnect_Open succeeded 4266 Running in "SunRise", Version: 12.2.282174.999 (SimConnect: 12.2.0.0) 4266 MSFS version = 12.2.282174.999 4266 MSFS 2024 Steam installation detected 4266 Checking for FS path in 'C:\Users\Harry\AppData\Roaming\Microsoft Flight Simulator 2024\UserCfg.opt' 4266 FS path found = D:\MSFS Community\ 4266 FLT path = "C:\Users\Harry\AppData\Roaming\Microsoft Flight Simulator 2024\" 4266 FS path = "D:\MSFS Community\" 4266 Initialising SimConnect data requests now 4266 Offset file 'D:\FSUIPC\myOffsets.txt' not found (info only) 4281 Number of FS control/events registered : 1795 4281 Mapping custom control numbers 69632 - 84232 (maximum defined by ini parameter MaxCustomControlNumber, defaults to 84232 when not present) 4281 Maximum number of custom events available is 1024 (defined by ini parameter MaxNumberOfCustomEvents) 4281 C:\Users\Harry\AppData\Roaming\Microsoft Flight Simulator 2024\MISSIONS\Custom\CustomFlight\CustomFlight.FLT 4375 User Aircraft ID 39387136 supplied, now being used (myftm=1) 4375 Requesting keyboard input... 4375 Requesting user aircraft data... 4610 Aircraft loaded: running normally now ... 5156 System time = 05/08/2025 18:38:40, Simulator time = 18:38:40 (17:38Z) 5156 Requesting Input Events.... 5156 Starting WAPI (WAPI enabled)... 5156 [INFO]: **** Starting FSUIPC7 WASM Interface (WAPI) version 1.0.4 (WASM version 1.0.7) using connection -1 5156 [INFO]: Connected to MSFS 5156 Aircraft="Lancaster NX611 Just Jane" 5156 -------------------- Starting everything now ---------------------- 5219 Lvars received: 302 L:vars & 0 H:vars now available 5219 Lvars/Hvars received - checking aircraft autos.... 30156 **** Restarting traffic scanning due to non-reception **** 546313 === Hot key unregistered 546313 === Stop called ... 546313 === Closing external processes we started ... 546828 === About to kill any Lua plug-ins still running ... 546985 Lua threads being terminated: 546985 1 = "D:\FSUIPC\spitfireBrake.lua" 547172 LUA: "D:\FSUIPC\spitfireBrake.lua": killed 547172 === Closing global Lua thread 547938 === About to kill my timers ... 548141 === Restoring window procs ... 548141 === Unloading libraries ... 548141 === stopping other threads ... 548141 === ... Button scanning ... 548250 === ... Axis scanning ... 548360 === Releasing joystick devices ... 548360 === Freeing macro memory 548360 === Removing any offset overrides 548360 === Clearing any displays left 548360 === Calling SimConnect_Close ... 548578 === SimConnect_Close done! 548578 === AI slots deleted! 548578 === Freeing button memory ... 548578 === Closing my Windows ... 548578 === Freeing FS libraries ... 549578 === Closing devices ... 549578 === Closing the Log ... Bye Bye! ... 549578 System time = 05/08/2025 18:47:45 549578 *** FSUIPC log file being closed Minimum frame rate was 45.6 fps, Maximum was 46.5 fps Average frame rate for running time of 542 secs = 46.0 fps Maximum AI traffic for session was 14 aircraft Traffic deletions 0 aircraft Memory managed: 10 Allocs, 8 Freed ********* FSUIPC Log file closed *********** Edited Tuesday at 05:49 PM by Hazzer111
John Dowson Posted Tuesday at 06:55 PM Report Posted Tuesday at 06:55 PM Did you assign your rudder and brake axis to the required offsets? This issue is now covered by this User Contribution entry: Can you please post there if you have issues setting this up. And for any problems, don't attach the lua file unless you have modified it as that is available, and if you have modified it than please explain what the modifications were. You should also enable logging in the lua script, by setting enableLog to true at the top of the lua script, and look at the log file as that shouldthen give you a clue as to what is happening. If you can't figure it out, show me / attach your FSUIPC7.log with the lua logging enabled in that script, and also your FSUIPC7.ini so that I can check your assignments. I am closing / locking this thread now - please use that one referenced above. John
Recommended Posts