SSID is not being sent
Issue #92
resolved
- Set an SSID in both the station preferences and in the advanced tab of an RF connection that can be heard by an I-gate. Use the same SSID in both places.
- Turn on the connection and make sure TX is enabled.
- Manually send a beacon.
- Check aprs.fi for both your callsign and your callsign-SSID. For example, see KI6HQT and KI6HQT-10 (https://aprs.fi/info/a/KI6HQT)..)
- Notice that the the SSID is missing on aprs.fi.
- Check the raw packet to confirm that the SSID wasn't sent.
- Now set the same SSID for an APRS-IS connection, and enable it with TX on.
- Send another beacon.
- Check aprs.fi, and you’ll find that the correct callsign-SSID is being sent over APRS-IS, but not RF. Here’s an example packet sent via APRS-IS:
2021-05-10 16:58:18 CDT: KI6HQT-10>APQTH1,TCPIP*,qAC,T2SWEDEN:=3015.37N/09744.60W#/A=000433QTH.app experimental digipeater
- Here’s the packet that was sent via RF:
2021-05-10 16:58:19 CDT: KI6HQT>APQTH1,WIDE2-1,qAO,KA5D-10:=3015.37N/09744.60W#/A=000433QTH.app experimental digipeater
- These two packets were sent by the exact same action of manually clicking the beacon button.
Comments (4)
-
reporter -
reporter - edited description
-
reporter Okay, I was wrong about what I fiddled with that caused the correct callsign to be sent. Updated the bug.
-
repo owner - changed status to resolved
Should be fixed in v0.4.3
- Log in to comment
Addendum: I seem to have inexplicably “fixed” this by fiddling with the beacon content--changing the source and position format. I trying to figure out exactly which control it was. However, since SSID isn’t set there, whatever happened really shouldn’t have.