Bug #2937
closedTYT TH-9800: 'frequency out of range' for valid frequencies
0%
Description
I understand that CHIRP supports certain bands.
But would it not be possible to enable bands that are supported by the radio?
The TH-9800 covers 4M | 70MHz; I downloaded the img from the radio, then populated that. But CHIRP complained about the frequency.
Files
Updated by Jens Jensen almost 9 years ago
Hi Simon, perhaps you have a model which has different band support than the ones we have.
Can you please provide an unmodified radio image which we can examine.
Please download an image from the radio and, without any further modification in chirp, save the .img, and attach here.
Updated by Simon Rodda over 8 years ago
Apologies for the delay; I will do this later.
This is the same problem as RM 3367, reported by William Michalson, for 220MHz.
Updated by Simon Rodda over 8 years ago
- File TH9800 capabilities.PNG TH9800 capabilities.PNG added
Here's a screenshot in the meantime of the radio's capabilities -
You can see that if the [TX|RX] start/end is blank, it can't handle that range.
And that 60MHz start/end for both TX & RX is SET to 66 - 88 MHz.
Updated by Simon Rodda over 8 years ago
- File TH9800 band snippet.PNG TH9800 band snippet.PNG added
It's raining like a so-and-so out there; so I ain't going to the car to download an img.
However, here's what's in a previous download.. see dat file format for explanation.
Updated by Simon Rodda over 8 years ago
Me again...
It seems revision 2565 was to fix this /very/ issue...
Updated by Simon Rodda over 8 years ago
Resolved...
Changed the max value for the 60M band in th9800.py to 71MHz:
rf.valid_bands = [(26000000, 33000000),
(47000000, *71000000*),
(108000000, 180000000),
(350000000, 399995000),
(400000000, 512000000),
(750000000, 950000000)]
- SR
Updated by Bernhard Hailer over 4 years ago
- Status changed from New to Closed
- Model affected changed from TH-9800 to TYT TH-9800
This appears to be complete (see #3367).
If there are further issues with this driver, please open a new bug report. Thanks!