APRS-IS Login Required to be Unique

[kb1lqc]

Summary

Logging into APRS-IS appears to require unique callsigns. This is problematic because I only have one! I want to connect faraday-aprs client to APRS-IS and also aprs2influxdb. What ends up happening is that APRS-IS just ignores the second connection. This means if aprs2influxdb is connected then Faraday data never gets to APRS-IS. Need a path around this.

Problem Explanation

ping @PhirePhly would you know any fix for this? Seems pretty restrictive.

Supporting Information

This is a handy spot to post any screenshots or file outputs in order to better support this issue. We want to keep the top of the ticket clutter-free as possible.

[PhirePhly]

You can append a one/two character alphanumeric SSID to your callsign to support multiple APRS stations under one callsign. I.e. my truck is W6KWF-1, my phone is W6KWF-5, and my logging client is W6KWF-DB.

https://github.com/PhirePhly/aprs_notes/blob/master/callsigns.txt

[kb1lqc]

Hmm @PhirePhly I'm trying/tried that and aprs.fi raw output is not showing me as getting in...

[kb1lqc]

To be clear this is the APRS-IS login that also requires a passcode @PhirePhly

[PhirePhly]

Are you using the SSID for generating the packet, logging into the APRS-IS server, and looking up the raw packets on APRS.fi?

[kb1lqc]

@PhirePhly I think so? I usually login to APRS-IS with KB1LQC and then the station I track is KB1LQC-1 and any other station I hear on RF.

Checking here: https://aprs.fi/?c=raw&call=KB1LQC-1&limit=50&view=normal
Note that I am currently using a different letter combination APRS-IS login to get this to work.. figured it doesn't actually go out over RF, especially as I believe my packets should be requesting not to (best I can do!)

[PhirePhly]

So what's the problem? I'm seeing your -0 station I-gating your -1 station.

You have no control over if someone else gates your packets back to RF, so it's customary to assume someone will and set your beacon interval accordingly.

[kb1lqc]

@PhirePhly my software that actually performs a socket connection to aprs-is is not KB1LQC, I'm using @kb1lqd call to do it (assuming twin powers is OK with this :P ) If I try to login with "KB1LQC-2" for instance... I literally see no packets getting into APRS-IS.

As for packet rate. No one has said anything in the months I've been doing this and also... sometime amateur radio needs a little kick in the but to get with the times.

[PhirePhly]

I can't really offer much help without knowing what you're sending to the APRS-IS server, what you're expecting to get back, and what the APRS-IS server is actually responding with.

I kind of think that was me saying something about your beacon rate right there, but I guess you can go stir the pot.