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
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.
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?
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 :P
Thank you
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?
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 :(
My guess is AD Lite is finding a "bad" record in the sqb file.
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:
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:
(http://sonicgoose.com/wp-content/uploads/2014/09/ADSB_Flowchart_3.png)
Excellent, thanks Ian.
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.
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.
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!
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 ;D
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.
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! :D
QuoteLastly, 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?
Anmer is on the right line. The plugin was added to allow VRS to write to an SQB file but it is not entirely compatible with the version written by BaseStation so you would get corruption even without two programs trying to write to the same database! There is a warning with the VRS plugin about all this.
So let BaseStation
read and write to its own SQB file and just point VRS to it so that it can
read the information. Just had a look at the test PC I set up last night and that is what I did.
I see now that you are using RTL1090. That was once the preferred program but not so sure now. Not sure if the newer ones give more data? But it might also be because people wanted to supply MLAT data for PlanePlotter so they used dump1090. You can decide what you want to use ;D
I'll try various ModeSMixer command lines later - can't remember how to get RTL1090 data passed on.
Yeah that's what I was thinking, Ian. That could explain why I have two entries per aircraft, both with a slightly (1 second or so) different tracking time. I'll select the checkbox to only allow VRS to write to a database it created - that should solve that one.
Yeah you could be right, I don't really have a preference as long as it works! Would you suggest dump1090 over RTL1090?
Thanks very much, Ian. I appreciate your help!
Ok... Quick update!
I changed my modesmixer.bat file to receive from RTL1090 and output to sbs and beast. I then connected Base station to the sbs feed and then connected ADL to the output of Base station. Then I started VRS and updated the receiver to the beast feed. Started it all up and it was working... For about 20 minutes until the integer error appeared :(
I then Downloaded modesdeco2 and set that up to receive from the USB Dongle and output to sbs and beast as Ian had advised above. I connected BS, ADL and VRS as above. It a now been running over an hour without the integer error! :D
The only thing I have noticed, unless it's just my mind playing up, but I feel like I'm getting less range/aircraft tracking this way rather than when using RTL1090. Have you experienced that?
A big thanks to both of you for your help! At last I feel like I'm getting somewhere! :D
You wrote your reply while I was compiling this! So ignore what is no longer relevant 8)
All I can say is that I don't really have a preference but ModeSDeco worked for me last night to set up VR and BS/ADL fairly easily.
More importantly it is still running without any problem 22 hours later.
Best way to run ModeSDeco (or dump1090) is as a batch file.{or not if it is working ok for you)
You've already run ModeSMixer so you will probably have installed the vcredist.exe files.
Put this in a text file in the ModeSDeco folder, rename it "start.bat" and that will set up the feeding of source data:
@echo off
cmd /c modesdeco2.exe --gain 49.6 --sbs10001 10001 --beast 31001
PAUSE
exitThen use the previous instructions to get BS/ADL and VRS working.
And this is the warning from the author of VRS:
QuoteThe database writer plugin is a plugin for Virtual Radar Server that will record flights and aircraft in an SQLite database. The schema of the database matches the schema established by Kinetic for their BaseStation program. Virtual Radar Server uses the records in the database to produce its reports.
Please do NOT install this plugin if you have a Kinetics radio!
If you are using Kinetics' BaseStation program then it will already be maintaining a database for you. If you install this plugin and use it to update the database that BaseStation is also updating then you will ruin your database.
OK so you don't have a Kinetics radio
BUT that was written before ModeSMixer, etc enabled people to use BS without an SBS-1/SBS-3. I would really recommend you just have VRS reading not writing the database.
As for range why not use the facility in VRS to show the receiver range - what is called the "polar plot" in some other software.
I'm wondering if RTL1090 is the source of the "integer" problem"?
I might have chance to try RTL1090/dump1090 later but if not, later this week.
And just occurred to me that the range "problem" might be a consequence of my "quick and dirty" setting of the gain parameter - changing that might help.
But for the full info on all that you need to have a read of the source explanations from the author at http://radarspotting.com/forum/index.php/topic,2978.0.html
Ah, sorry :P
Yeah I'm beginning to think that now too, remove it out the equation and the error disappears. Thanks, I've had a read through that link and the bit that jumps out at me is:
"I think that values --gain and --agc must be chosen experimentally for your receiving conditions and antenna-feeder device. This values is better to do the same as with RTL1090, for example, may be "auto". To do this delete the option --gain from cmd. If you, when working with RTL1090, use automatic gain control in RTL2832 chip, then add the option --agc"
So I guess that means I should remove the --gain 49.6 from the .bat file and make sure --agc is in there?
I guess if I run dump1090 I'd need to use modesmixer again to split the feed to BS and VRS?
Yeah I think that's what was doubling up the entries in my reports - Tgeres a checkbox to stop the writer plugin from writing to a .sqb that it never created - So I've checked that box too :)
Thanks again, Ian :)
I've been running RTL1090 on a dongle overnight feeding BS/ADL without any problem.
ModeSMixer batch file is:
@echo off
cmd /c modesmixer2.exe --inConnect 127.0.0.1:31001 --outServer sbs10001:10001
PAUSE
exit
Not been running VRS with this set up.
I'm more convinced than ever that writing to basestation.sqb with VRS when running BaseStation is creating bad records that AD Lite doesn't know how to handle and gives the integer error.
I'll try doing that later and see if I can get the error.
Hmm.. Maybe you're right. I've been running modesdeco2 since last night and everything is working as it should.
I'd still like to run a comparisson between RTL1090 and modesdeco2 though and see if I notice an increase in range - However when I tried adding --outserver beast:33001 to my modesmixer2.bat it crashed out. Am I doing something wrong? (Basically using your file in your last post and adding that after your sbs line).
Thanks again for your help, Ian. If there was a points or recommend button on here I'd definately be clicking it! :)
it doesn't work for me either and I don't know why.
Instead I just used the port 30003 output from BaseStation to feed VRS.
Strange.
Can you feed both VRS and ADL from the one port? That could be another option.
The range issue seems to have died down a little, in fact I'm now tracking some aircraft further than I was with RTL1090! I'll get a few days worth of data in and review again then :)
Thanks very much for your help again, Ian. Its greatly appreciated!
Yes BaseStation doesn't mind sharing data from port 30003. I've just started srv3003 as well which plots the receiver range from BS.
So I've got ADL, srv3003 and VRS getting data from port 30003
The hardware boxes SBS-1/e/er and SBS-3 will not share output. There was an early piece of software written by the guy who did RTL1090 called MultiEM which I have and works fine to share from the SBS-1e but not the SBS-3.
Hence, amongst the other capabilities, the importance of ModeSMixer!
And also why ModeSMixer doesn't need to have an SBS30003 output ;D
That's good, thanks Ian. I thought you could only have one thing pulling from each port.. obviously not!
I've downloaded and got running dump1090 to see how that fares.. my setup is below.
USB Dongle > Dump1090 > modesmixer > Base Station > Both ADL and VRS are feeding from BS:30003.
Seems to be running pretty well just now, no errors and pretty good range. Will see how this goes for a couple of days :)
Thanks again, Ian. Without your help this would have been much more difficult! :)
Once things are working ok, experiment to find the best setup.
And the real thanks are to Anmer for setting up this forum so we can exchange information.
Otherwise it is just what each individual knows but no sharing :(
Quote from: IanH on January 30, 2015, 09:10:44 PM
And the real thanks are to Anmer for setting up this forum so we can exchange information.
Anyone can set up a forum. The value is added by those who seek information and, more importantly, those who provide solutions, such as you Ian.
The alternative is a forum dominated by posts with content copied from other websites. ;)
Yeah, thanks to you both!
So it's now been running for the past 10 days or so. I've swapped around between RTL1090, Dump1090 and modesdeco2. For my setup, the best results were from Dump1090, so my setup is as below:
USB Dongle > Dump1090 > Modesmixer > Base station > VRS
V
AD Lite
So base station is feeding VRS and AD Lite. I've not had any "integer errors" for the past 10 days, and I'm getting not bad range too. So that's it... Now just need to start looking at an outdoor antenna to reach even further! :D
Thanks again for your help, Ian and Anmer - Much appreciated!
Thanks for the update.
Good evening to all,
Today i decided to run 24/7 my RTL2832-R820T2 usb dongle , instead of my old SBS-1 MKI.
My setup is dump1090 --> modesmixer2 --> Basestation --> VRS and AD Lite.
The .bat files i used were :
dump1090.exe --interactive --net --modeac --net-beast --net-http-port 8088 --net-ro-size 500 --net-ro-rate 5 --net-buffer 5 --aggressive --mlat --ppm 53
pause
modesmixer2 --inConnect 127.0.0.1:30005 --outServer sbs10001:10001 --web 8888 --db C:\modesmixer2\BaseStation.sqb --location 40.64:22.93
PAUSE
exit
And in VRS , Format : BaseStation and Port :30003
Also i'm feeding FR24 with no pronlems.
But when i'm running AD Lite (BaseStation path is C:\Program Files\Kinetic\Basestation2\BaseStation.sqb which is the active one) ,unfortunatelly stuck and gave the integer error...What's going on? Where is the fault?
Before usb dongle , i run the SBS-1 MKI with the above setup and all worked perfect!!!
Thanks a lot
AD Lite needs Basestation to be running to work. No Basestation and AD Lite won't run.
I m sorry, what do you mean? Usb dongle feed the targets throught modesmixer2 to Basestation and looks like that the. sqb database is working.
AD Lite checks if there is a running version of the BaseStation.exe .
Yes the Basestation is running all the time, dongle is feeding as i said with data throught modesmixer2
Does ADLite work if VRS isn't running?
Nope i've test it... I think the problem began and its due to USB dongle and all the setup... Before with SBS-1 run perfect
If all you changed was the receiver from SBS to DVB-T "dongle", that should not be the issue.
Its first time i m running usb dongle and AD Lite together, because i d like my aircraft database to be always up to date.
What I'm trying to say is if ADLite worked OK before with your setup using an SBS-1, just swapping it for a DVB-T should not cause ADLite to error.
Finally finished decorating lounge with associated moving of furniture. And with new carpet fitted today I should have some time to test a dongle with BS, VRS, etc. to see what the problem is. If I can find anything.