A350 - HOT Air valves

  • A minor issue, and not PC specific. The HOT Air valve logic is wired up incorrectly in the A350. Shutting off HOT Valve 2 does nothing, HOT air 1 switch controls Both 1 & 2 valves.

    The error is clear in the system.tmd code


    // hot air
    <[input_switch][HotAir1Switch][]
    <[string8][Message][AirConditioning.HotAir1]>
    <[float64][Value][1.0]>
    <[string8][Events] [ OverheadLowerCenterButtonSoundIn.Trigger ]>
    <[string8][EventsRelease][ OverheadLowerCenterButtonSoundOut.Trigger ]>
    >
    <[output][HotAir1][]
    <[string8][Input][HotAir1Switch.Output]>
    >
    <[logic_invert][HotAir1Off][]
    <[string8][Input][HotAir1Switch.Output]>
    >
    <[output_discrete][HotAir1OffOutput][]
    >
    <[output][HotAirValve1Position][]
    <[string8][Input][HotAir1Switch.Output]>
    >
    <[output][HotAir1Fault][]
    <[string8][Input][0.0]>
    >
    <[output][HotAirValve1Abnormal][]
    <[string8][Input][0.0]>
    >
    <[output][HotAirDuct1Abnormal][]
    <[string8][Input][0.0]>
    >

    <[input_switch][HotAir2Switch][]
    <[string8][Message][AirConditioning.HotAir2]>
    <[float64][Value][1.0]>
    <[string8][Events] [ OverheadLowerCenterButtonSoundIn.Trigger ]>
    <[string8][EventsRelease][ OverheadLowerCenterButtonSoundOut.Trigger ]>
    >
    <[output][HotAir2][]
    <[string8][Input][HotAir2Switch.Output]>
    >
    <[logic_invert][HotAir2Off][]
    <[string8][Input][HotAir2Switch.Output]>
    >
    <[output_discrete][HotAir2OffOutput][]
    >
               <[output][HotAirValve2Position][]
    <[string8][Input][HotAir1Switch.Output]>
    >
    <[output][HotAir2Fault][]
    <[string8][Input][0.0]>
    >
    <[output][HotAirValve2Abnormal][]
    <[string8][Input][0.0]>
    >
    <[output][HotAirDuct2Abnormal][]
    <[string8][Input][0.0]>
    >

  • While I am here, I may as well add this - Autobrake off logic is inhibited at too high a ground speed in the Aerofly version. In reality, it is available down to 5knots - Below is an edited version with the correct ground speed (I think by default it cuts off around 35knots in the sim)


    //Rob - Changed GS speed to 5knots 2.6m/s
    <[logic_greater][GroundSpeedAbove35Kt][]
    <[string8][Input0][InertialReferenceSystem.OutputGroundSpeed]>
    <[string8][Input1][2.6]>
    >

  • Thanks for the report, I've made a change to fix this.

    Regarding the autobrake off sound, I haven't found any real world documentation for the minimum speed so I decided to go with what the "other sim" projects do, which was 35kt. If you have an actual document from Airbus or real world flight training resources that actually define the threshold as 5kt then I can easily change that as well.

  • I orient myself as far as possible to the original manuals. Where does it say in the FCOMs that AutoBrake is used for taxiing?

    Tschüss, Michael (🍎🚁)

    Configurations:

    - MacBook Pro (16", 2024); Chip: Apple M4 Max; actual macOS
    - Controllers: | WinWing: URSA MINOR-Fighter-Joystick R, EFIS-L & FCU & EFIS-R | Thrustmaster TCA AIRBUS EDITION: 2x Quadrant, 2x Quadrant Add-On | Pro-Flight-Trainer: PUMA X | Steelseries: Nimbus+

    - iPad (12,9", 4th Generation, RAM: 6 GB); actual iOS | Steelseries: Nimbus+

  • It's different for the armed and active condition. It would be really bad IRL if the autobrakes would activate at such a low speed speed = during taxiing!

    This has nothing to do with taxiing. Let me clarify, on Qatars A350 fleet, on 'landing rollout.' You will hear 'Auto Brake Off'' if you either push the A/THR disconnect button on the roll-out, or apply manual brake pressure that exceeds the autobrake decel rate. The sound will play even if you disconnect at 15knots. In the Sim you won't hear that sound, it cuts off at 35knots or below.

    I have modified the sim to behave similarly to Qatar's fleet. A few other airlines also have this option.

  • Once again, this has nothing to do with automatic disengemment ot taxiing. On the real aircraft, during rollout, autobrakes disconnect at 10knots if the crew takes no action, this is correctly simulated.


    This is purely about the call-out. Jetpack understood my original post, nothing to worry about


    This topic is about the A350, not the A319/21 logic

  • Ich weiß das ChatGPT nicht immer korrekte Antworten liefert aber dort steht geschrieben das bei Airbus Flugzeugen die Automatischen Bremsen nicht von alleine deaktiviert werden sondern durch die Piloten. Die Piloten betätigen vor dem Verlassen der Landebahn entweder die Fuß/Bremsen leicht oder durch betätigung des Brems/Schalter um die automatische Bremsen zu deaktivieren. Vielleicht gibt es bei Airbus Flugzeugen abweichende Systeme oder Verfahrensweisen.

  • Do you have a link to support your claim? I've never seen any Airbus or Boeing where the autobrakes disengage on their own.

    A link? I am not posting links to FCOMS, here. Download one and read it; it clearly describes the autobrake/BTV logic on rollout with the A350. The devs have modeled the AB logic correctly; none of this is related to my original questions or the devs' answer. Maybe start a new topic?

  • Ich weiß das ChatGPT nicht immer korrekte Antworten liefert aber dort steht geschrieben das bei Airbus Flugzeugen die Automatischen Bremsen nicht von alleine deaktiviert werden sondern durch die Piloten. Die Piloten betätigen vor dem Verlassen der Landebahn entweder die Fuß/Bremsen leicht oder durch betätigung des Brems/Schalter um die automatische Bremsen zu deaktivieren. Vielleicht gibt es bei Airbus Flugzeugen abweichende Systeme oder Verfahrensweisen.

    You may as well use wiki if you are quoting chat GPT. Stick to Airbus or FTCM/FCOM


  • Thanks for the report, I've made a change to fix this.

    Regarding the autobrake off sound, I haven't found any real world documentation for the minimum speed so I decided to go with what the "other sim" projects do, which was 35kt. If you have an actual document from Airbus or real world flight training resources that actually define the threshold as 5kt then I can easily change that as well.

    I did a bit more digging and found the discrepancy, the Aerofly A350 simulates BTW logic a little differently to the real aircraft.


    Real Aircrat - If a high-speed turn off is selected, it will disengage AB at 35 knots. If you select a 90-degree turn off, it will disengage at 10knots.


    So it seems the Aerofly A350 simulates the 10knot disengage no matter what turn off is selected, and only gives the correct call out for a high speed exit. The inibuilds, team corrected the logic on their A350. Again, not a big deal at all ^^

  • I've now made the small change of decreasing the minimum speed for which the "autobrake off" callout is triggered to 5 knots for the A350, A320neo and A380. Not sure if the A320neo would use higher speeds to avoid false warnings during normal operations...

    The autobrake only disengages at 10kt in the BTV mode according to the FCOM. This makes sense because this braking mode is designed to vacate the runway as quickly as possible, so you don't want to stop on the runway.

    The BRK MED or RTO don't disengage automatically, here aircraft would come to a complete stop first, which is desired behavior in that case.

  • I did a bit more digging and found the discrepancy, the Aerofly A350 simulates BTW logic a little differently to the real aircraft.


    Real Aircraft - If a high-speed turn off is selected, it will disengage AB at 35 knots. If you select a 90-degree turn off, it will disengage at 10knots.


    So it seems the Aerofly A350 simulates the 10knot disengage no matter what turn off is selected, and only gives the correct call out for a high speed exit. The inibuilds, team corrected the logic on their A350. Again, not a big deal at all ^^

    There was no mention of a disengagement speed dependency on the selected turn-off type in the FCOM that I have. Makes sense though, perhaps I just have an older version of it. Can you send me a screenshot of that FCOM section please?

  • This is a tricky one as I'm limited as to what I can share, I don't mind taking pictures of the 777 FCOM/FCTM and OPS manuals, but my contact in QR is still flying with them, so I don't want to share anything A350-related that they send me. I'll hopefully be in QR in the next few months, so I can take some vids in the sim.

    They have sent me this regarding the 10 knot disengage. It seems to show the decel behavior ignores the type of exit. They are saying it depends on the software installed for the particular aircraft, which I agree with, it can vary, I've seen it on other fleets.


    But as mentioned, the HOT air was the main issue, as it's clearly a typo in the TMD code.