DannyEvans Posted August 11 Report Posted August 11 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
John Dowson Posted August 11 Report Posted August 11 Looking at your ini, the only thing you seem to be using FSUIPC for is the brake calibration, where you have set quite a big slope (flattened at the start and stepper later), and rudder calibration. You don't have any assignments at all, neither axes or buttons. Are your brakes assigned in P3D, or in iFly itself? I am not sure why brake calibration could affect the auto-brakes. 13 hours ago, DannyEvans said: 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. It is very large as you have so much logging enabled. Could you please just enable logging for the following (and disable the rest): Axis Controls, Events & Extras. Also, please add logging for offset 2F80 (as U8, and make sure to check to send to the normal log file). The file may still be too large to attach (your attachment limit will increase the more you post) - try compressing/zipping it. This will show if the auto-brake setting in offset 0x2F80 is being changed. If it is, we may need to enable IPC Write logging to see if this is being changed by an external program, but leave this off for the first log. It would also be useful if you could provide two log files - one with the FSUIPC calibration and the autobrake issue, and another with he calibration removed and the autobrake working as expected. You could also try with the toe brakes both assigned and calibrated in FSUIPC, to see if this makes a difference. Try assigning the toe brakes using the Send direct to FSUIPC calibration option. John
DannyEvans Posted August 11 Author Report Posted August 11 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
John Dowson Posted August 11 Report Posted August 11 26 minutes ago, DannyEvans said: My brakes are unassigned anywhere in P3D (except for "." for keyboard), but definitely not to any controller axis. Then where re your brakes assigned? 27 minutes ago, DannyEvans said: I also assigned the toe brakes in FSUIPC as suggested above. And then what ha[[ened? 27 minutes ago, DannyEvans said: 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 That doesn't help much - I need to see the full logs. But it does seem that something is turning off the autobrakes You can also use a free file transfer service to show me the logs, e.g. https://filetransfer.io/ 31 minutes ago, DannyEvans said: 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 2f80 just shows the autobrake setting as it is in the sim - nothing to do with reads. It is showing 1 (off) when calibrated, but going from RTO to off and back to RTO when calibrated, But hard to tell anything more when that is all that is logged. But looks lik it was never even set to RTO when calibrated, if the offset always holds 1. But, I really need to see the full logs to understand anything here. But it is certainly not FSUIPC altering auto-brake settings. May be the calibration is triggering iFly to turn this off, not sure. Where are your brakes assigned? And what happens if you remove the current assignment and assign in FSUIPC?
DannyEvans Posted August 12 Author Report Posted August 12 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.
John Dowson Posted August 12 Report Posted August 12 7 hours ago, DannyEvans said: Currently the Left/Right Brakes are only assigned via FSUIPC to my knowledge, as suggested. You have not assigned the brakes correctly in FSUIPC. You have assigned to send a single left/right brake control when entering an axis range using the right-hand side of the axis assignment panel, and that range is so large that the axis is always in that range and will never enter the range, so that they will not be triggered. To assign your toe brakes to an axis, you need to assign in the left-hand side of the axis assignment panel. And you still have AXIS_LEFT_BRAKE_SET and AXIS_RIGHT_BRAKE_SET events logged, which indicates that your toe brakes ARE assigned elsewhere. Controllers are set to ON in P3D, so your brakes are either assigned in P3D or assigned in iFly (if that is possible). Please check where the brakes are assigned, remove those, and assign correctly in FSUIPC. Please see the User manual if you do not know how to assign in FSUIPC. What is strange though, in both logs, is that the value in offset 0x2F80, the AutoBrake switch position, is 1, which is Off, so I am surprised the autobrakes are kicking in at all. What is the position of the auto-brake switch? For the next logs (both tests), can you also move the switch through all its positions (so I can see if that offset changes correctly) and then leave it in the desired position and let me know what that is, to check it matches the offset value. With the brakes calibrated, I also see: Quote 1465000 24036 *** TOE BRAKE AXIS, Left set = 0 (IN=-16383, OUT=-16383) 1465000 24036 Slope adjustment: axis=RightBrake, slope=15 - in=-16384, out=-16384 1465000 24036 *** TOE BRAKE AXIS, Right set = 0 (IN=-16383, OUT=-16383) 1465000 24036 *** Both toe brakes off ... Release Armed 1465016 24036 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -444 (0xfffffe44) AXIS_AILERONS_SET 1465016 24036 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 2151 (0x00000867) AXIS_ELEVATOR_SET 1465047 24036 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -403 (0xfffffe6d) AXIS_AILERONS_SET 1465062 24036 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 2157 (0x0000086d) AXIS_ELEVATOR_SET 1465078 24036 WRITE repeated 6844 times 1465078 24036 WRITE0[16472] 32FA, 2 bytes: 0F 00 .. 1465078 24036 WRITE0[16472] 3380, 74 bytes: 46 69 72 6D 20 6C 61 6E 64 69 6E 67 20 61 74 20 Firm landing at 1465078 24036 2D 32 31 35 20 66 70 6D 20 28 30 2E 38 39 67 29 -215 fpm (0.89g) 1465078 24036 20 61 6E 64 20 31 34 38 20 6B 74 73 2C 20 77 69 and 148 kts, wi 1465078 24036 6E 64 73 20 30 20 6B 74 73 20 61 74 20 30 31 31 nds 0 kts at 011 1465078 24036 20 64 65 67 72 65 65 73 2E 00 degrees.. 1465078 24036 *** AXIS: Cntrl= 66387 (0x00010353), Param= 11631 (0x00002d6f) AXIS_LEFT_BRAKE_SET 1465078 24036 *** AXIS: Cntrl= 66388 (0x00010354), Param= 11631 (0x00002d6f) AXIS_RIGHT_BRAKE_SET ... 1465172 24036 *** AXIS: Cntrl= 66387 (0x00010353), Param= 9993 (0x00002709) AXIS_LEFT_BRAKE_SET 1465172 24036 *** AXIS: Cntrl= 66388 (0x00010354), Param= 9993 (0x00002709) AXIS_RIGHT_BRAKE_SET ... 1465219 24036 *** AXIS: Cntrl= 66387 (0x00010353), Param= 8355 (0x000020a3) AXIS_LEFT_BRAKE_SET 1465219 24036 *** AXIS: Cntrl= 66388 (0x00010354), Param= 8355 (0x000020a3) AXIS_RIGHT_BRAKE_SET ... 1465281 24036 *** AXIS: Cntrl= 66387 (0x00010353), Param= 6717 (0x00001a3d) AXIS_LEFT_BRAKE_SET 1465281 24036 *** AXIS: Cntrl= 66388 (0x00010354), Param= 6717 (0x00001a3d) AXIS_RIGHT_BRAKE_SET ... 1465359 24036 *** AXIS: Cntrl= 66387 (0x00010353), Param= 5078 (0x000013d6) AXIS_LEFT_BRAKE_SET 1465359 24036 *** AXIS: Cntrl= 66388 (0x00010354), Param= 5078 (0x000013d6) AXIS_RIGHT_BRAKE_SET ... 1465406 24036 *** AXIS: Cntrl= 66387 (0x00010353), Param= 3440 (0x00000d70) AXIS_LEFT_BRAKE_SET 1465406 24036 *** AXIS: Cntrl= 66388 (0x00010354), Param= 3440 (0x00000d70) AXIS_RIGHT_BRAKE_SET ... ... and continuing, ending with brakes off: 1466172 24036 *** AXIS: Cntrl= 66387 (0x00010353), Param= -16384 (0xffffc000) AXIS_LEFT_BRAKE_SET 1466172 24036 *** AXIS: Cntrl= 66388 (0x00010354), Param= -16384 (0xffffc000) AXIS_RIGHT_BRAKE_SET So the autobrakes are being armed once you release the toe brakes, and some auto-brake controls ARE being sent, although not full and they decrease quite quickly over a period of 1 second. Without calibration: Quote 1027859 11784 WRITE repeated 5618 times 1027859 11784 WRITE0[16472] 32FA, 2 bytes: 0F 00 .. 1027859 11784 WRITE0[16472] 3380, 74 bytes: 46 69 72 6D 20 6C 61 6E 64 69 6E 67 20 61 74 20 Firm landing at 1027859 11784 2D 32 31 35 20 66 70 6D 20 28 31 2E 36 30 67 29 -215 fpm (1.60g) 1027859 11784 20 61 6E 64 20 31 34 35 20 6B 74 73 2C 20 77 69 and 145 kts, wi 1027859 11784 6E 64 73 20 30 20 6B 74 73 20 61 74 20 30 31 31 nds 0 kts at 011 1027859 11784 20 64 65 67 72 65 65 73 2E 00 degrees.. ... 1027922 11784 WRITE0[16472] 7B91, 1 bytes: 00 . 1027937 11784 *** AXIS: Cntrl= 66387 (0x00010353), Param= 15000 (0x00003a98) AXIS_LEFT_BRAKE_SET 1027937 11784 *** AXIS: Cntrl= 66388 (0x00010354), Param= 15000 (0x00003a98) AXIS_RIGHT_BRAKE_SET ... 1028141 11784 *** AXIS: Cntrl= 66387 (0x00010353), Param= 16383 (0x00003fff) AXIS_LEFT_BRAKE_SET 1028141 11784 *** AXIS: Cntrl= 66388 (0x00010354), Param= 16383 (0x00003fff) AXIS_RIGHT_BRAKE_SET ... 1030359 11784 *** AXIS: Cntrl= 66387 (0x00010353), Param= 16233 (0x00003f69) AXIS_LEFT_BRAKE_SET 1030359 11784 *** AXIS: Cntrl= 66388 (0x00010354), Param= 16233 (0x00003f69) AXIS_RIGHT_BRAKE_SET ... 1030578 11784 *** AXIS: Cntrl= 66387 (0x00010353), Param= 16083 (0x00003ed3) AXIS_LEFT_BRAKE_SET 1030578 11784 *** AXIS: Cntrl= 66388 (0x00010354), Param= 16083 (0x00003ed3) AXIS_RIGHT_BRAKE_SET ... 1030797 11784 *** AXIS: Cntrl= 66387 (0x00010353), Param= 15933 (0x00003e3d) AXIS_LEFT_BRAKE_SET 1030797 11784 *** AXIS: Cntrl= 66388 (0x00010354), Param= 15933 (0x00003e3d) AXIS_RIGHT_BRAKE_SET ... 1031047 11784 *** AXIS: Cntrl= 66387 (0x00010353), Param= 15783 (0x00003da7) AXIS_LEFT_BRAKE_SET 1031047 11784 *** AXIS: Cntrl= 66388 (0x00010354), Param= 15783 (0x00003da7) AXIS_RIGHT_BRAKE_SET .. 1031250 11784 *** AXIS: Cntrl= 66387 (0x00010353), Param= 15633 (0x00003d11) AXIS_LEFT_BRAKE_SET 1031250 11784 *** AXIS: Cntrl= 66388 (0x00010354), Param= 15633 (0x00003d11) AXIS_RIGHT_BRAKE_SET .. ... ending with brakes off: 1060797 11784 *** AXIS: Cntrl= 66387 (0x00010353), Param= -16383 (0xffffc001) AXIS_LEFT_BRAKE_SET 1060797 11784 *** AXIS: Cntrl= 66388 (0x00010354), Param= -16383 (0xffffc001) AXIS_RIGHT_BRAKE_SET i.e. applied full and decrease slowly over a period of 33 seconds. So the autobrake is working, just not very well! I don't know what could explain the difference here. Please try assigning your toe brakes in FSUIPC to see if that makes a difference, and make sure the assignments are removed wherever they are currently assigned. Also, move the autobrake knob through its different positions, and let me know which position you are using. Also, with different positions to see if that makes a difference. John
John Dowson Posted August 12 Report Posted August 12 (edited) I suspect that the aircraft is not using the AUTO BRAKE SWITCH CB simvar, as this always seems to be 1 (off). Could you check to see if there is an lvar available that holds the current autobrake setting? To do this, you need to assign a button or key press to the List Local Panel Vars control, and press the assigned button/switch once the aircraft is loaded. This will then list all lvars and their values to the FSUIPC6.log file. John Later: I see the autobrake selector switch position is available via the iFly SDK:: BYTE Autobrake_Selector_Status;//0:selector RTO 1:selector OFF 2:selector 1 3:selector 2 4:selector 3 5:selector MAX AUTO However, there is no access to this via FSUIPC at the moment. I do intend to investigate adding the iFly SDK data to FSUIPC offsets at some point, when time permits, but currently don't know when I will have time to look into this. So, for now, you need to tell me what position the switch is in - presumably you are using positions indicated by 2,3,4 or 5, no? Still worth checking the lvars though to see if there is also an lvar that holds this information. Edited August 12 by John Dowson Later added
John Dowson Posted August 12 Report Posted August 12 You could also try adding a null zone around the toe brakes, so any small changes (e.g. when using the rudder) doesn't de-activate the autobrake. Try something like: [JoystickCalibration] LeftBrake=-15750,16383/8 RightBrake=-15750,16383/8
DannyEvans Posted Wednesday at 12:44 AM Author Report Posted Wednesday at 12:44 AM 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
John Dowson Posted Wednesday at 11:03 AM Report Posted Wednesday at 11:03 AM 12 hours ago, DannyEvans said: and re-assigned them via FSUIPC before calibrating them this time around, But you assigned them using 'Send to FS as normal axis'. When assigned this way, the calibration is going to work the same way as when the brakes are assigned in P3D, i.e. the brake events are sent to the FS, then picked-up by FSUIPC, calibrated and re-sent. As I previously said, you should try assigning using 'Send direct to FSUIPC calibration'. When assigned this way, the calibration is done before the events are sent to the sim. Sorry if this wasn't clear, but can you please try that. 12 hours ago, DannyEvans said: The list local panel vars setting was also selected right when the test started. There are several lvars related to the brakes/auto-brakes that look interesting: Quote L:VC_Autobrake_SW_VAL = 10.000000 L:VC_Autobrake_Detent_SW_VAL = 0.000000 L:VC_Rudder_Pedal_Brake_Left_VAL = 0.000000 L:VC_Rudder_Pedal_Brake_Right_VAL = 0.000000 L:VC_GEAR_LIGHT_AUTO_BRAKE_DISARM_VAL = 0.000000 L:VC_Brake_Pressure_needle_VAL = 82.500000 L:Animation_Brake_Pressure_Right_VAL = 0.000000 L:Animation_Brake_Pressure_Left_VAL = 0.000000 Maybe worth monitoring some of these. You would need a lua script to do this, which I can provide. I'll try and does this later today. But it is clear that offset 0x2F80 isn't being used, so you can remove logging for that offset if you like. 12 hours ago, DannyEvans said: - Pressed down the pedals manually for full braking, and noticed poor braking action not consistent with maximum braking. I think this is because of the extreme slope you have now combined with the initial null zone. Once you have changed the toe brake assignments to Send direct to FSUIPC calibration, re-calibrate your brakes, giving an appropriate slope - look at the ini/out values as you are doing this, where the out value will be the amount of braking applied ranging from -16384 as no brakes to +16384 as full brakes. I would suggest starting with a slope value of 9 or 10: 15 is pretty excessive and won't give any breaking until the pedals are nearly 25% depressed, and effective breaking a lot later, e.g. 25% breaks when 5/8ths pressed. You can also reduce the initial null zone on the toe brakes to your preference - its the min value of the toe brake calibration. 12 hours ago, DannyEvans said: 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. I won't worry about that if momentary... 12 hours ago, DannyEvans said: Even during the climb-out, the autobrake is not reset from "RTO" to "Off", it has to manually be moved to "OFF". Isn't this always the case? 12 hours ago, DannyEvans said: 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. Does the disarm light come on before you start manually breaking? I can understand why it comes on when you manually start breaking, but not if before. Any manual breaking will/should disarm the autobraking. But, from your earlier logs, autobraking WAS initially working when calibrated in FSUIPC, but only partially and only for the first second or so after touchdown, and then it looked to be disarmed. Anyway, the logging of the lvars should hopefully show what is occurring in more detail. 12 hours ago, DannyEvans said: The only time the autobrakes still work is when the brake calibration is disabled/deleted (with Right/Left Brake Set Axis assigned via FSUIPC). A log of when autobrake is working/calibration disabled would also be useful, with the additional lvar logging. I will provide the lvar logging lua script later and let you know how to use this. John
John Dowson Posted Wednesday at 11:15 AM Report Posted Wednesday at 11:15 AM (edited) To log the lvars, please save the attached script to your FSUIPC6 installation folder: logLvars.lua Then add the following to your FSUIPC6.ini file: Quote [Auto] 1=Lua logLvars Before take-off, please again rotate the autobrake switch through the settings so that I can see the values associated with each setting. You can also now remove the assignment to list the lvars as it is no longer needed. John Later: I have also now added logging for the lvars when the OnGround flag changes, Edited Wednesday at 12:25 PM by John Dowson Script updated to log when OnGround flag changes
DannyEvans Posted Wednesday at 07:35 PM Author Report Posted Wednesday at 07:35 PM 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.
John Dowson Posted Wednesday at 10:04 PM Report Posted Wednesday at 10:04 PM Thats good news! I will check your logs tomorrow, but I would suspect it was the change in assigning the toe brakes using 'direct to FSUIPC calibration', instead of 'send to FS as normal axis'. I cant see how the other axes assigned in P3D could cause this, especially as it was working without the toe brake axes being calibrated in FSUIPC, and you only get the issue when the Toe brakes were calibrated. Some (complex) aircraft dont play well when using FSUIPCs axes calibration facilities when an axis is assigned in P3D or in FSUIPC using 'send to FS as normal axis'. For such axes, you should assign using 'send direct to FSUIPC calibration' and calibrate. This is also the better/preferred/recommended method anyway. The underlying issue is complex but due to conflicting priority levels used to trap and mask events in FSUIPC and the actual aircraft. John
John Dowson Posted Thursday at 09:16 AM Report Posted Thursday at 09:16 AM The log looks good! I think the lesson from this thread is that if you want to calibrate any axis in FSUIPC for the iFly 737, then you also need to have the axis assigned in FSUiPC using the send direct to FSUIPC calibration option, and not the send to FS as normal axis one. I consider this topic closed now (unless you have any more issues). You can remove the logging now, including removing the [Auto] section to start the lvar logging lua script. Regards, John
DannyEvans Posted Thursday at 10:31 PM Author Report Posted Thursday at 10:31 PM 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
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now