AD Lite Integer Error

[GlaMichael]

Hello All,

First time poster but long time reader - I think I've read the full forum several times over!

I'm having a problem with AD Lite, every so often it pops up with an integer error - Something like cannot convert "" to an integer.

I've read, and followed, the below thread but I still receive the integer error!

http://radarspotting.com/forum/index.php/topic,3842.0.html

Sometimes it will run happily for hours before popping up, other times it will only run a few minutes. I've tried uninstalling/re-installing, made sure .net framework was up-to-date but still nothing I can see aircraft appear on base station - So it's definately getting a feed from VRS rebroadcast.

Does anyone have any ideas why this keeps happening?

Thank you!

Michael

[GlaMichael]

This is the error message:-

Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.

Conversion from string "" to type 'Integer' is not valid.

Details:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.InvalidCastException: Conversion from string "" to type 'Integer' is not valid. ---> System.FormatException: Input string was not in a correct format.
   at Microsoft.VisualBasic.CompilerServices.Conversions.ParseDouble(String Value, NumberFormatInfo NumberFormat)
   at Microsoft.VisualBasic.CompilerServices.Conversions.ToInteger(String Value)
   --- End of inner exception stack trace ---
   at Microsoft.VisualBasic.CompilerServices.Conversions.ToInteger(String Value)
   at ActiveDisplayLite.ActiveDisplayLiteForm.TCPStart()
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
ActiveDisplayLite
    Assembly Version: 1.64.0.30
    Win32 Version: 1.64.0.30
    CodeBase: file:///C:/Users/**USERNAME**/AppData/Local/Apps/2.0/Q1E0V5JV.ANW/GCK3VE60.3ND/acti..tion_d45369983457ba68_0001.0040_c37daece00ff8ad5/ActiveDisplayLite.exe
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.5483 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5488 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Data.SQLite
    Assembly Version: 1.0.65.0
    Win32 Version: 1.0.65.0
    CodeBase: file:///C:/Users/**USERNAME**/AppData/Local/Apps/2.0/Q1E0V5JV.ANW/GCK3VE60.3ND/acti..tion_d45369983457ba68_0001.0040_c37daece00ff8ad5/System.Data.SQLite.DLL
----------------------------------------
System.Data
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_64/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Transactions
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_64/System.Transactions/2.0.0.0__b77a5c561934e089/System.Transactions.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Management
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
System.Web.Services
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Web.Services/2.0.0.0__b03f5f7f11d50a3a/System.Web.Services.dll
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
mvsmrqu-
    Assembly Version: 1.64.0.30
    Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
7tq0_wqx
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.EnterpriseServices
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_64/System.EnterpriseServices/2.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
----------------------------------------
Accessibility
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

[Anmer]

Sorry for the late reply, I've been away.

Can you describe your setup?

Receiver - Software - Database - ADLite

And are you "sharing data with anyone and/or importing database records from elsewhere, other than messages received from your receiver?

[GlaMichael]

Hi Anmer,

No problem, thanks for the reply

I've now got this fixed.. however in turn have knocked something else out of joint. AD Lite now runs fine - However I now have two entries per aircraft on my VRS reports!

My set up is:

USB ADS-B Receiver > VRS > Modesmixer > BaseStation > AD Lite.

I was feeding FR24 but I removed that in my attempt to get ADL to work.

I'll get there eventually

Thank you

[Anmer]

Thanks.

BaseStation was developed to be used with a Kinetic Avionics' receiver and AD Lite to work with the BaseStation sqb database.

Maybe the DVB=T receiver decoding and/or the VRS/Modemixer path is introducing "bad" data into the sqb file?

How did you fix the original issue?

[GlaMichael]

Yeah, I know I'm probably pushing the limits on trying to get it to work with USB and VRS but I know it's possible and I'd like to share how to do so when I get it - If anyone is interested obviously.

That was my thinking - I'll need to try retrace the steps and find out where.

Well I thought it was fixed as it ran for around 20 hours without issue - Its just this minute popped back up again

[Anmer]

My guess is AD Lite is finding a "bad" record in the sqb file.

[IanH]

Now that Anmer has established your setup (which was essential to understand the problem), there are alternative ways of doing the same thing but avoiding a long sequence where data may get a few bits wrong.

You don't say what you are using to get data from the USB receiver into VRS or what the USB receiver is.

Assuming it is a dongle, try using ModeSDeco to get the data from the dongle.
A command line of:

Code Select Expand

cmd /c modesdeco2.exe --gain 49.6 --sbs10001 10001 --beast 31001
will output SBS data on port 10001 and beast data on port 31001.

Set up BaseStation to get its network data from 127.0.0.1 on port 10001. Connect AD Lite to the BS output.

Set up VRS to get its data as 'AVR or Beast Raw Feed" on address 127.0.0.1 and port 31001.

That all worked for me -  and by splitting the output you don't carry errors into the next program.

USB ADS-B Receiver >  ModesDeco > BaseStation > AD Lite.
                                                          |
                                                          > VRS

Or if you want to continue using ModeSMixer, put it before VRS and send one input into VRS and another into BasesStation/ADLite. You will need something to get the data from the dongle - there are a variety of programs (dump1090, ModeSDeco, RTL1090, ADSB#) but what are you using now?

USB ADS-B Receiver > ?? > Modesmixer > BaseStation > AD Lite
                                                                     |
                                                                    > VRS

Let me know how you get on.


Edit: finally found the background for all this at SonicGoose which might be of use for what you are trying to do:

[Anmer]

Excellent, thanks Ian.

[GlaMichael]

Thanks very much Anmer and Ian - I appreciate your replies and help!

Sorry, Ian - I'll explain below hopefully in more detail.

USB Dongle > RTL1090 > VRS > Modesmixer > Base Station > AD Lite.

From what you have said above and looking at my "chain" VRS and Modesmixer are in the wrong place.

Do you know what the command line would be for modesmixer to output to both BS and VRS? Inconnect **RTL1090** outserver sbs10001:10001 outserver beast:31001?    Does that seem right?

Lastly, and sorry for all the questions!, would that not write two entries for each aircraft? One from VRS databasewriter and the other from SBS/ADL?

Thanks again for all your help!

Edit: Going back to what Anmer mentioned about the bad record in the sqb file. Is there any way to find if that's the case, and if possible who h record it is? The pre-populated sqb file I'm using was from the abs resources file.

[Anmer]

If you rename the sqb file, BaseStation will create a new, empty one when it is launched again.

AD Lite will "populate" an existing record in the sqb file.  It shouldn't write a new record.

[GlaMichael]

Thanks Anmer, I'll give that a go tonight as well as Ian's suggestions above.


I know ADL only 'updates' any missing aircraft info - But does Base Station not write flight info to the sqb? So both Base Station and VRS will be recording any tracked aircraft? Or is my logic wrong?

Thanks again, Anmer. I'd probably be going round in circles without the help from you guys!

[IanH]

Not so much in the wrong place but trying to separate the streams so that VRS and BaseStation get their own input from the receiver. That is the beauty of ModeSMixer.

That way you are not passing bad/corrupt information to another program which chokes on it.

I'll look at your other question late - food is calling 

[Anmer]

I'm away from home at the moment but from memory, VRS doesn't write records to the sqb file but references it for aircraft personalisation and to access a suitable silhouette/logo using the Operator Flag Code data.  But I may be wrong.

[GlaMichael]

Yeah I get what you mean, Ian. I'll give it a go later when I'm home and if that doesn't work I'll try ModeSDeco as you advised

Thanks Anmer, that's good to hear. I'll try do some testing and confirm your thoughts!