Finally! I've been able to get through all the custom feed requests. If you notice any errors or your feed was not included, please post here or send an email. I sent out about 20 emails asking if people still want to feed to a requested port or if they had errors and I needed to correct. Things I noticed: About 20-30% don't seem to understand the difference between sending to 53000 port and the 51000 port. 53000 numbered ports are for VRS ONLY, COMPRESSED VRS. 51000 numbered ports are for Pi ONLY, 30005, Beast Format. If you send BEAST to VRS or VRS to BEAST, your IP will be banned and nobody will get any use out of your data until you fix it. I did reconfigure the server to accept several VRS ports that were receiving BEAST - but only because I didn't have emails to contact them. 10% seem to send to ports that are already claimed. Please only request zCons-XXXXX named ports. If it has a name other than zCons-53xxx or zCons-51xxx, it's claimed. Please check here is no data on the port prior to sending to it. Go to it from the custom feeds link and select it, most of the time it will show a plane or two if there is data on it. Sometimes people are connected but not sending data. :/ Not much I can do about that, but you will get an email asking to swap ports. The best way to do it is find a port, check for aircraft, if no aircraft - start sending your data to it. Your traffic will appear at at most 20 seconds - if it works keep feeding - if not try another unclaimed port. Fill out the form to request a name, lat, long, etc ... #win I will go back and rotate through ports that people are no longer feeding and make them available. So what does it all do eventually!? Feeders on 51xxx ports are sending BEAST data; I have been able to tap into them, aggregate, and send data feeds to a bunch of researchers, students, and people looking for raw data! All thanks to you guys for feeding! Currently adding more and scaling it out, but so far processing 1M+ messages a minute from a fraction of the BEAST feeds and broadcasting over 40GB per day, per rebroadcast to each user who is using the data! I encourage everyone to feed using a Pi, if you already have one with a SDR and are feeding to VRS and rebroadcasting; I can help you setup how to feed ADSBx on the Pi and feed the unmolested BEAST data! Then you won't have to have VRS running all the time on your PC. VRS format isn't very useful for research and data analysis purposes, it is useful for tracking planes and it is aggregated into our feeds, but Pi with dump1090 BEAST is a much easier way to feed and uses less power than a PC VRS feeder. ADSBx is the only ADS-B site with global network proving data back to the community free of charge without strings attached, hidden fees, or 'optional donations'. Not saying we don't appreciate the donations that really help us keep the site up and running! Thanks to everyone!
Updated: 5/27/2018 Ports I have data on but no lat/long or request to claim. 51047 51084 51089 51141 51149 51152 51168 51214 51228 51289 53074
Hi Since few weeks I'm feeding data from my Pi to port 51267 Already claimed the feed, but got no response and the receiver name is still zCons-51267 Cheers Marek (Venray, The Netherlands)
It is a manual process. I only have so many hours to do things. Keep feeding. I'll get to it when I get to it. Thanks for feeding.
Ah, all clear now! I wasn't aware of that. Thanks! Yeah, I'm feeding 24/7 (since like 2 weeks to adsbexchange and ab. 2 years in total) Marek
Hi, I'm sending data (or at least I think I am) from my VRS to adsbexchange I've tried to add my custom feed a few times but is hasn't appeared on the map on both occassions should I re set it up via another zCons that is spare?
Yes it's full and people are stepping on each other. I need to find time to build out 1 or 2 more this week. Do you have a Pi you can feed from? Feeding from VRS has a lot of problems that feeding direct from dump1090 does not. One of them is people send our whole damn feed back to us because they can't read the instructions on not including the data they get from ADSBx. The other is they send Basestation and not CompressedVRS - which meant I had to create a server to catch the Basestation - this is a small amount of the total. And the biggest problem - timestamps are not correct because most of the time the windows clock is way off and not synced to NTP. Plus feeding from a PC is .. ugh .. that you have to have running all the time. If you are runnign VRS on a Pi and feeding ADSBx .. double ugh ... just feed from dump1090 on the Pi and use less bandwidth. "Hi, I'm sending data (or at least I think I am) from my VRS to adsbexchange I've tried to add my custom feed a few times but is hasn't appeared on the map on both occassions should I re set it up via another zCons that is spare?" And this is the problem - even tho it tells you to keep feeding. People don't see the name change in the next 5 minutes so they go to the next port. Pick a port - feed to it .. and keep feeding to it. Verify your data is what is appearing on that port. Keep feeding it. If the name doesn't change in a eek or in a month - don't panic .. just keep feeding .. if you see your data then we're getting it. I know hearing your own name is the sweetest sound - keep feeding even if name does change. I'll get to it. I promise. Sometimes I have to sleep and do other things. You're not adding your feed - you're filling out a form that is saved in a google spreadsheet - that someone (myself) then has to look at and make you actually filled out the correct info - which only about half of the people do. Then I have to go in a manually rename the VRS rename the VRS receiver to your requested named - and make sure the data that is coming in on it is actually sensible for he lat / lon you provided.
Hi, I only have VRS as it's all plugged into my PC I then send the data as shown on the How to Feed from VRS section of the site
For now just send to 41000 .. the compressedVRS port https://adsbexchange.com/how-to-feed-from-vrs/ thanks for feeding!
I feel dumb, and I searched everywhere on here. How do I setup a custom feed so it points to a port.... How do I even find what port it is sending on now, outside of Sniffing the traffic, which I don't want to do (don't have that easily setup)
/boot/piaware-config.txt /boot/adsb-config.txt depending on the image you are using ... has all the information custom feed server is full ... I have to set more up.
1st of all - thanks for the great job done, I'd like to support the community and I'm keep feeding 24/7 pc [vrs] on 41000 since register (better later than never but I'd like to feed to the custom one. I'm observing the 53041 which seems to be not in usage but I'm not able to feed into this port anyway. Any updates regarding free ports or should I constantly checking the availability ? btw - are we able to check my connection somehow ? Thanks!
I've been busy with other ADSBx things. I think the ports are mostly full, I looked briefly at the request sheet. I'll try to get 2 more custom feed servers added this weekend for beast feeds, and I'll add 50 more VRS ports.
Oh man, I couldn't even imagine such positive answer. Sounds like a great weekend plan - fingers crossed Thanks!
Is there any advantage to ADSBx for users to have a custom feed, I don't particularly want one but if it is useful to someone else then I could set one up. Running a beast/Pi setup in Southern UK
There is a nice advantage to ADSBx that we can segregate out a custom feed and route it or check on it. Theoretically I can pull stats from it, etc ,etc. Initally custom feeds were created because some people were non-stop complaining that ADSBx doesn't have a dashboard like FlightAware. Something I've been meaning to build is a per custom feed stat system. People like to see "their data" on "ADSBx" - even though I tell them they can go to global and see everything aggregated. But they say: "No I want to see only my data on ADSBX, If I can't see my data then I'll just feed FlightAware because they have a dashboard and I can see my data there and a green light that says I'm feeding. On FlightAware I can compete on leader boards and brag about how good my feed is. I want a premium account being a feeder! If I don't get things, I won't feed you." So I say - "Do whatever you want, but ADSBx is not FlightAware." You might think I'm joking but this is a real conversation I've had multiple times. There are some interesting people out there. The main reason people want a custom feed is they want to watch their feed. It's odd, because they won't see any MLAT on custom feeds because FlightAware threatened to sue if ADSBx (and everyone else) displayed their MLAT data. So ADSBx can't set dump1090 to forward-mlat because that would forward FA MLAT .. so all custom feeds can see is ADS-B traffic. Having a publicly availble custom feeds map is also is a massive waste of bandwidth, since a custom feeder sends data to ADSBx, usually from their local network, then they visit custom feeds which sends data back to them. That 1 data packet is sent several times when someone could just look at their feed on their local network or install VRS locally and use no external bandwidth ... etc etc .. If you have a remote Pi, then a custom feed can be useful. But there are better ways to view it like putting it on a zerotier network, etc, etc. Either way custom ports have turned out to be useful, so we'll keep them around. I got this email a week or so ago: "Subject: PROBLEM WITH LIVE TRACKING RADAR Message Body: SOME AIRPLANES AFTER HAVE LOST ITS TRACK, STAY FOR ABOUT THREE HOURS IN THE MAP. I CAN'T WORKING IN THESE CONDITIONS!!" My reply was: "It must be very hard to do any work with your caps lock stuck. James"
