V2.2.3 iGate/Digi firmware doesn't like tactical callsign (among other changes)

[arizonajon1]

Hi Ricardo -

In this most recent rev a number of things have changed.

I prefer using tactical callsigns like ARSTRA (Arrastra mountain), PSTEWA (Piestewa peak), SMITH4 (Smith peak 433 MHz), SMITH9 (Smith peak 900 MHz), etc., that are descriptive of the location the digi is at. I always put my callsign in the beacon text. This is quite common in the US.

One of them is the configuration complaining about not having a valid callsign. It appears to have accepted it since when it reboots the callsign is as I programmed it. It does not seem to transmit on RF. (This unit will be a digi only and will have no internet access.) Is the firmware preventing transmit since it doesn't like my callsign?

As I need to ensure that my beacon is transmitted no less than once every 10 minutes (regulatory rule), there doesn't seem to be a way to transmit the beacon less than once per 15 minutes. This could be a problem with tactical callsigns.

Note: In any event, I have to use tactical callsigns since I have so many LoRa modules %^)

Salud y 73 - Jon N7UV

[richonguzman]

I'm gathering info from APRS-Olympus to know the correct way to address this issue. Be back soon ...

[arizonajon1]

Hola Ricardo -

Any forward progress on the tactical callsigns and the no less than once every 10-minute beacon? I now officially have more boards than SSIDs.%^)

Again, a tactical callsign can be any alphanumeric set of characters, i.e., ABC123, SANDIA, EAGLE1, etc.

aprs.fi supports this, and most other TNCs (Kantronics, argent data, digipi, direwolf, microsat, IW3FQG's UIdigi, etc.) The key is the ability to present a legal ID regularly to stay within the rules, thus the need for <= 10 minute beacon at least here in the US.

Ciao - Jon