Manual SP english translated
Page 1
X52Pro_Tool IL2 + V1.00
1.
Program Purpose
This program gets the plane we're flying in 'IL2 Sturmovik 1946' all data
we want out of all the simulator can be facilitated through
'DeviceLink' and based on these:
•
Take the appropriate format to the desired data and displays in MFD
X52Pro, grouped into pages.
•
Sets the color settings and flashing leds all possible
the X52Pro, according to the parameters.
It also allows the use of the wheel to the right of the MFD to assign the
desired commands from the extensive list provided by the 'DeviceLink'. And have three
more on our X52Pro buttons (wheel up, wheel down and touch wheel) where
As an example we could assign one of the trim of the aircraft.
2. Some images
Tool for
IL-2 Sturmovik 1946 + Saitek X52Pro's MultiFunctionDisplay and Lights
V 1.00
37 ° 22'44 .65''N 6 ° 07'52 .17''W
© E69_Pon (JL Nogales)
Train down and led
blinking amber
Page 2
3. System Requirements
The hardware requirements for running the program are minimal. For a
idea, say that with my current machine is quite impossible to me to put the simulator mode
even close to 'perfect' and yet the program did not steal a single 'fps'.
I have a laptop with Centrino Duo processor T5200 at 1.6 GHz with 2 GB of RAM and a
Intel 945GM graphics card 128MB of shared memory. If someone wants to give me something
better ..., you know ;-)))
On the software side, commenting that use 'Windows XP Media Centre 32bit SP3 and
Directx 9. I could not test the program on other operating systems or 64 bits, but
I think that a priori should work without problems.
4. Terms of Use and License
The program will offer free, though subject to the User License Agreement
Final to be included in the package.
It's for personal and noncommercial use.
Although I have the utmost care so that no errors or viruses, I offer no warranty or
responsibility for its use.
Advise you to read all the details in the attachment 'CLUF.pdf'
5. Introduction
The program I developed using the 'Microsoft Visual Studio C + + 2008 Express Edition'.
I have used communication 'sockets' to deploy the client that contacts the
server 'DeviceLink' of the simulator. I have also used as reference documentation
'DirectOutput' Saitek SDK to manage the MFD and the LEDs of X52Pro. Also, use
also the 'DirectInput' DirectX9 SDK from Microsoft to manage some commands or
parameters that are not accessible via 'DeviceLink'.
The application does not need installation. Decompresses the entire contents of the package 'rar' in
a folder and run from there.
The first thing to do is set how you want the program to behave
by editing a text file. Included as an example the file 'My config.ini'.
How to use is something we discussed in the next section, although it should be noted that all
the world must at least indicate it your IP address (necessary for the use of DeviceLink).
The second is to connect the X52Pro. After running the program.
Immediately turn off the lights and the MFD HOTAS shows:
Simultaneously, the PC will open the following window:
Page 3
where we are asked the name of the text file that we will set up earlier (if
Pressing 'Enter' will use the default file 'My config.ini').
If there are errors in the configuration file, after rebooting the simulator and already in full
mission, you should see something like this in the PC
while the MFD X52pro the first page should appear that we
set and the LEDs will light up as we have indicated (see section 2).
To change the page on the MFD, use the wheel that is on your left, rotating
up or down.
To exit the program normally, if we expect to show up as
last message 'Press any key if you want success ...' and having as the active window
application just press any key and follow the signs.
I know many people do not like the interface of the program on the PC is in a
DOS window, but do not have time to learn to program in a
'Visual environment' and how little we ask for this window, I had only to be functional. So
I'm very sorry.
Page 4
6. Structure and editing of the text file that configures the
program
First indicate that this text file can have the name and extension
we want. Anyway, I recommend that the file that we use most often
call 'My config.ini' because they can load without having to write your name,
only by pressing 'Enter' key.
I have included a file 'My config.ini' sample recommend having open while
we see the following explanations.
Lines beginning with the character '*' are comments that do not affect the program.
Section [SOCKET]
This section is the only indispensably must modify the program to
to work.
We must enter the IP address is assigned to your PC, in my case is
192.168.1.128. This can be seen by opening a DOS window and running the command
'Ipconfig'.
If the IP is not correct, the program will be blocked waiting for communication after
enter the name of the configuration file and have to interrupt forcing the closure of
the window.
As a port number (Port), we can put for example 10000.
In addition, both the value of IP as the Port should be included in the file 'conf.ini' of the simulator,
under the [DeviceLink]. In my case looks like this:
[DeviceLink]
port = 10000
IPS = 192.168.1.128
In the 'Frequency', indicating the time in milliseconds that must elapse between each
iteration of data capture and presentation of the program. With a value of 200, not noticeable
performance gap between the aircraft and controls the display in the MFD and the LEDs,
keeping the PC without significant overhead.
This frequency is also directly related to the frequency of blinking
configured as flashing LEDs.
Section [PARAMETERS]
This section is where you indicate if you want a parameter in the file listings
is displayed on the MFD, which is assigned to an LED behavior, they become both
things at once or do not do anything with it.
This allows us, if we want, clean the simulator screen messages, since the data
appear there, and we seem to us important to move the X52Pro. We
well, in my view, a more realistic simulation.
To disable these messages from the simulator, simply put in the file 'conf.ini' the 'IL2
Sturmovik: 1946 'value' NoHudLog 'in the [game] to 1.
The format of the [PARAMETERS] is as follows (copied from 'My config.ini'):
P = Parameter / MFD Page N / MFD Line N / LED Tag / Off Color / Flash Off / Color On / Flash On / Color
While / Flash While / While value Start / End While value
In the file 'My config.ini' I further clarification on the values ??'While value Start' and
'While value End' which do not correspond with those included in the file 'DeviceLink.txt' of
simulator.
Let's explain with some examples:
Page 5
Temp_oilout engine P = 1 / 2 / 2 / POV 2 / off / N / network / Y / amber / N / 125 / 128
o The parameter here is the temperature of engine oil output # 1.
o MFD page showing the value is 2.
o MFD line showing the value in the page 2 is # 2.
o led the 'POV 2' will behave according to the values ??of the temperature of the oil.
o The LED is off ('off') when the temperature is below 125 ° C (see section
[UNITS]).
The LED will not blink or intermittently ('N') when the temperature is below
125 ° C, although in this case would not matter if it had been since we do because the color
indicated is off ('off').
o The LED is lit in red ('red') when the temperature exceeds 128 ° C (see
the [UNITS]).
o The LED will blink yes ('Y') when the temperature is above
128 ° C. Logically flashes red ('red').
o The LED is lit in amber ('amber') when the temperature is equal to or greater
at 125 ° C and less than or equal to 128 ° C.
The LED will not blink or intermittently ('N') when the temperature is equal to or
above 125 º C and less than or equal to 128 ° C.
P = azimuth / 1 / 1 / / off/N/green/N/off/N/10/350
o The parameter here is the magnetic bearing or azimuth.
or is shown on page 1 and line 1 of the MFD.
or not assigned any led to his behavior, because the field with the label led
empty (no matter the program so the possible configuration of the LEDs that
come later).
P = speedometer_indicated / / / Toggle 1_2 / network / Y / off / Y / network / N / 250 / 300
o The parameter here is the IAS (Indicated Air Speed).
or not displayed on the MFD as the page and line camps are empty.
o LED 'Toggle 1_2' will behave according to the values ??of the IAS.
o The LED is red ('red') when the speed is less than 250 km / h (see section
[UNITS]).
The LED flash or self ('Y'), naturally in red ('red'), when the speed is less than
250 km / h.
o The LED is off ('off') when the speed is greater than 300 km / h (see section
[UNITS]).
o LED does not blink when the speed is greater than 300 km / h, although it has
since we do ('Y') as the color indicated is off ('off').
o The LED is lit in red ('red') when the speed is greater than or equal to
250 km / h is less than or equal to 300 km / h.
The LED flashes or not ('N') when the speed is greater than or equal to 250 km / h is
less than or equal to 300 km / h.
P = variometer / / / / red/Y/amber/N/red/Y/-20/20
o In this case it shows the rate of rise in the MFD and neither assigns its
no LED behavior as page fields, line and led are empty. To the
be empty latter despises the rest of the software configuration of fields
led.
P = time of day / 5 / 3
o This type of parameter, in this case the time of day in the simulator can only be
in the MFD. The control of the LEDs is not accessible because the nature of value I
seemed appropriate to do so. In this example, the time is displayed on page 5 and the
Line 3 of the MFD.
P = Boost (WEP) On-Off / / / Fire D / green / N / network / Y
o In this kind of parameter does not apply a range 'while', as it only has two
states, on or off. In this example, shown in the MFD if the
Emergency power is active or not, but the led 'Fire D' indicates when it is in
Page 6
green ('green') and without flash ('N') that is off and when it is red ('red')
and intermittent ('Y') is turned on.
The maximum number of pages that can be displayed on the MFD is 37. The maximum number
of lines per page is 3.
The list of possible names of the LEDs is as follows (the POV 1 is not configurable):
•
Fire
•
Fire A
•
Fire B
•
Fire D
•
Fire E
•
Toggle 1_2
•
Toggle 3_4
•
Toggle 5_6
•
POV 2
•
Clutch
•
Throttle
The list of possible colors of the LEDs is:
•
off
•
network
•
green
•
amber
The colors of the LEDs 'Fire' and 'Throttle' are not controllable, can only be shut down or
on. Any of the labels 'red', 'amber' or 'green' the flash and the 'off' the
off. The color depends on the position of the guard button 'Fire' and the situation
throttle respectively. The flash itself is operative in both cases.
The possible values ??for the intermissions are 'Y' (intermittent activity) or 'N' (disabled
flashing).
There are some parameters that are not easy when we are flying the simulator 'online', in the
File 'My Config.ini' shows what they are. However, I use the mod 'DeviceLink_2_1' to
remedy this wrong decision by the developers of the simulator, in my
humble point of view, and to obtain these values ??well when I'm flying
'Online'.
I do not remember right now the link to the author of this great mod, but
'Google' with 'DeviceLink_2_1' I must find it easily.
I use the 'SAS ModActivator 3.6' and the 'HSFX 1.5' and it works beautifully
with both 'packs'. If anyone has any doubts ask the wing 'IL2' of
Forum 'Escuadrón69' to which I belong and I will answer here.
Section [UNITS]
This section is where we want to choose which units to display the different
parameters in the MFD.
The possible values ??are:
•
Metric
•
UK
•
USA
•
USSR
•
Japan
•
Jap-knot
Page 7
IAS parameter For example, if we choose to 'Metric' is in 'km / h', whereas if we
UK is in 'mph'.
You can choose the value you want regardless of the plane you want to fly.
Section [AIRPLANE]
This section exists to address the limitations of the 'DeviceLink' of the simulator to
in obtaining data on certain parameters. See item 7 of this manual for
more detailed description.
To make the program work properly, we must include, if there is already a line with
data plane that we fly. I have included data from all aircraft
came up simulator version 4.08 (or was it 7.4?). If the line does not exist and run
the program and a mission that airplane in the simulator, the software is close but
providing the name the 'DeviceLink' assigned to that plane.
The format of the [AIRPLANE] is as follows (copied from 'My config.ini'):
A = Name airplane by DeviceLink / / Radiator states / / Quantity of engines / / Prop. Auto pitch / / Mixture
control
Eye separation now the character of the various fields is / /
The first field is the name of the plane that provides the 'DeviceLink', I've said before how
get it.
The second field contains the various stages that the radiator may have under the plane
(Provided of course that the radiator is not assigned to an axis in the simulator). You can have the
following values:
•
Not
•
Auto-Closed-2-4-6-8-Open
•
Closed-2-4-6-8-Open
•
Closed-Open
The third field indicates the number of aircraft engines. It can be any value from 1 to 8.
The fields described below included with a view to future versions of
program.
The fourth field is to indicate whether the airplane has a position 'auto' in the Propeller Pitch.
The possible values ??are 'No' and 'Yes'.
The fifth field is to indicate the different stages of the aircraft allowed in the mix
fuel / air. The possible values ??are:
•
Not
•
100-120
•
0 ... 120
Section [KEYS OUT IL2 MFD]
I already mentioned in point 1 of this document that one of the objectives of the program was
allow the use of the right wheel of the MFD to assign the desired commands from the
extensive list provided by the 'DeviceLink'. Such a 'rotary' functions as if it were three
separate buttons.
The format of this section is:
M = MFD's button / Action name
Page 8
The first field refers to each of the three buttons that make the wheel.
You can have the following values:
•
Button Up MFD
•
MFD Button Down
•
Select Button MFD
The first value is the upward turn of the wheel, the second downward turn and the third
Pressing the wheel.
The second field refers to the commands of the simulator we can assign each
one of the three buttons above. These actions may be:
•
Radiator Up, +20%
•
Radiator Down, -20%
•
Select Engine Up, all-> left-> right-> 1 ... 8 (depending on number of aircraft engines)
•
Select Engine Down, 8 ... 1 (depending on number of aircraft engines) -> right-> left-> all
•
Power Up, +10%
•
Power Down, -10%
•
Flaps Up, +10% crossing trough 'takeoff'
•
Flaps Down, -10% trough crossing 'takeoff'
•
Weapon 1 On / Off
•
Weapon 2 On / Off
•
Weapon 3 On / Off
•
Weapon 4 On / Off
•
Weapon 1 +2 On / Off
•
Gunner Fire On / Off
•
Instant View with Padlock Forward On / Off
•
Online Rating On / Off
•
Radio Mute Key On / Off
•
Right Aileron, +10%
•
Left Aileron, -10%
•
Elevator Up, +10%
•
Elevator Down, -10%
•
Right Rudder, +10%
•
Left Rudder, -10%
•
Brakes Up, +10%
•
Down Brakes, -10%
•
Pitch Prop Up, +10%
•
Prop Pitch Down, -10%
•
Right Aileron Trim, +5%
•
Left Aileron Trim, -5%
•
Elevator Trim Up, +5%
•
Elevator Trim Down, -5%
•
Rudder Trim Right, +5%
•
Left Rudder Trim, -5%
•
Level Stabilizer
•
Toggle Engine
•
Boost (WEP) On / Off
•
Magneto Next
•
Prev Magneto
•
Supercharger Next Stage
•
Prev Supercharger Stage
•
Fire Extinguisher
•
Prop. Feather
•
Gear Up / Down
•
Rise Gear Manually
•
Lower Gear manually
•
Airbrake
Page 9
•
Tail Wheel Lock
•
Jettison Droptanks
•
Attach / Detach Aircraft
•
Gun Pods Toggle On / Off
•
Toggle Sight Mode (Auto)
•
Increase Sight Distance
•
Decrease Sight Distance
•
Adjust Sight Control to Right
•
Adjust Sight Control to Left
•
Increase Sight Altitude
•
Decrease Sight Altitude
•
Increase Sight Velocity
•
Decrease Sight Velocity
•
Open / Close Canopy
•
Arresting Hook Toggle
•
Toggle Chocks
•
Pilot or Gunner Position
•
Jump to Cockpit # 1 (Pilot)
•
Jump to Cockpit # 2
•
Jump to Cockpit # 3
•
Jump to Cockpit # 4
•
Jump to Cockpit # 5
•
Jump to Cockpit # 6
•
Jump to Cockpit # 7
•
Jump to Cockpit # 8
•
Jump to Cockpit # 9
•
Jump to Cockpit # 10
•
FOV 90
•
FOV 85
•
FOV 80
•
FOV 75
•
FOV 70
•
FOV 65
•
FOV 60
•
FOV 55
•
FOV 50
•
FOV 45
•
FOV 40
•
FOV 35
•
FOV 30
•
Toggle FOV
•
Increase FOV
•
Decrease FOV
•
Cockpit View
•
No Cockpit View
•
External View
•
Next Friendly View
•
View Next Enemy
•
Fly-by View
•
Padlock Enemy
•
Padlock Friendly
•
Padlock Enemy Ground
•
Padlock Ground Friendly
•
Next Padlock
•
Previous Padlock
•
External Padlock, Enemy Air
•
External Padlock, Friendly Air
Page 10
•
External Padlock, closest Enemy Air
•
External Padlock, Enemy Ground
•
External Padlock, Friendly Ground
•
External Padlock, closest Enemy Ground
•
Chase View
•
Next Chase Friendly View
•
Chase View Next Enemy
•
Toggle gunsight
•
Seat Position Toggle
•
Toggle Autopilot
•
Toggle Level Autopilot
•
Bail Out
•
Tinted Reticle Dimmer (German Plans)
•
Cockpit Lights
•
Toggle Nav. Lights
•
Toggle Landing Light
•
Wingtip Toggle Smoke
•
Toggle Map
•
Chat
•
Ratings Next Page
•
Speed ??Toggle Bar
•
Toggle Icon Types
•
Mirrors Toggle Show / Mode
•
Quick Start / Save Track
•
Mute
•
Radio Channel Switch
•
Accelerate Time x2/x4/x8
•
Normal Time
•
Decelerate Time x2/x4
•
PauseGame
•
Time Skip
When a command works incrementally, I've included after the command name
a semicolon and then the value in% of the increase.
7. Limitations on the 'DeviceLink' simulator
•
It is able to provide position data found in the radiator.
•
Not able to tell which engine is the one selected.
•
Although the information from the simulator does not say, the 'DeviceLink' is only able to
provide the number of engines when we are 'offline' and not when we are online.
•
Not able to detect when the propeller pitch set to 'auto' or 'manual'.
Also can not set the mode 'auto' or 'manual' with 'DeviceLink'.
•
No permit or know what state the mixture is not adjusted.
•
Command does not work 'Toggle Wing Fold' even though a priori contained in the file
'DeviceLink.txt' of the simulator.
The first two points that I could afford with the commands I've created for this purpose,
but they must meet certain requirements:
•
The parameter 'radiator' gives information only through the MFD or the leds when, for
control the radiator, use the commands I've created 'Radiator Up' and 'Radiator
Down 'and are assigned to buttons on the right wheel of the MFD. In addition, for
the information is correct, you can use the control commands
radiator has a built in simulator under 'Controls'.
•
The parameter 'selected engine' only gives information via LEDs or MFD
when, for selecting the motor, use the commands I've created 'Select Engine
Page 11
Up 'and' Select Engine Down 'and are assigned to buttons on the right wheel of
MFD. In addition, for the information is correct, you can not use the commands
engine selection has a built in simulator under 'Controls'.
The commands 'Radiator Up' and 'Radiator Down' allow the handling of the radiator without using the
cyclic command brings the simulator (if not using, of course, the option to assign an axis
that brings the new version of IL2 4101). So if we for example the radiator to 60% for
40% download with 'Radiator Down' to go there first by 80%, for 'open', for
'Closed' and 20%. With one touch I place in 40%.
The parameter 'selected engine', which displays on the MFD selected motors in
conjunction with the command 'Select Engine Up' and 'Select Engine Down', offer a new
ability to control Polymotor. I have always visible on the engine or engines MFD
current and I can change from one to another easily with the wheel of MFD.
The third point I've solved it by telling the program the number of engines via the file
configuration. I did so because not everyone will want to use the mod 'DeviceLink_2_1'
when flying 'online'.
About the fourth and fifth point I'm thinking about how to give a solution in
next version of the program and improve certain aspects of the parameters 'radiator' and
'Selected engine', all through the 'DirectInput' of the 'DirectX'
Author
Topic: IL-2 + Devicelink + X-52 PRO display (Read 12890 times)
