b3nn0 / ogn2dump1090 Goto Github PK

Is this an issue due to the injection of the data via MLAT?
The protocol seems to support both callsign and squawk, however it is not being pushed at all. Also it seems that the callsign/registration is not always pulled from the ddb.

OGN_setup.conf says:
CenterFreq = 868.8; # [MHz] with 868.8MHz and 2MHz bandwidth you can capture all systems: FLARM/OGN/FANET/PilotAware

PilotAware aircraft are not being picked up, or if they are they are not being forwarded to dump1090. I have confirmed this by using a PilotAware device at the same time as using OGN2DUMP1090, and aircraft shown on PAW are not showing on TAR1090 or in the Dump1090 output. FLARM is fine.

Hi,

is my assumption correct: ogn2dump1090 will inject (OGN) data into dump1090 and this will ouput the OGN-data to VRS (Virtual Rsadar Server) and tar1090 in the same stream as the regular decoded ADS-B-data goes out?

Will this OGN-traffic in tar1090 then marked as ADS-B or UAT...??

Hi,

is it possible to remove the ~ from the ID to mimic a valid ICAO-ID which is shown on VRS?
In tar1090 is shown as "Non-ICAO hex". It seems a FLARM-ID like FLR114102 gets ~114102

vradarserver/vrs#88 (comment)

Hi, in the documentation is stated:

This requires an already running dump1090-mutability or dump1090-fa instance with the --net argument.

I have this default stuff in there:
/usr/bin/dump1090-fa --quiet --device-type rtlsdr --device-index 10900001 --gain 60 --adaptive-range --fix --lat 47.xxxxx --lon 11.xxxxx --max-range 360 --net-ro-port 30002 --net-sbs-port 30003 --net-bi-port 30004,30104 --net-bo-port 30005 --json-location-accuracy 1 --write-json /run/dump1090-fa

Is this correct? If not, where (and what) do I have change?
And is there a way to test the injection of OGN-data into dump1090 in some way?

Thanks

I have got OGN2DUMP1090 running, but is there a way to send data not just to 127.0.0.1 (localhost), but also to a remote server or other feeder site such as adsb.fi or adsbexchange?