I have seen it, is an early version. How it works
- plug the stick (the stick works with command rtl_adsb)
- import plugin --works
- setup port -- works
- the RF symbol does not become green and no meassages comes in
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you run the rtl_adsb command manually in a terminal window, are you seeing any long hexadecimal ADS-B frames coming in? Note that the short frames don't contain anything useful to YAAC. If you're not receiving anything, you won't see anything in YAAC. For example, when I was testing at a ridiculous hour of the morning (when no flights were traveling the Instrument Flight Rules approach over my house), I didn't see any ADS-B frames either. In early evening when the wind was blowing the correct direction for Air Traffic Control to specify the IFR approach over my house, the frames were coming through thick and fast (and I could see the landing lights on the airplanes :-).
Admittedly, the RF control button won't become green because the timing in the reading thread only turns on the green extremely briefly after the completion of the receipt of each frame, not while the frame is actually coming in.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You need to upgrade your plugin and YAAC. This is reporting you have mismatching versions, such that the plugin is trying to access a field in a core YAAC data structure that no longer exists. Since this access is not in the current version of the ADSB plugin, at least that is out of date.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Running Windows 10 and have a NooElec Smart RTL-SDR dongle, set up so that it runs succesfully with SDR# or SDRUno. I have the ADSB plugin in and stored in the plugin directory. I see you recommend dump1090 -- is that for Windows? I downloaded the zip file. Now, how do I make it all work together?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
) and then configure an ADS-B port in YAAC in socket SDR mode, specifying localhost as the network address of the ADS-B decoder server, and the appropriate socket port number as defined by your program so that YAAC can receive the raw frames and process them.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
EDIT: I found I was in the wrong branch for dump1090 and found the Windows version. I got it running by itself, but cannot get YAAC to talk to it. Would also like to add support for UAT such as dump978 in case any firefighting/SAR/medical aircraft are in the area -- since they are usually below 18,000 ft, they can use UAT and many prefer UAT to ADS-B. Was recently working a SAR mission and it would have been great to plot where the SAR aircraft were. Being able to do all this data fusion on one screen with offline maps such as YAAC provides would be great.
Trying to get ADS-B to work with an RTL-SDR dongle and running ModeSDeco2 (http://xdeco.org/?page_id=39) as I am using a Win10 machine (rtl_adsb and dump1090 don't appear to be for Windows), but not having much luck. I cannot seem to get the ADS-B port (YAAC) to invoke the .bat file and based on a quick look, it seems like the internal ports (30003, 30001, etc) might not be lining up, but that is just a guess. ModeSDeco2 is working quite well by itself, I just can't seem to get it to communicate with YAAC.
Last edit: John 2017-11-14
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm not exactly sure how you would get UAT to work on Windows; I've found a set of directions that work on Linux (or other Unix-like derivatives) at this website: https://gist.github.com/fasiha/c123a9c6b6c78df7597bb45e0fed808f
It works by piping the generic rtl_sdr program into the dump978 program and subsequently piping dump978's output into uat2esnt to convert the format into dump1090's format (which YAAC understands). To do this in YAAC on a Unix-like system, you would have to configure your ADS-B port in YAAC to launch the following command:
Assuming all three subprograms (rtl_sdr, dump978, and uat2esnt) are on the PATH, this would invoke a bash shell program, which would then handle launching all three subsidiary programs and piping them together in order. I don't know what the Microsoft Windows equivalent of this would be. I don't know if dump978 would even compile and run on Windows.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I need to make a few changes to the ADS-B plugin to support piped commands like the ones above. Look for the release of adssbplugin version 0.0alpha5 soon.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So which is the correct ADSB plugin version? I have downloaded version 1.0, but the YAAC updater seems to think version 0.0alpha4 is the most up to date version.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The version of YAAC is not the same as the version of any given plugin. The ADS-B plugin is currently at version 0.0alpha4, whereas core YAAC is verson 1.0beta115 (as of today).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Build V0.0alpha5 of the ADS-B plugin now supports piped commands, so that you can use the dump978 and uat2esnt commands in a pipe to receive UAT aircraft beacons. In theory, you should be able to create two ADS-B ports (one for real ADS-B and the other for UAT) and receive both simultaneously, but you would need two SDR receivers to handle the two bands simultaneously.
Last edit: Andrew Pavlin 2017-12-18
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
I have seen it, is an early version. How it works
- plug the stick (the stick works with command rtl_adsb)
- import plugin --works
- setup port -- works
- the RF symbol does not become green and no meassages comes in
If you run the rtl_adsb command manually in a terminal window, are you seeing any long hexadecimal ADS-B frames coming in? Note that the short frames don't contain anything useful to YAAC. If you're not receiving anything, you won't see anything in YAAC. For example, when I was testing at a ridiculous hour of the morning (when no flights were traveling the Instrument Flight Rules approach over my house), I didn't see any ADS-B frames either. In early evening when the wind was blowing the correct direction for Air Traffic Control to specify the IFR approach over my house, the frames were coming through thick and fast (and I could see the landing lights on the airplanes :-).
Admittedly, the RF control button won't become green because the timing in the reading thread only turns on the green extremely briefly after the completion of the receipt of each frame, not while the frame is actually coming in.
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
I found out, it runs some 1.5 seconds than this
ADS-B: 8db958fb3bc3a7f9a4c1; DF=17 TC=11 ICAO=4b1945
informing 0 listeners of 98th new aircraft#4b1945
ADS-B: 8d6cdd999931be3d; DF=17 TC=19 ICAO=76cd6d
V[76cd6d]: subType=1 intent=false TI=0 Vew=8 Vns=-156 Vv=-277
informing 0 listeners of 99th new aircraft#76cd6d
ADS-B: 8a8088800dd8e8e59781; DF=17 TC=16 ICAO=801838
informing 0 listeners of 100th new aircraft#801838
ADS-B: 8d02b48c383c7eee51; DF=17 TC=11 ICAO=4032b4
informing 0 listeners of 101th new aircraft#4032b4
ADS-B: 8d7fe911bc09ee96d3; DF=17 TC=3 ICAO=471f4e
for aircraft#471f4e, unknown extended squitter DF=17 TC=3
ADS-B: 8dc6f2d9c7b6b0a4c4ae; DF=17 TC=27 ICAO=3c56f2
for aircraft#3c56f2, unknown extended squitter DF=17 TC=27
ADS-B: *8dca358c393b7fd89e27; DF=17 TC=11 ICAO=4ca355
Exception in thread "ADS-B stdout reader[rtl_adsb]" java.lang.NoSuchFieldError: rcptTime
at org.ka2ddo.yaac.adsbdecoder.AircraftState.decodePosition(AircraftState.java:201)
at org.ka2ddo.yaac.adsbdecoder.AircraftState.parse(AircraftState.java:92)
at org.ka2ddo.yaac.adsbdecoder.AdsbDecoderConnector.run(AdsbDecoderConnector.java:194)
at java.lang.Thread.run(Thread.java:748)
You need to upgrade your plugin and YAAC. This is reporting you have mismatching versions, such that the plugin is trying to access a field in a core YAAC data structure that no longer exists. Since this access is not in the current version of the ADSB plugin, at least that is out of date.
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Running Windows 10 and have a NooElec Smart RTL-SDR dongle, set up so that it runs succesfully with SDR# or SDRUno. I have the ADSB plugin in and stored in the plugin directory. I see you recommend dump1090 -- is that for Windows? I downloaded the zip file. Now, how do I make it all work together?
You'll need to get whatever ADS-B decoder program you use to generate raw ADS-B frames at a known server socket number (data that looks like this:
915DC78D91FFF3D7F591186D229A;
915DC78D91FFF7C78E0C7716A315;
*915DC78D998514AED468008543DD;
) and then configure an ADS-B port in YAAC in socket SDR mode, specifying localhost as the network address of the ADS-B decoder server, and the appropriate socket port number as defined by your program so that YAAC can receive the raw frames and process them.
EDIT: I found I was in the wrong branch for dump1090 and found the Windows version. I got it running by itself, but cannot get YAAC to talk to it. Would also like to add support for UAT such as dump978 in case any firefighting/SAR/medical aircraft are in the area -- since they are usually below 18,000 ft, they can use UAT and many prefer UAT to ADS-B. Was recently working a SAR mission and it would have been great to plot where the SAR aircraft were. Being able to do all this data fusion on one screen with offline maps such as YAAC provides would be great.
Trying to get ADS-B to work with an RTL-SDR dongle and running ModeSDeco2 (http://xdeco.org/?page_id=39) as I am using a Win10 machine (rtl_adsb and dump1090 don't appear to be for Windows), but not having much luck. I cannot seem to get the ADS-B port (YAAC) to invoke the .bat file and based on a quick look, it seems like the internal ports (30003, 30001, etc) might not be lining up, but that is just a guess. ModeSDeco2 is working quite well by itself, I just can't seem to get it to communicate with YAAC.
Last edit: John 2017-11-14
I'm not exactly sure how you would get UAT to work on Windows; I've found a set of directions that work on Linux (or other Unix-like derivatives) at this website:
https://gist.github.com/fasiha/c123a9c6b6c78df7597bb45e0fed808f
It works by piping the generic rtl_sdr program into the dump978 program and subsequently piping dump978's output into uat2esnt to convert the format into dump1090's format (which YAAC understands). To do this in YAAC on a Unix-like system, you would have to configure your ADS-B port in YAAC to launch the following command:
bash ( rtl_sdr -f 978000000 -s 2083334 - | dump978 | uat2esnt )
Assuming all three subprograms (rtl_sdr, dump978, and uat2esnt) are on the PATH, this would invoke a bash shell program, which would then handle launching all three subsidiary programs and piping them together in order. I don't know what the Microsoft Windows equivalent of this would be. I don't know if dump978 would even compile and run on Windows.
I need to make a few changes to the ADS-B plugin to support piped commands like the ones above. Look for the release of adssbplugin version 0.0alpha5 soon.
So which is the correct ADSB plugin version? I have downloaded version 1.0, but the YAAC updater seems to think version 0.0alpha4 is the most up to date version.
The version of YAAC is not the same as the version of any given plugin. The ADS-B plugin is currently at version 0.0alpha4, whereas core YAAC is verson 1.0beta115 (as of today).
Understood, but I am not talking about the version of YAAC. As you can see, YAAC says I have version 1.0 of the plugin.
Last edit: John 2017-11-23
Build V0.0alpha5 of the ADS-B plugin now supports piped commands, so that you can use the dump978 and uat2esnt commands in a pipe to receive UAT aircraft beacons. In theory, you should be able to create two ADS-B ports (one for real ADS-B and the other for UAT) and receive both simultaneously, but you would need two SDR receivers to handle the two bands simultaneously.
Last edit: Andrew Pavlin 2017-12-18