Bug #11226
closedTidradio H3 Settings menu
100%
Description
Chirp loads and finds Tidradio H3 no problem reads and writes as it should (I think)
Displays channel info But settings Menu does not display or maybe it does not download
"An error has occurred.. Setting Failed.."
program occasionally loses a channel memory but that could be me being stupid...
radio is also able to input Airband/6mtrs/4mtrs but not with chirp wont allow out of band
these 2 bugs not important
Thank you for your time!!
Files
Updated by Dan Smith about 2 months ago
Hi, can you try the attached module? Instructions are here: LoadingTestModules.
After this, the FM VFO value should be yellow, indicating that it's invalid and let you set something sane in there (like 89.0) to correct the problem. Let me know if that works for you and I'll get this fix into the next build.
Thanks!
Updated by Steve Hopkins about 2 months ago
- File chirp_debug-9svqrlsp.txt chirp_debug-9svqrlsp.txt added
Yes that cured it... menu showing lovely.. your a genius lol..
attached is debug log.. now all I got to do is try and put
into memory rx only frequencies.... ie: 6 mtrs and 4 mtrs must
be something I'm doing (I hope)
Updated by Dan Smith about 2 months ago
- Status changed from New to In Progress
- Assignee set to Dan Smith
- Target version set to chirp-py3
Great, thanks for the confirmation, I'll get the fix integrated into the next build.
For RX-only, just set the Duplex column to "off" for those memories.
Updated by Steve Hopkins about 2 months ago
yes... tried it.. I've seen that somewhere else on chirp
trouble with that is... put in "duplex off" first errors
invalid frequency... put in frequency first again invalid
frequency.. cant win.. but nice try lol
Updated by Steve Hopkins about 2 months ago
out of pure interest I have just tried.. valid frequency (145.00) then "duplex off"
then attempted to change frequency to 133.850 (local airport).. no go. frequency
outside of range (all in chirp.. didn't get as far as radio)
I'm to old for this malarkey. haha
Updated by Dan Smith about 2 months ago
It works for me with this driver, when I try, but maybe you've got something else going on. Can you open another bug (just to keep the issues separate)? Attach an radio .img that you're working on, a debug log captured from after you try to set duplex=off, and detailed steps on what you're doing and seeing? I'd definitely like to fix it if there's something really going on. Thanks!
Updated by Steve Hopkins about 2 months ago
yes I can do that.. I have just found another hiccup.. I installed a block set of
frequencies and then deleted the ones I did not want.. sent to radio.. They are
still there.. but memory slots are empty in chirp.. it can wait till tomorrow
thanks for your time Dan.... Steve.
Updated by Dan Smith about 2 months ago
Oh I see, you're trying a frequency that is actually outside the range of the radio... 133.85 is below what the driver thinks the radio can do, which is why it's refusing it. No relation to setting duplex=off. 145.00 should be able to do duplex=off fine.
TID wrote this driver themselves and it has lots of problems like this, including some other reports about the un-deletable channels. If you know the radio can go below 136MHz and do airband (i.e.) open another bug for that and I'll try to get them to take a look. Also, please do open another (separate) bug for the un-deletable channel issue and I'll do the same.
Updated by Dan Smith about 2 months ago
- Status changed from In Progress to Closed
- % Done changed from 0 to 100
Applied in changeset github|32f1a5fcae56627d0be351c659c3ce1bce417de7.