I have AdsbScope running with RTL1090 and feed to FR24 and it works fine.
I can also run FR24 feed using dump1090 but have not been able to figure out out to get dump1090 to work with Adsbscope.
Can someone help me with the connections between dump1090 and adsbscope?
js
Welcome
This may help:
http://sonicgoose.com/how-to-setup-adsbscope/
Or this:
http://bubbazanetti.blogspot.co.uk/2013/09/raspberry-pi-wth-rtl-sdr-receiving-ads.html
Basically, adsbScope needs to know which port has the decoded data from dump1090.
Quote from: Anmer on June 20, 2015, 08:47:21 AM
Welcome
This may help:
http://sonicgoose.com/how-to-setup-adsbscope/
That assumes RTL1090 and works fine but does not related to dump1090
>Or this:
>http://bubbazanetti.blogspot.co.uk/2013/09/raspberry-pi-wth-rtl-sdr-receiving-ads.html
That assumes PI and I have no idea how to relate that to anything.
>Basically, adsbScope needs to know which port has the decoded data from dump1090.
That seems to be my problem. When I start dump1090 it just starts running showing AC by the zillions but not a clue about what it's doing or where it's putting the data.
Thanks for getting back. This has been driving me nuts so any help will be most appreciated.
js
One more really basic problem here.
It is not clear to me which program is the client and which is the server nor what the terms really mean.
FR24 says that when running their feed which automatically loads dump1090, all abscope needs to know is the raw date client number but I don't know where to find that info.
When running only dump 1090 into adbscope, you say it wants the decoded data port number but where do I find this and where do I put it?
Thanks again,
Jack
On what are you running dump1090? What hardware and operating system?
And what receiver are you using?
You need to run Dump1090 with the required parameters:
--net = enable networking
--net-beast = output in Beast binary format so ADSBscope understands it
--net bo-port = changes the port where beat output is sent
This is the command line you need with ADBScope set up just as it was for RTL1090:
dump1090.exe --interactive --net --net-beast --net-bo-port 31001
Easiest to create a batch file in the dump1090 folder with these commands!
Quote from: Anmer on June 20, 2015, 07:32:39 PM
On what are you running dump1090? What hardware and operating system?
Dell laptop running XP.
>And what receiver are you using?
RTL dongal
I see another response here but need to digest it.
For openers, I want to rung ADSBscope from dumb 1090.
After I get that working, I want to feed into FR24 feed.
The idea is to be able to see my planes while feeding FR24.
js
Quote from: IanH on June 21, 2015, 04:20:36 PM
You need to run Dump1090 with the required parameters:
--net = enable networking
--net-beast = output in Beast binary format so ADSBscope understands it
--net bo-port = changes the port where beat output is sent
This is the command line you need with ADBScope set up just as it was for RTL1090:
dump1090.exe --interactive --net --net-beast --net-bo-port 31001
Easiest to create a batch file in the dump1090 folder with these commands!
Not real hip on command line stuff but are you saying to go to command line and paste that bit of code after the prompt and everything will be nice?
js
If you are not too familiar with the command line, creating a batch file to run the commands will be easier.
Find the folder where you have unzipped the dump1090.exe file. In that folder create a text file (with Notepad, for example) called dump.txt (or whatever you want to call it).
Copy the text
dump1090.exe --interactive --net --net-beast --net-bo-port 31001
pause
into the text file and save it.
Rename the dump.txt file to dump.bat - Windows might need you to confirm you want to do this.
Now when you double-click on dump.bat, it should start dump1090 with the required parameters to work with adsbScope.
The pause command is in there so that the batch file asks if you want to quit - useful for sorting out problems.
Quote from: IanH on June 22, 2015, 06:13:08 PM
If you are not too familiar with the command line, creating a batch file to run the commands will be easier.
Find the folder......
Cool! Worked right out of the box. You also furnished motivation to find out what a batch file is.
I have been on the internet since long before Al Gore invented it and somehow survived without ever needing to know.
Now for the next step:
FR24feed automatically installs dump1090 when the program is executed so it creates a conflict here I think.
First of all, it loads a version called mr-dump1090 and I have no idea what or why.
Secondly, I assume it has to have a different .bat file to set it up or is it just a matter of adding "mr-" to beginng of the code I just put in there?
What I tried and does not work was to make a mr-dump bat file and put it into the same folder.
Execute FR24feed>remove mr-dump from the task manager and then execute the mr-dump bat file.
The FR24feed just pings and displays no AC.
I seem to be missing something,
Thanks for the help, BTW.
Jack
OK, Plan B :)
The batch file set up the required data from dump1090 to appear on port 31001 since that is what adsbScope expected. Usually dump1090 outputs the data on port 30005.
If we can't adjust dump1090, we need to tell adsbScope where to find the data.
Back to an earlier reference: http://sonicgoose.com/how-to-setup-adsbscope/
In the section called "Connect ADSBScope to the Decoder" it shows a screen shot for Network Setup. The port number is shown as 31001 - change this to 30005, make sure all the other values are as shown, and close that window.
Hopefully it will now all work. I can't remember if there is a way to save adsbScope settings (PC running adsbScope is turned off right now) - if there is do it otherwise the port will need to be changed each time you start it.
If that doesn't work, we will need to see what the FR feeder is doing ;)
I can't get your last working but for what it's worth, this is what the batch file that comes with FR24 looks like....
dump1090.exe --interactive --net --net-ro-size 500 --net-ro-rate 5 --net-buffer 5 --net-beast --mlat
pause
Any clues there?
Jack
I was just about to reply that I did not think my previous idea would work. But looking at that FR24 batch file, it's not much different to mine.
Is that batch file in the FR24feeder folder?
I'm wondering why it says "dump1090,exe" when the file is called "mr-dump1090.exe"?
I ran that FR24 batch file with adsbScope set up as shown below and it worked!
[Attachment deleted by Admin to save file space]
Quote from: IanH on June 23, 2015, 06:23:52 PM
I was just about to reply that I did not think my previous idea would work. But looking at that FR24 batch file, it's not much different to mine.
The only thing notable is the mlat in it.
>Is that batch file in the FR24feeder folder?
Yes
>I'm wondering why it says "dump1090,exe" when the file is called "mr-dump1090.exe"?
I was hoping you would tell me that. BTW, I spent a good deal of time on the FR24 group and got a lot less help then here and I want to thank you profusely.
>I ran that FR24 batch file with adsbScope set up as shown below and it worked!
I will go out and give it a try but did you run run FR24feed or just the bat file?
js
IGNORE ALL THIS - I've just tried FRFeed.exe and there may be a simple fix if I can figure out!
The ideas below are probably not going to work!!
======================================================
Just the bat file - I'm not feeding FR24 via FRFeed so I don't want to confuse things.
If it doesn't work, I'm away for the next few days so maybe someone else can help.
Otherwise I'll see what you have found.
As for your questions in earlier posts, adsbScope is the Client. Anything feeding data to it is the Server in this context.
I'm assuming that you know how to change the port address to 31005 - it is under other/Network/Network setup in the adsbScope menus. Press the "BEAST" button and type in 31005 for Portnumber. Press the "Local" button to make sure the URL is 127.0.0.1.
Once that is set, and you have closed the window, hit the button that shows PCs in a circle - it has a label "start RAW-data client" if you hover the mouse pointer over it.
I will be away for the next few days. Report back here what you find -someone else might know the answer or I'll take a look when I get back. This should be simple to fix ;)
==========================================================
Quote from: IanH on June 23, 2015, 06:23:52 PM
I ran that FR24 batch file with adsbScope set up as shown below and it worked!
Me too. Works fine with ADSBscope and with the older version of FR24feed.
Now for plan C.
It needs to work with the current (new) version of FR24feed. Unfortunately, I do not know how to determine the versions of these (dos?) sort of programs.
The new version of FR24feed provides a whole page of stats and charts on one's feed in addition to feeding the mlat system. It also makes it possible to use the radar version of FR24.
The older version simply feeds the adsb into the system and might as well be into a sewer as far as the feeder is concerned.
So, if you or anyone has any ideas here, we are getting close but no cigar yet.
.....................
Don't know if this is a good place to ask but I am pretty confused on what Mlat really is.
All I have read is that it is a way to track planes that are not transmitting adsb but have yet to hear what they are transmitting that provides the data displayed.
In my limited experience, the Mlat planes are as likely as the FAA planes to not really be where the are supposed to be. Every adsb plane on my display within line of sight can be seen but this is far from the case with either of the others. So how does it really work?
js
Astronomy, Beer, Cheese, Fiber, Gems,
Nature, Radio, Sheep, Sausage, Silver
http://schmidling.com
Quote from: K9ACT on June 24, 2015, 01:40:09 AM
Don't know if this is a good place to ask but I am pretty confused on what Mlat really is.
It's best to keep to the original message topic but there's a free Guide here that explains MLAT on page 15:
http://radarspotting.com/forum/index.php?action=tpmod;dl=item92
Quote from: Anmer on June 24, 2015, 08:18:07 AM
Quote from: K9ACT on June 24, 2015, 01:40:09 AM
Don't know if this is a good place to ask but I am pretty confused on what Mlat really is.
It's best to keep to the original message topic but there's a free Guide here that explains MLAT on page 15:
http://radarspotting.com/forum/index.php?action=tpmod;dl=item92
Not sure I see the answer to my question there.
I understand the geometry involved but if the planes do not have Mode S capability, how are the Mode S receivers getting data from the plane to make the calculations?
Jack
Quote from: K9ACT on June 24, 2015, 04:15:14 PM
I understand the geometry involved but if the planes do not have Mode S capability, how are the Mode S receivers getting data from the plane to make the calculations?
MLAT plots can be calculated for Aircraft transmitting non-positional messages on 1090 MHz Mode-S.
Page 15:
As mentioned earlier, not all Mode-S transmissions include positional data. Typically
private and military aircraft don't transmit positions nor do some larger aircraft
operated by airlines such as Flybe.
Mlat uses data from three or more Mode-S receivers to calculate the aircraft's
location by means of geometry. The PP Mlat tutorial explains:
If you know the precise distance between an unknown location and three
known locations, then it is simply a matter of geometry to determine the
position of the unknown. In the case of multilateration using radio signals,
the distance is measured in terms of the travel time of the signal, at the
speed of light (300 metres per microsecond).As I said, it's a complex subject. Let's just say that PP Mlat is sometimes able to plot
the whereabouts of non-positional Mode-S aircraft. Commercial grade Mode-S
receivers, such as Kinetic's SBS-2 offer Mlat but at a much higher price than the
enthusiast can justify
If the aircraft isn't transmitting any Mode-S messages, MLAT (as we know it) can't be used to plot its position.
Quote from: Anmer on June 24, 2015, 04:37:57 PM
If the aircraft isn't transmitting any Mode-S messages, MLAT (as we know it) can't be used to plot its position.
Which is where the Beamfinder Plus feature comes into play.
From the PP help file:
"Mode-A/C transponder pings are transmitted in response to interrogation pulses from ground-based or airborne radar systems. Mode-A interrogations return the regular squawk code and Mode-C interrogations return the encoded altitude. Mode-A/C radar sites have a characteristic rotation period and a characteristic pulse repetition interval. If you are lucky, for some sites those values will be unique within your reception range."
Sorry to perpetuate the thread drift.
Tim
Quote from: Triple7 on June 24, 2015, 05:49:13 PM
Sorry to perpetuate the thread drift.
I was hoping this wouldn't happen. :-[
Back on topic please.
Quote from: Anmer on June 24, 2015, 04:37:57 PM
As I said, it's a complex subject. Let's just say that PP Mlat is sometimes able to plot
the whereabouts of non-positional Mode-S aircraft. Commercial grade Mode-S
receivers, such as Kinetic's SBS-2 offer Mlat but at a much higher price than the
enthusiast can justify[/color]
If the aircraft isn't transmitting any Mode-S messages, MLAT (as we know it) can't be used to plot its position.
I guess I missed the distinction of the "non-positional Mode-S".
So the question is, what is this info and do I assume that my receiver is picking this up and forwarding it to FR24?
js
Except for those using a Radarcape or the FR24 free receiver, the feeder utility will only be sending positional messages - ADS-B:
http://www.flightradar24.com/how-it-works
If you have other questions not related to "Dump 1090 problems with adsbscope", please post in another message thread.