From 8320a2c01fb0d89357a7681e9a4f43cf1a1c826c Mon Sep 17 00:00:00 2001 From: Chris Smith Date: Fri, 2 Apr 2021 01:06:49 -0500 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 71f66d8..aa7db38 100644 --- a/README.md +++ b/README.md @@ -32,7 +32,7 @@ This makes it possible to track an Iridium-based satellite device, say, on aprs. * Run the daemon. It should begin to scan your KML feed. - *Note:* I thought about just automatically calculating an APRS passcode rather than requiring it in the configuration, but this would be pretty catastrophic in case of typographical errors. If you don't already have the correct passcode, there -s a command-line option, *--genpass*, that will calculate it for you. At least this way, the software will print the SSID for which you've asked it to generate a code back to you, and you're likely to notice if it's not actually yours. If it is yours, you can just cut and paste the code into the configuration. Hopefully this prevents me from encouraging people to use SSIDs which should be assigned to other stations. You can generate a passcode like this: + *Note:* I thought about just automatically calculating an APRS passcode rather than requiring it in the configuration, but this would be pretty catastrophic in case of typographical errors. If you don't already have the correct passcode, there is a command-line option, *--genpass*, that will calculate it for you. At least this way, the software will print the SSID for which you've asked it to generate a code back to you, and you're likely to notice if it's not actually yours. If it is yours, you can just cut and paste the code into the configuration. Hopefully this prevents me from encouraging people to use SSIDs which should be assigned to other stations. You can generate a passcode like this: ``` ir-aprsisd --genpass --ssid N0CALL-66