Search the Community

Showing results for tags 'fsuipc'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • New Member Forums
    • Welcome New Members!
    • Help Using the AVSIM Forums
    • Help Creating an AVSIM Account and Logging on to AVSIM
  • AVSIM Fixed Based Operations (FBO)!
    • Hangar Chat
    • Virtual Reality (VR) Hardware and Games
    • Letters to the Editorial Staff of AVSIM
    • In Memoriam of Tom Allensworth
    • All About Us
    • Crash To Desktop (CTD) Forum
    • The Bargain Hunter's Shack
    • Classified Ads | Want Ads | Swap Meet
    • AVSIM's Round the World Race Forum
    • Review Feedback
    • The File Library General Forum
    • The Focus on Freeware Forum
    • Flight Sim & Aviation User Stories
    • In Memoriam
  • FlightSimExpo 2018
    • FlightSimExpo 2018 Discussions
  • FlightSimCon 2018
    • FlightSimCon 2018 Discussions
  • Microsoft Flight Simulator Forums
    • MS FSX | FSX-SE Forum
    • The Microsoft Flight Forum
    • The FS2004 (FS9) Forum
    • Flight Simulator Tips and Tricks
    • Shared Cockpits | Multi-Player Forum for FSX | FSX-SE | P3D
    • MS FSX | FSX=SE | P3D Simconnect Forum
    • MS FSX Missions Forum
    • MSFS Aircraft and Panel Design Forum
    • MSFS Scenery Design Forum
    • The Paint Shop - The Aircraft Painter's Forum
    • Mesh Scenery Design
    • TTools for MSFS Forum
    • Add On Developer's Forum
    • DX-10 Discussions, Hints and Help
  • The Prepar3D Forums
    • The Prepar3d Forum
    • Prepar3D Tips, Tricks and How To's
  • The X-Plane Forums
    • X-Plane Tips and Tricks
    • The X-Plane General Discussions Forum
    • The X-Plane Scenery Forum
    • The X-Plane Aircraft & Panel Design Forum
    • X-Plane Addons
    • X-Plane Add-On Developer's Forum
  • The Dovetail Games (DTG) Flight Simulator Forums
    • The Dovetail Flight Sim World
    • The DTG Flight School Forum
  • Screen Shots, Videos & The Gallery
    • The AVSIM Screen Shots Forum
    • Real Aviation Photos
    • Aviation and Flight Sim Video Forum
  • Hardware & Operating Systems Discussions
    • WIN10 OS Forum
    • WIN8 OS Forum
    • The Win7 OS Forum
    • MOBO | RAM | CPU | HDD | SSD | Desktops | Laptops
    • Monitors | Multi-Monitors | Video Cards | Drivers
    • Hardware Controllers | Joysticks | Drivers
    • Networks | WIFI | Routers | Ethernet | DSL | Cable Modems
  • Commercial Support Forums (Official)
    • The PMDG Support Forum
    • FS2Crew Support Forum
    • FSFX Packages Support Forum
    • Mindstar Aviation Support Forum
    • The RealityXP Support Forum
    • The Official DX10 Scenery Fixer Support Forum
    • The Multi-Crew Experience (MCE) Support Forum
    • Virtual Avionics Support Forum
    • Lorby-SI Support Forum
    • Pilot2ATC Users Forum
    • Propair Flight Official Support Forum
    • Icarus Development Forum
    • Remote CDU for Phone / Tablet Official Support Forum
    • Airline2Sim Support Forum
    • SX Airport Design Forum
    • P3D Tweak Assistant (PTA) and RealismShaderPack
    • The simPlugins Support Forum
    • SimSettingsManager Official Support Forum
    • simFDR General Support Forum
    • Blue Sky Star Simulations Support Forum
    • Capt. PERO Support Forum
    • The SkyPilot FSXAssist | P3DAssist Support Forum
    • Flysimware Forum
    • Mid-Atlantic Air Museum Simulations Support
    • Jane Rachel Whittaker - Blue Sock Studios Support Forum
    • FSReborn Series Support Forum
  • Commercial Support Forums (Unofficial)
    • Photo Scenery Support Forum
    • The TerraBuilder Forum
    • The Carenado Support Forum
    • The Alabeo Support Forum
    • The AS16 and ASCA | Active Sky | Active Sky Next | XPAX Support Forum
    • The OpusFSX Forum
    • Fly the MaddogX Unofficial Support Forum
    • The FTX | ORBX Support Forum
    • Lionheart Creations Forum
    • The Majestic Software | Dash 8 Support forum
    • The Commercial Level Simulations (CLS)
    • The AeroSim Support Forum
    • The VOXATC Support Forum
    • The I-Fly Support Forum
    • The MILVIZ Support Forum
    • Radar Contact Support Forum
    • The Level D 767 | Wilco PIC 767 Forum
    • Infinite Flight Forum
    • The Wilco Publishing and FeelThere Support Forum
    • Night Environment | Black Marble | Blue Marble Forum
    • The SIM720 Forum
    • Infinite Scuba Simulation Forum
  • Virtual Airlines News and Discussion
    • VA News and Announcements
    • VA World!
  • Other Civil Aviation Simulators
    • Terminal Reality's FLY Series
    • FLY! Legacy
    • The Rise of Flight General Forum
    • The AeroFly Simulator
    • The Outerra 3D Planetary Engine
    • The Flight Unlimited Series
    • The ProPilot Forum
    • The FlightGear Forum
  • Digital Combat Simulators (DCS) Forums
    • DCS World!
    • The DCS P-51 Mustang Forum
    • DCS A-10C Warthog
    • DCS Black Shark
  • Combat Flightsims
  • General Combat Flightsims
  • Falcon 4 - Allied Forces
  • Flight Schools
    • The Flight School Hangar
    • So You have Solo'd
    • Preflights
    • Weather - Understanding It and Safe Flight
    • Flight Planning
    • Mountain Flying
    • Float Plane Flying
    • Rotory Winged & Helicopter Flying
  • Freeware Support Forums
    • General Freeware Discussions
    • Little Navmap | Little Navconnect | Little Logbook Support Forum
    • The VATSIM | vPilot | FSInn Unofficial Support Forum
    • The Sweet FX Support Forum
    • The TinMouse Support Forum
    • The TileProxy Project Forum
    • LINDA
    • Desk Pilot - Shared Cockpits
    • Mario Noriega Designs
    • SimLauncherX
    • FreeMeshX Global Support Forum
    • FSLaunchPad
    • PSXseeconTraffic for FSX | P3D
    • Terminal Procedures Forum
    • The FS9 Evolution Forum
    • Ready for Pushback Forum
  • International Language Forums
    • Deutsches Forum fuer die Flusi Gemeinde
    • Türkler için Flight Sim forumu
    • Forum de la Communauté francophone de Simulateur de vol
    • Foro de vuelo virtual en español
    • Forum della Comunità Italiana di Flight Sim
    • O fórum em português
  • Other Forums
    • The Unofficial PSS Forum
    • 777 Studios!
    • Russian Flight Simulation and Aviation
    • Drawbridge Designs Forum
    • VictoriaPlus [Canada] Scenery Forum
    • Other Flight Simulation Software
    • Helicopter and Rotor Head Forum
    • Orbiter and Space Sims
    • Home Cockpit Builders
    • Racing Fools Forum
    • AVSIM User Surveys and Opinion Polls Forum
    • The Captain Sim Support Forum

Categories

  • Articles
  • AVSIM News
  • File Library News
  • AVSIM Reviews
    • Hardware
    • Aircraft
    • Scenery
  • Product Announcements & Press Releases
  • What's New @ AVSIM
  • Interviews
  • AVSIM Editorials
  • Guest Editorials
  • Obituaries

Categories

  • New Features
  • Other

Categories

  • AVSIM Publications

Blogs

  • Tom Allensworth's Blog
  • Gaiiden's Scroll
  • Brandon's Box
  • Jess B's X-plane blog thingy
  • Tom_Test's Blog
  • Alpha Floor's Logbook
  • GolfPilot
  • adi518's Blog
  • Chase's Blog
  • The Big Tour
  • Tales of a Wannabe Pilot
  • Farmer Looking Skyward

Forms

There are no results to display.


Found 54 results

  1. Hello, I have FSUIPC configured however at random times the Hat switch (look around the cockpit etc...) moves really slowly? Is there something I am missing in my configuration. At the minute the hat switch is assigned in "Axis Assignment", should it be somewhere else? (I have disabled my joystick in FSX control settings, so that's not the problem) -Open to all suggestions many thanks in advance Ols :)
  2. This problem has really been bothering me for a long time. I have tried basically everything in the book to solve it. When I switch tasks in flight, say to check vpilot or go to chrome, my controller resets and causes fsx not to read it anymore. I tried porting it through FSUIPC and the same problem occured. I've gone through device manager(making sure it doesn't cut off for power saving), and did the same thing in control panel. I have run fsx in compatability mode, still no luck. When I check fsuipc anything to do with the yoke disappears. I've updated the drivers on saitek, and the problem is still there. I'm pretty sure it has something to do with vas because whenever I go into a high end scenery area or I use a heavy payware aircraft it tends to happen more often. It's literally making it impossible to fly because I can't seem to go through a flight without this problem occuring. Sometimes I don't even need to do a task switch to get this to trigger, the yoke itself will just blip on and off and fsx will stop reading the yoke. This also happens with almost all my other joysticks as well. The only way I know about fixing it is by switching between fullscreen and windowed mode a ton of times, but that only works to a point. I am completely at a loss of what to do next. I've heard its a common problem with windows 8, but I still have no idea how to solve it.
  3. FSUIPC 5 with PMDG Aircraft

    Hi , Im looking at setting up my saitek yoke and throttle with fsuipc and the pmdg aircraft. I have managed to get the axis assignments working however I am struggiling with the button assignments. The buttons I want to assign are some of the lights such as landing , taxi and strobe and I also want the autopilot disconnect button as well. If anyone could link me or tell me step by step how to do this please I would be grateful. Thanks , Will
  4. I am experiencing a weird situation with my X55 throttle, FSUIPC5, PD3v4.1 and the PMDG 777. Basically, when I advance the throttle from idle, the speedbrake arms and the reversers deploy, then as I progress the throttle, the reverses go to idle and the normal engine thrust kicks in. Is there some setting I am missing that defines a region of the throttle as 'reversers'? If so, where is it located? I have controllers disabled in P3D and run everything through FSUIPC. I don't see this with other aircraft (non-PMDG). Has anyone else experienced this? If so, were you able to fix it?
  5. Hi Guys I would like to be able to "activate" by R/T and I/C buttons on the audio control panel of my Opencockpits pedestal, so that I can assign key presses in FSUIPC to activate PTT's in Teamspeak and vPilot. I am using Open Cockpits modules throughout except for the MCP and EFIS panels, which are from cpFlight. Below is my pedestal SIOC script. I have added a few lines right at the end of the script, under "Trial code for PTT's", which is my attempt at activating the captain's R/T button on the ACP. I have used the code posted by others on various forums as a starting point. Trouble is, I am not a programmer, and I'm really just working blind with this! Here's my setup. Visual-1 PC: is "flying" PC with Prosim server on it. I have also hooked up the pedestal to this PC using SIOC. Other PC's: 4 in total, all hooked up with FSUIPC / WideFS, and various modules using SIOC. Ideally, I would like the code to work no matter which PC I connect the pedestal to (using WideFS), but even if I can get it working just when connected to Visual-1 PC, then I'll be very happy indeed! So, if any SIOC / FSUIPC guru can offer the correct lines of code for me to insert into my script, I would be eternally grateful! // ***************************************************************************** // * Config_SIOC ver 5.0 - By Manolo V�lez - www.opencockpits.com // ***************************************************************************** // * FileName : pedestalB737_PM.txt, Ver.1.0 // * PMagenta & FSX Pedestal script // * Date : 22/06/2014 var 0,value 0 { &ent_com1 = 118 &dec_com1 = 0 &act_com1 = 118000 &enc_com1 = 1 &ent_com2 = 118 &dec_com2 = 0 &act_com2 = 118000 &enc_com2 = 1 &ent_nav1 = 108 &dec_nav1 = 0 &act_nav1 = 10800 &enc_nav1 = 1 &ent_nav2 = 108 &dec_nav2 = 0 &act_nav2 = 10800 &enc_nav2 = 1 &ent_adf1 = 10 &dec_adf1 = 0 &act_adf1 = 1000 &enc_adf1 = 1 &danta_adf1 = 1 &dants_adf1 = 1 &dadfa_adf1 = 0 &dadfs_adf1 = 0 &ent_adf2 = 10 &dec_adf2 = 0 &act_adf2 = 1000 &enc_adf2 = 1 &danta_adf2 = 1 &dants_adf2 = 1 &dadfa_adf2 = 0 &dadfs_adf2 = 0 // ATC &timerup = 0 &D_ACTIVE = 1200 &lastst = 0 &DIG_POS_STATUS = 5 &DIS_ATC = 1 &DIS_1 = 1 &DIS_2 = 0 &timeratc = 0 &timeratc = TIMER 1,0,35 } // ************************************************************ // ******************************** COM1 ********************** // ************************************************************ var 2300, name enc_com1_pro, STATIC { IF &enc_com1_pro = -1 { &enc_com1 = 0 } ELSE { &enc_com1 = 1 } } var 2308, name enc_com2_pro, STATIC { IF &enc_com2_pro = -1 { &enc_com2 = 0 } ELSE { &enc_com2 = 1 } } var 2316, name enc_nav1_pro, STATIC { IF &enc_nav1_pro = -1 { &enc_nav1 = 0 } ELSE { &enc_nav1 = 1 } } var 2320, name enc_nav2_PRO, STATIC { IF &enc_nav2_pro = -1 { &enc_nav2 = 0 } ELSE { &enc_nav2 = 1 } } var 2324, name enc_adf1_PRO, STATIC { IF &enc_adf1_PRO = -1 { &enc_adf1 = 0 } ELSE { &enc_adf1 = 1 } } var 2336, name enc_adf2_PRO, STATIC { IF &enc_adf2_PRO = -1 { &enc_adf2 = 0 } ELSE { &enc_adf2 = 1 } } var 2, name enc_com1 { if &enc_com1 = 1 { &io_pt_com1 = 1 &io_pt2_com1 = 1 call &sub_d_com1 &id2_com1 = &act_com1 } else { &io_pt_com1 = 0 &io_pt2_com1 = 0 &id_com1 = -999999 &id2_com1 = -999999 } } var 4, name ent_com1 var 6, name dec_com1 var 8, name ie_dec_com1, link IOCARD_ENCODER, input 0, type 2, aceleration 1, device 20 { if &enc_com1 = 1 { l0 = &ie_dec_com1 * 5 l1 = &dec_com1 + l0 if l1 < 0 { l1 = 975 } if l1 > 975 { l1 = 0 } &dec_com1 = l1 call &sub_d_com1 } } var 10, name ie_ent_com1, link IOCARD_ENCODER, input 2, type 2, aceleration 1, device 20 { if &enc_com1 = 1 { l0 = &ie_ent_com1 * -1 &ent_com1 = rotate 118,135,l0 call &sub_d_com1 } } var 12, name id_com1,link IOCARD_DISPLAY, digit 6, numbers 6, device 20 var 14, name sub_d_com1, link SUBRUTINE { l0 = &ent_com1 * 1000 &id_com1 = l0 + &dec_com1 } var 16, name io_pt_com1, link IOCARD_OUT, output 11, device 20 var 18, name ii_sw_com1, link IOCARD_SW, input 5, device 20 { if &ii_sw_com1 = 1 { if &enc_com1 = 1 { l0 = &ent_com1 * 1000 l0 = l0 + &dec_com1 l1 = div &act_com1 1000 l2 = mod &act_com1 1000 &act_com1 = l0 &ent_com1 = l1 &dec_com1 = l2 call &sub_d_com1 &id2_com1 = &act_com1 } } } var 20, name act_com1 var 22, name id2_com1,link IOCARD_DISPLAY, digit 0, numbers 6, device 20 { if &id2_com1 > 0 { &xp_com1 = div &id2_com1 10 } } var 24, name io_pt2_com1, link IOCARD_OUT, output 11, device 20 var 26, name xp_com1, value 11800 { l0 = &xp_com1 - 10000 &fcom1 = tobcd l0 } // ************************************************************ // ******************************** COM2 ********************** // ************************************************************ var 102, name enc_com2 { if &enc_com2 = 1 { &io_pt_com2 = 1 &io_pt2_com2 = 1 call &sub_d_com2 &id2_com2 = &act_com2 } else { &io_pt_com2 = 0 &io_pt2_com2 = 0 &id_com2 = -999999 &id2_com2 = -999999 } } var 104, name ent_com2 var 106, name dec_com2 var 108, name ie_dec_com2, link IOCARD_ENCODER, input 72, type 2, aceleration 1, device 20 { if &enc_com2 = 1 { l0 = &ie_dec_com2 * 5 l1 = &dec_com2 + l0 if l1 < 0 { l1 = 975 } if l1 > 975 { l1 = 0 } &dec_com2 = l1 call &sub_d_com2 } } var 110, name ie_ent_com2, link IOCARD_ENCODER, input 74, type 2, aceleration 1, device 20 { if &enc_com2 = 1 { l0 = &ie_ent_com2 * -1 &ent_com2 = rotate 118,135,l0 call &sub_d_com2 } } var 112, name id_com2,link IOCARD_DISPLAY, digit 70, numbers 6, device 20 var 114, name sub_d_com2, link SUBRUTINE { l0 = &ent_com2 * 1000 &id_com2 = l0 + &dec_com2 } var 116, name io_pt_com2, link IOCARD_OUT, output 75, device 20 var 118, name ii_sw_com2, link IOCARD_SW, input 77, device 20 { if &ii_sw_com2 = 1 { if &enc_com2 = 1 { l0 = &ent_com2 * 1000 l0 = l0 + &dec_com2 l1 = div &act_com2 1000 l2 = mod &act_com2 1000 &act_com2 = l0 &ent_com2 = l1 &dec_com2 = l2 call &sub_d_com2 &id2_com2 = &act_com2 } } } var 120, name act_com2 var 122, name id2_com2,link IOCARD_DISPLAY, digit 64, numbers 6, device 20 { if &id2_com2 > 0 { &xp_com2 = div &id2_com2 10 } } var 124, name io_pt2_com2, link IOCARD_OUT, output 75, device 20 var 126, name xp_com2, value 11800 { l0 = &xp_com2 - 10000 &fcom2 = tobcd l0 } // ********************************************* // ******************* NAV1 ******************* // ********************************************* var 54, name enc_nav1 { if &enc_nav1 = 1 { &io_pt_nav1 = 1 &io_pt2_nav1 = 1 call &sub_d_nav1 &id2_nav1 = &act_nav1 } else { &io_pt_nav1 = 0 &io_pt2_nav1 = 0 &id_nav1 = -999999 &id2_nav1 = -999999 } } var 56, name ent_nav1 var 58, name dec_nav1 var 60, name ie_dec_nav1, link IOCARD_ENCODER, input 9, type 2, aceleration 1, device 20 { if &enc_nav1 = 1 { l0 = &ie_dec_nav1 * 25 l1 = &dec_nav1 + l0 if l1 < 0 { l1 = 975 } if l1 > 975 { l1 = 0 } &dec_nav1 = l1 call &sub_d_nav1 } } var 62, name ie_ent_nav1, link IOCARD_ENCODER, input 11, type 2, aceleration 1, device 20 { if &enc_nav1 = 1 { l0 = &ie_ent_nav1 * -1 &ent_nav1 = rotate 108,117,l0 call &sub_d_nav1 } } var 64, name id_nav1,link IOCARD_DISPLAY, digit 21, numbers 5, device 20 var 66, name sub_d_nav1, link SUBRUTINE { l0 = &ent_nav1 * 100 l1 = div &dec_nav1 10 &id_nav1 = l0 + l1 } var 68, name io_pt_nav1, link IOCARD_OUT, output 12, device 20 var 70, name ii_sw_nav1, link IOCARD_SW, input 14, device 20 { if &ii_sw_nav1 = 1 { if &enc_nav1 = 1 { l0 = &ent_nav1 * 100 l1 = div &dec_nav1 10 l0 = l0 + l1 l1 = div &act_nav1 100 l2 = mod &act_nav1 100 &act_nav1 = l0 &ent_nav1 = l1 l0 = mod l2 10 l2 = l2 * 10 if l0 > 0 { l2 = l2 + 5 } &dec_nav1 = l2 call &sub_d_nav1 &id2_nav1 = &act_nav1 } } } var 72, name act_nav1 var 74, name id2_nav1,link IOCARD_DISPLAY, digit 16, numbers 5, device 20 { if &id2_nav1 > 0 { &xp_nav1 = &id2_nav1 } } var 76, name io_pt2_nav1, link IOCARD_OUT, output 12, device 20 var 78, name xp_nav1, value 10800 { l0 = &xp_nav1 - 10000 &fnav1 = tobcd l0 } // ********************************************* // ******************* NAV2 ******************* // ********************************************* var 154, name enc_nav2 { if &enc_nav2 = 1 { &io_pt_nav2 = 1 &io_pt2_nav2 = 1 call &sub_d_nav2 &id2_nav2 = &act_nav2 } else { &io_pt_nav2 = 0 &io_pt2_nav2 = 0 &id_nav2 = -999999 &id2_nav2 = -999999 } } var 156, name ent_nav2 var 158, name dec_nav2 var 160, name ie_dec_nav2, link IOCARD_ENCODER, input 81, type 2, aceleration 1, device 20 { if &enc_nav2 = 1 { l0 = &ie_dec_nav2 * 25 l1 = &dec_nav2 + l0 if l1 < 0 { l1 = 975 } if l1 > 975 { l1 = 0 } &dec_nav2 = l1 call &sub_d_nav2 } } var 162, name ie_ent_nav2, link IOCARD_ENCODER, input 83, type 2, aceleration 1, device 20 { if &enc_nav2 = 1 { l0 = &ie_ent_nav2 * -1 &ent_nav2 = rotate 108,117,l0 call &sub_d_nav2 } } var 164, name id_nav2,link IOCARD_DISPLAY, digit 85, numbers 5, device 20 var 166, name sub_d_nav2, link SUBRUTINE { l0 = &ent_nav2 * 100 l1 = div &dec_nav2 10 &id_nav2 = l0 + l1 } var 168, name io_pt_nav2, link IOCARD_OUT, output 76, device 20 var 170, name ii_sw_nav2, link IOCARD_SW, input 86, device 20 { if &ii_sw_nav2 = 1 { if &enc_nav2 = 1 { l0 = &ent_nav2 * 100 l1 = div &dec_nav2 10 l0 = l0 + l1 l1 = div &act_nav2 100 l2 = mod &act_nav2 100 &act_nav2 = l0 &ent_nav2 = l1 l0 = mod l2 10 l2 = l2 * 10 if l0 > 0 { l2 = l2 + 5 } &dec_nav2 = l2 call &sub_d_nav2 &id2_nav2 = &act_nav2 } } } var 172, name act_nav2 var 174, name id2_nav2,link IOCARD_DISPLAY, digit 80, numbers 5, device 20 { if &id2_nav2 > 0 { &xp_nav2 = &id2_nav2 } } var 176, name io_pt2_nav2, link IOCARD_OUT, output 76, device 20 var 178, name xp_nav2, value 10800 { l0 = &xp_nav2 - 10000 &fnav2 = tobcd l0 } // ********************************************* // ******************* ADF1 ******************* // ********************************************* var 218, name enc_adf1 { if &enc_adf1 = 1 { &io_pt_adf1 = 1 call &sub_d_adf1 &id2_adf1 = &act_adf1 &o_adf1 = 1 if &ant_adf1 = 1 { &danta_adf1 = 0 &dants_adf1 = 0 &dadfa_adf1 = 1 &dadfs_adf1 = 1 } else { &danta_adf1 = 1 &dants_adf1 = 1 &dadfa_adf1 = 0 &dadfs_adf1 = 0 } } else { &io_pt_adf1 = 0 &id_adf1 = -999999 &id2_adf1 = -999999 &o_adf1 = 0 &danta_adf1 = 1 &dants_adf1 = 1 &dadfa_adf1 = 1 &dadfs_adf1 = 1 } } var 220, name ent_adf1 var 222, name dec_adf1 var 224, name ie_dec_adf1, link IOCARD_ENCODER, input 18, type 2, aceleration 5, device 20 { if &enc_adf1 = 1 { l0 = &ie_dec_adf1 * 1 l1 = &dec_adf1 + l0 if l1 < 0 { l1 = 99 } if l1 > 99 { l1 = 0 } &dec_adf1 = l1 call &sub_d_adf1 } } var 226, name ie_ent_adf1, link IOCARD_ENCODER, input 20, type 2, aceleration 4, device 20 { if &enc_adf1 = 1 { l0 = &ie_ent_adf1 * -1 l1 = &ent_adf1 + l0 if l1 < 10 { l1 = 179 } if l1 > 179 { l1 = 10 } &ent_adf1 = l1 call &sub_d_adf1 } } var 228, name id_adf1,link IOCARD_DISPLAY, digit 37, numbers 5, device 20 var 230, name sub_d_adf1, link SUBRUTINE { l0 = &ent_adf1 * 100 l1 = &dec_adf1 &id_adf1 = l0 + l1 } var 234, name ii_sw_adf1, link IOCARD_SW, input 23,device 20 { if &ii_sw_adf1 = 1 { if &enc_adf1 = 1 { l0 = &ent_adf1 * 100 l1 = &dec_adf1 l0 = l0 + l1 l1 = div &act_adf1 100 l2 = mod &act_adf1 100 &act_adf1 = l0 &ent_adf1 = l1 &dec_adf1 = l2 call &sub_d_adf1 &id2_adf1 = &act_adf1 } } } var 236, name act_adf1 var 238, name id2_adf1,link IOCARD_DISPLAY, digit 32, numbers 5, device 20 { if &id2_adf1 > 0 { &xp_adf1 = &id2_adf1 } } var 240, name io_pt_adf1, link IOCARD_OUT, output 13, device 20 Var 242, name o_adf1 var 254, name xp_adf1 { l0 = div &xp_adf1 10000 l1 = l0 * 10000 l2 = &xp_adf1 - l1 l2 = div l2 10 &fadf1A = tobcd l2 l0 = l0 * 100 l1 = div &xp_adf1 10 l1 = l1 * 10 l2 = &xp_adf1 - l1 l2 = l2 + l0 &fadf1B = tobcd l2 } var 256, name ant_adf1, link IOCARD_SW, input 22, device 20 { if &enc_adf1 = 1 { if &ant_adf1 = 1 { &danta_adf1 = 0 &dants_adf1 = 0 &dadfa_adf1 = 1 &dadfs_adf1 = 1 } else { &danta_adf1 = 1 &dants_adf1 = 1 &dadfa_adf1 = 0 &dadfs_adf1 = 0 } } } var 258, name danta_adf1, link IOCARD_DISPLAY, digit 43, numbers 1, device 20 var 260, name dants_adf1, link IOCARD_DISPLAY, digit 44, numbers 1, device 20 var 262, name dadfa_adf1, link IOCARD_DISPLAY, digit 42, numbers 1, device 20 var 264, name dadfs_adf1, link IOCARD_DISPLAY, digit 45, numbers 1, device 20 Var 266, name S_ADF1TONE, Link IOCARD_SW, Input 24, device 20 { &toneadf1 = CHANGEBITN 0 &S_ADF1TONE } // ********************************************* // ******************* ADF2 ******************* // ********************************************* var 318, name enc_adf2 { if &enc_adf2 = 1 { &io_pt_adf2 = 1 call &sub_d_adf2 &id2_adf2 = &act_adf2 &o_adf2 = 1 if &ant_adf2 = 1 { &danta_adf2 = 0 &dants_adf2 = 0 &dadfa_adf2 = 1 &dadfs_adf2 = 1 } else { &danta_adf2 = 1 &dants_adf2 = 1 &dadfa_adf2 = 0 &dadfs_adf2 = 0 } } else { &io_pt_adf2 = 0 &id_adf2 = -999999 &id2_adf2 = -999999 &o_adf2 = 0 &danta_adf2 = 1 &dants_adf2 = 1 &dadfa_adf2 = 1 &dadfs_adf2 = 1 } } var 320, name ent_adf2 var 322, name dec_adf2 var 324, name ie_dec_adf2, link IOCARD_ENCODER, input 90, type 2, aceleration 5, device 20 { if &enc_adf2 = 1 { l0 = &ie_dec_adf2 * 1 l1 = &dec_adf2 + l0 if l1 < 0 { l1 = 99 } if l1 > 99 { l1 = 0 } &dec_adf2 = l1 call &sub_d_adf2 } } var 326, name ie_ent_adf2, link IOCARD_ENCODER, input 92, type 2, aceleration 4, device 20 { if &enc_adf2 = 1 { l0 = &ie_ent_adf2 * -1 l1 = &ent_adf2 + l0 if l1 < 10 { l1 = 179 } if l1 > 179 { l1 = 10 } &ent_adf2 = l1 call &sub_d_adf2 } } var 328, name id_adf2,link IOCARD_DISPLAY, digit 101, numbers 5, device 20 var 330, name sub_d_adf2, link SUBRUTINE { l0 = &ent_adf2 * 100 l1 = &dec_adf2 &id_adf2 = l0 + l1 } var 334, name ii_sw_adf2, link IOCARD_SW, input 95,device 20 { if &ii_sw_adf2 = 1 { if &enc_adf2 = 1 { l0 = &ent_adf2 * 100 l1 = &dec_adf2 l0 = l0 + l1 l1 = div &act_adf2 100 l2 = mod &act_adf2 100 &act_adf2 = l0 &ent_adf2 = l1 &dec_adf2 = l2 call &sub_d_adf2 &id2_adf2 = &act_adf2 } } } var 336, name act_adf2 var 338, name id2_adf2,link IOCARD_DISPLAY, digit 96, numbers 5, device 20 { if &id2_adf2 > 0 { &xp_adf2 = &id2_adf2 } } var 340, name io_pt_adf2, link IOCARD_OUT, output 77, device 20 Var 342, name o_adf2 var 354, name xp_adf2 { l0 = div &xp_adf2 10000 l1 = l0 * 10000 l2 = &xp_adf2 - l1 l2 = div l2 10 &fadf2A = tobcd l2 l0 = l0 * 100 l1 = div &xp_adf2 10 l1 = l1 * 10 l2 = &xp_adf2 - l1 l2 = l2 + l0 &fadf2B = tobcd l2 } var 356, name ant_adf2, link IOCARD_SW, input 94, device 20 { if &enc_adf2 = 1 { if &ant_adf2 = 1 { &danta_adf2 = 0 &dants_adf2 = 0 &dadfa_adf2 = 1 &dadfs_adf2 = 1 } else { &danta_adf2 = 1 &dants_adf2 = 1 &dadfa_adf2 = 0 &dadfs_adf2 = 0 } } } var 358, name danta_adf2, link IOCARD_DISPLAY, digit 107, numbers 1, device 20 var 360, name dants_adf2, link IOCARD_DISPLAY, digit 108, numbers 1, device 20 var 362, name dadfa_adf2, link IOCARD_DISPLAY, digit 106, numbers 1, device 20 var 364, name dadfs_adf2, link IOCARD_DISPLAY, digit 109, numbers 1, device 20 Var 366, name S_ADF2TONE, Link IOCARD_SW, Input 96, device 20 { &toneadf2 = CHANGEBITN 0 &S_ADF2TONE } // ********************************************* // ******************* ATC ******************** // ********************************************* Var 400, name DIG_POS_STATUS { &finatc = 0 IF &DIG_POS_STATUS = 5 { &timerup = 0 CALL &DIGITS2_SUB } else { &timerup = 1 CALL &DIGITS2_SUB } } Var 402, name DIG_1_SUB, Value 0 { CALL &DIGITS_SUB } Var 404, name DIG_2_SUB, Value 0 { CALL &DIGITS_SUB } Var 406, name DIG_3_SUB, Value 2 { CALL &DIGITS_SUB } Var 408, name DIG_4_SUB, Value 1 { CALL &DIGITS_SUB } Var 410, name D_ACTIVE, Link IOCARD_DISPLAY, device 20, Digit 90, Numbers 4 Var 412, name D_FAIL, Link IOCARD_DISPLAY, device 20, Digit 94, Numbers 1 Var 416, name DIS_ATC, Link IOCARD_OUT, device 20, Output 99 Var 418, name DIS_1, Link IOCARD_OUT, device 20, Output 100 Var 420, name DIS_2, Link IOCARD_OUT, device 20, Output 101 Var 422, name LED_FAIL, Link IOCARD_OUT, device 20, Output 98 Var 424, name E_LEFT, Link IOCARD_ENCODER, device 20, Input 113, Aceleration 0, Type 2 { IF &enc_atc = 1 { L0 = &E_LEFT * 1 &DIG_POS_STATUS = ROTATE 1 ,5 ,L0 } } Var 426, name E_RIGHT, Link IOCARD_ENCODER, device 20, Input 115, Aceleration 1, Type 2 { IF &enc_atc = 1 { IF &DIG_POS_STATUS = 1 { L0 = &E_RIGHT * -1 &DIG_1_SUB = ROTATE 0 ,7 ,L0 } IF &DIG_POS_STATUS = 2 { L0 = &E_RIGHT * -1 &DIG_2_SUB = ROTATE 0 ,7 ,L0 } IF &DIG_POS_STATUS = 3 { L0 = &E_RIGHT * -1 &DIG_3_SUB = ROTATE 0 ,7 ,L0 } IF &DIG_POS_STATUS = 4 { L0 = &E_RIGHT * -1 &DIG_4_SUB = ROTATE 0 ,7 ,L0 } } } Var 428, name I_IDENT, Link IOCARD_SW, device 20, Input 78 { IF &enc_atc = 1 { IF &I_IDENT = 1 { &IVAP_SB_IDENT = 1 } } } Var 430, name I_XPNDR, Link IOCARD_SW, device 20, Input 79 { IF &enc_atc = 1 { IF &STANDBY = 0 { CALL &check_xp } } } var 431, name check_xp, link subrutine { IF &I_XPNDR = 1 { &DIS_1 = 0 &DIS_2 = 1 } ELSE { &DIS_1 = 1 &DIS_2 = 0 } } Var 432, name STANDBY, Link IOCARD_SW, device 20, Input 139 { IF &enc_atc = 1 { IF &STANDBY = 1 { &IVAP_SB_MODE = 1 &DIS_1 = 0 &DIS_2 = 0 &DIS_ATC = 0 } ELSE { CALL &check_xp } } } Var 434, name I_R_ALT, Link IOCARD_SW, device 20, Input 140 Var 436, name I_R_XPN, Link IOCARD_SW, device 20, Input 141 { IF &enc_atc = 1 { IF &I_R_XPN = 1 { &IVAP_SB_MODE = 0 } } } Var 438, name I_R_TAO, Link IOCARD_SW, device 20, Input 142 { IF &enc_atc = 1 { IF &I_R_TAO = 1 { &TCAS_MAGENTA = 51 } } } Var 440, name I_R_TAR, Link IOCARD_SW, device 20, Input 143 { IF &enc_atc = 1 { IF &I_R_TAR = 1 { &TCAS_MAGENTA = 51 } } } Var 2348, name enc_atc_prosim, static { IF &enc_atc_prosim = -1 { &enc_atc = 0 } ELSE { &enc_atc = 1 } } Var 2350, name enc_atc { IF &enc_atc = 0 { &d_active = -999999 &d_fail = -999999 &DIG_POS_STATUS = 5 &DIS_1 = 0 &DIS_2 = 0 &DIS_ATC = 0 } ELSE { &DIS_ATC = 1 call &DIGITS_SUB &DIG_POS_STATUS = 5 IF &STANDBY <> 1 { call &check_xp } IF &XPDER_FAIL = 1 { &D_FAIL = -999997 &LED_FAIL = 1 } ELSE { &D_FAIL = -999999 &LED_FAIL = 0 } } } Var 442, name DIGITS_SUB, Link SUBRUTINE { L0 = &DIG_4_SUB * 1000 L1 = &DIG_3_SUB * 100 L0 = L0 + L1 L1 = &DIG_2_SUB * 10 L0 = L0 + L1 L0 = L0 + &DIG_1_SUB &D_ACTIVE = L0 &FS_XPDER_ID = TOBCD &D_ACTIVE } // ****************** TIMER **************** // ***************************************** var 443, name lockcount, value 0 var 444, name timeratc, link subrutine { if &timerup = 0 { &lastst = 0 } else { IF &DIG_POS_STATUS = 1 { IF &lastst = 0 { &D_ATC1 = -999999 } ELSE { &D_ATC1 = &DIG_1_SUB } } IF &DIG_POS_STATUS = 2 { IF &lastst = 0 { &D_ATC2 = -999999 } ELSE { &D_ATC2 = &DIG_2_SUB } } IF &DIG_POS_STATUS = 3 { IF &lastst = 0 { &D_ATC3 = -999999 } ELSE { &D_ATC3 = &DIG_3_SUB } } IF &DIG_POS_STATUS = 4 { IF &lastst = 0 { &D_ATC4 = -999999 } ELSE { &D_ATC4 = &DIG_4_SUB } } IF &lastst = 0 { &lastst = 1 } ELSE { &lastst = 0 } IF &finatc = 50 { &DIG_POS_STATUS = 5 } ELSE { &finatc = &finatc + 1 } } // DOOR IF &lockcount > 0 { &lockcount = &lockcount - 1 &STBAUTOL = CHANGEBITN 0 &STBAUTOL } ELSE { &STBAUTOL = 0 } // AILTRIM } var 446, name lastst var 448, name timerup Var 450, name D_ATC1, Link IOCARD_DISPLAY, device 20, Digit 90, Numbers 1 Var 452, name D_ATC2, Link IOCARD_DISPLAY, device 20, Digit 91, Numbers 1 Var 454, name D_ATC3, Link IOCARD_DISPLAY, device 20, Digit 92, Numbers 1 Var 456, name D_ATC4, Link IOCARD_DISPLAY, device 20, Digit 93, Numbers 1 var 458, name DIGITS2_SUB, link subrutine { &D_ATC1 = &DIG_1_SUB &D_ATC2 = &DIG_2_SUB &D_ATC3 = &DIG_3_SUB &D_ATC4 = &DIG_4_SUB } var 460, name finatc, value 0 // //////////////////////////////// // STABTRIM IDC // //////////////////////////////// // OUTPUTS-LEDS Var 2456, name STBLCKL, Link IOCARD_OUT, DEVICE 20, Output 96 // STAB TRIM LOCK FAIL INDICATOR Var 2458, name STBAUTOL, Link IOCARD_OUT, DEVICE 20, Output 97 // STAB TRIM AUTO-UNLOCK INDICATOR // SWITCHES-INPUTS Var 2670, name S_STBOVRD, Link IOCARD_SW, DEVICE 20, Input 135 // STAB TRIM OVERRIDE-NORM SWITCH Var 2672, name R_STBDUNLK, Link IOCARD_SW, DEVICE 20, Input 136 // STAB TRIM DOOR UNLOCK ROTARY SWITCH Var 2674, name R_STBDAUTO, Link IOCARD_SW, DEVICE 20, Input 137 // STAB TRIM DOOR AUTO ROTARY SWITCH Var 2676, name R_STBDDENY, Link IOCARD_SW, DEVICE 20, Input 138 // STAB TRIM DOOR DENY ROTARY SWITCH // //////////////////////////////// // END STABTRIM IDC // //////////////////////////////// // ///////////////////////////////////////////// // END AILERONS TRIM IDC // ///////////////////////////////////////////// // ****************************************************** // ******************* RUDDER TRIM ******************** // ****************************************************** Var 964, name S_RDAILUL, Link IOCARD_SW, device 20, Input 63 // RUDDER TRIM AILERON UP LEFT SWITCH Var 966, name S_RDAILUR, Link IOCARD_SW, device 20, Input 64 // RUDDER TRIM AILERON UP RIGHT SWITCH Var 968, name S_RDAILDL, Link IOCARD_SW, device 20, Input 65 // RUDDER TRIM AILERON DOWN LEFT SWITCH Var 970, name S_RDAILDR, Link IOCARD_SW, device 20, Input 66 // RUDDER TRIM AILERON DOWN RIGHT SWITCH Var 978, name E_RUDDER, Link IOCARD_ENCODER, device 20, Input 67, Aceleration 1, Type 2 // RUDDER TRIM ENCODER { l0 = &E_RUDDER * 500 &ruddert_o = LIMIT -16000, 16000, l0 } Var 980, name grudtrim, link USB_SERVOS, device 21, Output 1, PosL 0, PosC 511, PosR 1023 // RUDDER TRIM INDICATOR Var 982, name leftservo, value 623 // ***** Change de value for your left extreme value for 15 in the indicator **** var 984, name centerservo, value 510 // ***** change de value for your center value in the indicator **** Var 986, name rightservo, value 387 // ***** Change de value for your right extreme value for 15 in the indicator **** var 988, name runindicator, link subrutine { if &ruddert_o = 0 { l0 = &centerservo } else { if &ruddert_o < 0 // LEFT { l0 = &centerservo - &leftservo } else // RIGHT { l0 = &rightservo - &centerservo } l0 = l0 * &ruddert_o l0 = l0 / 16384 l0 = l0 + &centerservo } &grudtrim = l0 } // ///////////////////////////////////////////// // END RUDDER TRIM IDC // ///////////////////////////////////////////// // ///////////////////////////////////////////// // RADAR PEDESTAL IDC // ///////////////////////////////////////////// // RADAR Var 2686, name R_RADTST, STATIC, Link IOCARD_SW, DEVICE 20, Input 69 // RADAR TEST ROTARY SWITCH { IF &R_RADTST = 0 { IF &R_RADWX = 0 { IF &R_RADTURB = 0 { &R_RADMAP = 1 } } } ELSE { &R_RADMAP = 0 } } Var 2688, name R_RADWX, STATIC,Link IOCARD_SW, DEVICE 20, Input 70 // RADAR WX ROTARY SWITCH { IF &R_RADWX = 0 { IF &R_RADTST = 0 { IF &R_RADTURB = 0 { &R_RADMAP = 1 } } } ELSE { &R_RADMAP = 0 } } Var 2690, name R_RADTURB, STATIC,Link IOCARD_SW, DEVICE 20, Input 71 // RADAR TURB ROTARY SWITCH { IF &R_RADTURB = 0 { IF &R_RADWX = 0 { IF &R_RADTST = 0 { &R_RADMAP = 1 } } } ELSE { &R_RADMAP = 0 } } Var 2692, name R_RADMAP, STATIC // RADAR MAP ROTARY SWITCH // ANALOG Var 2698, name A_RADGAIN, Link IOCARD_ANALOGIC, DEVICE 20, Input 2, PosL 0, PosC 127, PosR 255 // RADAR GAIN POTENTIOMETER Var 2700, name A_RADGAINI, STATIC Var 2701, name A_RADTILT, Link IOCARD_ANALOGIC, DEVICE 20, Input 3, PosL 0, PosC 127, PosR 255 // RADAR TILT POTENTIOMETER { L0 = &A_RADTILT * 2 L0 = L0 - 255 &A_RADTILTI = L0 } Var 2702, name A_RADTILTI, STATIC // ///////////////////////////////////////////// // END RADAR PEDESTAL IDC // ///////////////////////////////////////////// // ///////////////////////////////////////////// // FIRE ENGINES IDC // ///////////////////////////////////////////// // OUTPUTS-LEDS Var 2410, name ENG1_OVHL, STATIC, Link IOCARD_OUT, DEVICE 20, Output 23 // ENGINE 1 OVERHEAT, declare variable in ProSim Indicators Var 2412, name APUBOTDISL, STATIC, Link IOCARD_OUT, DEVICE 20, Output 24 // APU BOTTLE DISCHARGE, declare variable in ProSim Indicators Var 2414, name APUDETINOPL, STATIC, Link IOCARD_OUT, DEVICE 20, Output 25 // APU DET INOPERATIVE, declare variable in ProSim Indicators Var 2416, name FIREFAULTL, STATIC, Link IOCARD_OUT, DEVICE 20, Output 26 // FIRE ENGINES FAULT, declare variable in ProSim Indicators Var 2418, name FIREWHELLL, STATIC, Link IOCARD_OUT, DEVICE 20, Output 27 // FIRE WHELL WELL, declare variable in ProSim Indicators Var 2420, name ENG2_OVHL, STATIC, Link IOCARD_OUT, DEVICE 20, Output 28 // ENGINE 2 OVERHEAT, declare variable in ProSim Indicators Var 2422, name LBOTDISL, STATIC, Link IOCARD_OUT, DEVICE 20, Output 29 // ENGINE 1 BOTTLE DISCHARGE, declare variable in ProSim Indicators Var 2424, name RBOTDISL, STATIC, Link IOCARD_OUT, DEVICE 20, Output 30 // ENGINE 2 BOTTLE DISCHARGE, declare variable in ProSim Indicators Var 2426, name FIRE1L, STATIC, Link IOCARD_OUT, DEVICE 20, Output 31 // ENGINE 1 FIRE HANDLE LIGHT, declare variable in ProSim Indicators Var 2428, name FIREAL, STATIC, Link IOCARD_OUT, DEVICE 20, Output 32 // APU FIRE HANDLE LIGHT, declare variable in ProSim Indicators Var 2430, name FIRE2L, STATIC, Link IOCARD_OUT, DEVICE 20, Output 33 // ENGINE 2 FIRE HANDLE LIGHT, declare variable in ProSim Indicators Var 2432, name FIREG1L, STATIC, Link IOCARD_OUT, DEVICE 20, Output 34 // FIRE ENGINE 1 GREEN LED, declare variable in ProSim Indicators Var 2434, name FIREGAL, STATIC, Link IOCARD_OUT, DEVICE 20, Output 35 // FIRE APU GREEN LED, declare variable in ProSim Indicators Var 2436, name FIREG2L, STATIC, Link IOCARD_OUT, DEVICE 20, Output 36 // FIRE ENGINE 2 GREEN LED, declare variable in ProSim Indicators // SWITCHES-INPUTS Var 2614, name S_OVHTDET1A, STATIC, Link IOCARD_SW, DEVICE 20, Input 46 // FIRE ENGINE 1 OVERHEAT A DETECTOR SWITCH, declare variable in ProSim Switches Var 2616, name S_OVHTDET1B, STATIC, Link IOCARD_SW, DEVICE 20, Input 45 // FIRE ENGINE 1 OVERHEAT B DETECTOR SWITCH, declare variable in ProSim Switches Var 2618, name S_FETSTOVH, STATIC, Link IOCARD_SW, DEVICE 20, Input 47 // FIRE ENGINES TEST OVH-FIRE SWITCH, declare variable in ProSim Switches Var 2620, name S_FETSTFAULT, STATIC, Link IOCARD_SW, DEVICE 20, Input 48 // FIRE ENGINES TEST FAULT-INOP SWITCH, declare variable in ProSim Switches Var 2622, name S_BELLCOUT, STATIC, Link IOCARD_SW, DEVICE 20, Input 49 // FIRE ENGINES BELL CUT OUT SWITCH, declare variable in ProSim Switches Var 2624, name S_OVHTDET2A, STATIC, Link IOCARD_SW, DEVICE 20, Input 51 // FIRE ENGINE 2 OVERHEAT A DETECTOR SWITCH, declare variable in ProSim Switches Var 2626, name S_OVHTDET2B, STATIC, Link IOCARD_SW, DEVICE 20, Input 50 // FIRE ENGINE 2 OVERHEAT B DETECTOR SWITCH, declare variable in ProSim Switches Var 2628, name S_EXT1TEST, STATIC, Link IOCARD_SW, DEVICE 20, Input 53 // FIRE ENGINE EXTINGUISHER 1 TEST SWITCH, declare variable in ProSim Switches Var 2630, name S_EXT2TEST, STATIC, Link IOCARD_SW, DEVICE 20, Input 52 // FIRE ENGINE EXTINGUISHER 2 TEST SWITCH, declare variable in ProSim Switches Var 2632, name S_HND1DW, STATIC, Link IOCARD_SW, DEVICE 20, Input 55 // FIRE ENGINE HANDLE 1 DW SWITCH, declare variable in ProSim Switches Var 2634, name S_HND1L, STATIC, Link IOCARD_SW, DEVICE 20, Input 54 // FIRE ENGINE HANDLE 1 LEFT SWITCH, declare variable in ProSim Switches Var 2636, name S_HND1R, STATIC, Link IOCARD_SW, DEVICE 20, Input 56 // FIRE ENGINE HANDLE 1 RIGHT SWITCH, declare variable in ProSim Switches Var 2638, name S_HNDADW, STATIC, Link IOCARD_SW, DEVICE 20, Input 58 // FIRE ENGINE HANDLE APU DW SWITCH, declare variable in ProSim Switches Var 2640, name S_HNDAL, STATIC, Link IOCARD_SW, DEVICE 20, Input 57 // FIRE ENGINE HANDLE APU LEFT SWITCH, declare variable in ProSim Switches Var 2642, name S_HNDAR, STATIC, Link IOCARD_SW, DEVICE 20, Input 59 // FIRE ENGINE HANDLE APU RIGHT SWITCH, declare variable in ProSim Switches Var 2644, name S_HND2DW, STATIC, Link IOCARD_SW, DEVICE 20, Input 61 // FIRE ENGINE HANDLE 2 DW SWITCH, declare variable in ProSim Switches Var 2646, name S_HND2L, STATIC, Link IOCARD_SW, DEVICE 20, Input 60 // FIRE ENGINE HANDLE 2 LEFT SWITCH, declare variable in ProSim Switches Var 2648, name S_HND2R, STATIC, Link IOCARD_SW, DEVICE 20, Input 62 // FIRE ENGINE HANDLE 2 RIGHT SWITCH, declare variable in ProSim Switches // ///////////////////////////////////////////// // END FIRE ENGINES IDC // ///////////////////////////////////////////// // ///////////////////////////////////////////// // FIRE CARGO IDC // ///////////////////////////////////////////// // OUTPUTS-LEDS Var 2438, name FCDISCL, STATIC, Link IOCARD_OUT, DEVICE 20, Output 87 // FIRE CARGO KORRY DISCH INDICATOR, declare variable in ProSim Indicators Var 2440, name FCDISCBARL, STATIC, Link IOCARD_OUT, DEVICE 20, Output 88 // FIRE CARGO KORRY DISCH BAR INDICATOR, declare variable in ProSim Indicators Var 2442, name FCAFTL, STATIC, Link IOCARD_OUT, DEVICE 20, Output 89 // FIRE CARGO KORRY AFT INDICATOR, declare variable in ProSim Indicators Var 2444, name FCAFTARML, STATIC, Link IOCARD_OUT, DEVICE 20, Output 90 // FIRE CARGO KORRY AFT ARMED INDICATOR, declare variable in ProSim Indicators Var 2446, name FCFWDL, STATIC, Link IOCARD_OUT, DEVICE 20, Output 91 // FIRE CARGO KORRY FWD INDICATOR, declare variable in ProSim Indicators Var 2448, name FCFWDARML, STATIC, Link IOCARD_OUT, DEVICE 20, Output 92 // FIRE CARGO KORRY FWD ARMED INDICATOR, declare variable in ProSim Indicators Var 2450, name FCDETFAULT, STATIC, Link IOCARD_OUT, DEVICE 20, Output 93 // FIRE CARGO DETECTOR FAULT INDICATOR, declare variable in ProSim Indicators Var 2452, name FCEXTFWDL, STATIC, Link IOCARD_OUT, DEVICE 20, Output 94 // FIRE CARGO EXT FWD GREEN INDICATOR, declare variable in ProSim Indicators Var 2454, name FCEXTAFTL, STATIC, Link IOCARD_OUT, DEVICE 20, Output 95 // FIRE CARGO EXT AFT GREEN INDICATOR, declare variable in ProSim Indicators // INPUTS-SWITCHES Var 2650, name R_FDETFA, STATIC, Link IOCARD_SW, DEVICE 20, Input 123 // FIRE CARGO DET SELECT FWD A ROTARY SWITCH, declare variable in ProSim Switches Var 2652, name R_FDETFNORM, STATIC, Link IOCARD_SW, DEVICE 20, Input 122 // FIRE CARGO DET SELECT FWD NORM ROTARY SWITCH, declare variable in ProSim Switches Var 2654, name R_FDETFB, STATIC, Link IOCARD_SW, DEVICE 20, Input 121 // FIRE CARGO DET SELECT FWD B ROTARY SWITCH, declare variable in ProSim Switches Var 2656, name R_FDETAA, STATIC, Link IOCARD_SW, DEVICE 20, Input 120 // FIRE CARGO DET SELECT AFT A ROTARY SWITCH, declare variable in ProSim Switches Var 2658, name R_FDETANORM, STATIC, Link IOCARD_SW, DEVICE 20, Input 119 // FIRE CARGO DET SELECT AFT NORM ROTARY SWITCH, declare variable in ProSim Switches Var 2660, name R_FDETAB, STATIC, Link IOCARD_SW, DEVICE 20, Input 118 // FIRE CARGO DET SELECT AFT B ROTARY SWITCH, declare variable in ProSim Switches Var 2662, name S_FARMF, STATIC, Link IOCARD_SW, DEVICE 20, Input 128 // FIRE CARGO FWD ARMED KORRY SWITCH, declare variable in ProSim Switches Var 2664, name S_FARMA, STATIC, Link IOCARD_SW, DEVICE 20, Input 127 // FIRE CARGO AFT ARMED KORRY SWITCH, declare variable in ProSim Switches Var 2666, name S_FTEST, STATIC, Link IOCARD_SW, DEVICE 20, Input 117 // FIRE CARGO TEST SWITCH, declare variable in ProSim Switches Var 2668, name S_FDISCH, STATIC, Link IOCARD_SW, DEVICE 20, Input 126 // FIRE CARGO DISCHARGE KORRY SWITCH, declare variable in ProSim Switches // ///////////////////////////////////////////// // END FIRE CARGO IDC // ///////////////////////////////////////////// // ///////////////////////////////////////////// // AUDIO FO IDC // ///////////////////////////////////////////// // OUTPUTS-LEDS Var 2392, name AU2VH1MI, STATIC, Link IOCARD_OUT, DEVICE 20, Output 78 // AUDIO2 VHF1 MIC LED, declare variable in ProSim Indicators Var 2394, name AU2VH2MI, STATIC, Link IOCARD_OUT, DEVICE 20, Output 79 // AUDIO2 VHF2 MIC LED, declare variable in ProSim Indicators Var 2396, name AU2VH1VO, STATIC, Link IOCARD_OUT, DEVICE 20, Output 80 // AUDIO2 VHF1 VOL LED, declare variable in ProSim Indicators Var 2398, name AU2VH2VO, STATIC, Link IOCARD_OUT, DEVICE 20, Output 81 // AUDIO2 VHF2 VOL LED, declare variable in ProSim Indicators Var 2400, name AU2NA1VO, STATIC, Link IOCARD_OUT, DEVICE 20, Output 82 // AUDIO2 NAV1 VOL LED, declare variable in ProSim Indicators Var 2402, name AU2NA2VO, STATIC, Link IOCARD_OUT, DEVICE 20, Output 83 // AUDIO2 NAV2 VOL LED, declare variable in ProSim Indicators Var 2404, name AU2AD1VO, STATIC, Link IOCARD_OUT, DEVICE 20, Output 84 // AUDIO2 ADF1 VOL LED, declare variable in ProSim Indicators Var 2406, name AU2AD2VO, STATIC, Link IOCARD_OUT, DEVICE 20, Output 85 // AUDIO2 ADF2 VOL LED, declare variable in ProSim Indicators Var 2408, name AU2MKRVO, STATIC, Link IOCARD_OUT, DEVICE 20, Output 86 // AUDIO2 MARKER VOL LED, declare variable in ProSim Indicators // INPUTS-SWITCHES Var 2584, name S_AU2VH1MI, STATIC, Link IOCARD_SW, DEVICE 20, Input 99 // AUDIO2 VHF1 MIC SWITCH, declare variable in ProSim Switches Var 2586, name S_AU2VH2MI, STATIC, Link IOCARD_SW, DEVICE 20, Input 100 // AUDIO2 VHF2 MIC SWITCH, declare variable in ProSim Switches Var 2588, name S_AU2VH1VO, STATIC, Link IOCARD_SW, DEVICE 20, Input 101 // AUDIO2 VHF1 VOL SWITCH, declare variable in ProSim Switches Var 2590, name S_AU2VH2VO, STATIC, Link IOCARD_SW, DEVICE 20, Input 102 // AUDIO2 VHF2 VOL SWITCH, declare variable in ProSim Switches Var 2592, name S_AU2NA1VO, STATIC, Link IOCARD_SW, DEVICE 20, Input 103 // AUDIO2 NAV1 VOL SWITCH, declare variable in ProSim Switches Var 2594, name S_AU2NA2VO, STATIC, Link IOCARD_SW, DEVICE 20, Input 104 // AUDIO2 NAV2 VOL SWITCH, declare variable in ProSim Switches Var 2596, name S_AU2AD1VO, STATIC, Link IOCARD_SW, DEVICE 20, Input 105 // AUDIO2 ADF1 VOL SWITCH, declare variable in ProSim Switches Var 2598, name S_AU2AD2VO, STATIC, Link IOCARD_SW, DEVICE 20, Input 106 // AUDIO2 ADF2 VOL SWITCH, declare variable in ProSim Switches Var 2600, name S_AU2MKRVO, STATIC, Link IOCARD_SW, DEVICE 20, Input 107 // AUDIO2 MARKER VOL SWITCH, declare variable in ProSim Switches Var 2602, name S_AU2RT, STATIC, Link IOCARD_SW, DEVICE 20, Input 110 // AUDIO2 R-T SWITCH, declare variable in ProSim Switches Var 2604, name S_AU2IC, STATIC, Link IOCARD_SW, DEVICE 20, Input 111 // AUDIO2 I-C SWITCH, declare variable in ProSim Switches Var 2606, name R_AU2FILTV, STATIC, Link IOCARD_SW, DEVICE 20, Input 109 // AUDIO2 FILTER V ROTARY SWITCH, declare variable in ProSim Switches Var 2608, name R_AU2FILTR, STATIC, Link IOCARD_SW, DEVICE 20, Input 108 // AUDIO2 FILTER R ROTARY SWITCH, declare variable in ProSim Switches Var 2610, name S_AU2NORM, STATIC, Link IOCARD_SW, DEVICE 20, Input 112 // AUDIO2 NORM SWITCH, declare variable in ProSim Switches { IF &S_AU2NORM <> 1 { &S_AU2ALT = 1 } ELSE { &S_AU2ALT = 0 } } Var 2612, name S_AU2ALT, STATIC // declare variable in ProSim Switches // ///////////////////////////////////////////// // END AUDIO FO IDC // ///////////////////////////////////////////// // ///////////////////////////////////////////// // AUDIO CAPTAIN IDC // ///////////////////////////////////////////// // OUTPUTS-LEDS Var 2374, name AU1VH1MI, STATIC, Link IOCARD_OUT, DEVICE 20, Output 14 // AUDIO1 VHF1 MIC LED Var 2376, name AU1VH2MI, STATIC, Link IOCARD_OUT, DEVICE 20, Output 15 // AUDIO1 VHF2 MIC LED Var 2378, name AU1VH1VO, STATIC, Link IOCARD_OUT, DEVICE 20, Output 16 // AUDIO1 VHF1 VOL LED Var 2380, name AU1VH2VO, STATIC, Link IOCARD_OUT, DEVICE 20, Output 17 // AUDIO1 VHF2 VOL LED Var 2382, name AU1NA1VO, STATIC, Link IOCARD_OUT, DEVICE 20, Output 18 // AUDIO1 NAV1 VOL LED Var 2384, name AU1NA2VO, STATIC, Link IOCARD_OUT, DEVICE 20, Output 19 // AUDIO1 NAV2 VOL LED Var 2386, name AU1AD1VO, STATIC, Link IOCARD_OUT, DEVICE 20, Output 20 // AUDIO1 ADF1 VOL LED Var 2388, name AU1AD2VO, STATIC, Link IOCARD_OUT, DEVICE 20, Output 21 // AUDIO1 ADF2 VOL LED Var 2390, name AU1MKRVO, STATIC, Link IOCARD_OUT, DEVICE 20, Output 22 // AUDIO1 MARKER VOL LED // INPUTS-SWITCHES Var 2554, name S_AU1VH1MI, STATIC, Link IOCARD_SW, DEVICE 20, Input 27 // AUDIO1 VHF1 MIC SWITCH Var 2556, name S_AU1VH2MI, STATIC, Link IOCARD_SW, DEVICE 20, Input 28 // AUDIO1 VHF2 MIC SWITCH Var 2558, name S_AU1VH1VO, STATIC, Link IOCARD_SW, DEVICE 20, Input 29 // AUDIO1 VHF1 VOL SWITCH Var 2560, name S_AU1VH2VO, STATIC, Link IOCARD_SW, DEVICE 20, Input 30 // AUDIO1 VHF2 VOL SWITCH Var 2562, name S_AU1NA1VO, STATIC, Link IOCARD_SW, DEVICE 20, Input 31 // AUDIO1 NAV1 VOL SWITCH Var 2564, name S_AU1NA2VO, STATIC, Link IOCARD_SW, DEVICE 20, Input 32 // AUDIO1 NAV2 VOL SWITCH Var 2566, name S_AU1AD1VO, STATIC, Link IOCARD_SW, DEVICE 20, Input 33 // AUDIO1 ADF1 VOL SWITCH Var 2568, name S_AU1AD2VO, STATIC, Link IOCARD_SW, DEVICE 20, Input 34 // AUDIO1 ADF2 VOL SWITCH Var 2570, name S_AU1MKRVO, STATIC, Link IOCARD_SW, DEVICE 20, Input 35 // AUDIO1 MARKER VOL SWITCH //Var 2572, name S_AU1RT, STATIC, Link IOCARD_SW, DEVICE 20, Input 38 // AUDIO1 R-T SWITCH Var 2574, name S_AU1IC, STATIC, Link IOCARD_SW, DEVICE 20, Input 39 // AUDIO1 I-C SWITCH Var 2576, name R_AU1FILTV, STATIC, Link IOCARD_SW, DEVICE 20, Input 37 // AUDIO1 FILTER V ROTARY SWITCH Var 2578, name R_AU1FILTR, STATIC, Link IOCARD_SW, DEVICE 20, Input 36 // AUDIO1 FILTER R ROTARY SWITCH Var 2580, name S_AU1NORM, STATIC, Link IOCARD_SW, DEVICE 20, Input 40 // AUDIO1 NORM SWITCH { IF &S_AU1NORM <> 1 { &S_AU1ALT = 1 } ELSE { &S_AU1ALT = 0 } } Var 2582, name S_AU1ALT, STATIC // ///////////////////////////////////////////// // END AUDIO CAPTAIN IDC // ///////////////////////////////////////////// // ********* OFFSETS **** Var 5250, Link FSUIPC_OUT, name fcom1, Offset $034E, Length 2 // COM1 Active Var 5252, Link FSUIPC_OUT, name fcom2, Offset $3118, Length 2 // COM2 Active Var 5254, Link FSUIPC_OUT, name fnav1, Offset $0350, Length 2 // NAV1 Active Var 5256, Link FSUIPC_OUT, name fnav2, Offset $0352, Length 2 // NAV2 Active Var 5258, Link FSUIPC_OUT, name fadf1A, Offset $034c, Length 2 // adf1 Active part1 Var 5260, Link FSUIPC_OUT, name fadf1B, Offset $0356, Length 2 // ADF1 Active part2 Var 5262, Link FSUIPC_OUT, name fadf2A, Offset $02D4, Length 2 // ADF2 Active part1 Var 5264, Link FSUIPC_OUT, name fadf2B, Offset $02D6, Length 2 // ADF2 Active part2 Var 5266, Link FSUIPC_OUT, name toneadf1, Offset $3107, Length 2 // ADF1 TONE Var 5268, Link FSUIPC_OUT, name toneadf2, Offset $02FB, Length 2 // ADF2 TONE Var 5270, name FS_XPDER_ID, Link FSUIPC_INOUT, Offset $0354, Length 2 Var 5272, name IVAP_SB_MODE, Link FSUIPC_INOUT, Offset $7B91, Length 1 Var 5274, name IVAP_SB_IDENT, Link FSUIPC_INOUT, Offset $7B93, Length 1 Var 5276, name XPDER_FAIL, Link FSUIPC_INOUT, Offset $0B6F, Length 1 { IF &XPDER_FAIL = 1 { &D_FAIL = -999997 &LED_FAIL = 1 } ELSE { &D_FAIL = -999999 &LED_FAIL = 0 } } Var 5278, name TCAS_MAGENTA, Link FSUIPC_INOUT, Offset $04F4, Length 2 Var 5288, name ruddert_o, link FSUIPC_INOUT, offset $0c04, length 2, type 1 // Rudder trim { CALL &runindicator } Var 5290, name ailt_o, link FSUIPC_INOUT, offset $0c02, length 2, type 1 // Ailerons trim //Trial code for PTT's Var 9210, name FO_JoyStick64, Link FSUIPC_INOUT, offset $3340, length 4, type 1 // PTT Var 9212, Link IOCARD_SW, Device 20, Input 38, Type I { &FO_JoyStick64 = CHANGEBIT 0 v9211 // toggle bit 0 of joystick 64 } Thanks a bunch.
  6. Optional Throttle Assignments

    As PMDG is currently working on the 747-8, I thought that this would be the perfect time to make a suggestion. It seems that for quite a while there has been an ongoing problem with the use of FSUIPC to assign throttle inputs to hardware axes. I was hoping that PMDG and Peter would eventually find a solution but it doesn't look like it will happen. The only thing that has prevented me from moving all throttles assignments off of FSUIPC is that I am hooked on flying your 747 and I need the ability that FSUIPC gives me to assign multiple throttle inputs to a single axis (eg., 1>1+2 & 2>3+4). It would be great if PMDG could add optional menu item that would do this internally. What do you think?
  7. Hello guys, I ask the experts .... my request is not aircraft specific, even if this case relates to MD11; I'm trying to assing to a joystick button a spoiler detent to increase/decrease speedbtrakes without success. I can only assign "Spoiler ON / OFF" but not incremental notches like for flaps to understand; I see in FSUIPC "Button and Keypresses/FS Control" there is the Spoiler Incr and Decr command but it seems to have no effect, at least on PMDG MD11. Does anyone know where I am wrong or suggest me the correct configuration in FSUIPC? Thanks in advance, Riccardo
  8. Hi All, I have completed a control panel with potentiometers and switches using a Leo Bodner controller for the A2A Comanche. Using Linda and FSUIPC it is working ok. But I have a linear pot (axis) that I planned to use to operate the fuel primer, after skimming over the FSUIPC Manual it wasn’t apparent to me how to do this. I am able to use an axis to control flaps position using FSUIPC. My goal is to move the pot the full extend position to full retract position and have FSUIPC send a signal to Linda to activate the fuel primer for each cycle of the pot. Can this be done? I presently activate the fuel primer with a switch. Thanks for looking at this. Rozel
  9. Hello, I'm flying and really enjoying the DC-6. I'm using P3Dv4. My question to the community is this: how can I map joystick buttons to autopilot functions? If I knew the control names, I could do it. I fully understand how to use FSUIPC. It's that there's so many entries in FSUIPC for autopilot functionality... I'm wanting to map the following items: On/Off switch Alt Hold switch The disengage lever (sorry to not recall its name) An axis (if possible) or buttons to the gyropilot left/right knob Mode selector (gyropilot, localizer and approach) Glide wheel or pitch wheel up/down I'd be very grateful if someone has this information. Thanks
  10. <problem solved> Hello pilots, I have a strange problem with my IVAO IVAP client in combination with FSUIPC5103 "Press the key to be sent when you press this button" feature in P3DV4. Let my try to explain: I configured a few buttons on my joysticks (yoke and HOTAS Warthog) via the FSUIPC "Buttons + Switches" tab and the option "Press the key to be sent when you press this button". A specific example is a button that when pressed should output the "S" corresponding the keyboard "S" for this explame to P3D view switching. This works perfect in P3D until I start the Ivao IVAP client. The functions stops working the minute I start the IVAP client (ivap_dllhost). All other functionalies like joystick use, throttle assignment etc all woks fine. Even in the same FSUIPC tab "Buttons + Swtches" the option "select for FS control" in combination with "control sent when button pressed" works fine. But not the option "Press the key to be sent when you press this button". When looking in FSUIPC "Buttons + Switches" tab I do see that when pressing the joystick button the function works. So the button works fine but the "function" is just blocked in the simulator by IVAP because it will not do what is programmed for. When I close IVAP via the windows task manager the function "Press the key to be sent when you press this button" works again. So its a combination of the specific option in FSUIPC and IVAO IVAP. The problem is that I configured a button on my yoke via the first option "Press the key to be sent when you press this button" to configure the "0" key on my keyboard that relates to Teamspeak push to talk key. This options, as mentioned above stops working the minute I start IVAP. I configured IVAP via the following manual: https://flightsimeindhoven.wordpress.com/category/knowledge-base/ivao-ivac-ivap/ Please note that IVAP works fine (flights are tracked by tracker). I also have FSX Steam installed and have no problems at all with the above settings. Does anyone experiance the same problem? Is there a workaround to configure the "push to talk" option from Teamspeak to a joystick button without the use of the "Press the key to be sent when you press this button" option in FSUIPC? Or a solution overall? Thank you for your help! Mike
  11. Simconnect issue

    Hi everyone. I have some problems with SimConnect or FSUIPC. I did a flight from EHAM to my brand new scenery Flightbeam KMSP. At 50% of my flight it freeze every few seconds. After a few 10 minutes later this issue disappeared. A few hours later this issue started again. Later I saw that my memory was at 100%, and a few seconds later my sim rant into OOM. Few minutes later the sim closed itself and my RAM was at normal again. After that I start P3D again, it was loading and the same happens again. But this time my computer froze and I did a hard shutdown. Now I flying back from KMSP to EHAM. And around 50% of my flight, I have again issues. I chose to play it save and close the simulator and restarting it form my last autosave. Again a few hours later, its happening again. This time I decide to just let the sim run, and the sim ran into a fatal error. Now I did some research, and discovered this in the FSUIPC logfile: 'No SimConnect events or states being received!'. Can a single scenery airport cause this? P3D fatal error: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2017-07-08T16:09:36.901370500Z" /> <EventRecordID>38317</EventRecordID> <Channel>Application</Channel> <Computer>Skynet</Computer> <Security /> </System> <EventData> <Data>Prepar3D.exe</Data> <Data>3.4.9.18400</Data> <Data>57d9b14e</Data> <Data>SimConnectP3D3.dll_unloaded</Data> <Data>3.2.2.16659</Data> <Data>58f1f032</Data> <Data>c0000005</Data> <Data>00001ec0</Data> <Data>6678</Data> <Data>01d2f7eb3cac8c87</Data> <Data>F:\Program Files\Lockheed Martin\Prepar3D v3\Prepar3D.exe</Data> <Data>SimConnectP3D3.dll</Data> <Data>d6251f2f-63f7-11e7-9e4d-d8cb8a9cd07e</Data> <Data /> <Data /> </EventData> </Event>
  12. FSUIPC is a powerful tool for programming hardware controls in FSX and Prepar3D. All of the control variables present in the simulator are directly accessible through FSUIPC and it provides more flexibility than the control settings resident in the simulator. FSUIPC can also be used to access local panel variables (LVARS) that were introduced by the developer of the particular add-on aircraft. Since the developer determines the nomenclature of the panel variables Mr. Dowson (FSUIPC developer) of course couldn't predict what those names would be. So....he provided us with a way to identify developer panel variables and access/control them through FSUIPC Macros. This tutorial is presented in a very elementary style that will be greatly oversimplified for many of the simmers that visit AVSIM. If so, just roll your eyes and remember that some folks are just beginners. This tutorial will take you through setting the control for the Lift Dump on the Carenado Premier 1A. If you don't have the Premier....no matter. The steps are the same for every aircraft and every LVAR. I will show how it's done using a keystroke, a button, a switch, and a lever (axis). So, let's get started. 1. Identify the variable you want to control. In this case, we want to control the Lift Dump function, but we don't know what variable controls it. Use the following procedure to identify the variable. a. Start the simulator and get the subject aircraft running. b. Using the mouse, activate the control in question. In this case, unlock and deploy the Lift Dump. c. Open the FSUIPC window. Select the "Buttons + Switches" tab. Check the "Profile specific?" option. Press the joystick button you want to use to find the Lift Dump variable. (This can be a temporary assigment because you will not normally use this when flying. The assignment can be cancelled later and returned to its previous function.) d. In this case the button I pushed was the Joystick #0, Button #25. On the right of the FSUIPC box, check "Select for FS control". In the pull-down menu under "Control sent when button pressed", select "List Local Panel Vars". Click "OK" to close the FSUIPC window. e. Un-pause the simulator. Press the button you just selected to list the panel variables. Exit the simulator. f. Go to the "Modules" folder in your simulator directory and open the file "FSUIPC4.log" in notepad. g. At this point you still don't know exactly what you are looking for. You must look through the log for something that looks like what you want. You can use the "find" function in notepad to help. In this case, I entered "Dump" in the find function. h. In this case, the find function returned something called "L:ASD_390_LEVER_LIFT_DUMP = 1.00". Looks pretty promising. Remember that we deployed the Lift Dump with the mouse prior to scanning for the panel variables. The "=1.00" suggests that this "L:ASD_390_LEVER_LIFT_DUMP" has been deployed. We would expect to see "=0.00" for something that hasn't been actuated. We're feeling pretty good that this is the variable that we want. Note: If you want to save this log for future reference you must rename it to something else. Each time you exit the simulator FSUIPC will overwrite the "FSUIPC4.log" file and it will not contain LVARS unless you push the "List local Panel Vars" button. 2. Now that we have likely identified the variable we want, it's time to build a FSUIPC macro that will allow us to control it. a. On the start menu, open "Computer" and select "Organize" and "Folder and Search Options" b. Select the "View" tab and scroll down until you see "Hide extensions for known file types". This should NOT be checked. c. Go to the desktop and right-click. Select "New" and "Text Document". d. You should now have a file on your desktop entitled "New Text Document.txt". Rename it "390_Dump_Toggle.mcro". The computer will object to changing the file extension with a warning. Click "yes". The title should be as short and descriptive as possible because, as you will see later in the tutorial, not all of the macro will show when you are selecting it in FSUIPC. The "390" identifies the airplane, the "Dump" identifies the function, and the "Toggle" identifies how it will be used. e. Open the new .mcro file. Type "[Macros]" in the first line. In the second line type "1=L:ASD_390_LEVER_LIFT_DUMP=Toggle". Save the file. Note: The number will always be "1" because FSUIPC allows only one macro per LVAR macro file. The LVAR we are trying is "L:ASD_390_LEVER_LIFT_DUMP". The options for the command of execution are "Set", "Toggle", "Inc", "Dec", "Sbits", "Cbits", and "Cyclic". If you can read "genius", a fuller explanation of these can be found in a pdf file included in your FSUIPC Documents folder entitled "FSUIPC4 for Advanced Users" on page 42. For the purposes of this tutorial, we will only address "Set" and "Toggle". Set works well if you are going to use a switch or axis for control and toggle works best for buttons or keypresses. 3. Place the new macro into the Modules folder in your base simulator directory (the same folder that contains "FSUIPC4.dll"). 4. Start the simulator and get the Premier 1A running. Open FSUIPC from the "Add-Ons" menu. KEYPRESS 1. Select the "Key Presses" tab in the FSUIPC window. Check the "Profile specific" box and press the "Set" option on the left side of the window. 2. Press the key you want to use to toggle the Lift Dump. I used "D" in the example. Press the down arrow to the right of the "Control sent when keys pressed" section. A pop-up menu should emerge with "390_Dump_Toggle:L:ASD 390 LEVER LIFT DUMP....." as an option. Notice that you can't see the entire macro and you can't see whether the command was set or toggle or whatever. That's why you name the macro descriptively. Select that and click "OK". With the toggle function there is no need to set a parameter. 3. Un-pause the simulator and try your new macro. Press "D" and the Lift Dump should deploy. Press "D" again and it should retract. If it works...you're done. 4. If it doesn't work, there could be several causes. One, you may not have identified the correct variable. Sometimes they have goofy names and it's difficult to sort them out. You also may have mis-formatted the macro itself. It is very strict and must be formatted exactly right. BUTTON TOGGLE 1. The idea is exactly the same as using the keypress except it's programmed in the "Buttons + Switches" tab of FSUIPC. Check the "Profile specific" box, check the "Select for FS control" box, select the down arrow button in the "Control sent when button pressed" and select "390 Dump Toggle:L:ASD....." as before. Click OK and try the button in the simulator. SWITCH SET 1. Make a copy of your macro and rename it "390_Dump_Set.mcro". Open the file and change "Toggle" to "Set". 2. Restart the simulator. Macros are only loaded into FSUIPC during simulator startup. Any changes made while the simulator is running will not be loaded. 3. With the sim running select FSUIPC from the "Add-Ons" menu. 4. Selecting a switch is very similar to selecting a button. Check the "Profile specific?" box. Actuate the switch to be used. In the example I used Joystick #0, Switch #19. Check the "Select for FS control" box and select "390 Dump Set:L:ASD....." in both the "Control sent when button pressed" box and the "Control sent when button released" box. 5. Enter "1" in the parameter that you want to deploy the Lift Dump and enter "0" into the parameter that you want to retract it. Either parameter will work. The choice of parameter placement governs the direction of the switch. Sometimes it's trial and error (developers occasionally get the commands backwards as well). Click OK and give it a try. USING AN AXIS This is my preferred method because it most closely resembles levers typically used for spoilers and lift dumps. I have two propeller levers and two mixture levers going unused in most jets so I like to use them for spoilers and lift dumps. 1. Get the sim and the airplane running as before. 2. Open FSUIPC from the "Add-Ons" menu. 3. Click on the "Axis Assignment" tab. 4. Move the lever you want to use for the lift dump. I use the #2 propeller lever. If you have used FSUIPC before you know that you may have to monkey with the "Rescan" or "Ignore Axis" buttons to get to the lever you want. 5. Once you are sure that the desired lever is the one selected, check the "Send to FS as normal axis" bullseye. 6. On the right side of the FSUIPC window you will see a section that says "Set up to 10 ranges for action". Pull the lever half way back and select the "To" button. Pull the lever all the way back and select the "From" button. Check the "Up" and "Down" boxes. You should see something like this. 7. Just like we did with the switch, select "390 Dump Set:L:ASD....." on both the "Control sent when range entered" and "Control set when range exited" boxes. Set parameter "1" for range entered and parameter "0" for range exited. Click OK and give it a try. This should get you going with FSUIPC Macros. As I said earlier, more detailed information can be found in your FSUICP Documents folder. Happy Simming!
  13. Hi people, I am a RW 320 pilot looking to set up FS labs A320. To that end, I have recently bought a copy of P3D V4 and I'm having a lot of trouble setting up my Saitek Pro thrust quadrant, MadCatz joystick and Saitek rudder pedals. I am looking for an idiots guide to FSUIPC5. Although there is indeed already a lot of information from Pete Dowson and others about this software it all assumes a certain amount of knowledge that I simply don't have. I have tried to register on Pete's support Forum so that I can ask this question but I never received the registration email despite the site saying that it's been sent (yes I've checked my junk mail folder) The video's that assist to some extent don't seem to be quite the same as what I'm looking at. I would appreciate your help.
  14. I am in the midst of setting up my yoke and throttle quadrant in P3D v4, and I am trying to do it without the need to purchase FSUIPC 5. There's a decent chance I'll cave. FSUIPC 4 has a default Delta value of 256 in the Axis Assignment tab, which I believe reduced my CH throttle quadrant levers from any noticeable jitter. P3D v4, on the other hand, is picking up the slightest bit joystick jitter as if the Delta was significantly lower. The in-sim effect is causing my cockpit levers to jitter quite noticeably. Changing the axis sensitivity in P3D doesn't seem to affect this Delta. So, my question is how do I adjust the Delta that Prepar3D reads in without needing to install FSUIPC 5?
  15. I am trying to add some functionality v4 that FSUIPC provided me in v3, and I can't seem to figure out how to add new key assignments. I am currently attempting to add new assignments to the standard.xml file in AppData\Roaming\Lockheed Martin\Prepar3D v4\Controls In particular, I'm trying to add keys to toggle my beacon, taxi, and navigation lights. I'm using the eventIDs from http://www.prepar3d.com/SDKv2/LearningCenter/utilities/variables/event_ids.html For example, I added this in my <Name>KEYBOARD_MAIN.Native</Name> section <Entry> <Key>CTRL+SHIFT+P</Key> <Down>TOGGLE_TAXI_LIGHTS</Down> </Entry> Upon loading P3D v4, that assignment gets removed. Any thoughts? Thanks.
  16. Hi all. I am struggling to get Linda to make "bigger strokes" when using the X-55 trim buttons (wheel) on the throttle, its painfully slow. I have set up FSUICP according to this thread to make the aileron Trim faster using OFFSET SWORD Increment / Decrement http://a2asimulations.com/forum/viewtopic.php?f=115&t=40237#p303155 This works a treat, but as its a button assignment I really want Linda to do this for me not FSUIPC, can anyone help me with the required Linda code please. Many thanks Rog.
  17. FSX, PMDG, and FSUIPC

    Hi, everyone, Currently, I am running PMDG 747 -400X in FSX on a desktop in Windows 7 (64-bit), with FSUIPC used to control my CH Eclipse Yoke, a CH Throttle Quadrant and its relevant Keyboard Commands. Can anyone tell me how I can double-up the commands that I presently have available? I have been thinking about using Button 1 on the Yoke (PTT usually) as a Shift Button but I do not appear to be able to program the Shift Key in. I know that if I program button 1 as a Shift Key, I will lose its availabllity as a PTT, but this is more than compensated for by the extra number oif Commands that I would get as a result of successfully doing this. I have read Pete Dowson's 'Application Interfacing Modules for MS FSX' etc, (both the normal one and the Advanced one), but do not see how I can do this. Any useful suggestions would be most welcome, but please, please, make it so simple that a 3-year oild could understand it. I am not a geek or nerd, but I do love flying, and having recently had my PPL taken away for medical reasons, this is now my only way of feeling part of the party again! Regards and Happy Flying to everyone, Philhen1943
  18. Hi All, I'm wondering if there's a way to read the text of FSUIPC messages that isn't tied to the simulator panels. My screen reading technology doesn't seem able to get anything from them, probably because of the technique use to draw the controls on screen. Nevertheless, a lot of add-ons seem to use the messages for various purposes, and it seems reasonable that something like this might exist. I'm envisioning a program rather like an old-style computer console, possibly even running in a Windows command prompt. It would display the messages as they come in, and that's probably about it. The key for me is that my screen reader needs to be able to access them, and it can't currently. Any thoughts on this?
  19. Hello all. I have been using a joystick with twisting function for my FSX. I just got my rudder pedal and trying to separate the tiller and rudder. So far I have managed to use the tiller by the joystick twisting without affecting the rudder but when I use the rudder pedal, the tiller turns and steer the aircraft on the ground. So is there a way to assign rudder pedal to rudder function only? I'm testing on PMDG 777 but I think the same will be for your 737 and MD11? (Yes, I have searched google for couple hours) Hoang Le.
  20. Dear Community, I am trying to rewrite an EPIC script that works for the standard FSX planes, sending offsets to control various values. My script is sending the values itself. It does not simply send increments ("turning the knobs"). Looking at the PMDG_NGX_SDK.h, my impression is that the events only "turn knobs", but I have not found events to send values. Only the offsets in the section "MCP direct control seem to send direct values. Is this correct? I am looking for a way to send NAV and COMM radio frequencies to the NGX. Best, Holger
  21. When I load the 737NGX and configure the Ailerons and Elevator. The Ailerons only move 2 degrees Left and right Elevator only an inch forward and back and the rudders hardly move. It doesn't matter if I config them through FSX-SE or Fusipc it still happens but not on other aircraft. Help Richard Preece
  22. Help any one Ive had a complete fresh reinstall of my system and finally moved over to FSX Steam Im having dificulty configuring the Saitek Joystick and Rudder, Its been recommended that for the PDGM 737 the throttles are configured through FSX which I have done and Ive tried to configure the elevators, Ailerons and Rudders through FUSIPC. however when I have done this the Ailerons only move 2 degrees in either direction the elevatoes only move about an inch forward and back and the Rudders hardly move at all. Ive tried running them back through settings within FSX-SE and taking out any conflicting commands in FSUIPC but I get the same. the Joy stick is calibrated and works for my Otter. So Have I missed something or has anyone had a similar issue and resolve it. a push in the right direction would be greatfull Regards Richard Preece
  23. Hello everyone, I am facing some problems with FSUIPC4 on FSX Gold Editition. I have installed FSUIPC as adminstrator and all of its files are installed in FSX's modules folder. However, FSUIPC never gets loaded by FSX. I realised that as soon as I launched FSX after installing FSUIPC, because the Simulator did not ask for my authorization to run FSUIPC. I checked FSUIPC Install log file, everything ok. I checked FSX.dll, everything looks normal. I really cannot understand what the problem is. I would appreciate your some help. Respectfully, GeKa
  24. Hello, Could you help me please ? How can i use functions who are in actions.lua through FSUIPC ? actions.lua from : http://www.avsim.com/topic/341971-pmdg-737-ngx-module-47-new/ Example in FSUIPC : Key presses : SET : CTRL + J >>> NGX_PUMP1_AFT_toggle or Buttons + Switches : SET : 1 >>> NGX_PUMP1_AFT_toggle Thanks for help. PS : i have create a specific FSUIPC macro for the test, but i dont want do this for each function. PMDGBaseVar = 0x00011000 -- 69632 PMDG_ClkL = 0x20000000 -- 536870912 PMDG_ClkR = 0x80000000 -- -2147483648 PMDG_dec = 0x00002000 -- 8192 PMDG_inc = 0x00004000 -- 16384 PMDG_RelL = 0x00020000 -- 131072 PMDG_RelM = 0x00040000 -- 262144 PMDG_RelR = 0x00080000 -- 524288 function NGX_PUMP1_AFT_off () if ipc.readLvar('ngx_switch_37_a') ~= 0 then ipc.control(PMDGBaseVar+37, PMDG_ClkR) DspShow("PMP1", "Aoff") end end function NGX_PUMP1_AFT_on () if ipc.readLvar('ngx_switch_37_a') ~= 100 then ipc.control(PMDGBaseVar+37, PMDG_ClkL) DspShow("PMP1", "A on") end end if ipc.readLvar('ngx_switch_37_a') == 100 then NGX_PUMP1_AFT_off() else NGX_PUMP1_AFT_on() end PS : i have also test an include in lua MACRO file !? But dont still work ? require("scripts.actions") NGX_PUMP1_AFT_toggle() end Thanks for advance; Sky
  25. Hi all B777 fans! I am having a problem with my PMDG B777. After I updated the FSUIPC on my computer the B777 stopped during loading. When the countdown clock is passing 17 it disappears but everything seems to work as it shall.Exept i can't control the throttle from my joystick and the tail rudder and elevator won't move at all with both the joystick and my keyboard. I have the newest version of the 777 and FSUIPC. Have tried to uninstall B777 and do a clean install of the plane. Nothing works exept removing the FSUIPC. The problem have not happend before the update of the FSUIPC. the problem happend first with the FSUIPC version before the current one FSUIPC4 4.958. Do anyone have a fix to this? I have the non registered version of FSUIPC. I just love the PMDG 777 so i really want to get this fixed as fast as possible. I have had the problem for many weeks now. So need some assistance from you guys! Thanks in advance Best regards Even Schjenken