Bug #11996
closedFM VFO/CH inverted
100%
Description
(Describe what you were doing)
Setting FM VFO/CH mode
(Describe what you expected to happen)
VFO = FM VFO mode, CH = selet from code plug FM channels
(Describe what actually happened instead)
It's inverted from what the radio expects; If set to VFO in cps, the radio comes up in channel mode, if set to CH in cps, the radio comes up in VFO mode.
(Has this ever worked before? New radio? Does it work with OEM software?)
No. Yes. No - OEM cps is wrong too.
Files
Updated by Jarvis Whitman 8 days ago
- File config.txt config.txt added
- File TIDRADIO_TD-H8_TID1_20250520.img TIDRADIO_TD-H8_TID1_20250520.img added
- File win_system_info.txt win_system_info.txt added
- File debug_log.txt debug_log.txt added
[Uploaded from CHIRP next-20250516]
Updated by Fred Trimble 7 days ago
- File tdh8.py tdh8.py added
- Status changed from New to In Progress
- Assignee set to Fred Trimble
- % Done changed from 0 to 50
It's inverted from what the radio expects; If set to VFO in cps, the radio comes up in channel mode, if set to CH in cps, the radio comes up in VFO mode.
Jarvis,
Thanks for reporting this obscure bug. Try this attached modified TD-H8 driver to see if it fixes the issue.
Please use the LoadingTestModules process to test out the modified driver and report any findings here.
This is a simple one-line code change to reverse the order of the settings literals. As a side note this inversion bug also effects the TD-H3 so this fix is relevant for that model too.
Updated by Jarvis Whitman 6 days ago
Wow! That was quick!
You guys supporting CHIRP are doing a fantastic job! SO many radios. SO
many config options. So many releases.
I'm curious to know how many folks are indeed working on it? And is there
room for one more (me)? I've been a software engineer for 45 years, albeit
not that great with python yet. I do have about 15 different radio models
though...and more coming.
73
-Jason Loefer
WW1SGT
On Wed, May 21, 2025 at 4:08 PM Fred Trimble redmine@chirpmyradio.com
wrote:
Updated by Fred Trimble 6 days ago
- % Done changed from 50 to 90
If you fell like contributing by all means jump in and get your feet wet. You shouldn't have any problem with the Python coding. The learning curve will be in the git workflow to get your changes merged into master successfully.
Easy Fixes like this one would have been perfect for a first try!
A git Pull Request has been created to get these changes merged into master and the next CHIRP build.
The PR also contains another commit that changes the sense of the FM "Forbid Receive" setting heading short-text. I noticed that this was reversed too and the setting actually allowed received signals to interrupt FM reception instead of blocking an interruption.
Thanks, Fred
Updated by Jarvis Whitman 5 days ago
I wondered about that FM forbid. TIDRADIO should probably rename that to "Broadcast FM", and "FM-DW" to "Interrupt FM". What it ACTUALLY does in the radio if "FM-DW" / "Forbid Receive" is off and a signal is received, it often voices over broadcast FM with the received signal. Weird.
...and rename "D. Wait" to "Dual Watch".
Thank you, Fred, and for several things! I might just have to do that! I've worked with git-based workflows recently. We'll have to do this sooner or later anyway as we're hoping to get CHIRP support for radios we're building...in the USA.
Updated by Anonymous 5 days ago
- Status changed from In Progress to Closed
- % Done changed from 90 to 100
Applied in changeset github|a50213c937e1c183926d890c9322e9a4f48ecd83.