The Device Link tips and questions thread. | Forums

[Bearcat99]

In light of a request by TAGERT and other device link users concerning this issue I am starting this thread on Device Link. I am starting it here because it a technical issue and also this board has a smaller number of stickies...

Please limit your posts here to specific questions or tips concerning device link. All superfluous posts will be deleted.

What I would like, before any posts really get rolling is for all those who either use it or are familiar with it to post here the what, why and how of the tool. This Device Link FAQ thread will be 100% user built from the ground up so if it flies or dies it will be up to the Device Link users themselves. If you see something that has already been said no need to repeat it... occasionally I will trim the thread to keep it as to the point as possible.

Thank you all for your cooperation ... and let the thread begin....

[TAGERT.]

First a little DeviceLink discription/summary. The initial and/or real purpose of DeviceLink is to provide the home build ****pit guys with a way to send and receive data to/from IL2-PF. DeviceLink is the gateway between the real world gauges and levers and the simulation world gauges and levers. With your own hardware and a little software you can read out the simulation altitude via DeviceLink and use it to cause the real altitude gauge in your home build ****pit to display the altitude. You could also have a switch on your home build ****pit that is used to raise and lower the landing gear. In short, you could have a gauge and or lever in a home build ****pit to control just about everything in the simulation.

That is the initial and/or real purpose of DeviceLink, but there is an added benefit to DeviceLink.

You can capture all that data to a file. Then look at (plot) the data to see what is actually going on as opposed to what people *think* is going on. This comes in very handy to see if a bug is a true bug, or just another case of the user misconception of what was actually going on.

My first contribution to this thread shall be a cut-n-paste from a post by lurker_hlb3 that tells you step by step how to install and setup UDPSpeed. The UDPSpeed program works in real time to display these values to the screen and/or save them to a file. UDPSpeed also works during playback of track files! Which comes in very handy during testing.

There are other progams out there that interface with DeviceLink. But, UDPSpeed is a good place to start.

lurker_hlb3 from SimHQ:
Recently I was reading the following thread here in the forums:

2.04 Easter Eggs / Unlisted Changes
http://www.simhq.com/simhq3/sims/boards/bbs/ultimatebb....ic;f=98;t=011402;p=2


Within the thread there is a pictures of a Bf109 with some extra read outs on the on the screen. Upon further investigation, downloaded the UPDSpeed program ( version 1.1 ) from the following site:

http://www.barans.ru/upload/alezz/UDPSpeed/UDPSpeed.zip


To my surprise I found that this tool developed by Alezz and Hruks (from the Ukraine and Russia) was amazingly useful when I was flying FB. Its open architecture allows great flexibility on “whatâ€Â� and “howâ€Â� information is displayed. You can setup a variety of customized displays based different types of aircraft or what ever you. I personally have 4 different setups for the aircraft that I like to fly ( Bf109s, Fw190’s / Ta152, and LW Jets and Rockets ).

So what follows is information that I’ve learning about this program and how to set it up.


Warning

You must have AEP loaded and patched to 2.01 or this will not work.


Part I

1. Down load UPDSpeed at http://www.barans.ru/upload/alezz/UDPSpeed/UDPSpeed.zip

2. create a working directory some where on your system.

3. unzip UPDSpeed within your working directory.

4. you will find 6 directories, 1 .ini file and 1.exe

Alt
Azimut
Energy
Fuel
Speed
Variometer

UDPSpeed.ini
UPDSpeed.exe

5. before you process go to your FB directory and add the following to your conf.ini file:

[DeviceLink]
port=21100
IPS=127.0.0.1
host=127.0.0.1

6. return to your working directory and launch UPDSpeed.exe program

7. after launch you will see 6 Russian style Instrument

8. place your mouse pointer over the Instrument and select the right mouse button

9. you will see the following:

Mode >
Show >
Additional >
About
Exit

10. Place mouse pointer over Mode > and you will see:

Pribor >
Label >

Place mouse pointer over Label and you will see:
Vertical
Horizontal


Select Vertical

11. The Instrument now turn into labels:

A:0.0
C:0.0
E:0.0
F:0.0
S:0.0
V:0.0

Red labels on a black background.

A=Altitude
C=Course
E=Energy
F=Fuel
S=Speed
V=Variometer

Note:
The Mode option is for displaying UPDSpeed data in ether Instrument (Pribor) or Label mode (Label) and either in a Vertical or Horizontal manner

12. Place mouse pointer over Label display and using the right mouse select Model > Label > Horizontal

you will note that the labels now display in a Horizontal manner

13 Place mouse pointer over Label display and using the left mouse you can now move the display around to any where on the display and the UDPSpeed program will “rememberâ€Â� the location and will display it there until remove it. Also when you relaunch UDPSpeed the information will be at the same location.

14. Place mouse pointer over Label display and using the right mouse select Show

you will see the number 1 through 6 displayed with a check by each.

15. select the number 1

16. you will note that the A:0.0 as disappeared . ( special note: if the labels goes all black, just exit using the right mouse button and then restart UDPSpeed )

Note: The Show option allows you to pick and choose “whatâ€Â� you want to display

17. Place mouse pointer over Label display and using the right mouse select Additional > Pribors > 2

you will see a black square or an Instrument displayed.

Place mouse pointer over black square or Instrument and select the right mouse button.

Select mode and then label and the black square or a Instrument will turn into a label.

18. Place mouse pointer over “Additionalâ€Â� label and you will also the “Hideâ€Â� & “Exitâ€Â� options

19. Place mouse pointer over Label display and using the right mouse and you will see the “aboutâ€Â� option.This provides info about the creators of this program.

20. Place mouse pointer over Label display and using the right mouse and you will see the “exitâ€Â� option.

Part II.

How to customize UPDSpeed for FB AEP 2.01 +


First the name of the runtime directory where UDPSpeed program plus the ini file and the instrument sub directories live can be name what ever you like. I personnel have four different custom UPDSpeed directory (i.e. UPDS_bf109, UDPS_fw190, UDPS_K4_D9, UDPS_jets) for the different LW aircraft that I fly.

Once you have created your runtime directory, place the UDPSpeed.exe and UDPSpeed.ini into the directory. Now this is “IMPORTANTâ€Â�, the order of the instrument sub directories will control the order that the instrument/labels will be displayed. I personally use a
number plus the under score symbol and the name of the instrument/labels to control the order of my label displays. Example:

1_Course
2_Speed
3_Alimeter
4_gload

Again you will note these sub directories can be named what ever you want. The sub directory that you want to use as your template for these instrument sub directories is the Azimut directory from the UPDSpeed.zip file,

Once you look inside the Azimut directory, you will find two bmp files and the 4C.ini file. The 4C.ini file is the key to create each of you custom instruments. Open the 4C.ini with notepad/wordpad and you will see the following:

[Main]
Prefix=C:
ArrowCounter=1
Bitmap=bg_crs.bmp
Mode=1
PosX=80
PosY=50
AddPanel=0
Visible=1
RequestString=/42

[Arrow1]
//ÃÅ*îìïà ñ
Bitmap=arrow_cur1.bmp
PosX=88
PosY=87
CenterX=62
CenterY=50
DataIndex=42
Data1=0
Angle1=90
Data2=360
Angle2=450



The following is a detailed Breakdown of the 4C.ini file

[Main]

Prefix=C:

The description of what is being represented Example if this was Aircraft Course then you and change the C to be HDG or CUS or
what ever you want.

Warning; recommend you use 5 character or less due to label display restrictions

ArrowCounter=1
Bitmap=bg_crs.bmp

Number or Arrows used by program when in Instrument Mode (Pribor) and Which bmp graphic to use.

Mode=1

I have not figured out what this means

PosX=80
PosY=50

Position on the monitor


AddPanel=0

Is it be used by the Additional sub-menu

Visible=1

Is the label/ Instrument displayed


RequestString=/42

The value that is being broadcasted via UDP from FB. The example here is Aircraft Course ( Azimuth )

See later in this doc for detail breakdown of all the useful values that can be added here



[Arrow1]
//ÃÅ*îìïà ñ
Bitmap=arrow_cur1.bmp

Graphic to be used if in instrument/Pribor mode

PosX=88
PosY=87
CenterX=62
CenterY=50

Position of instrument/Pribor


DataIndex=42

Same as RequestString in the Main section

WARNING
For things to work correctly the RequestString and the DataIndex have the same value.

Data1=0
Angle1=90
Data2=360
Angle2=450

Data for the display when instrument/Pribor mode


More on how to customize this file later

Now go back to your runtime directory and open the UDPSpeed.ini file with notepad/wordpad. You Will see the following:


UDPSpeed.ini

[UDP]
IP=127.0.0.1
Port=21100

[Log]
Write=0
Name=C:\fbapi.log

[Modes]
VerticalMode=0
ModeOfPribor=1
DemoMode=0

[Window]
PosX=17
PosY=9

[Labels]
Color=255
Brush=0
FontSize=14

[Main]
TimerMS=1001

[Variables]
Mass=1


Breakdown

[UDP]
IP=127.0.0.1
Port=21100

IP of the computer, which is running UDPSpeed. 127.0.0.1 is equal to your local computer The port that UDPSpeed gets its FB information


[Log]
Write=1
Name=C:\fbapi.log

Write=? Is to enable/disable logging of FB data that UDPSpeed is receiving 1=on 0=off Name=xxx is the location of the log


[Modes]
VerticalMode=0
ModeOfPribor=1
DemoMode=0

VerticalMode=x If UDPSpeed is displaying label/ Instrument information in a Vertical or Horizontal mode. 0= Horizontal 1=Vertical

[Window]
PosX=17
PosY=9

Position of the main UDPSpeed label/ Instrument information window

[Labels]
Color=255
Brush=0
FontSize=14

Color and size of data when in Label mode
Color=XXX is the RGB value of Label ( 255 is RED )
Brush= contrast of the color value ( 0 is = to black )
FontSize=XX how big the labels are.

Special Note: I personnel leave the Color/Bush values alone, but change the Font value to 10.

[Main]
TimerMS=1001

Hoe often the data is updated in milliseconds ( 1000 ms = 1 second )

[Variables]
Mass=1

This has something to do with the “Energyâ€Â� instrument in the original

UPDSpeed.zip download

Now its time to create your custom instrument sub-directories. But first a breakdown of the useful instrument from DevicesLink.txt

Breakdown of the codes for Instrument data that are transmitted via Device Link interface in FB.Special Note: These are only the ones
that I have tested and recommend for uses with UDPSpeed. You can see ALL the values listed in the DeviceLink.txt [located in FB main director]

speedometer 30 [kph]
variometer 32 ( how fast your climbing or diving ) [ meters / second ]
altimeter 40 [meters]
azimuth 42 [ Degrees ] ( Aircraft course )
fuel 50 [ Kilograms ]
overload 52 [ G load ]
rpm 64 [ Engine RPM ]

SPECIAL NOTE: When used with jets the values are “NOTâ€Â� accurate.

manifold 66 [millibars]
temp_oilin 68 [deg.C]
temp_oilout 70 [deg.C]
temp_water 72 [deg.C]

SPECIAL NOTE: When used with jets the value is for Tail Pipe Temperature

temp_cylinders 74 [deg.C]


Recommend Director names and content of the 4C.ini files

Altimeter

Director Name: X_ Altimeter
4C.ini content

[Main]
Prefix=Alt:
ArrowCounter=1
Bitmap=bg_crs.bmp
Mode=1
PosX=883
PosY=674
AddPanel=0
Visible=1
RequestString=/40

[Arrow1]
//ÃÅ*îìïà ñ
Bitmap=arrow_cur1.bmp
PosX=86
PosY=87
CenterX=62
CenterY=50
DataIndex=40
Data1=0
Angle1=90
Data2=360
Angle2=450

manifold

Director Name: X_ Ata
4C.ini content

[Main]
Prefix=ATA:
ArrowCounter=1
Bitmap=bg_crs.bmp
Mode=1
PosX=883
PosY=617
AddPanel=0
Visible=1
RequestString=/66

[Arrow1]
//ÃÅ*îìïà ñ
Bitmap=arrow_cur1.bmp
PosX=86
PosY=87
CenterX=62
CenterY=50
DataIndex=66
Data1=0
Angle1=90
Data2=360
Angle2=450


Azimuth

Director Name: X_ Ata
4C.ini content

[Main]
Prefix=HDG:
ArrowCounter=1
Bitmap=bg_crs.bmp
Mode=1
PosX=883
PosY=674
AddPanel=0
Visible=1
RequestString=/42

[Arrow1]
//ÃÅ*îìïà ñ
Bitmap=arrow_cur1.bmp
PosX=86
PosY=87
CenterX=62
CenterY=50
DataIndex=42
Data1=0
Angle1=90
Data2=360
Angle2=450

temp_cylinders

Director Name: X_ Ata
4C.ini content


[Main]
Prefix=Head:
ArrowCounter=1
Bitmap=bg_crs.bmp
Mode=1
PosX=883
PosY=674
AddPanel=0
Visible=1
RequestString=/68

[Arrow1]
//ÃÅ*îìïà ñ
Bitmap=arrow_cur1.bmp
PosX=86
PosY=87
CenterX=62
CenterY=50
DataIndex=68
Data1=0
Angle1=90
Data2=360
Angle2=450

Fuel

Director Name: X_ Ata
4C.ini content

[Main]
Prefix=Fuel:
ArrowCounter=1
Bitmap= bg_crs.bmp
PosX=854
PosY=10
Mode=1
AddPanel=0
Visible=1
RequestString=/50

[Arrow1]
//ÃÅ*îìïà ñ
Bitmap=arrow_cur1.bmp
PosX=86
PosY=87
CenterX=62
CenterY=50
DataIndex=50
Data1=0
Angle1=90
Data2=360
Angle2=450

Overload

Director Name: X_ gload
4C.ini content

[Main]
Prefix=G's:
ArrowCounter=1
Bitmap=bg_crs.bmp
Mode=1
PosX=64
PosY=41
AddPanel=0
Visible=1
RequestString=/52

[Arrow1]
//ÃÅ*îìïà ñ
Bitmap=arrow_cur1.bmp
PosX=86
PosY=87
CenterX=62
CenterY=50
DataIndex=52
Data1=0
Angle1=90
Data2=360
Angle2=450


Speedometer

Director Name: X_ speed
4C.ini content

[Main]
Prefix=IAS:
ArrowCounter=1
Bitmap=bg_crs.bmp
Mode=1
PosX=883
PosY=674
AddPanel=0
Visible=1
RequestString=/30

[Arrow1]
//ÃÅ*îìïà ñ
Bitmap=arrow_cur1.bmp
PosX=86
PosY=87
CenterX=62
CenterY=50
DataIndex=30
Data1=0
Angle1=90
Data2=360
Angle2=450

temp_oilin
Director Name: X_ oil_in
4C.ini content

[Main]
Prefix=oil_in:
ArrowCounter=1
Bitmap=bg_crs.bmp
Mode=1
PosX=883
PosY=674
AddPanel=0
Visible=1
RequestString=/68

[Arrow1]
//ÃÅ*îìïà ñ
Bitmap=arrow_cur1.bmp
PosX=86
PosY=87
CenterX=62
CenterY=50
DataIndex=68
Data1=0
Angle1=90
Data2=360
Angle2=450

temp_oilout

Director Name: X_ oil_out
4C.ini content

[Main]
Prefix=oil_out:
ArrowCounter=1
Bitmap=bg_crs.bmp
Mode=1
PosX=883
PosY=674
AddPanel=0
Visible=1
RequestString=/70

[Arrow1]
//ÃÅ*îìïà ñ
Bitmap=arrow_cur1.bmp
PosX=86
PosY=87
CenterX=62
CenterY=50
DataIndex=70
Data1=0
Angle1=90
Data2=360
Angle2=450

Rpm

Director Name: X_ rpm
4C.ini content

[Main]
Prefix=RPM:
ArrowCounter=1
Bitmap=bg_crs.bmp
Mode=1
PosX=64
PosY=41
AddPanel=0
Visible=1
RequestString=/64

[Arrow1]
//ÃÅ*îìïà ñ
Bitmap=arrow_cur1.bmp
PosX=86
PosY=87
CenterX=62
CenterY=50
DataIndex=64
Data1=0
Angle1=90
Data2=360
Angle2=450


Variometer

Director Name: X_ variometer
4C.ini content

[Main]
Prefix=Var:
ArrowCounter=1
Bitmap= bg_crs.bmp
PosX=400
PosY=50
Mode=1
AddPanel=0
Visible=1
RequestString=/32

[Arrow1]
//ÃÅ*îìïà ñ
Bitmap=arrow_cur1.bmp
PosX=86
PosY=87
CenterX=62
CenterY=50
DataIndex=32
Data1=0
Angle1=90
Data2=360
Angle2=450


temp_water

Director Name: X_ water
4C.ini content

[Main]
Prefix=H2O:
ArrowCounter=1
Bitmap=bg_crs.bmp
Mode=1
PosX=64
PosY=40
AddPanel=0
Visible=1
RequestString=/72

[Arrow1]
//ÃÅ*îìïà ñ
Bitmap=arrow_cur1.bmp
PosX=86
PosY=87
CenterX=62
CenterY=50
DataIndex=72
Data1=0
Angle1=90
Data2=360
Angle2=450


Part IV

Now that you’ve created your custom runtime UDPSpeed directories you can place them “anywhereâ€Â� within your computer. I personally have them in my main FB directory. For everthing to work correctly you need to start UDPSpeed and then position your labels where you want them.

Once this is done startup FB


Enjoy

Lurker

[Diablo310th]

Bearcat......ty very much for this. Tagert...a veruy good start with UDPSpeed. Let everyone be aware also that another program is out there called UDPGraph which is far more flexible. It can be found in that same article at SimHq just ****her down the thread. Also......everyone be aware that UDPSpeed and UDPGraph only work offline. No one ahs found a way to make it work online yet that I know of.

[TAGERT.]

Originally posted by Diablo310th:
Bearcat......ty very much for this.

Yes Thanks Bearcat!!

Originally posted by Diablo310th:
Tagert...a veruy good start with UDPSpeed. Let everyone be aware also that another program is out there called UDPGraph which is far more flexible. It can be found in that same article at SimHq just ****her down the thread.

I was going to include it, but the link to UDPGraph looked dead?

http://www.avcsite.ru/il2dl/graph.htm

That and I didnt have a good step by step on how to set it up.

Originally posted by Diablo310th:
Also......everyone be aware that UDPSpeed and UDPGraph only work offline. No one ahs found a way to make it work online yet that I know of.

I never really looked into that too hard.. I know the reasoning is that some consider it a cheat.. that and it supose to put a little burden on the server.. But, I seem to recal that *if* the server enables DeviceLink that *some* of the info will work.. but not all. I dont recall which do and dont.. Does the DeviceLink doc address that? Anyway, I have to admit, I personally dont care about spinning any guages on a home build ****pit! But some do, my only real interest is in proving and disproving bugs!

PS if anyone has a full up version of UDPGraph that they downloaded before the sight went down I could host it for dl on my page.

[triggerhappyfin]

Would it be possible to get slipindicator working with this UDBspeed gadget?
Would be nice now when trimming is so essential.

[EURO_Snoopy]

Would you guys like a Device Link Chapter in the IL2 CC Manual?

I could also expand the FAQ to include device Link

IL2CCM

[Diablo310th]

quote:
Originally posted by Diablo310th:
Tagert...a veruy good start with UDPSpeed. Let everyone be aware also that another program is out there called UDPGraph which is far more flexible. It can be found in that same article at SimHq just ****her down the thread.

I was going to include it, but the link to UDPGraph looked dead?

http://www.avcsite.ru/il2dl/graph.htm

That and I didnt have a good step by step on how to set it up.

quote:
Originally posted by Diablo310th:
Also......everyone be aware that UDPSpeed and UDPGraph only work offline. No one ahs found a way to make it work online yet that I know of.

I never really looked into that too hard.. I know the reasoning is that some consider it a cheat.. that and it supose to put a little burden on the server.. But, I seem to recal that *if* the server enables DeviceLink that *some* of the info will work.. but not all. I dont recall which do and dont.. Does the DeviceLink doc address that? Anyway, I have to admit, I personally dont care about spinning any guages on a home build ****pit! But some do, my only real interest is in proving and disproving bugs! Wink

PS if anyone has a full up version of UDPGraph that they downloaded before the sight went down I could host it for dl on my page.
______________________________________________

Tagert.....pm me and i'll arrange to get you teh last copy of UDPGraph that I know of and I will search for teh thread on setting it up and how to run it. Also...yes if the server enables DeviceLink parts of it will work but not any of the really good stuff. I think it was jsut a couple functions that would work if any at all. of use.

[Diablo310th]

Originally posted by EURO_Snoopy:
Would you guys like a Device Link Chapter in the IL2 CC Manual?

I could also expand the FAQ to include device Link

IL2CCM

Snoopy...I think that would be great. Lets try to get all our ducks in a row with all the available programs and setups then post it.

[TAGERT.]

PS where is BaldieJR? I thought he was big into this stuff? Im sure he would have some good input to all this!

[TAGERT.]

Originally posted by EURO_Snoopy:
Would you guys like a Device Link Chapter in the IL2 CC Manual?

I could also expand the FAQ to include device Link

IL2CCM

That would be cool!
But, we also need a forum where guys can get togther and share info, lessons learned and new ideas.. Which in turn could be folded back into your FAQ page as we learn them.