User Manual - Starting With SC-Pascal Scripts - Rev 1.1
User Manual - Starting With SC-Pascal Scripts - Rev 1.1
User Manual
SC-MAN-SCP-E-11-0009
LOG
INDEX
1 Definitions and acronyms ..........................................................................................................................3
1.1 Definitions .........................................................................................................................................3
1.2 Acronyms ..........................................................................................................................................3
2 Related documentation .............................................................................................................................4
3 Purpose of this document .........................................................................................................................4
4 Introduction to the Scripts.........................................................................................................................4
1 Previous Requirements..............................................................................................................................5
1.1 Connections and Hardware Requirements .......................................................................................5
1.2 Software Interface Requirements (Scripts).......................................................................................8
2 Classification of the Scripts ......................................................................................................................10
2.1 Classification according to the hardware to controlling .................................................................10
2.2 Classification according to the software (simulator) or plugin .......................................................10
3 Running the Script ...................................................................................................................................11
3.1 Running scripts ................................................................................................................................12
3.1.1 FSX with ORION and L4SC ...........................................................................................................12
3.1.2 FS9/PMDG ..................................................................................................................................13
3.1.3 FS9 or FSX with Project Magenta ...............................................................................................13
3.1.4 FS9/FSX with Prosim737 (General Requirements) .....................................................................14
3.1.5 FS9 or FSX with iFLY using iFlyToFsuipc ......................................................................................17
3.1.6 FS9 or FSX with iFLY using IOCP ..................................................................................................18
3.1.7 X-PLANE with PM (XPUIPC).........................................................................................................18
3.1.8 X-Plane with Fran Sedano plugin ................................................................................................19
3.1.9 FS9 or FSX with Sim-Avionics ......................................................................................................19
1.1 DEFINITIONS
Item Definition
Backlight Lighting which illuminates the letters, lines or other features of a panel from the
inside or back of the module.
Switch and Hub Device A device for connecting many Ethernet cables. For use when you want to connect
many Ethernet devices to a single computer.
SC Pascal A programming language and a high level editor/compiler. All script provided by
Sismo are programmed in this language. There are manuals for learning this
language on our website. You can also download the program from our website.
Crossed Ethernet Cable A type of Ethernet cable used to connect a module directly to a computer.
Standard Ethernet Cable If you are using a standard Ethernet cable, you should connect the module to a
Hub/Switch or to your Router (and not directly to the computer)
Mother – Daughter Master – Slave board
Ethernet Local area network data transfer protocol. An alternative to USB.
IOCP Input/output completion port (IOCP) is an API for performing multiple
simultaneous asynchronous input/output operations in Windows NT.
FSUIPC Flight Simulator Universal Inter-Process Communication. For controlling
asynchronous input/output operations in flight simulation.
UDP A protocol within the TCP/IP protocol suite
DHCP Dynamic Host Configuration Protocol, A protocol that provides a means to
dynamically allocate IP addresses to computers on a local area network. To be
deactivated or the IP addresses will change!
Script A program which controls the SC-MB and allows the user to assign the functions of
one of the Plug&Fly Modules (AFT, FWD, etc.) to the Motherboard.
Add-on Company ProSim, iFLy, PMDG. They are companies which interface the hardware with the
flight simulation software.
Autosense a feature found in network adapters that allows them to automatically recognize
the current local network's speed and adjust its own setting accordingly
Plug&Fly Modules Require no building or skills in electronics. They are fully equipped to be installed
on your simulator. They are the FWD, AFT, MIP, Pedestal, MCP and EFIS.
1.2 ACRONYMS
Item Definitions
PCB Printed Circuit Board.
GND Ground – Return path for electric current in a circuit
PRM Plug Ready Module
2 RELATED DOCUMENTATION
The intention of this document is to show the necessary steps for launching the software interface (scripts)
which SISMO Soluciones provides, allowing the connection and communication with the Flight Simulator
used by each user.
Sismo Soluciones provides the necessary script in executable format (.exe) to their
customers, that is to say, with a simple double click on the script, the user will be able
to make it works with his simulator. This way of proceeding is based on the computing
industry of professional software, dispensing of having to open additional programs
and load text files, providing in this respect a major agility of use at the moment of
executing it.
Nevertheless, despite not being the subject of this manual, the scripts can also be edited by means of
programming in SC-Pascal language which specifically has developed Sismo.
In this case and for those users who do not have many computing knowledge but have the illusion to build
a flight simulator and their own scripts, a manual for programmers with many and easy examples can be
downloaded at Sismo web, and also the Sismo FORUM is available to share your doubts and questions.
1 PREVIOUS REQUIREMENTS
The scripts are compatible with any operating system, but for its correct use, it is indispensable to achieve
and bear in mind the following requirements:
1. All the modules, equipments, and PRMs must be well connected and wired. There are 2 ways for
doing it:
a) Acquire one of the SISMO Plug&Fly Modules (MCP-2EFIS, DST, PEDESTAL, FWD-OVH ó AFT-
OVH):
In this case, the equipment is already well wired and connected and the user does not need to
do anything else.
If you acquired a Plug&Fly module: it is VERY IMPORTANT to have already configured your
equipment as the User Manual of the respective Module shows before following the next
instructions.
Below, some of the User Manuals are shown (picture). These manuals contain the instructions
to configure each Plug&Fly Module (available at Sismo Download Section).
It is not necessary to read the b) section if the Module was already configured, so let’s jump to
the section 2 of this chapter for following with the explanations.
b) Connections and wiring using the SimCard Ethernet -> for users who want to wire up the cockpit
Modules by themselves:
The switches, leds, PRMs, modules… must be connected to the SimCard Ethernet exactly equal
as the Contact Map shows. The Contact Map can be asked for whe acquiring the SimCard
Ethernet if the user requires it.
This is VERY IMPORTANT, because if the connections are made in an anarchic manner and
without obey the Sismo Contact Map, the inputs and outputs of the modules will not
correspond with the assigned ones in the script.
Example: hook-up of a FO-DS PRM with a SimCard MB Ethernet using 1 GIC of fast hook-up
without welds and following the CONTACT MAP provide when acquiring the SimCard
ETHERNET.
The simplest way to make the connections is using the GICs (Generally Interface Card) which
facilitate the connections with the different components, because they allow to connect PRMs
with connectors by means of flat cables or allow to connect components through free wiring to
threaded green terminals, so it will not be necessary welds. In this way, the connections are
easy to make, are clean and allow a better maintenance, giving also a bigger reliability to any
solution.
For example, it is possible to do the complete hook-up of all the PRMs of TERAS Main
Instrument Module 737NG with only 4 GICs and 1 SimCard Ethernet without to make any weld
and obeying the Contact Map which the script follows.
Take a look to the next video-link:
http://www.youtube.com/user/SismoSoluciones#p/a/u/1/0ouRsOyB014
Anyway, the user will be able to choose the type of connection which is more convenient for
him but always obeying the mentioned Contact Map.
2. Install the last available Build of SC-Pascal editor/compiler in the control computer (HOST) where
the Module or SimCard Ethernet was configured. The SC-Pascal editor/compiler can also be
downloaded for free from the Sismo Soluciones web.
- The "config.ini" file. It is the configuration file which must be filled out and later saved with the
changes done specifically by each user. Find in the chapter 5 all the instructions in the matter.
- OPTIONAL: a Direct Access of the script, which can be placed at the Auto-Start Windows folder.
Then, the script can be run automatically each time the user switches on the computer which
controls the SISMO Module and the script will be in standby waiting that the Simulator is also
running.
Now, this example shows the interior of a folder which contains a script for MCP-2EFIS TERAS
737NG for FSX by Default and its corresponding "config.ini" and the Direct Access together inside
the same folder:
IMPORTANT: The user must have as many folders as scripts and each of them with its corresponding
"config.ini" file.
To obtain the last upgrade version of the script, ask for it to us at Sismo web Forum www.sismo-
soluciones.com
When a new script update
is gotten, it must be
included in the same folder
as this example shows. But
the user only will be able
to execute one of them.
3. The folder that includes both the script and the file "config.ini" must be stored in the same
computer where the Sismo Ethernet Module was previously configured.
In order to obtain a more wide vision of the types of simulators and plugins for which Sismo Soluciones has
developed scripts, now, a classification of the different types of scripts available and the minimal
specifications necessary for its correct execution is detailed, allowing to facilitate in this respect the suitable
choice:
Each script must be saved in a specific folder with its corresponding "config.ini" file. For example, if you
have 3 scripts for running (MCP-2EFIS, MIM and FWD-OVH), there should be 3 folders, each one with its
corresponding script and its specific "config.ini" file.
In the following table, all the types of simulators and plugins for those that Sismo has developed scripts are
shown. Remember that this is an open list and can be changed constantly according to the new
improvements and creations of new plugins.
In addition, it also appears interesting information for the user about minimal necessary requirements to
achieve by the software (simulator) or plugin like minimal versions as well as the protocol of
communications (FSUIPC, IOCP or XPUIPC) and which version to install in the computer where the simulator
is going to be executed, in order that the information of the simulator could be transmitted through the
script and sent to the hardware.
SIMULATOR
(*1) There are 2 versions of FSUIPC and IOCPServer : one for FS9 and other one for FSX. Proceed to install the one that corresponds, otherwise it will
not work.
(*2) Only it is necessary to place correctly the 'LVLdSDK.dll' file. The instructions are sent to you attached with the script.
(*3) In PMDG, a lot of variables are sent by keyboard, but it is not necessary to worry about this because the script takes charge of everything. The
only thing that it is necessary to do is to configure the keyboard from PMDG (one of PMDG options allows to do it) writing the same 'keys' that in
the script. For that, the document "737Kbd.ini" for PMDG keys appears together with the script. It also can be done through the document which is
attached as "keyboard map.pdf".
Note: these versions must be equal or lower to the versions install by the user because the script will have to
read correctly the information from the simulator.
Once the "config.ini" file was filled out adequately (this task is made
Sismo support before the script is sent to the user), proceed to make
the following steps for launching the script.
A program window will be shown on your screen (see picture on the
right).
IMPORTANT (only when running more than one script): in case to have more than SISMO Modules and in
this way also more than one script, remember that each Sismo Ethernet Module must be configured with a
different Ethernet port (HOST PORT). For better understanding see the example with 2 different scripts (A
and B):
“config.ini” file of the MIM with SimCard Ethernet A.
//------------------------------------------------------------------
// UDP PORT
//------------------------------------------------------------------
[HOST_PORT]
PORT = 1028
Check that the ports were set to different values to avoid conflicts (1028 and 1029). It is necessary to
mention that the same HOST PORT written in the "config.ini" file for each case must also be identified and
saved in the Configuration Page (CONFIG PAGE of SISMO Ethernet Module). e.g.: MIM 1028; FWD-OVH 1029.
NOTE: In case the user uses FSUIPC and launches the script from another computer of his network (but not from the computer where the simulator
was installed), it will have to execute also wideFS correctly configured. The use of wideFS is necessary because FSUIPC characteristics require it. This
is not necessary for IOCP.
3.1.2 FS9/PMDG
Follow these steps to launch the corresponding scripts for FS9/PMDG.
1. Instalar FSUIPC para FS9 (para ello contante con la empresa distribuidora).
2. Edit the “config.ini” file. –This step is done by Sismo Support
before to send the script-
3. Run FS9 with PMDG plane.
3. Run the PMDG MCP-2EFIS script.
3. Run the PMDG MIM script.
3. Run the PMDG FWD-OVH script.
3. Run the PMDG PEDESTAL script.
Follow these steps to launch the corresponding scripts for FS9/FSX and Project Magenta.
1. Install FSUIPC for FS9 or FSX according to the simulator to launch (to do that, please contact with the
distribution company).
2. Install WideFS in case to networked with the scripts from a remote computer (to do that, please
contact with the distribution company).
3. Edit the “config.ini” file. –This step is done by Sismo Support before to send the script-
4. Run FS9 or FSX.
4. Run the 3 Project Magenta programs which are needed: Autopilot MCP Build 446 or superior, GC Build
470 or superior and PmSystems Build 180 or Superior. It is supposed that this software has previously
been configured (to do that, please contact with the distribution company).
4. (Optional for Pedestal) Run “SA_WXR Software” for Radar Panel and “FSPS Software” for Fire Panel and
Cargo (contact to Achilles: www.thefsps.com)
4. Run the PM MCP-2EFIS script.
4. Run the PM MIM script.
4. Run the PM FWD-OVH script.
4. Run the PM PEDESTAL script.
3.1.4.1 MCP-2EFIS with Prosim737 (jump this step if you do not have MCP-2EFIS)
4. Edit the “config.ini” file. –This step is done by Sismo Support before to send the script-Remember that
the SC-PASCAL PORT can be filled out with any available port. 8097 Port will be used by default.
5. Run the Prosim MCP-2EFIS script.
6. Open and configure ProsimMCP.
7. Write the IP Address of the computer where the MCP was configured into the field specially indicated
by ProsimMCP for Sismo MCP. Write also the port 8097 (SC_PASCAL PORT) if in the “config.ini” 8097
was the port leaved by default.
11. At Prosim737, go to “Config->Drivers” and write the IP Addreses of the respective computer where
each Sismo Ethernet Module was configured. Write also the SC-Pascal Port written for each Sismo
Module in the “config.ini”
(e.g.: PEDESTAL: IP Address 192.168.1.100 Port 8093)
MIM
FWD-OVH
AFT-OVH
18. Check that the importation of the “config.xml” was done correctly.
This can be done looking at each servo on the Gauges Prosim737 Tab which you want to control and
check that the servo is edited as IOCP and with a number –see red square above-
E.g.: if the user has a MIP, he will have to configure the Flap and Brake pressure gauges and check that
IOCP and a number is shown at Prosim Gauges Tab –Look to the picture above and check that Brake
pressure has IOCP and 744.
19. Move the status bar of each servo at Prosim Gauge Tab and check that the servo moves mechanically
its needle.
20. Match the status bar of each servo at Prosim Gauge with the mechanically needle of the servo
E.g. 1000 status bar of the Brake pressure at Prosim Gauge Tab must be equal to the 1000 position of
the needle of the Brake Pressure Servo Instrument.
21. Configure all the positions.
22. Save the changes.
Follow these steps to launch the corresponding scripts for FS9/FSX and Project Magenta.
11. Install FSUIPC for FS9 or FSX according to the simulator to launch (to do that, please contact with the
distribution company).
12. Install WideFS in case to networked with the scripts from a remote computer (to do that, please
contact with the distribution company).
13. Edit the “config.ini” file. –This step is done by Sismo Support before to send the script-
14. Run FS9 or FSX.
5. Run iFLY 737NG addon.
6. Run iFlyToFsuipc application.
7. Run the iFLY MCP-2EFIS script.
7. Run the iFLY MIM script.
7. Run the iFLY FWD-OVH script.
7. Run the iFLY PEDESTAL script.
7. Run the iFLY AFT-OVH script.
2. Install WideFS in case to networked with the scripts from a remote computer (to do that, please
contact with the distribution company).
3. Edit the “config.ini” file. –This step is done by Sismo Support before to send the script-
4. Run FS9 or FSX.
5. Run the Sim-Avionics addon. It is supposed that this software has previously been configured (to do
that, please contact with the distribution company).
6. Open the “Sismo Soluciones Fsuipc Offsets” file
7. Open the “FSUIPC_IO.INI” file (C:\Sim-Avionics\Server)
8. Look for each variable of the “Sismo Soluciones Fsuipc Offsets” file into your “FSUIPC_IO.INI” file, and
rewrite the values of each variable according to the values that appears at the “Sismo Soluciones Fsuipc
Offsets” file.
9. Save the changes of the FSUIPC_IO.INI file and close it.
10. Run Sim-Avionics – Server program, and go to the Control Panel tab. Click on the “Use INPUT
Offsets”and “Use OUTPUT Offsets”, and click off “Process Switch Update On Offset Change Only”. See
picture below:
END OF DOCUMENT