DL wrapper now updated to 2.1.0.

Many internal changes to the wrapper. Besides a mulitude of bug fixes I've changed the zip file to show the layout of the structure I have the files stored in my source code control system. I've included not just the source code, but the solution and build files for Visual Studio .Net 2003. I've also included a little udpserver test app to bounce your app against to if basic setup is working. Here are the notes from the included README. LOTS of NEW METHODS ADDED!

quote:

Changes:

v2.1 - Incremented to 2.1 to represent the additional functionality added to the library.
- Added a SuperChgNxt and SuperChgPrv methods for increasing and decreasing the supercharger.
- Added SelectEng3 and SelectEng4 methods for being able to Select engines 3 and 4
- Added methods for turning Toggling WEP and a method for checking it's state (Get_WEP)
- corrected the assumption all float returned values would be greater than zero.
- Added the following instrument functions:
float Get_IAS(void);
float Get_Alt(void);
float Get_AngSpd(void);
float Get_Azimuth(void);
float Get_BeaconAzimuth(void);
float Get_Pitch(void);
float Get_Roll(void);
float Get_Slip(void);
float Get_Turn(void);
float Get_Vario(void);
float Get_Fuel(void);
bool Set_IAS(void);
bool Set_Alt(void);
void Set_AngSpd(void);
bool Set_Azimuth(void);
bool Set_BeaconAzimuth(void);
bool Set_Pitch(void);
bool Set_Roll(void);
bool Set_Slip(void);
bool Set_Turn(void);
void Set_Vario(void);
bool Set_Fuel(void);

and associated private vars.

- Added the following controls methods:
float Get_Aileron(void);
bool Query_Aileron(void);
bool Set_Aileron(float pos);
float Get_Elevator(void);
bool Query_Elevator(void);
bool Set_Elevator(float pos);
float Get_Rudder(void);
bool Query_Rudder(void);
bool Set_Rudder(float pos);
float Get_Power(const int eng_idx);
bool Query_Power(const int eng_idx);
bool Set_Power(const int eng_idx,float pos);
float Get_PropPitch(const int eng_idx);
bool Query_PropPitch(const int eng_idx);
bool Set_PropPitch(const int eng_idx,float pos);
float Get_Brakes(void);
bool Query_Brakes(void);
bool Set_Brakes(float pos);
float Get_AilTrim(void);
bool Query_AilTrim(void);
bool Set_AilTrim(float pos);
float Get_ElvTrim(void);
bool Query_ElvTrim(void);
bool Set_ElvTrim(float pos);
float Get_RudTrim(void);
bool Query_RudTrim(void);
bool Set_RudTrim(float pos);

- Added a 'power' private var to the m_engine_type structure.
- Added a 'prop_pitch' private var to the m_engine_type structure.

There will be more changes, mostly additional functions coming soon but wanted to get this one out as I did fix a few bugs too.

The doc files were generated via doxygen and are included in the zip. They can also be viewed online HERE

As usual feel free to email me any bugs, suggestions or requests.

Click Here to download version 2.1.0

I have quite a simple question regarding UdpGraph. Is function "overload" same thing as G-load?

Been asked to show a program using my library. I'll post up a little demo program (complete with source code) later today.

See the info for the wrapper at the www.wingwalkers.org forum under hardware/software. New wrapper Here

OK, I've updated the DeviceLink Wrapper to version 2.1.1 and I've written a small application showing how one could use it. Actually, I've written another series of classes based off a base Aircraft Class with various component classes. I've totally abstracted away the devicelink layer so you don't need to know anything about it. A simple Aircraft object instantiation will take care of all the networking for you as long as you have the config.ini with the proper IP and port number. Simply takes a

C_Aircraft ac;

in your code and all the UDP client stuff is taken care of.

This sample app is the beginning of an app I'm writing for our squad training office. This first version simply records the following data every 1/2 second to a comma seperated text log file:

IAS, ALT, ANGSPD, AZIMUTH, ROLL, PITCH, TURN, SLIP, VARIO, FUEL

The default name of the text file is "logfile.cvs" but you can pass another name on the command line if you wish. It will, for now, also create a bbbr_debug.txt file with extra debug info. If you have problems running the sample program and want to let me know I'll need that file to help me trouble shoot.

To use the app make sure you've setup your game to work with DeviceLink per the instructions provided in your Devicelink.txt file found in the main IL2 directory. Unzip the app zip file to whereever you want. Be sure to tell your unzip program to extract the paths as well. you'll find the executable in the dl_test\trunk\bin\Release directory and it's called dl_test.exe. You can either just double click on it to run with a default logfile name or run it from the command line and give it a filename as a parameter. IMPORTANT: Your IL2 game must be started first. You don't have to be flying yet, but the game needs to be launched first. I'll fix that later, but this was just an early prototype.

Then again, the program is just meant to serve as an example. I've included allt he source code and build files in the zip. Get it Here

and you can view all the docs Here

You can post questions to me about this at the www.wingwalkers.org forum

Updated wrapper to 2.1.2. Streamlined some code and finished up the multi-engine support now. Same links apply.

You can download the latest DeviceLink wrapper: DeviceLink Wrapper Class

and the latest sample application: Sample Application

Online docs for each (Docs are also in the zip files as well):

DeviceLink Wrapper Docs

Sample App Docs

This is version 2.1.3 of the wrapper and here are the latest notes from the ReadMe.

quote:

Changes:
v2.1.3
-- refactored SelectEng1-4 methods into a single private method of selecteng(code). Maintained the API
so it is backwards compatible.
-- Added enum WeapType {MG, CANNON, ROCKETS, BOMBS, MGCANNON} for setting up the Query, Set and Get of Weapons
-- corrected logic error in setctrl() method when compiling under Visual Studio 2005.
-- bumped SendMsg buffer to 80 bytes from 64.
-- added a private array m_weap of WeapType. It's initialized in the constructor.
-- added Query_Gunpods to query game on whether gunpods are on or off and assign to private m_gunpods
-- added ToggleGunPods to switch them on/off
-- added GetGunPodsState which returns m_gunpods to a higher application
-- changed constructor to initialize many of the private variables rather than assign them values. Little cleaner that way.
-- cleaned up many routines that were adding extraneous "R/" to command codes.
-- Added ToggleBombSight method for the auto bombsight
-- Added IncSightDist
-- Added DecSightDist
-- Added AdjSightRight
-- Added AdjSightLeft
-- Added IncSightAlt
-- Added DecSightAlt
-- Added IncSightVelocity
-- Added DecSightVelocity
-- Added ToggleHook for the arresting hook
-- Added Query, Set and Get _Airbrakes methods
-- Added Query, Set and Get _Tailwheel methods
-- Added Query, Set and Get _LvlStab methods
-- Added a Set_CowlFlaps method for incrementing the Cowl flap position.
-- Added ManualGearDown and ManualGearUp methods

WWSensei
Thx for your hard work!

quote:

Originally posted by rssmps:
WWSensei
Thx for your hard work!

no need for thanks as I enjoy coding. Thanks for the thought though. I do appreciate it. Working on 2.1.4 now and hope to finish ALL the remaining function calls.

Hi all,
A new version of UDPSpeed and my new high-res BF-109K gauges are available for download here.

For those unfamiliar with it, UDPSpeed is a program written by Hruks and Alezz which allows you to display working cockpit gauges on a second screen. For best results, the screen should be that of a second PC networked to the PC you play IL2 on, but it is also possible to run the program on the same PC as the sim (by replacing both the IP addresses in the instructions below with "127.0.0.1"). BTW if you are using a second PC, then it doesn't have to be very powerful - I've run UDPSpeed in the past on an old 460Mhz laptop with 60MB of RAM.

In addition to UDPSpeed itself, this zip also contains a complete 1280x1024 set of my BF-109K instruments, along with a selection of generic warning lights and indicators. N.B. You do not have to be flying a 109 to use the instruments - they'll work with any plane, Allied or Axis. The gauges will also work when you're viewing an NTRK, so you can watch the track from an exterior view on your main screen whilst still keeping an eye on all the instruments on your second screen.



From top left, the set consists of: speedometer, artificial horizon with slip and turn indicators, VSI, tachometer, altimeter, compass with nav beacon indicator, clock, manifold pressure gauge, coolant temperature gauge, oil temperature gauge, landing gear indicator, prop pitch indicator, fuel gauge, war emergency power light, supercharger light, magnetos indicator, aileron and rudder trim indicator, tail wheel lock light, arresting hook light, elevator trim & G-force indicator, flaps position indicator, air brake light, and finally a low fuel warning light. N.B. The image above has been scaled down.



QUICK START GUIDE
=================
1. Set up a network connecting the PC you play IL2:FB/AEP/PF on (the host) to the PC you want to display the gauges on (the client).

2. Create a folder called UDPSpeed anywhere on your client PC and unzip the files into it. Your UDPSpeed folder should now contain sub folders for each gauge along with the UDPSpeed initialization file and executable.

3. Open the file "UDPSpeed.ini" in your UDPSpeed folder with notepad and check the IP address at the top. It should match that of your host PC. If it doesn't, then amend it. (You can check your IP address by clicking Start, Run, typing "cmd" followed by Enter, then typing "ipconfig" followed by Enter).

3. Open your conf.ini file (in the FB/PF folder on your host PC) and paste the following text at the end of it:

[DeviceLink]
port=21100
host=192.168.0.1

This tells IL2 itself the IP address of the host PC and must therefore match the address you used in the previous step. Obviously if your host PC uses a different address, then amend your conf.ini accordingly.

4. Set the desktop on your client PC to 1280x1024 (This set of instruments is designed to be viewed at that resolution). If you're viewing the gauges on a CRT rather than a TFT then the aspect ratio will be slightly distorted. You can fix this by using a higher resolution, but obviously the gauges won't then cover the whole screen.

5. Double click the file "UDPSpeed.exe" in your UDPSpeed folder on your client PC. The gauges should appear.

6. Fire up IL2 on your host PC and load a mission. Once the mission has loaded and you're airborne, the gauges should be active. (If you use the autopilot during take-off, toggle it off and on again once you're off the ground).



LIMITATIONS
===========
1. 1C:Maddox have severely limited the variables which can be exported from a multiplayer game. Most of the main gauges will therefore only work when flying offline. If, like me, you'd like to see this restriction lifted then I suggest you contact 1C:Maddox and ask them to make the necessary changes to the sim (perhaps via a variable which a multiplayer server admin could edit e.g. AllowDevicelink=1).

2. The timing of the lights on the landing gear indicator is slightly wrong. This is because the current version of UDPSpeed doesn't have the ability to round up Devicelink key values.

3. FB/PF doesn't export a value for prop pitch for planes with automatic control (like the BF-109), so you won't see the needle move in this plane. When flying a plane with manual prop pitch control, however, you'll see the larger needle move (down for 100%, up for 0%).

4. FB/PF doesn't export a value for your radiator/cowl flap setting so it's not possible to make a gauge for that.



CREATING YOUR OWN GAUGES
========================
The beauty of UDPSpeed is that it enables you to make just about any type of gauge or indicator you want. You can model and render them in a program like 3D Studio Max (as I did) or use photos of real gauges. In either case you'll almost certainly also need to do some editing of the images with a program like Photoshop.



NEW FUNCTIONALITY IN THIS VERSION OF UDPSPEED
=============================================
The following new commands can be used to slide arrows (in addition to rotating them):

DataIndexSlide=X Devicelink key number to be used to control the sliding (like DataIndex).
SlideTo=X Direction in which to slide. Possible values are:
0 = Slide To None?
1 = Slide vertically
2 = Slide horizontally
3 = Slide along the X axis of the arrow
4 = Slide along the Y axis of the arrow
DataSlide1=X Equivalent to "Data1", but for sliding arrows.
Slide1=X Specifies the distance to be slid in pixels.

For examples of the new syntax in use, read the ini files in the artificial horizon or trim indicator folders.

Cheers,
DD

SWEET! Good job DD. I will try these out tonight...

Worth logging on for this one

Thanks DD and Sensei for both your contributions

Love the gauges.
If only I knew what all the tech talk meant I would try to use them.

Beautiful gauges!! Thank you so much DD!!

for some reason when I run the new higher resolution gauges on my laptop (fairly new) the lag for the gauge response is so much (about 1 update per second) that they are pretty much unusable. seems to work fine with the older spit gauges.

I'm curious if anyone knows what the performance penalty would be if I ran a second monitor with UDPSpeed of my main computer

DeviceLink Wrapper library 2.1.4 is posted.

From the ReadMe.

quote:

Changes:
v2.1.4
-- Added GetCurCockpit method to return what cockpit the user is currently in. 0 is always pilot
-- Added Get_Overload method
-- Added Get_ShakeLvl method
-- removed private selecteng method. Turns it was identical to toggleswitch
-- Added SelectAllEngines method
-- Added UnSelectAllEngines method
-- Added SelectLeftEngines method
-- Added SelectRightEngines method
-- Added ToggleSelAllEngines method
-- Added ToggleSelLeftEngines method
-- Added ToggleSelRightEngines method
-- Added ToggleSelEng1 method
-- Added ToggleSelEng2 method
-- Added ToggleSelEng3 method
-- Added ToggleSelEng4 method
-- Added Query, Set and Get methods for _WingFold
-- Added Query, Set and Get methods for _Canopy
-- Added Query, Set and Get methods for _TailHook
-- Added Query, Set and Get methods for _Chocks
-- Added Query, Set and Get Methods for _Gunner
-- Added JumpToCockpit for jumping up to 10 different cockpits (max game supports)
-- Corrected several comments for functions so Doxygen could produce the proper
annotated function and private variable descriptions

This will be the last version I will push. This library covers about 95% of the functionality of DL and finishes what I needed for my own private projects. I will be happy to fix any bugs or add functionality if requested however. I have NOT updated my sample application yet.

You can download the latest DL wrapper: DeviceLink Wrapper Class

and the latest sample application: Sample Application

Online docs for each (Docs are also in the zip files as well):

DeviceLink Wrapper Docs

Sample App Docs

Hi,

Is there a way to improve fluidity and speed of those instruments ? I've tried to modify the time process of the update, but even with hight speed update, instruments seems to jerk...

Anyway, ty for this helpfull post and those beautifull instruments...

Posted a bug fix to 2.1.4. It's now 2.1.4.1. Had a bug in Get_Roll where I was returning the beacon_azimuth rather than roll because of brain dead typo cut and paste error....arghhhhh!

Same links apply as previous message.

Sensei...can you explain how to use your wrapper using guages? Is that possible yo use ur wrapper with UDPSpeed or UDPgraph? I've followed uyour work but don't fully understand how you use it in game. I'm a long time user of both UDPSpeed and Graph.

quote:

Originally posted by Diablo310th:
Sensei...can you explain how to use your wrapper using guages? Is that possible yo use ur wrapper with UDPSpeed or UDPgraph? I've followed uyour work but don't fully understand how you use it in game. I'm a long time user of both UDPSpeed and Graph.

Simple. You don't. My library would be used by something like UDPSpeed/UDPGraph. I don't think the author of those used my library, but my library is not an application, but a library a programmer would use to build a program like UDPSpeed.

I wrote a small sample application to demonstrate how a programmer would use it, but the sample program is just that--a sample.

The main application I'm writing using the library is one for GoFlight modules. Also, someone has written an interface application for the Logitech G-15 keyboard and recently a maker of a full motion simulator has picked it up to use in his pit.

quote:

Originally posted by bubba3884:
for some reason when I run the new higher resolution gauges on my laptop (fairly new) the lag for the gauge response is so much (about 1 update per second) that they are pretty much unusable. seems to work fine with the older spit gauges.

I'm curious if anyone knows what the performance penalty would be if I ran a second monitor with UDPSpeed of my main computer

BUMP

Do the new gauges work fluidly for anyone?