Glad you sorted it all out. The observations I was going to make were:
- There is no problem feeding from VRS, if the right format is used. Unfortunately that is not the case with all feeders. Using the image avoids that problem, since there is no format setting that needs to be selected by the feeder.
As for timing, ensure the PC clock is accurate. If you want to be absolutely sure, and never worry about it, install PC clock sync software. Dimension4, aka D4, is great and free.
- ADS-B Exchange has 2 live maps. One accessible by clicking on Global Radar View, and the other by clicking on Custom Feeds.
The Global Radar View, as the name implies, is global. All the data from all the feeders are displayed there. There is no way to differentiate who fed what.
The Custom Feeds map allows anybody to see what each feeder, with a ‘dedicated’ port, is feeding.
-
By default, as per general instructions, feeding from VRS will use port 41000. In this case, there is no way to see just your traffic. For that, you need to setup a custom port in the 53XXX range.
-
If you use the ADSBX image, or the adapted ADSBX Piaware image, a custom port is in the 51XXX range.
-
To select a custom port, one must use the Custom Feeds map, not the Global Radar View. The latter does not have a receiver option on the Map menu.
Open the Map menu, select receiver. Scroll down the list, and look for a zCons-51XXX if using the image, or a zCons-53XXX if feeding from VRS.
Wait a couple of minutes, if no planes are displayed, chances are the port is available. Use that port number when configuring the image or VRS. Wait a few minutes and your traffic should show up on the map.
- After this is done and working, and if you want to keep the port for your ‘exclusive’ use, send the email, as described in the custom feeds instructions, asking for the port to be customized for you. It may take up to 2 weeks, after the request is received, for the customization to be done. It’s done by a volunteer. He said it takes 4+ hours to set them up. He works on the custom feed requests every couple of weeks.
Give it another name, the user name as you asked before, can be the same. Suggest you use just a name, not the port number as part of the name. The port could still be ‘hijacked’ by another feeder, so masking the port number will help keep it free for your ‘exclusive’ use.
Write the port number down for future reference, if you need to re-image the SD card, or re-install VRS.
Regarding MLAT, as mentioned many times before, the MLAT data provided by FA cannot be re-distributed.
There is no major benefit or advantage about MLAT, as it’s used for positioning the plane on the map. Ok, there is, but it’s not a biggie for me. The plane is still ‘detected’ using Mode S. The map is nice, but it’s just a visual thing, great to show other people. I have now switched the map off, and keep just the list.
ADS-B Exchange MLAT is not widely available. It may not be the case in your area, but it’s in mine. Very few ADS-B Exchange feeders here, not enough data for MLAT.
As mentioned before, MLAT is not as relevant in Europe as it is in North America. That will hopefully change in approximately 2 years time.
Enough, I guess. Hopefully the above will help others.