Jump to content
The simFlight Network Forums

marcoswmd

new Members
  • Posts

    2
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    United Arab Emirates

marcoswmd's Achievements

Newbie

Newbie (1/14)

  • One Month Later Rare
  • Week One Done Rare
  • First Post Rare
  • Conversation Starter Rare

Recent Badges

0

Reputation

  1. Hi John. Thank you for your reply. So, basically, the engine fire handles allow the pilots to activate the fire extinguishing system individually in the engines or APU. When pulled (from "bottom" 0: In to "top" 2: Out, I believe), they basically isolate the Engine/APU from all the systems that are connected to them in order to allow the insertion of the fire extinguishant element into them and optimize its extinguishing effect. After pulling any of the handles, you can discharge the fire extinguishant from the LH Fire Extinguishing Bottle by rotating the handle to the left (3: Turned Left), or from the RH one by rotating it to the right (4: Turned right). The handles are normally locked to prevent inadvertent activation and are automatically unlocked and illuminated when a fire is detected in the related engine/APU. However, there are some cases when pilots need to pull the Fire Handles and isolate the Engines/APU even when a fire is not detected. For those cases, there is a Fire Unlock Switch underneath each Fire Handle that unlocks them, which I was able to configure using the codes described in my first post. #define EVT_FIRE_UNLOCK_SWITCH_ENGINE_1 (THIRD_PARTY_EVENT_ID_MIN + 976) #define EVT_FIRE_UNLOCK_SWITCH_APU (THIRD_PARTY_EVENT_ID_MIN + 977) #define EVT_FIRE_UNLOCK_SWITCH_ENGINE_2 (THIRD_PARTY_EVENT_ID_MIN + 978) Obviously, I was pressing the respective Fire Unlock Switches when trying to configure and pull the Fire Handles without an active fire indication. Maybe with this explanation, you will be able to work something out. I am not a computer expert, but I read the FSUIPC User Manual and managed to understand most of it, and I will try to understand the Rotor Brake control method and Offset concept through the Advanced Manual. Thanks a lot again!
  2. Hello everyone. This is my first post here, so please be patient 😅 I am trying to separately assign them to two switches on my Warthog Hotas Throttle quadrant using 69632 + 697 and 6971 with the appropriate parameters without success on FSUIPC7 (THIRD_PARTY_EVENT_ID_69632+). The terminology in the SDK is a bit confusing compared to the others: EVT_FIRE_HANDLE_ENGINE_1_TOP (THIRD_PARTY_EVENT_ID_MIN + 697) EVT_FIRE_HANDLE_ENGINE_1_BOTTOM (THIRD_PARTY_EVENT_ID_MIN + 6971) I am not sure what "TOP" & "BOTTOM" are referring to, since the parameters include 0: In and 2: Out (which may be "Botton" and "Top" respectively), as copied below: unsigned char FIRE_HandlePos[3]; // 0: In 1: Blocked 2: Out 3: Turned Left 4: Turned right If anyone could configure those handles, please help me out, since they play a fundamental role in executing most of the engine memory items and it is essential to have them assigned to switches. Thanks, guys PS: I was indeed able to configure the Fire Unlock Switches normally using the codes below and they are being pressed while I try to configure the Fire Handles. #define EVT_FIRE_UNLOCK_SWITCH_ENGINE_1 (THIRD_PARTY_EVENT_ID_MIN + 976) #define EVT_FIRE_UNLOCK_SWITCH_APU (THIRD_PARTY_EVENT_ID_MIN + 977) #define EVT_FIRE_UNLOCK_SWITCH_ENGINE_2 (THIRD_PARTY_EVENT_ID_MIN + 978)
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.