search

cfr34k / t-echo-lora-aprs

LoRa-APRS firmware for the Lilygo T-Echo
Other
21 stars 4 forks source link

Adopt "APL" tocall standard for APRS - LoRa #12

Closed EA2CW closed 7 months ago

EA2CW commented 1 year ago

Now the tocall of the firmware is APZTK1, but almost all LoRa firmwares are adopting the "APL" prefix. Could be possible to change yours from APZTK1 to, f.i. APLZTK or something like that? We at EA2RCF have developed a new map interface of all the the APRS-LoRa resources at: http://lora.ham-radio-op.net/?center=42.5005,-2.6312&zoom=8 but only the items starting with "APL" will be shown What do you think? Thank you very much! Mikel EA2CW

cfr34k commented 1 year ago

Hi, yes, I'd love to do that. The APZxxx destinations are for experimental devices and I think my firmware is now major enough to change that. However I'm not sure how I can make sure that there are no conflicts with other firmwares/devices. Do you know if there is some organization that assigns destination calls? Then I could ask there. Thanks! Thomas DL5TKL

EA2CW commented 1 year ago

Hello Thomas, First of all thank you for your work, I love using the Lilygo T-Echo as most simple APRS-LoRa tracker.

Related to the device-id request, you have an aprs-device id database (and ask for & update protocol) just here in github at: https://github.com/aprsorg/aprs-deviceid/tree/main Which is managing this now. You can find more information about registering new ID's here: https://github.com/aprsorg/aprs-deviceid/blob/main/ALLOCATING.md Hope this is information enough to do it

73, Mikel EA2CW

cfr34k commented 1 year ago

Great, thanks for the links, that’s just the info I needed! :) I'll probably take a little time until I can take a look at the details as I am currently at the CCCamp.

73 de Thomas DL5TKL

cfr34k commented 12 months ago

Hi Mikel, just a short update: I have now requested a new allocation of the APLETK destination call.

EA2CW commented 12 months ago

Good news! Hope you have success with that!

EA2CW commented 11 months ago

Finally been asigned APLETK id, congrats!

cfr34k commented 11 months ago

Yes, very nice :) I have already changed it in the code, so all new builds will use the new tocall.

My plan is to officially release it with version 1.0, together with BLE KISS support (see #13). However, that is quite a big feature and will probably take some time to implement and test.

cfr34k commented 7 months ago

Ok, I found that the KISS support required too many changes to think about and there were already a lot of smaller changes and fixes queuing up, so I decided to release version 1.0 anyway. So now APLETK is the official destination call for this firmware!

Thanks again @EA2CW for your tips!