+- rksoftware NewForum (https://rksoftwareforum.flightsim4fun.com)
+-- Forum: My Category (https://rksoftwareforum.flightsim4fun.com/forumdisplay.php?fid=1)
+--- Forum: My Forum (https://rksoftwareforum.flightsim4fun.com/forumdisplay.php?fid=2)
+---- Forum: Oi4FS24 (https://rksoftwareforum.flightsim4fun.com/forumdisplay.php?fid=3)
+---- Thread: OI4FS2024 Duspanel and Servo Gauges (/showthread.php?tid=5)
OI4FS2024 Duspanel and Servo Gauges - sisoffi - 05-16-2026
Hi everyone,
first of all, congratulations for the excellent work on OI4FS2024.
The software connects perfectly with the PMDG 737 under Microsoft Flight Simulator 2024 and overall it looks like a very solid and promising solution.
However, we are currently experiencing a couple of important issues with our OpenCockpits setup and we would like to understand if we are missing something in the configuration.
1. Overhead switches affecting DU selectors / GPWS tests
Sometimes, when operating certain switches on the overhead panel, the DU selectors on both CPT and FO sides suddenly change position/state by themselves, and at the same time the GPWS warning tests start triggering (WINDSHEAR, PULL UP, etc.).
This behavior appears random and is extremely annoying during operation.
Has anyone experienced something similar?
Could this be related to overlapping offsets/events or incorrect variable mapping?
2. Servo gauge configuration problems
We are also having major issues configuring the servos.
Compared to the original standard OpenCockpits configuration package, we only managed to discover that:
- Servo 1 for EGT is actually driving the Fuel indication instead.
So our main questions are:
- How are the servos supposed to be configured correctly in OI4FS2024?
- Is there a reference mapping table available for OpenCockpits gauges/servos?
- Do we need to manually remap every servo output?
- Is there a calibration procedure or recommended setup method?
Thanks in advance!
RE: OI4FS2024 Duspanel and Servo Gauges - roarkr51 - 05-17-2026
(05-16-2026, 07:09 AM)sisoffi Wrote: Hi everyone,
first of all, congratulations for the excellent work on OI4FS2024.
The software connects perfectly with the PMDG 737 under Microsoft Flight Simulator 2024 and overall it looks like a very solid and promising solution.
However, we are currently experiencing a couple of important issues with our OpenCockpits setup and we would like to understand if we are missing something in the configuration.
1. Overhead switches affecting DU selectors / GPWS tests
Sometimes, when operating certain switches on the overhead panel, the DU selectors on both CPT and FO sides suddenly change position/state by themselves, and at the same time the GPWS warning tests start triggering (WINDSHEAR, PULL UP, etc.).
This behavior appears random and is extremely annoying during operation.
Has anyone experienced something similar?
Could this be related to overlapping offsets/events or incorrect variable mapping?
2. Servo gauge configuration problems
We are also having major issues configuring the servos.
Compared to the original standard OpenCockpits configuration package, we only managed to discover that:But overall, all gauges appear completely mismatched and incorrectly assigned/calibrated.
- Servo 1 for EGT is actually driving the Fuel indication instead.
So our main questions are:Any help or documentation would be greatly appreciated.
- How are the servos supposed to be configured correctly in OI4FS2024?
- Is there a reference mapping table available for OpenCockpits gauges/servos?
- Do we need to manually remap every servo output?
- Is there a calibration procedure or recommended setup method?
Thanks in advance!
Hi,
The DU issue has been a long time issue not completly solved in the driver/script yet. As i don't have the home cokcpit up and running anymore it is hard for me to troubleshot this issue. I know it has been debated in the old forum. If anyone found I fix for it I relaly don't know.
here is an old topic:
https://forum.flightsim4fun.com/NF/viewtopic.php?t=1107
YOu should also go to SIOC's IOCPConsole and try to figure out wheat is causeing/ interfering
To calibrate your servos read the thread from the old forum
https://forum.flightsim4fun.com/NF/viewtopic.php?p=4171&hilit=servo+calibration#p4171
Also look into the old forum for more help, there are tons of info there.
Hope this helps you
RE: OI4FS2024 Duspanel and Servo Gauges - NobbyC_B738 - 05-18-2026
Hi,
I had knob mismatch on the OVH as well and I'm in direct contact with another user who had DU knob mismatch on the MIP. We had the mismatch problems mainly after lights tests and after change of el. states. (e.g. switching to APU power or switching off battery). I could solve for both of us because causes were the same.
Before I can try to help you, I need some information:
1) do you have knob mismatch after switching lights test on or off? Sometimes several lights tests are neccessary to reproduce the problems)
2) do you have knob mismatch after el. state change?
3) do you have some annunciators connected to the 7 additional outputs on the P2 connector of one or more mastercards (output 49 ... 55)?
RE: OI4FS2024 Duspanel and Servo Gauges - sisoffi - 05-26-2026
(05-18-2026, 08:28 PM)NobbyC_B738 Wrote: ThannkYou Norbert!
both MAIN PANELS ENG PRI in captain side, and ND in Fo side move immediatly when start OC4.
while the alerts start when i touch something referring to BLEED pumps.
many thanks,
Simone
Hi,
I had knob mismatch on the OVH as well and I'm in direct contact with another user who had DU knob mismatch on the MIP. We had the mismatch problems mainly after lights tests and after change of el. states. (e.g. switching to APU power or switching off battery). I could solve for both of us because causes were the same.
Before I can try to help you, I need some information:
1) do you have knob mismatch after switching lights test on or off? Sometimes several lights tests are neccessary to reproduce the problems)
2) do you have knob mismatch after el. state change?
3) do you have some annunciators connected to the 7 additional outputs on the P2 connector of one or more mastercards (output 49 ... 55)?
RE: OI4FS2024 Duspanel and Servo Gauges - NobbyC_B738 - 05-28-2026
(05-26-2026, 08:01 PM)sisoffi Wrote:Hi Simone,(05-18-2026, 08:28 PM)NobbyC_B738 Wrote: ThannkYou Norbert!
both MAIN PANELS ENG PRI in captain side, and ND in Fo side move immediatly when start OC4.
while the alerts start when i touch something referring to BLEED pumps.
many thanks,
Simone
Hi,
I had knob mismatch on the OVH as well and I'm in direct contact with another user who had DU knob mismatch on the MIP. We had the mismatch problems mainly after lights tests and after change of el. states. (e.g. switching to APU power or switching off battery). I could solve for both of us because causes were the same.
Before I can try to help you, I need some information:
1) do you have knob mismatch after switching lights test on or off? Sometimes several lights tests are neccessary to reproduce the problems)
2) do you have knob mismatch after el. state change?
3) do you have some annunciators connected to the 7 additional outputs on the P2 connector of one or more mastercards (output 49 ... 55)?
sounds as if some cables are mixed up or if you have some wrong assignments in script.
Let's solve one problem after the other and start with DU selector knobs. What happens after starting software and initial DU knob mismatch? When you then turn hardware DU knobs to left and right through all positions. Will software knobs on screen follow exactly the position of the hardware knobs or will software knobs jump to different positions?
RE: OI4FS2024 Duspanel and Servo Gauges - idj4 - 08-06-2026
Hi all
I think I’ve found the problem for the DU mismatch, which seems to occur, mainly, when starting Oi4FS and when using the lights test switch. I’ve also noticed that the N1 Set & SPD Ref rotaries move too when a light test is executed.
I think the culprit is by having the two additional outputs included in the script, these being for the Take Off and Cabin Alt, which are not included on the Opencockpits MIP, but can be added to outputs 54 & 55 on the P2 connector.
Being as the MIP doesn’t have a great amount of inputs & outputs (mines single seat, so it has even less) I decided to create a test script for the MIP by adding 1 input and 1 output at a time. After all the inputs were scripted the problem wasn’t there. It’s when I started to add the outputs the problem returned once I added the Take Off & Cabin Alt. I didn’t delete them from the script, but commented them out….and viola, the problem was gone again.
Not too sure why this is happening, but my next test is to move them from the P2 connector and connect them to the output card, and update the script accordingly, and see what happens… For whatever reason, they seem to be causing a conflict with the PMDG events.
Regards
Ian
RE: OI4FS2024 Duspanel and Servo Gauges - idj4 - 08-08-2026
I have changed the outputs for the TO & CA to outputs 16 & 17. I decided to change output 51 too, for the Speed brake Extended. Although this wasn't causing any problems, I decided not to use the P2 connector at all.
The result is perfect. The mismatch issue has gone. When executing a light test too, everything seems to be ok. As I have only a single side MIP, I don't have the F.O AFDS module, so I'm ok to use outputs 16, 17 & 18 which would otherwise be used on the F.O AFDS.
Hope this helps others with the same problem.
Regards
Ian
RE: OI4FS2024 Duspanel and Servo Gauges - NobbyC_B738 - 08-08-2026
Hi Ian,
I can comfirm your findings regarding P2 connector and that was exactly the reason why I asked that question in my first reply in this thread:
"3) do you have some annunciators connected to the 7 additional outputs on the P2 connector of one or more mastercards (output 49 ... 55)?"
Nothing to do with new variables, that have never been used before in the scrip. I use lots of such variables without any problem. The only reason is the use of the P2 connector. I tried 3 different mastercards and I always have had knob mismatch problems when using P2 connector. Disconnecting P2 and connecting the outputs to J2 connector of another (fourth) mastercard solves the problems immediately. I told my findings to another user, who has DU mismatch problems and he also confirms that he has got rid of the problems after disconnection outputs on P2 and connecting to a free J2 output
As a matter of fact it is a hardware problem and no script problem. I have started to find the real reason for that. But this will take some time because I'm actually rebuilding my complete OVH.
My ideas: during lights test 38 Annunciators are getting +5V over individual wires of the 40 pol. ribbon IDC cable (each appr. 0,02 A). But they all have their common ground connection on only one of these 0.08 mm² wires. That gives the wire 38 x 0,02 A = 0,760 A, what is just about acceptable for such a small wire. But when you have connected 7 additional annunciators on P2 than your card has to manage 45 x 0,02 A = 0,9 A, what may be too much for a wire or conductive track on the circuit board. The wire or conductive track than works as a resistor and for a short time during start of lights test you can have 2 different potentials on the ground track of the mastercard what may end up in uncontrolled switching of inputs. I could see this on SIOC monitor: When doing lights test with 45 annunciators connected to a mastercard, I saw some short flickering on some of the inputs that may be responsible for the uncontrolles switching of some knobs.
Another problem may be the poor PSU delivered by OC. If the PSU is not stable enough, voltage can drop during start of lights test.
As I said I'm actually rebuilding my OVH. What I do is to put 1mm² ground cables in parallel to each ribbon GND wire, and additionally I will connect all cards to a powerful high end PC PSU.
When I have finished I will report if P2 connectors can be used with better voltage stability measures or if P2 still causes trouble.