Differences

This shows you the differences between two versions of the page.

--- flight:adsb-server-writeup [2023/05/01 15:31] – [MLAT] 2m0iig
+++ flight:adsb-server-writeup [2023/05/08 16:19] – [MLAT Client] 2m0iig
@@ Line 40: / Line 40: @@
   * [[https://github.com/wiedehopf/tar-1090|tar1090]] (web front-end)
   * [[https://github.com/wiedehopf/mlat-server-sync-map|mlat-server-sync-map]] (displays web-based MLAT sync information map/data tables)
-  * 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://github.com/wiedehopf/readsb|readsb]] and [[https://github.com/wiedehopf/mlat-client|mlat-client]]
+  * Feeder setup scripts for easy installation by users (named however you want, we'll clone these from elsewhere and modify them and the other software along the way). This consists of [[https://github.com/wiedehopf/readsb|readsb]] and [[https://github.com/wiedehopf/mlat-client|mlat-client]]
 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 259: / Line 259: @@
 ==== MLAT Client ====
-We're gonna fill in that MLATSERVER line now, along with a few other things. Inside MLATSERVER enter the "server_hostname:31090" that you set up your server on earlier. After the UAT_INPUT line add the following:
+We're gonna fill in that MLATSERVER line now, along with a few other things. Inside MLATSERVER enter the "server_hostname:31090" that you set up your mlat-server on earlier. After the UAT_INPUT line add the following:
 <code>
@@ Line 272: / Line 272: @@
 RESULTS4 therefore needs to be set to the port you picked earlier that doesn't conflict with any other aggregator website's MLAT results port.
-So, make changes to your client, push them to your repo, and then let your feeders loose on it to reinstall everything and set up MLAT.
+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 "mlat-client" file in the root of it. Here's the relevant line, 105:
+<code>
+uuid_path = [ '/usr/local/share/xxxx/xxxx-uuid', '/boot/xxxx-uuid' ]
+</code>
+Change the right bits to your client's install folder in /usr/local/share/
+So, make changes to your clients, push them to your repos, and then let your feeders loose on them to reinstall everything including MLAT.
 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.