aprsorg / aprs-deviceid

APRS device identification data: tocalls.txt + mic-e-types.txt current master allocations (YAML, JSON, XML)
60 stars 23 forks source link

New APRS Device ID for LY3PH APRS-ESP #66

Closed erstec closed 7 months ago

erstec commented 2 years ago

Please add new TOCALL for my new embedded APRS Tracker / IGate / Digi Open Source Project - APRS-ESP

It's in hw/fw testing / pre-release stage now. Last '??' digits will be used for versioning/hardware/features separation

73, LY3PH / Ernest

erstec commented 2 years ago

Project assembled, tested and released, still with experimental destination.

hessu commented 1 year ago

Hi,

Sorry for the very long delay. I have assigned you with APESP?, I hope that's alright. We only have 676 4-letter prefixes in the AP?? space available, with 5-letter prefixes there's more space to grow.

erstec commented 1 year ago

Hi,

Sorry for the very long delay. I have assigned you with APESP?, I hope that's alright. We only have 676 4-letter prefixes in the AP?? space available, with 5-letter prefixes there's more space to grow.

Thank you! Due to mentioned limitations APESP? is ok of course!

73!

oh2th commented 8 months ago

In May 2020 these two were allocated as: APESPG = ESP SmartBeacon APRS-IS Client APESPW = ESP Weather Station APRS-IS Client

Could these be restored as they were? Opened #144

hessu commented 8 months ago

Hi,

Unfortunately I have missed the APESPG and APESPW allocations to OH2TH by Bob in 2020, and then subsequently made an overlapping allocation. This needs to be resolved by reallocating.

Here's the number of stations seen in 2024 (according to my database on aprs.fi) using different APESP? tocalls:

APESPW   2
APESPG   45
APESP1   2

Do you have any visibility if these are running the software from @oh2th or from @erstec ? Have you released code using these tocalls?

erstec commented 8 months ago

@hessu APESP1 is what mine project using, FW is deployed and running on several (at least I know) nodes. We can split interval, like APESPx, where x is digit are more than enough for me.

hessu commented 8 months ago

If you're currently using APESP1 only, the simple approach would be to make an allocation of APESP1 to you to resolve the overlap. Would that be alright for you?

erstec commented 8 months ago

Yes, it's ok, Thank you

oh2th commented 7 months ago

Sounds like aplan

hessu commented 7 months ago

Hi,

I have fixed the allocations as agreed above.