CHIRP

I see at least one problem I can fix, related to your DV channels. That's not the problem with the first few errors, but starting with memory 4.

Dan Smith wrote in #note-1:

Can you look at the first memory in the radio (or RS92) and describe it for me? Any weird characters in the name? Set for some special mode or something out of the ordinary?

Bank A memory 000 is just 146.52 FM simplex, named '2M Call'. Bank B doesn't have 000. Both banks memory 001 is also 146.52, no name.

I see at least one problem I can fix, related to your DV channels. That's not the problem with the first few errors, but starting with memory 4.

Far as I can tell, scrolling through the radio, I don't even have any DV channels set up. Memory 4 on both banks is a regular FM repeater.

I have no problem wiping the radio and starting over, if you think that might help. It's been a LONG time since I was last using this radio, so I'm not sure if it even has a "reset" option...

Actually, scratch the question about memory 1 and the statement about DV. I think maybe this is related to it trying to pull both A and B band memories at the same time. It should be only doing one at a time, but it looks like maybe something about that locking isn't working. The 92 is a strange duck - no other icom (or anything else) radio behaves quite like it.

I'll dig out my 92 tomorrow and see if something has regressed.

(just saw your reply)

Nope, don't reset it (yet). I'll circle back tomorrow.

Okay, I've been able to reproduce the problem. Something is very wrong for sure, I'll have to spend some time digging into why because it's not immediately obvious.

Since you're on linux, I assume you could do some testing from a git repo easily right? The ic9x driver is split between two files which makes LoadingTestModules not work as expected. But if you can, I can push something up to a branch for you to try.

This driver is a real mess, one of the oldest in the chirp tree, rarely ever used or maintained, an from a time period before a lot of conventions in chirp drivers were established. Basically, it's a big mess. I've got some hacks made to the driver that makes it load all the memories consistently for me, but it would be good to get confirmation from you that it does for you as well before I keep charging down this road.

Dan Smith wrote in #note-6:

Since you're on linux, I assume you could do some testing from a git repo easily right? The ic9x driver is split between two files which makes LoadingTestModules not work as expected. But if you can, I can push something up to a branch for you to try.

Yes, with a bit of instruction. I'm not a full-time dev but have used git on occasion. I know enough to be dangerous, anyway... :)

Okay, looks like you're using pipx, which may be a problem, but try this:

pipx install git+https://github.com/kk7ds/chirp@fix-ic9x

You probably have to uninstall the version of chirp you have installed with pipx first.

It's not perfect and still occasionally fails to talk to the radio, but it is substantially better-behaved in my experience.

The missing text thing is something specific to the GTK widgets on Linux and isn't related to any of this. I don't know why it happens, it almost never does for me but does more for some others. Try resizing the cells to see if that helps.

I don't see any obvious failures in your log, although it's super big. What memory were you editing when it failed?

Okay, cool, well, I'm thinking this is a substantial improvement from what is in the tree at the moment, so I'm inclined to push this through and then we can iterate on the details. I see the failures in the log - I'm guessing we're not waiting long enough for the set_memory response sometimes (or something like that).