CHIRP

Okay, so this is what you need to do:

1. Get the radio set on a memory channel that you're going to tweak.
2. Power down the radio, power it up in clone mode
3. Download the radio, save that as imageA
4. Reboot the radio, and change the flag per the instructions in the manual to make it display the name instead of the frequency. Try not to do anything other than just this operation. Don't even dial to a different memory and come back.
5. Once the radio is showing the name, power it off and back into clone mode
6. Download the radio save that as imageB
7. Attach both here, and tell me which memory you used.

Dan Smith wrote in #note-1:

Okay, so this is what you need to do:

I think it is easier than all this. I found the "LOW" button has some text above it "A/N", which I guessed means Alpha/Numeric, which does the toggle right there. Sure enough, I rebooted the radio, and it seems to have stuck. This was more of a user/newbie error on radio operation, than a Chirp issue, I think.

If you could keep this ticket open a couple days, I will fully test it out and just close this myself if all set.

Thank you so much.
D.

...That's how you toggle it on the radio. If you want chirp to be able to set that flag then you need to do the above procedure for me to be able to suss out the actual bit in memory that is being toggled when you toggle it on the radio. In step 4, you would push the Low(A/N) button.

I was right there, and then thought I had it. I'm done for today, but can look at this again this week. Please tell me that an upcoming version will not require the "load module from issue" to test out, or at least in the beginning.

Thanks.

Did you ever get to look at these 2 groups of image files?

I did. The first two are exactly identical, so you didn't capture toggling the flag between imageA and imageB. The second group has more that one change in it, which means it's really not possible to suss out the thing we need. I did spend some time trying to guess at some things, but nothing came of it - apologies for not following up.

Yes, that is much better. Can you now do memory zero so I can get my bearings on where the start of the array is? Sometimes it's easy to spot but I think this is using multiple bits per channel so I just want to be sure.

Also, is imageA showing frequency and imageB showing name or the opposite?

At first I thought I was in the wrong. Then I realized what I did. Memory 00 had no name, so I gave it one (DAN).

I suppose I can go back and name it in Chirp, then bring it over again, and toggle it on. Is that what you'd like me to do?

Yeah, you need to give it a name so you can toggle it, but I need a before and after just the toggle operation on memory zero. It doesn't matter what you name it, I just need the before/after toggle.

Lots of changes between those two images and not in the place that I expect based on my previous guess.

Sorry, but I'm going to have to put this aside. It's just too laborious and I've gotta get on to other things. If I get access to an FT-2800 at some point I'll circle back to this and tease out the flags.

No problem.

I'll give this a whirl again also. It's weird, because it doesn't seem to always take the same steps. If nothing else, I was able to back up the original radio programming, and load in a new file.

In the meantime, might as well clean up the dialogs language, to make using it as easy and straightforward as otherwise possible. We'll get this, don't worry. Will let you get on to other things.

Maybe you can get some other 2800 owners to hop in as well.

Good night.

Doug Nelson wrote in #note-19:

OK, I am going to try to do this change one more time.

Did you get a chance to check the latest pair of files?

?

Any luck with this pair of files? I can do again if necessary.

Looks like this bug is still open. Let me know if I can help any further on this.

Please let me know if we can visit this issue again.
Thank you.

Dan Smith wrote in #note-26:

Thanks for confirming Andy. I think we might as well close this as I was assuming the radio had a per-memory flag like most. Since it's a little more state than setting, it's probably not very important to implement. If someone comes along and adds some radio-wide settings for this radio, then they might want to expose that knob, but I'll go ahead and close this per-memory one in favor of that, if it ever happens.

Just for continuity, and for going forward, I created this bug you described.

https://chirp.danplanet.com/issues/10780