New Model #8859

Anytone 778UV (VOX) 3.00 version

Added by Jonathan Williams about 1 month ago. Updated 8 days ago.

Status:Closed Start date:03/02/2021
Priority:Normal Due date:
Assignee:Jim Unroe % Done:

100%

Category:-
Target version:chirp-daily
Chirp Version:daily Equipment Loan Offered:No

Description

There is a new (VOX) 3.00 version of the 778UV that is not supported by CHIRP. This new version requires the 3.00 version of the CPS software to be programed. In the download folder it is also referred to as the (VOX) version of the radio. My other 778UV that is compatable with the 2.00 CPS software works fine in CHIRP. Can support for this new 3.00 (VOX) version of the 778UV please be added to CHIRP if possible.

Screenshot 2021-03-02 155202.jpg - Error in CHIRP when trying to download from radio. (19.2 kB) Jonathan Williams, 03/02/2021 03:58 pm

RetevisRT95-P.py (34.9 kB) AJS QUIDZ, 03/07/2021 06:18 pm

Retevis_RT95-P-recent.img (12.8 kB) AJS QUIDZ, 03/07/2021 08:48 pm

RT95-P_Browse.png (29.9 kB) Jim Unroe, 03/08/2021 01:59 pm

anytone778uv_vox.py (63.1 kB) Jim Unroe, 03/08/2021 01:59 pm

Default Key Layout (VOX) 3.00.jpg (38.8 kB) Jonathan Williams, 03/08/2021 04:23 pm

anytone778uv_vox2.py (63.3 kB) Jim Unroe, 03/08/2021 06:35 pm

6 character channel name (VOX 3.00).dat (44.9 kB) Jonathan Williams, 03/08/2021 07:22 pm

debug.log (29.2 kB) Jonathan Williams, 03/08/2021 07:38 pm

debug 778UV-P.log (29.2 kB) Jonathan Williams, 03/08/2021 07:45 pm

anytone778uv_vox3.py (63.3 kB) Jim Unroe, 03/08/2021 08:01 pm

first successful download unedited.img (12.8 kB) Jonathan Williams, 03/09/2021 09:50 pm

second download after first base reupload.img (12.8 kB) Jonathan Williams, 03/09/2021 09:50 pm

anytone778uv_vox4.py (63.3 kB) Jim Unroe, 03/12/2021 01:58 pm

4 CHIRP Images.zip (7.2 kB) Jonathan Williams, 03/13/2021 09:16 pm

anytone778uv_vox5.py (65.5 kB) Jim Unroe, 03/15/2021 06:42 pm


Related issues

duplicated by Bug #8867: anytone 778uv Closed 03/05/2021
duplicated by Bug #8955: New AnyTone AT-778UV giving error "Radio version not in a... Closed 04/02/2021

Associated revisions

Revision 3481:975f31e5d96e
Added by Jim Unroe 27 days ago

[AT-778UV] Add anytone778uv.py driver to cpep8.manifext

This patch adds the anytone778uv.py driver to the cpep8.manifest in order to
enable style checking.

related to #8859

Revision 3482:9d2390ab9a62
Added by Jim Unroe 27 days ago

[AT-778UV] Add support model variants that include VOX

This patch adds support for the new model variants that now include VOX:

Anytone AT-778UV VOX 3.0
Retevis RT95 VOX 2.0

fixes #8859

History

Updated by neil neil about 1 month ago

ditto, but didnt see your post till mine got posted. debug log in mine for chirp devs.

Updated by AJS QUIDZ about 1 month ago

Good AM

I was able to connect my retevis rt95 with vox using the module in the attached file.

What I did is include in the module my type of unit, like so...

@directory.register
class RetevisRT95P(AnyTone778UVBase):
VENDOR = "Retevis"
MODEL = "RT95-P" # Allowed radio types is a dict keyed by model of a list of version # strings
ALLOWED_RADIO_TYPES = {'RT95-P': ['V100']}

I can configure the memories but not the settings...
Well for now its more of a consolation to not manually input my saved channels anymore.
I hope this helps and that in due time someone can add this model: Retevis RT-P/Anytone 778UV-P

Updated by Jim Unroe about 1 month ago

  • Status changed from New to Feedback

AJS QUIDZ wrote:

Good AM

I was able to connect my retevis rt95 with vox using the module in the attached file.

What I did is include in the module my type of unit, like so...

@directory.register
class RetevisRT95P(AnyTone778UVBase):
VENDOR = "Retevis"
MODEL = "RT95-P"
  1. Allowed radio types is a dict keyed by model of a list of version
  2. strings
    ALLOWED_RADIO_TYPES = {'RT95-P': ['V100']}

I can configure the memories but not the settings...
Well for now its more of a consolation to not manually input my saved channels anymore.
I hope this helps and that in due time someone can add this model: Retevis RT-P/Anytone 778UV-P

There is one or more settings that are out of range. Please include a freshly downloaded CHIRP Radio Images (*.ing) file for testing.

Jim KC9HI

Updated by AJS QUIDZ about 1 month ago

Here are the memories I was able to input in my radio using the said module...
I am not an expert programmer or anything, this is just more of a trial and error thing...

Thank you

Updated by Jim Unroe about 1 month ago

AJS QUIDZ wrote:

Here are the memories I was able to input in my radio using the said module...
I am not an expert programmer or anything, this is just more of a trial and error thing...

There are 2 reasons the Settings tab doesn't show up for you.

1. You are using a copy of the driver module that predates the addition of the Settings menus.
2. The Key mode 2 P2 and Key mode 2 P5 settings both only have 17 choices and they are currently set to an out-of-range choice of 18.

options = ["A/B", "V/M", "SQL", "VOL", "POW", "CDT", "REV", "SCN", 
           "CAL", "TALK", "BND", "SFT", "MON", "DIR", "TRF", "RDW",
           "NULL"]                                          

So what needs to be figured out is...

What are the valid choices for this radio? and Do the valid choices include and 18th choice?

If there is not a valid 18th choice, then the out-of-range choice must be forced to a default valid choice.

A couple of temporary solutions for the out-of-range settings would be...

1 Use the CHIRP Developer Function "Browser" to change keyMode2P2 and keyMode2P5 "Dec" values from 18 to some other value in the range of 1 to 17 (see attached "RT95P_Browse.png).

2 Edit the driver module to temporarily add an 18th selection as shown below.

options = ["A/B", "V/M", "SQL", "VOL", "POW", "CDT", "REV", "SCN", 
           "CAL", "TALK", "BND", "SFT", "MON", "DIR", "TRF", "RDW",
           "NULL", "unk"]                                          

So what I have done as a quick-and-dirty test is added the 18th selection (unk) to the options list as shown in 2 above and included selections for both radio models in the attached temporary/test driver module.

Vendor: Anytone | Model: AT-778UV-P
Vendor: Retevis | Model: RT95-P

Download the temporary driver module by left-clicking on the anytone778uv_vox.py link on this page (do not right-click to download) and then click the Download link on the page that loads. Enable Enable Developer Functions in the Help menu so you can temporarily load the driver module using the Load Module selection that is now available in the File menu.

If anyone could shed some light on the valid "options" for these 2 settings it would be helpful. Also, can anyone provide a link for downloading the OEM programming software related to these Anytone and/or Retevis models?

Jim KC9HI

Updated by Jonathan Williams about 1 month ago

Here is the link to download the OEM programming software for the New (VOX) 3.00 version of the 778UV. It should be the 4th link down in the list. It has instructions in the .zip for determining which CPS version to use for your radio. Another difference I have noticed with the new radio, is that it supports 6 characters for channel names instead of the previous 5 in the older versions of the radio.

http://anytone.net/download.html

Here are all the possible selections in the dropdown for the programable keys:
[A/B] [V/M] [SQL] [VOL] [POW]
[CDT] [REV] [SCN] [CAL] [TALK]
[BND] [SFT] [MON] [DIR] [TRF]
[RDW] [VOX] [NULL]

I have attached a screenshot of the default programable key layout.

Updated by Jim Unroe about 1 month ago

Jonathan Williams wrote:

Here is the link to download the OEM programming software for the New (VOX) 3.00 version of the 778UV. It should be the 4th link down in the list. It has instructions in the .zip for determining which CPS version to use for your radio.

I had found the link but I wasn't sure which of the 3 downloads for the AT-778UV to use. Thank you for clarifying that. The instructions seem to work for the AnyTone model but not the Retevis model.

Another difference I have noticed with the new radio, is that it supports 6 characters for channel names instead of the previous 5 in the older versions of the radio.

Interesting. Would you attach an image from your radio so I can investigate? Have 1 or more channels programmed with a 6-character name.

http://anytone.net/download.html

Thanks

Here are all the possible selections in the dropdown for the programable keys:
[A/B] [V/M] [SQL] [VOL] [POW]
[CDT] [REV] [SCN] [CAL] [TALK]
[BND] [SFT] [MON] [DIR] [TRF]
[RDW] [VOX] [NULL]

I have attached a screenshot of the default programable key layout.

This definitely helps for the AT-778UV. It somewhat helps for the RT95 but would feel more comfortable if I could locate the Retevis OEM programming software as well.

Attached is a test driver module that should work and support the added VOX PF key. I would recommend that you save the first successful download, unedited, as a CHIRP Radio Images (*.img) file and keep it in a safe place as a backup. Attach a copy here as well for testing purposes. Then review all of the channels and setting to make sure everything looks as it should. If everything looks then upload the still unedited tab back to the radio. Download a second time and attach to this issue so the two files can be compared. Test the radio to see that it still operates at before.

Jim KC9HI

Updated by Jonathan Williams about 1 month ago

"Interesting. Would you attach an image from your radio so I can investigate? Have 1 or more channels programmed with a 6-character name."

I attached a saved image from the 778UV CPS software with two channels that have 6 character channel names.

"Download the temporary driver module by left-clicking on the anytone778uv_vox.py link on this page (do not right-click to download) and then click the Download link on the page that loads. Enable Enable Developer Functions in the Help menu so you can temporarily load the driver module using the Load Module selection that is now available in the File menu."

Using these instructions, and after loading the vox2.py module (red screen) I get the original error popup "Radio version not in allowed list." and it wont download from the radio.

Updated by Jim Unroe about 1 month ago

Jonathan Williams wrote:

Using these instructions, and after loading the vox2.py module (red screen) I get the original error popup "Radio version not in allowed list." and it wont download from the radio.

Cause the error, close CHIRP, then attach the debug.log file.

Jim

Updated by Jonathan Williams about 1 month ago

Here you go.

Updated by Jonathan Williams about 1 month ago

I realized a mistake I made before, by not selecting the -P version in the dropdown. Even after selecting the -P model I still get the same error when trying to download from the radio. I have attached the new debug log.

Updated by Jim Unroe about 1 month ago

Jonathan Williams wrote:

I realized a mistake I made before, by not selecting the -P version in the dropdown. Even after selecting the -P model I still get the same error when trying to download from the radio. I have attached the new debug log.

OK. Hopefully this is better.

Jim

Updated by AJS QUIDZ about 1 month ago

Jim Unroe wrote:

Jonathan Williams wrote:

I realized a mistake I made before, by not selecting the -P version in the dropdown. Even after selecting the -P model I still get the same error when trying to download from the radio. I have attached the new debug log.

OK. Hopefully this is better.

Jim

Thanks Jim

This py file is way better, it works with my rt95-P...
I was able to change settings and upload my channels in the memory successfully...

More power to you and 73!

AJSQ

Updated by Jonathan Williams about 1 month ago

Apologies I didn't notice you posted a v3 of the module. Using the v3 I can download from the radio and program channels into it and upload them to the radio. Editing settings seems to work fine.

The only issue I have found is CHIRP only lets me use 5 character channel names (older model limitation) instead of 6 like the OEM programming software lets me for this new model.

I also followed these instructions below and uploaded the resulting CHIRP images.

"I would recommend that you save the first successful download, unedited, as a CHIRP Radio Images (*.img) file and keep it in a safe place as a backup. Attach a copy here as well for testing purposes. Then review all of the channels and setting to make sure everything looks as it should. If everything looks then upload the still unedited tab back to the radio. Download a second time and attach to this issue so the two files can be compared. Test the radio to see that it still operates at before."

Updated by Jim Unroe about 1 month ago

AJS QUIDZ wrote:

Thanks Jim

This py file is way better, it works with my rt95-P...
I was able to change settings and upload my channels in the memory successfully...

More power to you and 73!

AJSQ

Does this RT95 also have VOX like the Jonathan's AT-778UV?

Jim KC9HI

Updated by Jim Unroe about 1 month ago

Jonathan Williams wrote:

The only issue I have found is CHIRP only lets me use 5 character channel names (older model limitation) instead of 6 like the OEM programming software lets me for this new model.

I'm not exactly sure how best to "fix" this issue yet. Usually when the name field is expanded in memory, the added characters are added to the end of the name. In the case of your radio it looks like the additional character is added to the front. So when you use CHIRP to name a channel, what is see in the display of the radio is missing the first character of the name, right? Also when you download from your radio, any 6 character names programmed with the OEM software are missing the first character in CHIRP, right?

Jim

Updated by Jim Unroe about 1 month ago

Jonathan Williams wrote:

I also followed these instructions below and uploaded the resulting CHIRP images.

Both images are identical, which is what we would want the result to be. It also provided me images that have channels programmed with 6-character names. Thanks.

Jim

Updated by AJS QUIDZ about 1 month ago

Jim Unroe wrote:

AJS QUIDZ wrote:

Thanks Jim

This py file is way better, it works with my rt95-P...
I was able to change settings and upload my channels in the memory successfully...

More power to you and 73!

AJSQ

Does this RT95 also have VOX like the Jonathan's AT-778UV?

Jim KC9HI

Yes it does...I think its the new firmware of this kind of radios.
its version 1.10
previous is version 1.00

Updated by AJS QUIDZ about 1 month ago

Jim Unroe wrote:

Jonathan Williams wrote:

The only issue I have found is CHIRP only lets me use 5 character channel names (older model limitation) instead of 6 like the OEM programming software lets me for this new model.

I'm not exactly sure how best to "fix" this issue yet. Usually when the name field is expanded in memory, the added characters are added to the end of the name. In the case of your radio it looks like the additional character is added to the front. So when you use CHIRP to name a channel, what is see in the display of the radio is missing the first character of the name, right? Also when you download from your radio, any 6 character names programmed with the OEM software are missing the first character in CHIRP, right?

Jim

Yes this is the case...
I manually programmed the radio's channel name but when you download it using CHIRP the first letter is missing...
So basically when you upload the memories in the radio it'll only show 5 characters.

Updated by neil neil about 1 month ago

this version only allows 5 letter names, radio supports 6 letters.

Updated by Jim Unroe about 1 month ago

neil neil wrote:

this version only allows 5 letter names, radio supports 6 letters.

Yes. This is a known difference between the older non-VOX models and new models with VOX. I am working through the differences/issues one step at a time. I am waiting for Retevis to respond with answers to several questions I have asked them.

However, in the mean time, I have cobbled up some support for 6-character channel names. It should work for the radio models with VOX but will technically "break" support for non-VOX models. They will have to key in 6-characters (the first character can be a space or anything else to take up space) and only the trailing 5 character entered name will show in the radio's display (or just use CHIRP without this test driver module ;-) ).

Jim KC9HI

Updated by Jonathan Williams about 1 month ago

Jim Unroe wrote:

However, in the mean time, I have cobbled up some support for 6-character channel names. It should work for the radio models with VOX but will technically "break" support for non-VOX models. They will have to key in 6-characters (the first character can be a space or anything else to take up space) and only the trailing 5 character entered name will show in the radio's display (or just use CHIRP without this test driver module ;-) ).

Jim KC9HI

v4 is working great for me with the 6 character channel names. Thank you for all of your hard work.

Updated by neil neil about 1 month ago

Hi Jim, thanks for #4 of the .py file. are there any issues with this one? i have not found any. 6chr working fine and settings also seem ok too.
Memmory edits too, all fine.
is there anything to look out for to check?
only thing i have noticed, and worth pointing out in case, times of data transfer using chirp and anytone cps.
Is mre data being transfered on chirp, or is it just baud rate different? i have no idea.

acps read - 1min10s
cps writ - 1min15s

chp read - 1min35s
chp wrte - 1min33s

Updated by Jim Unroe about 1 month ago

I finally got a chance to install the VOX software and compare its settings with the non_VOX software to find out what, if any, other settings were added, removed or changed. There are a few. With most of the differences I already know what I have to do to get CHIRP in sync with the new radios. With 3 of the settings I will need some help.

What I need is for one or more of you to provide me with some CHIRP Radio Images (*.img) files that I can use to figure out where in memory the various VOX SET settings are stored.

Here is what I need done...

1 download from radio to the factory software.
2 on the Function Setup panel set the following VOX SET settings.
  [ ] VOX On/Off
  VOX Delay [2.0S     ]
  VOX Levle [5        ]
3 upload to radio from factory software.
4 download from radio to CHIRP
5 save tab as "VOX_defaults.img" 
1 download from radio to the factory software.
2 on the Function Setup panel set the following VOX SET settings.
  [✓] VOX On/Off
  VOX Delay [2.0S     ]
  VOX Levle [5        ]
3 upload to radio from factory software.
4 download from radio to CHIRP
5 save tab as "VOX_enabled.img" 
1 download from radio to the factory software.
2 on the Function Setup panel set the following VOX SET settings.
  [✓] VOX On/Off
  VOX Delay [4.5S     ]
  VOX Levle [5        ]
3 upload to radio from factory software.
4 download from radio to CHIRP
5 save tab as "VOX_Delay_4.5S.img" 
1 download from radio to the factory software.
2 on the Function Setup panel set the following VOX SET settings.
  [✓] VOX On/Off
  VOX Delay [2.0S     ]
  VOX Levle [9        ]
3 upload to radio from factory software.
4 download from radio to CHIRP
5 save tab as "VOX_Level_9.img" 

Try not to turn any knobs or press any buttons during this process. It will create "noise" that will make it harder to reverse engineer the memory locations. Once the 4 "image" files have been created and saved, add them to this issue (attaching the 4 files as a single ZIP archive would be a plus).

Don't forget to save the state of your radio before you start. That way once you are done, you can upload your saved image file to get back to where you were before you created the images needed for reverse engineering.

Thanks in advance.

Jim KC9HI

Updated by Jonathan Williams about 1 month ago

Jim Unroe wrote:

I finally got a chance to install the VOX software and compare its settings with the non_VOX software to find out what, if any, other settings were added, removed or changed. There are a few. With most of the differences I already know what I have to do to get CHIRP in sync with the new radios. With 3 of the settings I will need some help.

What I need is for one or more of you to provide me with some CHIRP Radio Images (*.img) files that I can use to figure out where in memory the various VOX SET settings are stored.

Here is what I need done...

[...]

[...]

[...]

[...]

Try not to turn any knobs or press any buttons during this process. It will create "noise" that will make it harder to reverse engineer the memory locations. Once the 4 "image" files have been created and saved, add them to this issue (attaching the 4 files as a single ZIP archive would be a plus).

Don't forget to save the state of your radio before you start. That way once you are done, you can upload your saved image file to get back to where you were before you created the images needed for reverse engineering.

Thanks in advance.

Jim KC9HI

Here you go. I hope I did everything correctly, and this helps you out.

Updated by Jim Unroe 30 days ago

  • Status changed from Feedback to In Progress
  • Assignee set to Jim Unroe
  • Target version set to chirp-daily

Jonathan Williams wrote:

Here you go. I hope I did everything correctly, and this helps you out.

Perfect. Exactly what I was looking for. I'll try to find some time to work on this some more later today.

Thanks,
Jim KC9HI

Updated by Jim Unroe 28 days ago

OK. Here is version 5. It adds the settings that that are new to the VOX version. It removes the settings that not in the VOX version. It also repairs the 5-character name support for the non-VOX radios.

Give it a go. Report any issues.

Thanks,
Jim KC9HI

Updated by Jonathan Williams 28 days ago

Jim Unroe wrote:

OK. Here is version 5. It adds the settings that that are new to the VOX version. It removes the settings that not in the VOX version. It also repairs the 5-character name support for the non-VOX radios.

Give it a go. Report any issues.

Thanks,
Jim KC9HI

v5 is working well for me! Thanks Jim!

Updated by neil neil 28 days ago

thanks again, yes, all seems ok here, just played with file 5 ok

Updated by Jim Unroe 26 days ago

  • Status changed from In Progress to Resolved
  • % Done changed from 90 to 100

It has been over 24 hours since I posted "vox5" and there has been no reports of problems. That's good enough for me so I just submitted a formal patch for consideration. Support should be in the next CHIRP daily build following acceptance. Just keep using the temporary "vox5" driver until support is "built in".

Jim KC9HI

Updated by Jonathan Williams 26 days ago

Jim Unroe wrote:

It has been over 24 hours since I posted "vox5" and there has been no reports of problems. That's good enough for me so I just submitted a formal patch for consideration. Support should be in the next CHIRP daily build following acceptance. Just keep using the temporary "vox5" driver until support is "built in".

Jim KC9HI

Thanks so much for your hard work on this Jim. I really appreciate it!

Updated by Anonymous 8 days ago

  • Status changed from Resolved to Closed

Applied in changeset 9d2390ab9a62.

Also available in: Atom PDF