Sure a EFIS is fixed in its length and high. But Small Elements that are much more difficult to handle like bigger ones are (for me) a Problem.Įach Cockpit element got one thing nearly "endless". And you can use it same way.īut I personlay not recommend them. Who cares if your LED now light 1-2 milliseconds later like with the other formula And pretty sure the Mega chip will not overheat with this additional process. Thats why the most easy solution is if($=16383,0,$)īut again. Cause in that Offset we got the nice situation that Gear UP means Offset is "0" -> the OFF Situation here is already fit without any IF-ELSE is needed. So as i wrote the OR is not realy needed. And there with 386CPU and only 4-8 Mhz we get instructed to reduce amount of code as best as possible. Whatever i come from a long long forgotten time in Basic Programming when i was in school. So it´s not a real difference what formula we use. ![]() Those little script lines and if conditions are a verry small amount of Systemwork. I not know if Users have experience in programing. (i kwnow what formula means, i'm a c# programmer so it's familiar hehehe). Maybe, this is the best solution for little panels Here we say If value is 0 OR 16383 then set to 0 Else set to 1. LED is ON that time cause Value is not zero that moment.įor better understanding. So LED is OFF again.īetween the Value is increase within some seconds from 1-16382. At Gear DOWN our formula set Value to Zero Again. IF Value is exactly "16383" THEN change it to "0" ELSE ( in all other situations value is not 16383) show the original Value "$".Īt Gear UP the Original Value is used and it´s Zero. LED will light always if Offset is not equal to zero. Simply Boolean)įrom Code side it is easy. A LED in Mobiflight knows 2 different Status. But the Device Side use here screwed terminals ! From China you get them much more cheaper. On that PCB there are onboard lines that connect the inner holes ( you solder the devices) with the outer holses ( you solder the Pin connector to Mega). Also a advantage is you not need to use the same hole for both. A regulary empty Breadboard platine will not work cause some of the Connectors on the mega are a little out of the middle. And on backside of PCB you solder Pin rows that fit into the Mega. Here you solder all the wires from devices to that PCB. Our user Karl (Helimech) for example use those. ![]() between it is 1-16382 and will light."Ĭan be a solution? Is if($=16383,0,$) the between function?Ībout shield. In case "0" is still OFF we simply say if($=16383,0,$). "The Transit should work between UP and DOWN. I found a workaround in another post in this forum to try to fire the UNLK led. Yes, i want to connect the default A320Neo because JH is not compatible yet with fs2020. If YES the simply wait until all the Systems are implement and then use it. Check all the Hardware by testing with other functions if LED and Switches work. ![]() Technical we could tet it with shared screen in some weeks. Simply Rule: Mobiflight can only Read or Write Data if FSUIPC support that stuff. Here pretty sure we still get in trouble in case all these new functions are not already implement by Pete Dowson in his FSUIPC! May you like to think about Arduino shields in the future to have just one conncetor and not a lot of Duponts on the Mega.ĭo we talk about Stock Airbus A320 in FS2020 ? Nearly perfect Panels and a tidy wire system. ASKID ON/OFF works using eventid "ANTISKID_BRAKES_TOGGLE" with params 1 for the ON, and 0 for OFF I can't found Offsets or EventID for the HotBrake and TerrON, can you help me?Ĥ. The Abrake Max works, it set MAX Abrake in sim, Abrake MED and LO doesn't work.ģ. I read fsuipc manual and i found some about offsets of the Autobrake Set : 0=RTO, 1=OFF, 2 = Brake1, 3=Brake2, 4 = Brake3, 5 = Brake MAX.ĪBRAKE MAX, EventID SET_AUTOBRAKE_CONTROL, params 4ĪBRAKE MED, EventID SET_AUTOBRAKE_CONTROL, params 3ĪBRAKE LO, EventID SET_AUTOBRAKE_CONTROL, params 2 The event fired by sim as param 0 = ON, 1 = OFF. Using fsuipc console i found this is the event fired when i push one of the abrake button in sim. ABRAKE push button : i use event id "SET_AUTOBRAKE_CONTROL". Landing Gear status : I can match all offsets for LandingGear extended, but if i try to assign LandingGear moving (for UNLK lights) when i push "USE" set LangingGear (extracted), any idea (it seems the offsets are the same)?Ģ. So i have some problem with offsets/eventidġ. I already had some p&p devices but with MSFS i can't use them, so i decided to build from scratch my home cockpit.įist panel is the BRAKE PANEL (i have to backlight it)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |