CHIRP

I don't see anything in the debug.log file that shows where a UHF frequency was entered and CHIRP complained about it. To create a clean debug.log file you should...

1. close CHIRP
2. open CHIRP
3. cause error
4. close CHIRP

I do see where many channels are programmed at the 20KHz bandwidth. The driver only support the 12.5 KHz and 25 KHz bandwidths. This is not really a problem since CHIRP automatically "promotes" the 20 KHz bandwidth to 25 KHz.

You should mention which frequency/frequencies that you are trying to enter and if you have switched the radio's service setting to "Mode 2" (frequency unlocked). By design, CHIRP only supports UHF frequencies from 430.000-440.000 MHz when the radio is not set to Mode 2.

I would also suggest that you attach a CHIRP Radio Images (*.img) file that 1 or more of these "out of the frequency range" channels for a developer to experiment with.

Jim KC9HI

I followed the instructions for the debug file before sending it. If you still want me to recreate it and upload it after reading this response please let me know.

I found nothing in the chirp software regarding 20 KHz vs 25 KHz bandwidth. However if I use the software from Midland it lists the 2M channels as 20 KHZ and the 70cm channels as 25 Khz. I really don't like using Windows for my OS so I chose to install Chipr on my Linux partition.

The 70cm channels that I use in my radios range from 443 MHz through 444M MHz so I understand why I might be seeing the error message. One thing that I find curious is that I cannot find any option in the software for Mode 2 (frequency unlocked). The closest thing I have found is using the menu Radio>Channel Defaults>North American Band Plan. What I assume is that the US 70cm band of 420 thru 450 MHz should be supported there. Another thing that I find curious is that if I use Chirp for my Yaesu FT-60R I have full access to the entore US 70cm band from 420 thru 450MHz.

The 443 and 444 MHz channels in my Midland radios were downloaded form the radios to the Chirp software on my laptop. The image file is uploaded with this response. Thank you for your time in helping me work through this.

Martin Groat wrote:

I followed the instructions for the debug file before sending it. If you still want me to recreate it and upload it after reading this response please let me know.

But you didn't do it the way I requested because there are no errors pertaining to entering a frequency that is out-of-range the debug.log file.

I found nothing in the chirp software regarding 20 KHz vs 25 KHz bandwidth. However if I use the software from Midland it lists the 2M channels as 20 KHZ and the 70cm channels as 25 Khz. I really don't like using Windows for my OS so I chose to install Chipr on my Linux partition.

Correct. CHIRP does not support the 20 KHz bandwidth. That is way I am recommending that you set the channel's bandwidth to either 12.5 KHz or 25 KHz when programming using the OEM software. Like I said, it doesn't really matter because CHIRP forces it to 25 KHz anyway. It is just one less thing for CHIRP to do since 20 KHz is typically not used by hams.

You don't have to run Windows to use CHIRP. The problem is the configuration of your radio. CHIRP is designed to match the capability of your radio and your radio is currently set to only TX/RX within the 430.000-440.000 MHz UHF frequency range so CHIRP matches that frequency range. Unfortunately due to a mistake by the radio manufacturer, you must change your radio to Mode:02 to get support for the full USA UHF amateur band.

The 70cm channels that I use in my radios range from 443 MHz through 444M MHz so I understand why I might be seeing the error message. One thing that I find curious is that I cannot find any option in the software for Mode 2 (frequency unlocked). The closest thing I have found is using the menu Radio>Channel Defaults>North American Band Plan. What I assume is that the US 70cm band of 420 thru 450 MHz should be supported there. Another thing that I find curious is that if I use Chirp for my Yaesu FT-60R I have full access to the entore US 70cm band from 420 thru 450MHz.

The firmware of these radios incorrectly limits the Mode 1 (US) UHF frequency limits to the same frequency limits as Mode 3 (EU): 430.000-440.000 MHz. Unfortunately this does not coincide with the actual band limits that are available to US amateur radio operators: 420.000-450.000. CHIRP is designed to match the frequency ranges that the radio is currently configured to.

Since all of these radios have this bug, the only way to get support for the full 420.000-450.000 MHz USA amateur band is to set the radio to Mode:02 which allows VHF: 136.000-174 MHz and UHF: 400.000-480.000 MHz.

CHIRP has full access to 420.000-450.000 MHz on your FT-60R because it has full access to this frequency range. Your DBR-2500 does not. This is a limit of the radio, not CHIRP.

You can google to find instructions for changing the Anytone AT-778UV, Retevis RT95, Midland DBR-2500 and other variants band limits between Mode:01 (US), Mode:02 (unlocked) and Mode:03 (EU). Here is a "Youtube":https://www.youtube.com/watch?v=V1PsSyk1-Lo video that explains the process. I have also attached the instructions that I created for myself to explain the process.

The 443 and 444 MHz channels in my Midland radios were downloaded form the radios to the Chirp software on my laptop. The image file is uploaded with this response. Thank you for your time in helping me work through this.

Once you have configured your radio to Mode:02, you should be able to use CHIRP to enter the frequencies that you require.

Jim KC9HI

Instructions provided, no feedback.