Assignment of DCMotors Plus card

[Skycowboy]

Hej,

I'm working with another SIOC-script and a new SIOC.ini to assign my motorized B737 Throttle from OC.
I'm succesfull with the parking brake (servo, light etc.) in connection to MSFS2020/PMDG 737-700. And step by step
I'll try to extend the script and functions until the complet control stand will working.

Now I tried to combine it with my working Oi4FS-PM B737 v5.1.txt, therefore I extended the Oi4FS script with parking brake script lines which are
working as I described above.
My problem is, if I configure Oi4FS for FS PM B737 I get the DCMotors Plus Module to select (step 3.), also - ok, but there is no Panel as step 4. I could assign.
Then I tried to integrate it as follows.
I set the IDX for DCMotors Plus to 14 by main window in SIOC by Config Devices button and changed/extended manually the SIOC.ini MASTER=14,14,1,14 and started SIOC with Oi4FS-PM B737 v5.1.txt again. Unfortunately after start Oi4FS the SIOC.ini was automatically changed, that all before assigned devices are now in brackets and DCMotors Plus device MASTER=14,14,1,14 was activ (means without brackets) only.
How could I integrate my DCMotors Plus device and the needed scripts (parking brake, Flaps etc.) in the very good working Oi4FS application (Oi4FS-PM B737 v5.1.txt).

På forhånd tak og god weekend!
Rolf

[Skycowboy]

Hej,
this day I tried it again. First the basic settings of Oi4FS which are running very well with MSFS2020/PMDG 737-700 and my AFT-and FW-OVH respectively my MCDU (s.SIOC.ini and SIOC Main Window in the attachment).

Then I extendet manually the line MASTER=14,14,1,14, because Config with Oi4FS wasn't possible (no Panel available (s. my post from yesterday above).
After that I reloaded SIOC and in the SIOC Main Window IDX 14 for my DCMotors PLUS device was assigned now and the SIOC.ini included and kept all card assigments (s. SIOC.ini 2 and SIOC Main Window 2),
but now OVH amd MCDU function are disabled. Reloading SIOC didn't changed it.
How could I get this new config in SIOC.ini (entry the DCMotors PLUS card) and simultaneously my hardware is working farther?
Any help or hints are very aprechiated!

SIOC.ini.png (38.93 KiB) Viewed 2289 times

SIOC Main Window.png (30.63 KiB) Viewed 2289 times

SIOC.ini 2.png (39.4 KiB) Viewed 2289 times

[Skycowboy]

SIOC Main Window 2t.png (30.31 KiB) Viewed 2289 times

Best regards
Rolf

[mvr1918]

My problem is, if I configure Oi4FS for FS PM B737 I get the DCMotors Plus Module to select (step 3.), also - ok, but there is no Panel as step 4. I could assign.
Then I tried to integrate it as follows.
I set the IDX for DCMotors Plus to 14 by main window in SIOC by Config Devices button and changed/extended manually the SIOC.ini MASTER=14,14,1,14 and started SIOC with Oi4FS-PM B737 v5.1.txt again. Unfortunately after start Oi4FS the SIOC.ini was automatically changed, that all before assigned devices are now in brackets and DCMotors Plus device MASTER=14,14,1,14 was activ (means without brackets) only.
How could I integrate my DCMotors Plus device and the needed scripts (parking brake, Flaps etc.) in the very good working Oi4FS application (Oi4FS-PM B737 v5.1.txt).

First, if you manually make a configuration file, you should not make it in SIOC.ini but rather in a airplane.ini such as PMDG B737.ini.
This because the SIOC.ini is always overwritten with the content of the airplane.ini when the driver starts if it is initiated from Oi4FS.

You can add the line THROTTLE,IDX14 to Oi4FS.ini to be able to make a configuration

so the end of Oi4Fs.ini looks like
...
AUDIO_R,IDX22
THROTTLE,IDX14
[END]

[Skycowboy]

Hej Roar,

thank you so much for your help!

I added THROTTLE,IDX14 to Oi4Fs.ini as you recommended. Then I configured Oi4FS for FS PM B737 new and I got in step 4.Panels the possibility to dial THROTTEL (s.below), but after clicking Throttel at the end of config process the config window disappeared suddenly automatically.

Then I started Oi4FS with running MSFS2020 and got this SIOC main window (please see below). Now, one client is connected. I think this is the motorized B737 TQ from OC because it's working as a server, too.
What irritates me is the circumstance that IDX 14 is not assigned in the first line of Devices in SIOC main window.
The FS_PM B737.ini please see below, too.
I'm very satisfied, that OVH and MCDU is working furthermore - that's a very nice progress in relation to the non activation some days before.

But, I noticed that "my" by parking brake lines expanded script (I took Oi4FS-PM B737 v5.1.txt) wasn't compiled after start Oi4FS with PMDG B737 driver. Deleting Oi4FS-PM B737 v5.1.ssi from SIOC folder didn't change it Oi4FS respectively SIOC loaded the old Oi4FS-PM B737 v5.1.ssi and didn't compile it new.
How could I create a new actually compiled .ssi file. and will it be a problem, that IDX 14 wasn' assigned under Devices of SIOC, but a (I think) correct entry in the FS_PM B737.ini?

PS Red LED of hardware B737 OC TQ don't illuminated by activating the brake lever/switch.

På forhånd tak og god aften

Config.png (53.05 KiB) Viewed 2281 times

!
Rolf

SIOC - Main Window .png (30.67 KiB) Viewed 2281 times

FS_PM B737.ini.png (35.43 KiB) Viewed 2281 times

[mvr1918]

A link to download a new updated Oi4FS v2.3 that detects the DCMOTORSPLUS card has been PM you.

You can use the SCRIPT page in Oi4FS to compile your modified script from txt to ssi file.

[Skycowboy]

Hej Roar,

that's very kind and I'm looking foreward with updated Oi4FS. I'll keep you informed gladly!

På forhånd tak og god aften!
Rolf

[Skycowboy]

Hej Roar,

very great. You are a genius!
Now the updated Oi4FS version detects the DCMOTORSPLUS and IDX is correct.
Compiling the changed script was succesfull, too and connection respectively Data transfer between B737 TQ OC and MSFS2020 PMDG737-700 seems to work because after setting parking brake by hardware the PRK BRK lever virtuall was moving, too - indeed the virtual PRK BRK lever released immediately,
but I'll change the PRK BRK script lines and I'm sure the complete B737 TQ OC will work step by step.

Med stor taknemmelighed og hilsen!
Rolf

SIOC Main Window 2.png (30.24 KiB) Viewed 2268 times

FS_PM B737.ini 2.png (35.52 KiB) Viewed 2268 times

[Skycowboy]

I got the parking brake from my motorized B737 TQ - OC working by changing your Oi4FS v5.1 script with PMDG 737-700. It was a little bit tricky because there are a few interdependencies like footbrakes in relation to set and release PRK BRK and servo release, delay etc. I use Offsets from FSUIPC respectively Pete Dowson, because I've no other DataRefs or Events/Variables. TOGA switch is working by Offset from FSUIPC, too.

Now, I'm trieing to change your Oi4FS v5.1 script to change it in order to make it suitable to work with my flap lever. I got values from 0 to 16383 if I move the PMDG flap lever (readable by IOCP-Console) and I use the FSUIPC Offset $0BDC (please see script cutout below). I got the same values if I move the B737 hardware flap lever because I set the suitable values in the script.
But unfortunately the virtual flap lever of the PMDG 737-700 didn't move if I move my hardware lever. In the offset table of Pete Dowson I found a notice in relation to Offset $0BDC that it seems a read status, only (maybe).

Would it be possible to use your EVENT Var 2857 FLAPS_DECR and Var 2858 FLAPS_INCR and if yes, I'm not sure whether it will depict the 8/9 "notch" of flap lever or switch step by step without to consider the order? And, how could I integrate this EVENT in my script lines?

Flaps TQ OC.7z

(554 Bytes) Downloaded 145 times

I hope, you could help me or give me an advice, again.

Med stor taknemmelighed og god dag!
Rolf

[mvr1918]

No need to use FSUIPC.

All Controll Stand settings can be controlled via these SIOC events:

using value -1 will work for most of them

2321 = CONTROL_STAND_AT1_DISENGAGE_SWITCH
2322 = CONTROL_STAND_AT2_DISENGAGE_SWITCH
2323 = CONTROL_STAND_ENG1_START_LEVER
2324 = CONTROL_STAND_ENG2_START_LEVER
2325 = CONTROL_STAND_FLAPS_LEVER
2326 = CONTROL_STAND_FLAPS_LEVER_0
2327 = CONTROL_STAND_FLAPS_LEVER_1
2328 = CONTROL_STAND_FLAPS_LEVER_10
2329 = CONTROL_STAND_FLAPS_LEVER_15
2330 = CONTROL_STAND_FLAPS_LEVER_2
2331 = CONTROL_STAND_FLAPS_LEVER_25
2332 = CONTROL_STAND_FLAPS_LEVER_30
2333 = CONTROL_STAND_FLAPS_LEVER_40
2334 = CONTROL_STAND_FLAPS_LEVER_5
2335 = CONTROL_STAND_FWD_THRUST1_LEVER (use 2815)
2336 = CONTROL_STAND_FWD_THRUST2_LEVER (use 2816)
2337 = CONTROL_STAND_HORN_CUTOUT_SWITCH
2338 = CONTROL_STAND_PARK_BRAKE_LEVER
2339 = CONTROL_STAND_REV_THRUST1_LEVER (use 2815)
2340 = CONTROL_STAND_REV_THRUST2_LEVER (use 2816)
2341 = CONTROL_STAND_SPEED_BRAKE_LEVER ( 8192 will move up, 16384 will move down)
2342 = CONTROL_STAND_SPEED_BRAKE_LEVER_DOWN ( -1 will set )
2343 = CONTROL_STAND_SPEED_BRAKE_LEVER_ARM ( -1 will set )
2344 = CONTROL_STAND_SPEED_BRAKE_LEVER_50PCT ( -1 will set )
2345 = CONTROL_STAND_SPEED_BRAKE_LEVER_FLT_DET ( -1 will set )
2346 = CONTROL_STAND_SPEED_BRAKE_LEVER_UP ( -1 will set )
2347 = CONTROL_STAND_STABTRIM_AP_SWITCH
2348 = CONTROL_STAND_STABTRIM_AP_SWITCH_GUARD
2349 = CONTROL_STAND_STABTRIM_ELEC_SWITCH
2350 = CONTROL_STAND_STABTRIM_ELEC_SWITCH_GUARD
2351 = CONTROL_STAND_TOGA1_SWITCH
2352 = CONTROL_STAND_TOGA2_SWITCH
2353 = CONTROL_STAND_TRIM_WHEEL ( 8192 will move up, 16384 will move down)


2815 = THROTTLE1_LEVER (0-16383 set Throttle1 Lever, - -4096 set REVERSE1 LEVER)
2816 = THROTTLE2_LEVER (0-16383 set Throttle2 Lever, - -4096 set REVERSE2 LEVER)