DannyEvans

Hi John, Sorry for the wait, I was finally able to test out the latest calibration to confirm the results and it was successful again! You were absolutely right, I think it is the axis assignment direct to FSUIPC calibration option that looked like the root cause. I read up on your instructions again, I'm sorry for having missed it in one of your earlier posts! Would've saved us some time. Thank you again for all your help and bearing with my (lack of) technical troubleshooting skill lol. I hope you have a fantastic day! 😄 - Danny

Hi John, I've just had a very interesting test. In addition to what you mentioned above, I decided to see if deleting all my other axis in P3D and re-assigning them via FSUIPC would potentially help, so I set up my Aileron/Elevator/Rudder/Throttle axis via the same method as the brakes (minus the calibration), checked off the option to eliminate control spikes, and ran the test again. Much to my surprise, the autobrakes actually worked this time around! I suspect that one of the previously assigned axis may be interfering with the brakes in some way behind the scenes but I'm not 100% sure. I've attached the new ini file and the log file with the lua scrip to this link for review: https://limewire.com/d/OhIeb#RRJi8EaOc7 I will test the same scenario again at a different airport potentially and see if I can replicate the success. I will keep you posted on the follow up results.

Hi John, Sorry for the delay, just got back from work and was able to test it again as specified. I deleted any Brake Right/Left axis assigned in P3D to the Saitek Pedals and re-assigned them via FSUIPC before calibrating them this time around, along with setting the null zone listed above. The list local panel vars setting was also selected right when the test started. N For the New Test Scenario: - Loaded the flight - Tested the brakes manually - Cycled autobrakes from RTO-1-2-3-4(Max) back to RTO - Took off as normal and approached CYYZ ILS 24L, the selected autobrake level was "3" - On landing noticed the same issue with the autobrakes not working/activating - Pressed down the pedals manually for full braking, and noticed poor braking action not consistent with maximum braking. - Came to a complete stop on manual brakes, released the brakes, paused the sim, and shut it down. Not sure if it's relevant, but before takeoff when switching the autobrakes to "RTO" the Autobrake Disarm lights came on momentarily, even if toe brakes or parking brakes were not applied. Even during the climb-out, the autobrake is not reset from "RTO" to "Off", it has to manually be moved to "OFF". Later in the test, at the moment of touchdown, the Autobrake button remains physically set at "3", however the Autobrake Disarm light appears, and remains on right through the rollout, and even once manual braking is applied to come to a stop. It only goes off once the autobrakes are set to "OFF" in the aircraft. The only time the autobrakes still work is when the brake calibration is disabled/deleted (with Right/Left Brake Set Axis assigned via FSUIPC). Even then, when the pedals are pressed the aircraft seems to apply maximum braking instantaneously regardless of the physical amount the pedals are actually depressed to. Assigning a slope value of 15 for progressive braking is the only thing that prevents this behavior. The new log and ini file is here: https://limewire.com/d/PDEYr#QUh2AoUszJ

I ran the tests again to get new log files, this time from brakes off on takeoff to a full stop landing (short flight starting and ending at CYYZ). Currently the Left/Right Brakes are only assigned via FSUIPC to my knowledge, as suggested. In both tests, the results were the same when trying with & without the brakes calibrated. I used your link and I attached both the logs, along with my user controls file for P3D and my current FSUIPC.ini (without the brakes calibration). https://limewire.com/d/Elgms#WwQbqWkls4 I hope that's a little bit more useful! If there's anything else you would like me to try and log please let me know.

Hi, Thanks so much for getting back to me. My brakes are unassigned anywhere in P3D (except for "." for keyboard), but definitely not to any controller axis. I also assigned the toe brakes in FSUIPC as suggested above. I recorded both logs as requested but even after compressing it to a .rar they're still too big to be attached. What I did instead was take any entries that have 2F80 in either log and just put those into one file (attached) and labeled it accordingly. Hybrid log File.rar From what I can tell, when the brakes calibration is active, 2F80 or any autobrake command isn't read, but without the calibration the log entries did read it and activate the autobrakes on touchdown. Really strange. Should I try it again with the IPC Write logging enabled? Danny

Hi There, I'm having an issue with the 737 Max disarming autobrakes on touchdown whenever the toe-brakes are calibrated via FSUIPC. I've isolated this issue to just the IFly's Max, no other aircraft (payware or default) are affected. I'll provide my system/hardware details below and a test scenario: System/Hardware - i7-9700, RTX3060, 32GB Ram, 1 TB SSD, Fully updated windows/drivers - Thrustmaster Airbus Joystick (brake axis deleted) - Cyborg V.1 Joystick (brake axis deleted) - Logitech Flight Rudder Pedals (Where toe brakes are calibrated) - FSUIPC6, Version 6.2.2 (Registered) - Prepar3D V5.4.9.28482 - Windows 11 Version 24H2 - iFly 737 Max (Latest version) Prior to Touchdown: - Stabilized ILS Approach - Speedbrakes Armed - Flaps 30 - Autobrake 3 On Touchdown: - Power Idle - Speedbrakes Deploy - Autobrake setting remains on 3, Disarm amber light ON, brakes do not apply - Only ground friction and reverse thrust marginally slow down the aircraft - Toe Brakes manually pressed via rudder pedals, actual braking commences Notes: I've tested regular braking of the plane while taxiing, parking, using the realistic parking brake mode, and for differential braking, it all seems to be working perfectly except for the autobrakes on touchdown. In the air on approach, there's no error or issues of any kind, and there is no indication the brakes are being applied erratically by hardware spikes/3rd party software. The issue happens right on touchdown. Temporary Workaround: The only solution (not really) that I've focused on has been when I isolated the issue to the FSUIPC brake calibration not working well with the iFly MAX. When I delete the brake calibration lines in the FSUIPC.ini file, the iFly's autobrake system works great on touchdown, however manual braking becomes very rough (i.e. Even with the brakes manually depressed say only 20%, a 100% brake force will apply, the action is not progressive as compared to when it's calibrated via FSUIPC). As a result, deleting the FSUIPC calibration does bring the autobrake functionality back, however it comes at the cost of having an incorrectly calibrated default manual braking axis. Additional References: Below is the Brake Section of my aircraft.cfg: [brakes] parking_brake = 1 toe_brakes_scale=0.80 auto_brakes = 4 hydraulic_system_scalar = 1 Below is the Brake Calibration from my FSUIPC.ini file: [JoystickCalibration] LeftBrake=-16383,16383/8 RightBrake=-16383,16383/8 SlopeLeftBrake=15 SlopeRightBrake=15 Finding Summary The core issue here seems to be that the FSUIPC brake calibration is somehow disarming the iFly Max's autobrake function on touchdown. It confuses me because this product does require the latest version of FSUIPC to function, however any calibration made via FSUIPC is wreaking havoc with the aircraft's autobrake system. I will attach my FSUIPC log file, my FSUIPC settings, and all relevant screenshots of the issue. Any help I can get on this would be greatly appreciated! Thank you in advance for your help ****Update, I can only attach my INI file for FSUIPC, my log file from the latest file is too large to be attached or even pasted below. The logging was started at approx. 1000 AGL on approach to CYUL ILS RWY06L in the iFly 737 Max 8, and was stopped during the rollout on the runway after touching down. I used FS interrogate to identify any Brake-related codes in the log file. During the logging period, manual brakes were not used at all, nor was manual braking registered in the sim from what I could see. What's interesting though is that the log file read a bunch of lines coded as Read "32F9" which is the "Brake being used Flag", var U8, Size 1, Read Only, Category Controls. I'm absolutely confused over what is really causing this issue, and if it's an FSUIPC issue or an iFly issue (as no other aircraft is experiencing anything like this). FSUIPC6 INI File.ini