Need testers for 737 systems simulator software

[bagarie]

Hi Marty,

thanks for reply.
I know as upgrade the firmware. But the only problem is that the 3.01 dont' work with the Old driver for PMDG that I'm still using.
anyway it's a my problem..
You have a PM.

Regards
Arnaldo Vacca

[Air Canada]

HI Marty
have a question.
when I run prosim737 and go to the config menu (File--->config) then go to the Switches tab to enter a state. For example I'm configuring a Taxi Light Switch.
So I go scroll down to Lights Taxi option. Now there are 2 optons. 1 for off and the other for on.
So I guess I have to select only 1 option which will be Lights Taxi On (correct) and then from the next column, I select IOCP from the drop down list (since I'm using O/C cards and using SIOC) and then on the next column I enter the var # (which for example in my case is var 101)...

now here's where I get confused when I generate a sioc stub.

this is what is shows up as
Var 0101, Link IOCARD_SW, Input 141 // Lights taxi Off

this is the strange part I don't get is the comment line (Lights Taxi Off )

why is it putting a comment as Off when I selected the On option in the config--->switch tab.

and the rest are exactly the same..

Meaning, all the switches that have 2 states (Off and On) I have only selected the On state and when I generate a sioc stub, the comments are show as Off. So this is gettting confusing for me when I'm editing the sioc stub to enter my inputs for the switches.

Do I have manually go and change the Off comment to On when I edit the sioc stub.

I do realize that the comment string plays no part as t's only a comment, but the comment part helps when I'm editting the stub and to know which input# goes with which switch.. But the Off comment is always confusing or am I ding somehting wrong..

thanks.

AC

[metamarty]

HI Marty
have a question.
when I run prosim737 and go to the config menu (File--->config) then go to the Switches tab to enter a state. For example I'm configuring a Taxi Light Switch.
So I go scroll down to Lights Taxi option. Now there are 2 optons. 1 for off and the other for on.
So I guess I have to select only 1 option which will be Lights Taxi On (correct) and then from the next column, I select IOCP from the drop down list (since I'm using O/C cards and using SIOC) and then on the next column I enter the var # (which for example in my case is var 101)...

now here's where I get confused when I generate a sioc stub.

this is what is shows up as
Var 0101, Link IOCARD_SW, Input 141 // Lights taxi Off

this is the strange part I don't get is the comment line (Lights Taxi Off )

why is it putting a comment as Off when I selected the On option in the config--->switch tab.

and the rest are exactly the same..

Meaning, all the switches that have 2 states (Off and On) I have only selected the On state and when I generate a sioc stub, the comments are show as Off. So this is gettting confusing for me when I'm editing the sioc stub to enter my inputs for the switches.

Do I have manually go and change the Off comment to On when I edit the sioc stub.

I do realize that the comment string plays no part as t's only a comment, but the comment part helps when I'm editting the stub and to know which input# goes with which switch.. But the Off comment is always confusing or am I ding somehting wrong..

thanks.

AC

Hello,

This is indeed a bug. Fortunately, it only happens witch some switches. I have already fixed it, so in won't happen in the next release.

[colossos]

Hallow Marty

I use fsx with fsuipc register and MCP – cdu – efis – usb servo – usb outputs – multiradio hardware all from opencockpits in two pc.
1 pc
Fsx – Fsuipc – cdu hardware - prosim737– prosim cdu – prosim MCP

2 pc
MCP – Efis – multiradio – usb servos – usb outputs – prosim display – fsuipc wide client – BU0836X card

I have built my own cockpit (captain’s side) and I used the prosim737 and all combine almost perfect. In MCP – EFIS I used your script which works perfect. In USB Servo & USB Outputs I use my own script which also works perfect. However I have a small problem when I run prosim with my USB Outputs because the A/P signaling in Captain's annunciators don’t operate by my script when I engage the A/P; in antithesis with A/T which operate normal with my script. Of course in my script I use the IOCP & FSUIPC offsets. So is there any mode to fix this small problem?

Also I want to ask you something else. I have FSUIPC and I have install BU0836X card in my second PC and with this card via Widefs I can manage some switches in FS. The question is why the prosim don’t see this card but only my joystick (installed in first PC) and second in configuration panel of prosim737 you have some sections for Switches indicators and others. What can I do with that that I can’t do it with Fsuipc or it is there for some other reason? To make a script for example? I don’t know I tried to read some other post to understand but I am still confused. Can you give me an example so as to understand what I can do with this ability’s?

Thank you

[metamarty]

Hallow Marty

I use fsx with fsuipc register and MCP – cdu – efis – usb servo – usb outputs – multiradio hardware all from opencockpits in two pc.
1 pc
Fsx – Fsuipc – cdu hardware - prosim737– prosim cdu – prosim MCP

2 pc
MCP – Efis – multiradio – usb servos – usb outputs – prosim display – fsuipc wide client – BU0836X card

I have built my own cockpit (captain’s side) and I used the prosim737 and all combine almost perfect. In MCP – EFIS I used your script which works perfect. In USB Servo & USB Outputs I use my own script which also works perfect. However I have a small problem when I run prosim with my USB Outputs because the A/P signaling in Captain's annunciators don’t operate by my script when I engage the A/P; in antithesis with A/T which operate normal with my script. Of course in my script I use the IOCP & FSUIPC offsets. So is there any mode to fix this small problem?

How did you configure these items in Prosim737? By default there is no output for the indicators. You'll have to tell Prosim737 what to do with the indicators. This can be an FSUIPC offset or a SIOC variable.

Also I want to ask you something else. I have FSUIPC and I have install BU0836X card in my second PC and with this card via Widefs I can manage some switches in FS. The question is why the prosim don’t see this card but only my joystick (installed in first PC) and second in configuration panel of prosim737 you have some sections for Switches indicators and others. What can I do with that that I can’t do it with Fsuipc or it is there for some other reason? To make a script for example? I don’t know I tried to read some other post to understand but I am still confused. Can you give me an example so as to understand what I can do with this ability’s?

Thank you

Prosim737 will list all gamedevices that have been connected to the computer that it runs on. To use the inputs from the badnar card, you will need to connect it to the computer running Prosim737.

The configuration items are to tell Prosim what to do with the specific inputs and outputs. Prosim737 is a complete simulator, so it contains all the switches and indicators. FS may have some of these too, but if you run Prosim, they are not used. I would advice not to use FSUIPC for switches and indicators whereever possible. It best to let Prosim737 connect directly to SIOC to set variables. This is a faster and more failsafe communication system.

You may also consider moving all the hardware control to your main FS computer and only use PC 2 for ProsimDisplay. This will keep all the IO and hardware connection on one PC.

[hark40]

Hello Marty,
I am running MCP, ASA panel and Master Lights panel (from Sismo Solutions)with a config.xml file and two SC-Pascal script which connects with Prosim and FSX.
Everything works ok using IOCP offsets but when moving CRS FO encoder the button "Recall" is activated automatically without pressing it. Happen the same when moving IAS encoder with the "ASA Test Capt 1" and "ASA Test F/O 1".

do you know why can it happen?
Thank you

[metamarty]

Hello Marty,
I am running MCP, ASA panel and Master Lights panel (from Sismo Solutions)with a config.xml file and two SC-Pascal script which connects with Prosim and FSX.
Everything works ok using IOCP offsets but when moving CRS FO encoder the button "Recall" is activated automatically without pressing it. Happen the same when moving IAS encoder with the "ASA Test Capt 1" and "ASA Test F/O 1".

do you know why can it happen?
Thank you

Hello,

This is something that you will have to ask Sismo, as they did the complete support for it. I currently don't know what the sismo config looks like. I can give you some general advice though. If you look int the main Prosim737 window under the tab "Warning", you will see the the recall buttons. They are probably grayed out, meaning that they are under hardware control. If you move the MCP knobs, you should check if the recall drop down moves to "Pushed". If this happens, then the recall button gets triggered, so the IOCP variable linked to it was activated by the SC-Pascal script. Unfortunately, I don't have the SC-Pascal scripts or the configuration that they give you, so I cannot be of more assistance.

[colossos]

How did you configure these items in Prosim737? By default there is no output for the indicators. You'll have to tell Prosim737 what to do with the indicators. This can be an FSUIPC offset or a SIOC variable.

Hi marty

In my script I have configured the output to operate from “0810” FSUIPC offset for the A/T signaling in MIP. Now with prosim when I push N1 to ON in my MCP hardware; the A/T switch in FSX go ON so the offset change and by this way casually and my led is going on and off by my script.
But in case of A/P signaling because when I engage A/P by prosim nothing happened in FSX that’s why my script don’t see the offset chance.

Prosim737 will list all gamedevices that have been connected to the computer that it runs on. To use the inputs from the badnar card, you will need to connect it to the computer running Prosim737.

The configuration items are to tell Prosim what to do with the specific inputs and outputs. Prosim737 is a complete simulator, so it contains all the switches and indicators. FS may have some of these too, but if you run Prosim, they are not used. I would advice not to use FSUIPC for switches and indicators whereever possible. It best to let Prosim737 connect directly to SIOC to set variables. This is a faster and more failsafe communication system.

You may also consider moving all the hardware control to your main FS computer and only use PC 2 for ProsimDisplay. This will keep all the IO and hardware connection on one PC.

Any way I tried to configure by the “indicators MCP/Throttle” but unfortunately I didn’t make it. I put in MCP CMD A (for example) the offset in 8 bit u 0x07BC but nothing at all. Maybe I didn’t make something right. I don’t know

Also I tried to configure some switches but except lights I didn’t make it too. By the way in “switches” section why we need except the joystick inputs; an FSUIPC offset or a SIOC variable. I mean when I want to config a switch; it will be probably with one of my joystick switches. Why I will need the FSUIPC offset or a SIOC variable?

thank you

[metamarty]

Hi marty

In my script I have configured the output to operate from “0810” FSUIPC offset for the A/T signaling in MIP. Now with prosim when I push N1 to ON in my MCP hardware; the A/T switch in FSX go ON so the offset change and by this way casually and my led is going on and off by my script.
But in case of A/P signaling because when I engage A/P by prosim nothing happened in FSX that’s why my script don’t see the offset chance.

Prosim does not use the FS autopilot, so you will not see much by looking at FSUIPC offsets. I believe you are using an OpenCockpits MCP, so all lights and switches are handled by the Prosim MCP SIOC script. This is where you will find all the indicators. If you are using an opencockpits MCP, there is no need to change anything, because it will work out of the box with the provided SIOC script. If you need any access to the indicator information, you can change the ProsimMCP SIOC script.

Any way I tried to configure by the “indicators MCP/Throttle” but unfortunately I didn’t make it. I put in MCP CMD A (for example) the offset in 8 bit u 0x07BC but nothing at all. Maybe I didn’t make something right. I don’t know

This may be a bit unclear, but by default ProsimMCP does not use the switches and indicator configurations in Prosim737 because most people simply connect ProsimMCP to a hardware panel. Allways reading the switches from Prosim737 would interfere with the hardware panel, so it is turned off by default. If you want to use these configuration items, open the ProsimMCP configuration panel and check "Control via Prosim737 configuration". The lights will then work.

Also I tried to configure some switches but except lights I didn’t make it too. By the way in “switches” section why we need except the joystick inputs; an FSUIPC offset or a SIOC variable. I mean when I want to config a switch; it will be probably with one of my joystick switches. Why I will need the FSUIPC offset or a SIOC variable?
thank you

Prosim is very flexible in configuration. It is basically a box with lights and switches. You only need to tell Prosim how you want to control the switches. This can be any way you want and not every combination seems logical. I can imagine some obscure company providing a panel for FS with a driver that is setting FSUIPC variables and cannot do anything else. You can then tell prosim to pick up the settings from there. Opencockpits works with SIOC, so people connecting switches with OpenCockpits hardware will get SIOC variables that represent their switches and this can be configured too.

To make your switches work, you should always ask yourself "How are the switches communicatin with the computer?". You then configure this in Prosim and check if it works. Most switches will work best with Phidgets, joystick cards and SIOC. As a last resort, you can use FSUIPC input.

[colossos]

Hallo Marty

I thing we have a miss understood here by my fault maybe. So I will try to make clear what is the real problem that I have.
First of all I have to tell you that my opnecockpits MCP hardware operate with prosim 737 MCP and your script; marvelous just marvelous like all the others efis; fmc. So it does not need to change anything.
Also I use BU0836X joystick card and it is connected with the prosin737 in “IO Modules” section. Also I can see that if I go prosin737 file configswitches; I can see my card on the list.
Besides I can configure the switches (I have tested it) who concerning lights but nothing else. And here is the problem. Why I can not config other switches “APU” for example (I have test a lot off) since I am doing the same procedure with the same card? That’s my first problem.

Now as for the second I attach you a photo to help to realized what exactly my problem is.

Thank you for your bearing