Bug #11232
closedTidradio H3 deleted memories still showing in radio
100%
Description
please find attached debug log and image file for this bug as suggested by Dan White (thanks)
a few days ago I entered a block of memories about 35 in all.. I then deleted the ones i did not want (DMR repeaters) just leaving me with the FM repeaters..
Yesterday I noticed that a few of the memories still exist in the radio but not in the Tidradio or chirp software (not all were erased) memory #49, 43, 42, 41, 155, 154 and a few more are still in the radio some with names and some without....
I suppose I could overwrite them one by one... tedious.. not really a problem until you want to scan then its all over the place........ thanks in advance
Files
| TD-H3_20240310.img (8.18 KB) TD-H3_20240310.img | Image file | ||
| Screenshot1.jpg (162 KB) Screenshot1.jpg | Screen shot of blank memories | ||
| tdh8.py (73.2 KB) tdh8.py | 5a628240 |
Updated by Dan Smith 8 months ago
Thanks Steve. Per our discussion I've pinged some of the people involved with this driver and will direct them here.
I know @Henry Grasman tried to fix this recently, so perhaps he has some ideas?
Updated by Steve Hopkins 8 months ago
thanks dan. much appreciated. I have also just fired in the "out of band memories" as a bug as well....
I like the radio... it feels good works well.. and is more sensitive than my yaesu ft60 the only fault
with the radio I can find is speaker is to small for good audio, but I will look into replacing this next.....
Updated by Steve Hopkins 8 months ago
I will wait with anticipation and baited breathe... thanks Dan
Updated by Dan Smith 8 months ago
Okay Steve, if you want to give something another try, please try the new attached module. Note that it requires today's build in order to work. I'm hoping that this resolves the problem where chirp thinks memories are set (or deleted) and the radio disagrees. Note that it can only "fix" a memory if you touch it in some way. Just loading an image or downloading from the radio won't change anything. You need to make some change to each memory in order to affect it. So one way to "fix" a specific memory is just just cut it (which should clear it) and then paste it right back where it goes.
I'm trying to get my hands on an H3 so I can do some of my own testing here, but until then, I'm hoping you can give this a shot. It has some fixes that comes from information TID provided to help.
Let me know how it goes!
Updated by Dan Smith 8 months ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Applied in changeset github|38ca750c7e05d5dd1c8f645928c1432d39973300.
Updated by Steve Hopkins 8 months ago
High Dan... Sorry for delay (been away)
Yes it seems to work... copy and paste all ok... as a matter of interest
copy and paste whole blocks seems to work also..... maybe that method
would work for all 200 memories (did not try that) all in one go..
thanks for your time and effort... steve
Updated by Dan Smith 8 months ago
- Has duplicate Bug #11241: Tidradio H8 Unlocked -- Issue with Memories 177-180 added
Updated by Dan Smith 8 months ago
- Related to Bug #11244: copy and paste memories.... missing added
Updated by Steve Hopkins 8 months ago
lost and found... sorry couldn't resist bad humour..
all memory power setting set to low in chirp since update..... radio fine
chirp wont allow high power...
Updated by Dan Smith 8 months ago
We did make a change to the power leveling because the H3 doesn't support "mid" apparently but perhaps that wasn't quite right. I still don't have a radio to test with, so I wasn't able to confirm.
I'm sorry to keep making you open new bugs, but if you could for the power issue I'll surely have a look. Thanks a lot for your help and patience, I know the other H3 owners appreciate the improvements you're helping get in :)
Updated by Steve Hopkins 8 months ago
ok...
you don't need radio connected.. chirp does not allow to change power level
option shows low/high (as it should).. click high nothing happens....... stays low
Updated by Dan Smith 8 months ago
Yeah I understand and I'll work on that tonight after work. I just want another bug to "charge" the fix against for documentation. I can certainly open it myself if you're exhausted (understandably), no problem. What I meant was I don't have a radio yet to test with to make sure the power change that was involved in the previous set of fixes was actually honored by the radio, so I didn't actively try yet.