Welcome to the forum for MobiFlight! Feel free to reach out to the community in case you have questions, issues or just want to share great ideas or details about your latest home cockpit project.
You like MobiFlight? Donate via PayPal and support the MobiFlight development. Thanks!
Hi,
Tried to configure 2 inputs in mobiflight to GEAR down and gear up but it is not working.
Input 40 - gear down
Input 41 - gear up
a) configured devices for pin40 and pin41 as button
b) upload configuration
c) in the "Inputs" tab added 2 lines
d) first one I set "on press" FSUIPC offset 0x0BE8 to 0 (gear up) and "none" "on Release".
e) for the second I set "on press" FSUIPC offset 0x0BE8 to 16383 (gear down) and "none" "on Release".
For the wiring I am using a simple wire from Ground directly to pin 40 or 41.
Stopped the Mobiflight and start him again.
The problem is that when I pin the 41 for gear down, doors in the aircraft open and then the gear goes up again.
Any ideas about what is happening?
Thaks a lot guys.
Carlos
I am lost in this. I really can´t figure out what is going on. I even created 6 "inputs" one pair for each gear, 0x0BEC for nose gear, 0x0BF0 for right main gear and 0x0BF4 for left main gear as shown in the FSUIPC4 Offsets Status.pdf from Pete. Current version of FSUIPC4 is 4.964.
The mobiflight software show "Modules" a green sign and "FSUIPC" also a green sign.
I really need some light. I have already configures 6 leds as OUTPUS showing the gear in movement and gear down and locked. This is working perfectly.
I added a log in the FSUIPC application on 0BE8 offset.
Then I went to P3D and pressed "G" key. The gear is down.
When I pin the Ground wire in pin for gear up (I send 0 in Mobiflight) the P3D shows in the windows that the value changed to 0. But when the gear reaches the full up position the value is changed again to 16383 and the gear starts going down again.
I am really confused about this. Is this a bug in the Mobiflight?
Am I doing something wrong?
How can we check the FSUIPC version being used by Mobiflight?
Why do you use 2 Pins for that..... Normaly i would say you have ONE Switch..... In ON Position Gear is Down.... In OFF Position Gear is UP.
So Simply make ONE Config... On Press 163838 On Release 0 .... Both On Offset 0BE8
The Offsets behind 0BEC 0BF0 0BF4 are only used for OUTPUT.... You not have a gear leaver for every Gear speperate.... You only have ONE Leaver... So You Write only Offset 0BE8 !!!
Last Note.... Not make Tests with a improvisional Building like Wires to GRD.... Simply use a cheap switch for that..... IF you have a Issue somewhere or a "Short circuit" then you not see the reason for that !
AND.... Get Shure you are in the Air ! If you try to GEAR UP whuile on GRD than its logical the Offset stay in DOWN.... the Gear can´t transit while on GRD.
Thanks a lot for your answer.
a) I was using 2 switches because my switch is in fact a pressbutton so if I release the button the gear would rectract. Even spending one more button it should work... but it does not.
b) I tried to use your idea. I added only a button and what happens is that when I press the button, the value 16383 is in fact sent to P3D through MobiFlight (I can see it in the FSUIPC log) but half a second the value returns to 0. So the gear does not go down. This is the problem!
c) The aircraft is flying. The 0BEC 0BF0 0BF4 are read/write offsets. If I try to use only the nose gear offset I can do it with the MobiFlight, but as I said, the nose gear goes up and then goes down again.
In fact there is something that is not ok. I have removed all leds and and all devices and I ONLY have the pin 40 working in MobiFlight for the gear 0BE8 offset. The problem is the same. The value truns to 16383 and suddenly goes back to 0.
Can you tell me if we need to use a resistor with the button? I am using the button connected directly from ground to the pin.
I went into the settings of the MobiFlight and turned on the debug logging. Then I realized that something is going wrong here because whenever I press the button the ewvent is shown as "onRelease" and when I release the button he MobiFlight throws the "OnPress" event. Even so, and changing the values for the offset , things do not work.
I changed the offset to 0BDC (flaps).
0 means full retract and 16383 means full extended.
Added to my ONLY button in MObiflight and everything works fine!!! When the button is pressed the flaps goes to full flaps and as soon as I release the button, the flaps start to retract.
The only weird thing here is that the MobiFlight log shows a wrong event in the log. When I press the button it shows "OnRelease" and when I release the button it shows "OnPress"... weird.... anyway it works very good with flaps... but what´s the problem with 0BE8? Just changind the value for offset and the gear does not work.
OK.
Lots of new informations.
Now we have TWO Problems.... 1. Why is GEAR not working .....2. Why is Press Release inverted
At First. Please Confirm you use a ARDUINO MEGA ! ( Pretty Shure but only to prevent a missunderstanding)
The situation that a Press is shown as release is confusing. I not see that before.
Electrical you are correct... You bild a circuit between the Button Pin ( You set as Button in Devices Settings) and the Switch.... And from other side of Switch to GRD of SAME Arduino !!!
Please confirm additional you RESET the Arduino after flashing the firmware and/or setting new devices.
Simply push the Button on Arduino Mega OR Remove the USB Wire.... Wait some Seconds. Close Mobiflight.... Set the Wire again and start Mobiflight again.
In some rare situations a RESTART must be done after adding new devices on the Board !
****
Now to the GEAR....
A Idea....
Please observe the Gear Controll Offset 0BE8 4 Byte INT with a OUTPUT Config ( No device needed... We only need the Value ! )
Then use the G Button or the Viortual Gear Leaver with Mouse and check how the value is working.....
In FSX some Aircrafts NOT go through 16383.... They STOP at 16381 for example....
MABY This is the Problem taht in your testing Aircraft the Down position is BEFORE 16383 and a setting OVER this Point occure in a GearUp again.
Alternate.... Myself i not do Inputs via Offsets.... I mostly use Events or if needed Key Commands (Via FSUIPC) .
What you can do is for example the EventID´s...,.
GEAR UP 66079
GEAR DOWN 66080
Please try out this stuff... Report Experience please !
EDIT: And please Confirm you do the Tests with a STANDARD Aircraft.... Not with a ADDON !!!!
a) The reverted events showed in log are absolutely correct. My mistake, sorry. The younger event appear on top of the list and I was looking to the bottom of the list... sorry. Solved.
b) I tried this solution with a button with P3D V4 and FSUIUPC 5.121b and gess what..... IT WORKS FINE !!!! Gear and Flaps work fine. So this let me think there is something like some kind of incompatibility between P3D and FSUIPC. I am going to do 2 things. 1st) I am going to try your idea... EventId´s. and 2nd) I will try to update the P3D to the latest version of V3.
This means I am doing everything ok and also means MobiFlight has no problem. This feels very, very good.
Just to report... I used EventId´s and works perfectly !!!!
I am still going to update the P3D to the latest version of version 3 and I will post here if the problem persists using the offset method.
I have 2 P3D versions installed on my PC.
I have P3D version 3.2.3.16769 working with FSUIPC version 4.971 .
And also the 64bits P3D V4 version 4.0.23.21468 and FSUIPC 5.121b .
I believe P3D V3 lastest version is 3.4.9. I need to upgrade them both...
a) The reverted events showed in log are absolutely correct. My mistake, sorry. The younger event appear on top of the list and I was looking to the bottom of the list... sorry. Solved.
CHECK !
About the Gear problematic....
Here a mixup of different Versions "can" be the problem !
As you say... FSUIPC 5.xx is concepted for P3D V4 (64bit) ...... Here it workes.
It the other installation you simply got a logic issue.....
Its correct that FSUIPC 4.xxx is for P3D V3.xx BUT..... There was always the policy that BOTH must be UptoDate same time to work perfect !
So if you use a P3D Old Version like 3.2.x then you need the FSUIPC Version that was buif for THAT Release.... Maby 4.96 or 4.97 or 4.98
Or inverted.... If you use newest FSUIPC 4.99x Release from 2017 you should work with latest P3D V3.4xxxx Version.
Again... Not Shure if THIS is the problem.... But it looks like ! If you want simply try out and get latest versions of BOTH programms.
Whatever.... eventID are working.... Keybind is working too.... Problem SOLVED !