Hi all, i set up my reciever near Kassel, Germany. On the coverage maps i see, it´s in Area 4A. Due to my coverage range and location i think, it would be better sorted in Area 5 oder 4B. In Main Direction for 4A is a gap due a mountain in sightline... Can anybody tell me at which criterias the Areas are coordinated?
Looking at 4B MLAT there are line of sight issues. Areas are mnaually broken up based on load and geography.
yeah, but i think, my location should be Area 5... in 4A it will be the most easterly station, in 4B the most northly. In 5 its the most westly, but in this direction the range is the biggest... Even its on the border maybe you will use the data in more than one location? If you want then do so.
Can I get SSH access to your Pi? I think I can figure out how to get you in both using 2 MLAT clients
I'm on the edge of 2 zones as well. (currently zone 5, forum name = mlat name) I'm very handy and have no problem running a 2nd client if you would provide the command line options required. (on a different note: are stations with red sync excluded from calculations or how does that work?)
I'm not totally sure how it's going to work. SSH would make it easy since I can monitor with our MLAT and proxy server. We can do it over ZeroTier, that's secure and requires no open firewall ports.
Red dots could be your feeder or them. If there are a lot of red on your feeder, then it's likely your feeder. If very few red then it's the other feeder, mouse over the see the feeder name. Yes it drops way out of spec data.
We can do... first tell me how the zoning works... if its depending on the coordinates, wrong coordinates should give other zone but then mlat is wrong... whats your idea?
Or you only want to connect fixed server ? For this i think the command line would work as wiedehopf says, too...
Are you competent enough to create a bash script and have it execute on boot? Copy adsbexchange-mlat_maint.sh Edit it Set up to start on reboot I don't have the desire or time to play basic linux teacher.
/usr/bin/mlat-client --input-type dump1090 --input-connect localhost:30005 --lat 51.365208 --lon 9.430923 --alt 215m --user 34292$ I think, im firm enougt for doing the changes... nobody offered a 8x multifeeder so i had to do it byself... i also have a server running under linux...
8x multifeeder? Are you running that one rodney stitched together. That's also not the full connect string ... nano doesn't word wrap ...
sry ;-) /usr/bin/mlat-client --input-type dump1090 --input-connect localhost:30005 --lat 51.365208 --lon 9.430923 --alt 215m --user 34292 --server feed.adsbexchange.com:31090 --no-udp --results beast,connect,localhost:30104
Feeding FR24, FA, OSN, PF, RB, ADSBx, ADSBHub, EA-Radar. Data from original Flightfeeder (remote using combine1090, with its original antenna) and 820T2 at the Raspi (with filter, preamp and DIY 8x CoCo antenna) both on same roof. CPU Load about 35% on 3B+. Up to 230 kBit/s at daytime ;-) The Raspi with preamp is better at high distance while the Flightfeeder greps very strong signals better.
