flight:adsb-server-writeup
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
flight:adsb-server-writeup [2023/04/27 19:48] – [MLAT Server] 2m0iig | flight:adsb-server-writeup [2023/05/08 16:19] – [MLAT Client] 2m0iig | ||
---|---|---|---|
Line 40: | Line 40: | ||
* [[https:// | * [[https:// | ||
* [[https:// | * [[https:// | ||
- | * Feeder setup scripts for easy installation by users (named however you want, well clone these from elsewhere and modify them and the other software along the way). This consists of [[https:// | + | * Feeder setup scripts for easy installation by users (named however you want, we' |
I found it easier to clone all of these repos and push my own changes so that we had a single source for everything that could be replicated if needed in the future with minimal effort. | I found it easier to clone all of these repos and push my own changes so that we had a single source for everything that could be replicated if needed in the future with minimal effort. | ||
Line 104: | Line 104: | ||
RECEIVER_OPTIONS="" | RECEIVER_OPTIONS="" | ||
DECODER_OPTIONS=" | DECODER_OPTIONS=" | ||
- | NET_OPTIONS=" | + | NET_OPTIONS=" |
JSON_OPTIONS=" | JSON_OPTIONS=" | ||
</ | </ | ||
- | You'll need to make some edits, remove some things and add some things. In reality any of the options can go into any of the four fields, but it helps to keep them somewhat organised. With this config we' | + | You'll need to make some edits, remove some things and add some things. In reality any of the options can go into any of the four fields, but it helps to keep them somewhat organised. With this config we're: |
- | * A network port for Beast data from feeders, 30004 | + | * Enabling a network port for Beast data from feeders, 30004 |
- | * Network | + | * Enabling network |
* Removing ALL RTL-SDR configuration options | * Removing ALL RTL-SDR configuration options | ||
* Passing receiver IDs to the map for tracking how many are receiving a particular plane | * Passing receiver IDs to the map for tracking how many are receiving a particular plane | ||
* Disabling the maximum range beyond which a signal will be discarded, which isn't needed for an aggregator if you think about it | * Disabling the maximum range beyond which a signal will be discarded, which isn't needed for an aggregator if you think about it | ||
- | * Specify | + | * Specifying |
You can find out everything does in the --help - there are many options. Then we can restart readsb: | You can find out everything does in the --help - there are many options. Then we can restart readsb: | ||
Line 238: | Line 238: | ||
The key thing here is to have the mlat-server running and listening for data on a specific port (which we'll configure feeders to send to later). 31090 is the default for this. The calculated positions and results need sending onto the aggregator readsb process so they show up on the aggregated map, and so the server readsb needs setting up to expect an input with this data on the right port, which can be any free port on your server. | The key thing here is to have the mlat-server running and listening for data on a specific port (which we'll configure feeders to send to later). 31090 is the default for this. The calculated positions and results need sending onto the aggregator readsb process so they show up on the aggregated map, and so the server readsb needs setting up to expect an input with this data on the right port, which can be any free port on your server. | ||
- | After this server side work you should also configure your feeder clients to send MLAT data to the server, and also have them forward any MLAT results sent back from your MLAT server to your website' | + | After this server side work you should also configure your feeder clients to send MLAT data to the server, and also have them forward any MLAT results sent back from your MLAT server to your website' |
==== MLAT Server ==== | ==== MLAT Server ==== | ||
Line 254: | Line 254: | ||
==== readsb configuration change ==== | ==== readsb configuration change ==== | ||
- | Now we need to let readsb know to open a port to receive these calculated positions. | + | Now we need to let readsb know to open a port to receive these calculated positions. |
Restart the readsb service. | Restart the readsb service. | ||
==== MLAT Client ==== | ==== MLAT Client ==== | ||
- | We're gonna fill in that MLATSERVER line now, along with a few other things. Inside MLATSERVER enter the " | + | We're gonna fill in that MLATSERVER line now, along with a few other things. Inside MLATSERVER enter the " |
< | < | ||
Line 270: | Line 270: | ||
Results 2 and 3 seem redundant (edit: 3 seems to be ADSB Exchange related...), | Results 2 and 3 seem redundant (edit: 3 seems to be ADSB Exchange related...), | ||
- | So, make changes | + | RESULTS4 therefore needs to be set to the port you picked earlier that doesn' |
- | Now restart all of the services or reboot, whatever, and make sure everything | + | One other thing we **have** to do is tell the mlat-client where to look for your site's UUID when it's being compiled by a user. This is best done by cloning the mlat-client repo and then changing the " |
+ | |||
+ | < | ||
+ | uuid_path = [ '/ | ||
+ | </ | ||
+ | |||
+ | Change the right bits to your client' | ||
+ | |||
+ | So, make changes to your client, push them to your repo, and then let your feeders loose on it to reinstall | ||
That's it! You're done! When you have enough positional data you'll get MLAT tracks on your aggregator website, plus that data will be sent back to your feeders. | That's it! You're done! When you have enough positional data you'll get MLAT tracks on your aggregator website, plus that data will be sent back to your feeders. |
flight/adsb-server-writeup.txt · Last modified: 2023/05/08 16:20 by 2m0iig