Project

General

Profile

Actions

Bug #10454

closed

Retevis H777S Unable to Modify Frequency Values

Added by Ethan Creveling over 1 year ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
03/17/2023
Due date:
% Done:

100%

Estimated time:
Chirp Version:
next
Model affected:
Retevis H777S/RT24
Platform:
Windows
Debug Log:
I read the instructions above:

Description

I am trying to program my Retevis H777S model radio to match the same settings that our H777 model is programmed to. The problem is, after turning my radio on, connecting it using the dual jack - USB cable, and downloading the settings to CHIRP, the Frequency field is greyed out and immutable. The image file that we are using and has been working great for our regular H777 models is able to have the frequency field be modified and set to whatever we choose. Other fields in the image file are able to be modified with the H777S except the frequency and a couple of others.

I tried downloading the H777 Image file to my H777S, but it seems CHIRP detects that the devices are different and doesn't detect a response from the radio when trying to upload the image.

I attached three screenshots: one of the uploading of the H777S radio, one image of the immutable frequency field for the H777S, and another of the modifiable frequency field for the regular H777 model

Anyone have any ideas? I need the frequency values and to be the same amongst models so that they can intercommunicate.

Thanks!
Ethan


Files

Screenshot 2023-03-17 145248.png (61.3 KB) Screenshot 2023-03-17 145248.png Ethan Creveling, 03/17/2023 11:54 AM
Screenshot 2023-03-17 145227.png (54.4 KB) Screenshot 2023-03-17 145227.png Ethan Creveling, 03/17/2023 11:54 AM
Screenshot 2023-03-17 145127.png (44.8 KB) Screenshot 2023-03-17 145127.png Ethan Creveling, 03/17/2023 11:54 AM
IMG_6863.tif (126 KB) IMG_6863.tif Doug Liman, 06/21/2023 04:41 AM
retevis_h777s_full_band.py (20.7 KB) retevis_h777s_full_band.py Jim Unroe, 06/21/2023 06:44 PM
Actions #1

Updated by Jim Unroe over 1 year ago

The Retevis H777 is sold as a full band UHF radio so CHIRP is programmed to support the full UHF band.

The Retevis H777S is sold as an FRS radio. CHIRP is programmed to match the factory software which only support the FRS frequencies.

Are you able to program the frequencies that you want with the H777S' factory software?

Jim KC9HI

Actions #2

Updated by Ethan Creveling over 1 year ago

Jim Unroe wrote in #note-1:

The Retevis H777 is sold as a full band UHF radio so CHIRP is programmed to support the full UHF band.

The Retevis H777S is sold as an FRS radio. CHIRP is programmed to match the factory software which only support the FRS frequencies.

Are you able to program the frequencies that you want with the H777S' factory software?

Jim KC9HI

Hi Jim,

Thanks for the response! I tried the native Retevis software and found that like CHIRP, it must be expecting only FRS compatible frequencies so they are immutable there as well.

I guess we will have to return these H777S radios and purchase H777 in order to program the frequencies to what are already deployed at our company.

Thanks!

Actions #3

Updated by Doug Liman over 1 year ago

I have the same problem with Retevis rb75 which is sold as a gmrs radio but will not let me change frequencies

I get one of two things - either an error box (see attachment) or after overwriting it just reverts back to the originally assigned frequency

Im trying to make all channels on the radio the sane frequency to dummy proof

Actions #4

Updated by Jim Unroe over 1 year ago

Give this test driver module a try. Here is how: LoadingTestModules

Jim KC9HI

Actions #5

Updated by Jim Unroe over 1 year ago

  • Status changed from New to In Progress
  • Assignee set to Jim Unroe
  • Target version set to chirp-py3
Actions #6

Updated by Jim Unroe over 1 year ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100
  • Model affected changed from Retevis H777S to Retevis H777S/RT24

A patch has been submitted. Support will be in the next CHIRP build following acceptance.

Jim KC9HI

Actions

Also available in: Atom PDF