Contact info not being applied in Channels (part4)

Report any bugs or errors you find here.
Post Reply
VA2PPZ
Posts: 6
Joined: Mon Mar 10, 2025 4:43 pm
Callsign: VA2PPZ

Contact info not being applied in Channels (part4)

Post by VA2PPZ »

Now, when changing a contact in channel.
The following error code appears.
You do not have the required permissions to view the files attached to this post.
User avatar
MM7DBT
Site Admin
200posts
Posts: 219
Joined: Wed Jun 02, 2021 6:59 pm
Location: Scotland
Callsign: MM7DBT

Re: Contact info not being applied in Channels (part4)

Post by MM7DBT »

While looking at this, I noticed that too.. I'll look into it and see why.

As for the main issue, see this;
Screenshot 2025-03-10 195619.png
Unfortunately the AnyTone Import was written before this issue was introduced. Hence why it allows importing more than 255 contacts.

You can test this yourself, simply delete contacts until you have 255 or less. Then write the codeplug to the radio and the channel contacts should work fine.

As to why this happens, see a previous post of mine below..

This has been an issue since 2022 or earlier.. whenever the added APRS to the firmware.
You do not have the required permissions to view the files attached to this post.
-73 de MM7DBT
User avatar
MM7DBT
Site Admin
200posts
Posts: 219
Joined: Wed Jun 02, 2021 6:59 pm
Location: Scotland
Callsign: MM7DBT

Re: Contact info not being applied in Channels (part4)

Post by MM7DBT »

MM7DBT wrote: "Default Contact ID" cannot be higher than 255 due to a limitation on how the ID is stored in the radio. (stored as 1 byte, so only 0-255 is allowed)

Originally it was stored as 2 bytes but when APRS was added, they are using 1 bit of the second byte to store the selected APRS channel.
This broke the selected contact for each channel so now you can only select the first 255 contacts.

I've done some testing with it and even the original CPS has trouble dealing with it, often setting incorrect contacts when it is over the limit.
Below is from a Facebook comment I made when someone reported the same problem.
So... with some playing around with the radio, it seems the firmware only supports the first 255 contacts as a 'Default Contact'

I've written 1000 contacts to the radio with 10 channels, each has the +100th contact selected. i.e Ch1 is Contact 100, Ch2 is Contact 200, Ch3 is Contact 300 etc etc

No issues writing to the radio, but then looking at the channels on the radio.. only Ch1 and Ch2 are correct.. after that they are all wrong.

Editing the channel on the radio to select the contact and save the channel results in it being set to 'Contact: OFF'
Set it to Contact 255.. works fine
Set it to Contact 256.. it breaks!

This was not an issue before APRS was added to the original Kydera firmware since the 'Default Contact ID' could use the full 2 bytes.. now it's limited to 1 byte 🤔
-73 de MM7DBT
User avatar
MM7DBT
Site Admin
200posts
Posts: 219
Joined: Wed Jun 02, 2021 6:59 pm
Location: Scotland
Callsign: MM7DBT

Re: Contact info not being applied in Channels (part4)

Post by MM7DBT »

Version 0.5.0310.1 should fix that error when changing contact :smile:
-73 de MM7DBT
VA2PPZ
Posts: 6
Joined: Mon Mar 10, 2025 4:43 pm
Callsign: VA2PPZ

Re: Contact info not being applied in Channels (part4)

Post by VA2PPZ »

Good afternoon David,
Thank you very much for the quick response concerning my observations yesterday.

I did as you recommended, that is to say.
Reduce the quantity of contacts to under 255.
I would have to say, it eliminated 99% of my problems.

I have since learnt a few things which I want to share with others who may eventually read this post.
If working with either versions of the OE CPS (9.1.1.95 or v9.2).
It is best to first read the code plug "presently" in the radio, then save (THE CONTACT LIST & CHANNELS) as an excel file on the desktop,....then rework that file with additions/modification.
Save the file named for easy reference to import back into the radio (ie:CONTACT)

(NOTE): I have also found that the cell values in excel must not exceed 10 characters, or else odd behaviour will happen once imported back to the radio.
The characters in the cell should also be LEFT justified........like this > [xxxxxx ]


The radio code plug has been reworked with the OE CPS, and it works as expected. (and backed up for safety).
I have also read and made a backup using your CPS.
The code plug was saved, and then imported back to the radio successfuly.
The channel function relies on the "contacts" in order to get the RADIOID reference.
It's a shame we're limited to the 255 entries, but we can live with that.
It is an inexpensive radio with surprising capabilities after all.

Thanks again for the help.

Salutations &73

Perry
Post Reply