You are sending the WRONG format of data. YOU ARE SENDING BASESTATION NOT BEAST. You need to figure out the correct port the radarcape that sends BEAST. DO NOT SEND BASESTATION. YOUR IP IS BANNED UNTIL YOU FIX THIS.
Thank you for pointing that out. I have now stopped adsbexchange-feed and adsbexchange-mlat. I'm sorry that I became a trouble. Since both the adsbexchange-mlat log entries and the /coverage and /sync/feeder page display seemed fine, I thought the data from the Radarcape was fine. Although MDA wrote above from port 10006 which I use also for other feeds. I will do my best to still be able to provide useful data for adsbexchange from Radarcape. Hints are welcome.
Ok I removed IP ban ... That is what you need to change. I believe beast output is port 10003 NOT 10006 .... according to docs ..
ADSBx feeder ... aka the socat one ... socat tcp:localhost:10003 tcp:feed.adsbexchange.com:30005 more or less .. without many ags ... only the important stuff here - I don't know what you've done , what your files look like or what is going on ... you need to use beast not basestation mlat .. should also probably be using 10003 The data coming form your IP was SBS basestation CSV spam ..
The Radarcape is stating Port 10006 Binary formatted raw data with all Mode-S data formats (CRC pre-checked, no Mode-A/C) see the link to the Radarcape he posted: http://t958ehxgihvoitij.myfritz.net:8082/dataportstatus.html Also the MLAT client worked off port 10006, and that only works with beast data? So i'm quite confused. According to that Radarcape status webpage, 10006 should be binary data and the correct port. You were addressing kabelwalter or someone else who posted in regards to Radarcape in this thread?
Well something isn't right ... data from his IP is SBS Basestation spam ... I'm just informing of what it is ... the rest I have no control over .. I was addressing @kabelwalter from 213.153.90.177
Yeah that's the same address as the myfritz URL. I'm aware you can't influence the Radarcape, just saying that it's really strange. Anyway 10003 will be lots of data because of Mode A/C So if anything 10004 sounds better because it's only the interesting messages i think. But i don't know what that Radarcape is doing. Maybe it's not the radarcape. Very confused as you checked his stream before and it was working. Maybe the Radarcape has an option to change the output from beast to SBS? Walter, can you show the config file once more: cat /etc/default/adsbexchange
I setup a listener to look at the incoming data ... we shall see if he turns things back on and tries again
cat /etc/default/adsbexchange RECEIVERPORT="30005" USER="Scharnhausen" RECEIVERLATITUDE="48.711" RECEIVERLONGITUDE="9.26532" RECEIVERALTITUDE="365" RESULTS="basestation,listen,31003" MLATSERVER="feed.adsbexchange.com:31090" INPUT="127.0.0.1:10006" INPUT_TYPE="radarcape_gps" I notice that the variable "RESULTS" contains "basestation"?! After installing from wiedehopfs source: git clone https://github.com/wiedehopf/adsb-exchange.git that line was RESULTS="beast,connect,localhost:30104 --results basestation,listen,31003" On wiedehopfs advice I removed the first parameters as I had Sep 18 09:26:16 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:26:16 2019 Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused Sep 18 09:26:47 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:26:47 2019 Beast-format results connection with ::1:30104: [Errno 111] Connection refused As long as I don't change anything in the config, it probably won't do any good if I restart the transfer?
With the test described above it doesn't hurt, so turn it back on. Did you change any other settings in the Radarcape since you configured ADSBX feeding?
Mhh .. I've nothing made. Only stoping and starting the service. Very strange Thank you for your patience.
It would need to be the Radarcape suddenly switching port 10006 from beast to basestation. Which i really can't imagine. Did you try feeding from another device? Pretty sure James only sees this by IP, so if you had one good feed and a bad feed, the who IP would light up red Do a reboot of the Radarcape now, maybe the problem occurs again. Could be that it's basestation on startup somehow and then gets configured by the radarcape to be beast? Grasping at straws here. Or what do you mean started/stopped the service?
As far as I remember, I restarted the service for the last time when I removed "beast,connect,localhost:30104 --results" from the RESULTS varriable. After that the error messages in the log were gone, which means it was restarted. It remains strange. Please write me again if data comes in the wrong format.
You are also making the assumption that it was working in the first place. The biggest problem with remote support.
Well, he was using the scripts which use the same input for MLAT and ADS-B. The MLAT was syncing and you showed a screenshot of the incoming data. So it was working fine at some point, no?
After updating my Radarcape receiver to the latest firmware I activated there the internal ADSB Exchange feed. As I see on the Status page it connects to feed.adsbexchange.com:30005. Although https://adsbexchange.com/myip/ shows: lines out output: 15 Data incoming from: 213.153.90.177 Route: beast_front Port: 30005 Backend: beast_back Connected: merge-1-0 Age: 9h19m Data incoming from: 213.153.90.177 Route: MLAT_front Port: 31090 Backend: MLAT_back_4B Connected: mlat-d Age: 7m22s I'm wondering if my data are accepted as http://www.adsbexchange.com/coverage-4B does still show since days my previous entry Scharnhausen-01, but without data? Thank you for your help. Walter
