mudhorn/iR-APRSISD
1
0
Fork 0
mirror of https://github.com/kemenril/iR-APRSISD.git synced 2024-11-09 23:24:07 -08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update README.md

Browse source
This commit is contained in:
Chris Smith 2021-04-05 03:34:28 -05:00 committed by GitHub
parent 8a3fb1c768
commit 3be5383d22
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -42,7 +42,7 @@ This makes it possible to track an Iridium-based satellite device, say, on aprs.
### Multiple inReach devices ### Multiple inReach devices
Some preliminary but untested support is now included for multiple inReach devices on the same feed. There are a few strategies for dealing with multiple devices: Support is now included for multiple inReach devices on the same feed. There are a few strategies for dealing with multiple devices. I do not have a way to test it on my own, but it has been tested and I'm told it works. I will do my best not to break it in an update. Here's how you use it:
* Just define a single SSID in the configuration file, leave the Devices section undefined, and the software will increment the number on your SSID for each new IMEI it finds in the feed. Mappings generated this way will be consistent within a single run, but may -- or may not -- change if you run the service again. * Just define a single SSID in the configuration file, leave the Devices section undefined, and the software will increment the number on your SSID for each new IMEI it finds in the feed. Mappings generated this way will be consistent within a single run, but may -- or may not -- change if you run the service again.
@ -50,7 +50,7 @@ Some preliminary but untested support is now included for multiple inReach devic
* Run multiple instances of the daemon, each with an IMEI specified on the command-line, or each with a new configuration file and a Devices section that includes some but not all of the devices you want to watch. * Run multiple instances of the daemon, each with an IMEI specified on the command-line, or each with a new configuration file and a Devices section that includes some but not all of the devices you want to watch.
If you have multiple inReach devices, try doing any one of the above, and if my guesses about the KML feed behavior are correct, they should all be accessible. If you have multiple inReach devices, that should get them all tracking.