394 replies to this topic

[Paul Henty]

Attached is Version 2.0 of my FSUIPC Client DLL for .NET

This update mainly introduces some utility classes for easier handling of Latitudes/Longitudes and AI Traffic Information.

Features:

• Object-Oriented class interface better suited to .NET than the other procedural .NET SDKs.
  
  
• Data from FSUIPC is returned directly to your .NET variables.  Supported types are:

• Byte, Int16, Int32, Int64, UInt16, UInt32, UInt64, Double, Single
  
• String (Unicode/ASCII conversion and termination handled for you)
  
• BitArray (Allows you to easily manage the bit field type offsets)
  
• Array of Bytes (Allows you to read and write raw blocks of data if you need that level of control.)

• Writes are handled just by assigning a new value to the local .NET data variable.  The write to FSUIPC will be handled automatically during the next Process().
  
  
• Errors are handled by .NET exceptions, not by checking return values.
  
  
• The DLL can be use with any .NET language.  Documentation and example projects for C# and Visual Basic.NET.
  
  
• The library has full internal documentation that will appear on the IntelliSense popup menus in Visual Studio.
  
  
• Just as fast as the procedural-style .NET SDKs.
  
  
• Thread safe.  Can be used in multi-threaded applications, with each thread communicating with FSUIPC, without corrupting the data.  (Only one thread can talk to FSUIPC at a time – other threads will block until the connection is free).

New for version 2.0:

• Slight change of Licence terms.  If you want to use this DLL in a Freeware, Shareware or Commercial application, it is now required that you credit the use of this DLL and its author.  See the new user guide for details.
  
  
• You can now create more than one Offset with the same address.
  
  
• Added the ability to process multiple offset groups in a single process() call.
  
  
• Added a property to get the current version of flight sim you are connected to.
  
  
• Added a feature to read AI Traffic Information from FSUIPC.  AI Planes are returned to you as a strongly-typed List<> of AIPlaneInfo instances.  AIPlaneInfo provides all information available from FSUIPC plus lots of extra info (e.g. Distance and Bearing from the player) in a ready-to-use .NET class.
  
  
• Added a feature to write into the internal FSUIPC AI Traffic Tables.  (This does not add AI planes into flight sim.)
  
  
• Added classes for dealing with Longitudes and Latitudes.  These understand the raw FS Units provided by FSUIPC (both the 8-Byte and 4-Byte types) so conversion to and from degrees is easy.  Also has a very flexible ToString() method to enable output in a number of human-readable formats.
  
  
• Added classes for dealing with Longitude and Latitude Spans (distances).  These classes can be used to convert Lon/Lat spans to and from metres or feet.  Lon/Lat spans can be calculated between two Lon/Lats.
  
  
• Added a class to deal with a Lon/Lat point.  This represents a point on the Earth but can also be used to calculate the distance and/or bearing to another point.
  
  
• Added a class representing a Quadrilateral area on the Earth.  Its primary function is to test if a lon/lat point is contained within the Quadrilateral. This is useful for testing if you are on a runway.  The Quadrilateral can be generated from a set of four Lat/Lon points, or from basic runway information such as that found in the output of MakeRunways.exe by Pete Dowson.
  
  
• It is now possible to connect to multiple instances of WideFS on the same machine using this DLL.
  
  
• Re-formatted and extended the User Guide.  
  
  
• Completely new reference documentation produced using DoxyGen for a much-improved HTML reference manual.
  
  
• Updated the example application in C# and VB.NET.  Now contains demonstrations of the new features including an AI Traffic Radar display.

The zip file contains the DLL, documentation and an example project in C# and Visual Basic.NET (Visual Studio 2008 format).

NOTE: This DLL will not work with Visual Studio 2003 or earlier as it uses 'generics' which were not invented until Visual Studio 2005.

Microsoft have free versions of Visual Studio 2010 compilers for VB, C#, C++ and J# here:

http://msdn.microsof...studio/express/


Paul

Attached Files

•  FSUIPCDotNetClient2.0.zip   1.46MB   853 downloads

[Rhysa]

I have to say a purpose built module for .Net like this has been long overdue. Its great to see that someone who really knowns their stuff has put together a great module for the community. Its going to make coding for FSUIPC much more efficient. As developer of a few small addon's I'm happy to say I can discard the old methods and will be using this module from now on.

So thanks, and keep up the good work!

:D  :D  :D

[LuisDeSa]

Hi,

I can not read aircraft position using this DLL. Could anyone be so kind to post the code to get the latitude (or longitude) of the aircraft?

Luis

[Paul Henty]

Hi Luis,


The Lon and Lat offsets are 64 bit Integers which are called Long in C# and VB.  (The underlying class is System.Int64 if you are using a different language).


So the declaration of the offsets would be:


C#

private Offset<long> latFS = new Offset<long>(0x0560);
private Offset<long> lonFS = new Offset<long>(0x0568);

VB.NET

Private latFS As Offset(Of Long) = New FSUIPC.Offset(Of Long)(&H560)
Private lonFS As Offset(Of Long) = New FSUIPC.Offset(Of Long)(&H568)

I've called them LonFS and LatFS because they return Lon and Lat in FS internal units.

After calling Process() you can transform the FS Units into degrees with the following lines (as described in the FSUIPC Documentation) and you end up with a Double floating point type that holds the Lon/Lat as degress.

C#

// Convert Lat and Lon from FS Units into degrees (as a double),
double lat = (double)latFS.Value * 90d / (10001750d * 65536d * 65536d);
double lon = (double)lonFS.Value * 360d / (65536d * 65536d * 65536d * 65536d);

.
VB.NET

' Convert Lat and Lon from FS Units into degrees (as a double).
Dim lat As Double = latFS.Value * 90D / (10001750D * 65536D * 65536D)
Dim lon As Double = lonFS.Value * 360D / (65536D * 65536D * 65536D * 65536D)

Paul

[LuisDeSa]

Hi Paul,

Thank you very much for the explanation. I am using the DLL in SBuilder (scenery creation programme) and I get an error in the situation that I will try to explain:

My programme has an option to show the FS aircraft on the Sbuilder display. When the user sets this option and until he disconnects the option, the programme displays the aircraft position at regular intervals (set by a timer). This is the code for the timer event:

Try
            FSUIPCConnection.Process()
            AircraftLatitude = CDbl(LatAircraft.Value)
            AircraftLatitude = AircraftLatitude * 90.0 / (10001750.0 * 65536.0 * 65536.0)
            AircraftLongitude = CDbl(LonAircraft.Value)
            AircraftLongitude = AircraftLongitude * 360.0 / (65536.0 * 65536.0 * 65536.0 * 65536.0)
        Catch ex As Exception
            MsgBox("Error communicating with FSUIPC!", MsgBoxResult.Ok)
            AircraftVIEW = False
            ShowAircraftMenuItem.Checked = False
            Me.Timer2.Enabled = False
            Exit Sub
        End Try
        UpdateDisplay()

This runs fine except if the user closes FS. Then SBuilder (in debug mode) reports an error in the DLL or it crashes in normal operation. I could start the shown routine with:

Try
            FSUIPCConnection.Close()
            FSUIPCConnection.Open()
            FSUIPCConnection.Process()
...


but this does not look good as the timer interval can be very short (100ms or so depending on the settings of the user of my programme).

Many thanks for any tip,

Regards,

Luis

[Paul Henty]

Hi Luis,

The code you have posted looks OK to me.  You've setup a Try/Catch block, so when the Process() executes and FS isn't arouond anymore the DLL should throw an error.  You're catching this so there shouldn't be an unhandled exeption thrown to the debugger.

You're right about the Close(), Open() at the start of your timer loop - you don't want to do that.  It shouldn't be necassary.

I can't really tell from your post what's going on - could you let me know:

1. Which line(s) the exception is being thrown on
2. The exact message and type of the exception(s)
3. Do you have any other methods in your application that also call Process()?


Regards,


Paul

[rabbitcancer]

I'm writing a program using the .net package you provided to extract the com2 active frequency.  I am somewhat of a programming amateur, so please forgive me...

From what i've read, the frequency drops the leading '1' and stores only the xx.xx portion in Binary Coded Decimal format - ok, I've read up on that and understand how it works, but how the heck do i
a) pull it from fsuipc (type integer?)
b) convert it to xx.xx format for display in a text field?

any help you can spare would be great - i realise that this is probably a really stupid question.

cheers,
Devon.

[Paul Henty]

Hi Devon,

Not a stupid question - it's simple when you know how, but if you don't know then it's not so easy!

The offset for COM2 is specified as 2 bytes in the programmer’s documentation so we declare it as a 16 bit integer (ie, System.Int16, or Short in VB, or short in C#):

VB:

Dim com2bcd As Offset(Of Short) = New FSUIPC.Offset(Of Short)(&H3118)

C#:

Offset<short> com2bcd = new Offset<short>(0x3118);

After processing, the value of this offset will be a number with the frequency encoded in BCD format.  Each group of 4 bits out of the 16 specifies a digit in the frequency.  To get this into a string representing the frequency we need to convert each group of 4 bits into a digit representing the value stored in those 4 bits.  

This is the same as converting a binary number into Hexadecimal format.  Fortunately the .NET framework can do this for us.  We use one of the overloads of the ToString method.  We pass in "X" to request the number to be formatted in Hex:

VB:

Dim com2String As String = com2bcd.Value.ToString("X")

C#:

string com2String = com2bcd.Value.ToString("X");

What we now have is a four digit string where the first two are before the decimal point and the last two are after.

For example if the frequency is 119.45 what we will have now is "1945".

All we need to do now is put the missing 1 on the front and insert the decimal point thus:

VB:

com2String = "1" & com2String.Substring(0, 2) & "." & com2String.Substring(2, 2)

c#:

com2String = "1" + com2String.Substring(0, 2) + "." + com2String.Substring(2, 2);

If you want to set a com frequency you'll need to reverse the process.  The following shows using the static Parse method on the System.Int16 class to set the value of the com2bcd offset we declared.  Note that you need to parse the 'interesting' four digits so you'll need to get the new frequency into that format first.

VB:

Dim newCom2Frequency As String = "1945" ' Set to 119.45
com2bcd.Value = Short.Parse(newCom2Frequency, Globalization.NumberStyles.AllowHexSpecifier)

C#:

string newCom2Frequency = "1945"; // Set to 119.45
com2bcd.Value = short.Parse(newCom2Frequency, System.Globalization.NumberStyles.AllowHexSpecifier);

Hope this helps.  If you need any more info just ask...


Paul

[rabbitcancer]

Paul - Thanks so much.  I haven't gotten back to the PC, but everything you've written seems so logical.

As I'm new to .net, I was unaware of that function shortcut, so you've probably saved me tons of agony there - Thanks again.

If it makes you proud of me - I did eventually figure out how to retrieve the value with a short (i realized this as I was grabbing the value for Com1 as well and it occurred that I was 'running too far' from the offset) - but the next step would have had me befuddled for ages.

...and the concat line at the end is very helpful.

What a great New Years Day present - Cheers!!!!

Best regards,
Devon.

[rabbitcancer]

Hi Paul,  

Just a follow-up.

Not only did your code help - it unlocked the floodgates.  I have completed my app as a tray application and it's running marvelously.

On that note - I am also experiencing the same problem if FS is closed when the app is running (in debug mode) - could it be a 'throw' exception is needed?  

I've set my app up with the idea of being loaded before FS - in this manner, it polls for FSUIPC every five seconds with the .open method until FS is detected and once it is, it begins polling offsets with the .process method every 1/2 second.  If the connection drops, I've written it to halt using the .process and resume 5-second monitoring with .open ...

Sounds great  -but what actually happens is that I must run the app while FS is open or it doesn't detect - also, if I close FS while the app is open, i also get an exception error...I shall try and post the trouble spot later today if needed.  Based on what I've read above and experienced myself - I believe the issue resides in the exception handling for the .process method as it is the first to get hit by a dropped connection and because my program does not report an error if fs is not loaded when it boots - only when FS closes which means that the .process method is catching (or throwing rather) the exception as the .open is not being used at that stage.  Any thoughts?

Your experience and assistance is greatly appreciated.

Regards,

Devon.

[Paul Henty]

Hi Devon,

I'm assuming that your app executes the Process() in a try, catch block.  If FS is closed the Process() method should throw an FSUIPCException which you have to catch and then do whatever you need to.  If you are doing this (as Luis above seems to be) but there's still an unhandled exception appearing from somewhere then there seems to be a problem.

Can you let me know the exact exception wording (message) and its classtype.  

Can you also do me a quick favour?  If you use C# or VB.NET can you load up one of my sample programs and see what happens when you unload FS while it's are running?

It should handle it gracefully - ie, there should be a message box telling you the connection has been lost and the [connect] button should light.  

If you can give my any code snippits that would help too.  My email address is in the documentation if you'd prefer email.

Paul

[rabbitcancer]

Good ideas, Paul - I'll take a look at that tonight.  (I'm on Edinburgh time GMT+0)

Quick answer is yes - I'm definitely using a try/catch block.  (with a throw i think)

I wouldn't have modified it from your original too much - although the app looks a lot different because my app doesn't have a form per se - just a tray icon with a righty-popup.

Let me get back to you...

Devon.

[rabbitcancer]

Hi Paul - haven't forgotten about you, just been busy last couple days...hoping to look into this tomorrow...

Question: if the fsuipc.close() is not in a try/catch block, could this cause issues?

[rabbitcancer]

Paul,

If you get a chance - could you send me your email address to devon.leslie@gmail.com

The code is working in debug state - but in publish state the program jams occasionally and the audio doesn't work at all.

I'm prepared to send you the entire project if you could look through it.

Let me know,
Devon.

[Anders Persson]

Paul

Just wanted to say a BIG THANK YOU for the great client dll you created.
It is very good.
Thanks a lot!  :D

[Graham Pollitt]

Hi

I can read the lat and longitude as for example 47.xxxxxx and -122.xxxxxx degrees.

Showing the co-ordinates in FS displays N47*26.75 W122*18.26.

Does anyone know the code for converting the decimal degrees into degrees, minutes and seconds in VB.net?
I am trying to code an app to 'read' where the plane is ie on a taxiway, parking or runway

many thanks
Graham

[Paul Henty]

Hi Graham,

1. Take off the degrees part so you're left with only the value after the point

2. Multiply the result by 60 to convert to minutes.  

In .NET you can use the Math.Truncate method to get the integer portion and then subtract it leaving only the bit after the point.

Here's how the whole thing looks:  (This assumes a double called Lon has already been created and is holding the location in decimal degrees.  What you end up with is another double which holds the number of Minutes represented by the deciimal portion of Lon).

C#

double lonMinutes = Math.Abs(lon - Math.Truncate(lon)) * 60d;

VB.NET

Dim lonMinutes As Double = Math.Abs(lon - Math.Truncate(lon)) * 60D

BTW the 'Abs' method makes sure the answer is +tve.  Otherwise for -tve degrees you'll end up with a -tve seconds value which probably isn't what you want.  If you do, just delete "Math.Abs" - Leave the brackets in though!

The same thing will work for Lat.

LonMinutes now holds the number of minutes before the decimal point with the seconds represented as the part after the decimal point.

That's as far as the FS display goes.  You can however do the same operation on lonMinutes to get the number of seconds if you need to.

I assume you need to do this for display purposes.  If you are just trying to test the position of the aircraft in code I think it would be much easier just to use the raw decimal degrees that you get from FSUIPC.  That way you only have to test one number and don't have to go through the conversion.

If you need any more info let me know.


Paul

[Graham Pollitt]

I appreciate your detailed reply Paul. Thankyou

I am coding a flight monitor to check I am flying the aircraft using correct procedures at each stage of flight.

What I am trying to achieve is to detect whether the aircraft is on the runway, taxiway etc and then checking the appropriate lights, flaps etc are on/set.

You make a good point of not converting the lat/long and I think that I will follow that. I am going to get the lat/long values from the airport charts and make a table so I can check the aircraft pos against it and know where I am.

The charts are in dec,min,sec format so is there a quick fire way of converting this back into decimal format as read via your offsets?

thanks again for your support
Graham

[Paul Henty]

Quote

The charts are in dec,min,sec format so is there a quick fire way of converting this back into decimal format as read via your offsets?

Say you have:

40* 24' 36.1"

1. take the minutes and divide by 60 to convert to degrees: 24/60 = 0.4  

2. take the seconds and divide by 3600 to convert to degrees: 36.1/3600 = 0.0100278

3. Add them both to the number of degrees:

40 + 0.4 + 0.0100278 = 40.4100278

so in short it's:

Degrees + (Minutes / 60) + (Seconds / 3600)

If the lon or lat degrees are -tve (e.g. -40* 24' 36.1")

Then it's:

Degrees - (Minutes / 60) - (Seconds / 3600)

-40 - 0.4 - 0.0100278 = -40.4100278

I'm going to look at adding a Lon/Lat class or type into the DLL.  It'll let you convert between the FS Integer format, the degrees decimal format, the degrees,minutes,seconds format and let you extract the degrees or minutes or seconds portion of the value.

I'll try and get it done over Easter but I can't promise.

Paul

[Graham Pollitt]

My program can now check if a plane is on/off a runway

KSEA works perfect as the runway is more or less straight up

However, when trying to add KBFI I discovered a fatal flaw in my coding. I never thought that not all runways are that straightforward eg KBFI runway runs at 310degrees, which is -50degrees offset from north.

Basically in my code I get the lat/long of my plane and check it against the 'box' of the runway. KSEA is fine as it is more or less a perfect rectangle at true north.

Here is my code for checking I am on runway.

(bl is bottom left, tr is top right etc)


            'are we on ground and within the left side limits of the runway, left and right
            If onground = 1 And latitude > departurerunwaybllat And longitude > departurerunwaybllong And latitude < departurerunwaytllat And longitude > departurerunwaytllong Then

                'are we within the right limits of the runway, left and right
                If latitude < departurerunwaytrlat And longitude < departurerunwaytrlong And latitude > departurerunwaybrlat And longitude < departurerunwaybrlong Then

'plane is on runway

etc


This works perfect for a 'straight-upwards box'.

How can I rotate this 'box' 50 degrees to the left so I can check the lat/long of KBFI?

Many thanks
Graham