New Model #8005
closedYedro Yc- M04vus = Retevis RT95 = Anytone AT778uv
100%
Description
I recently bought a radio with the following characteristics:
Brand: Yedro
Model YC-M04VUS
It's exactly the same radio as Retevis RT95 and Anytone AT778uv, just with another brand.
When I tried to program it with chirp (on Linux), I get the following error:
An error has occurred
Radio version not in allowed list for Retevis-RT95: 000: 49 59
43 4d 30 34 55 56 IYCM04UV
008: 01 56 31 30 30 00 00 06 .V100...
Is there a possibility to add support to this radio?
I'm able to test it!
Thanks a lot for Chirp, I am using it with a couple of radios without any issue.
Regards
Files
Updated by Fernando Sclavo over 4 years ago
I know a little (very little to be honest) of Python, but looking on source code, found that drivers/anytone778uv.py check and has a list of accepted models, it's safe to try to add the following paragraph to this list?:
@directory.register
class YedroYCM04vus(AnyTone778UVBase):
VENDOR = "Yedro"
MODEL = "YC-M04VUS"
# Allowed radio types is a dict keyed by model of a list of version
# strings
ALLOWED_RADIO_TYPES = {'IYCM04UV': ['V100']}
I took the values from the error message, doesn't know if they are correct.
Updated by Joe Milbourn over 4 years ago
that looks good, just remove the leading I from IYCM04UV, so allowed radio types looks like
ALLOWED_RADIO_TYPES = {'YCM04UV': ['V100']}
Updated by Fernando Sclavo over 4 years ago
Thanks Joe, removed "I" from model and work's great! I could read and program my radio whitout issues.
What can I do to get this change included in official Chirp?
Updated by Fernando Sclavo over 4 years ago
This is the exact code appended at the end of anytone778uv.py file:
@directory.register
class YedroYCM04vus(AnyTone778UVBase):
VENDOR = "Yedro"
MODEL = "YC-M04VUS"
# Allowed radio types is a dict keyed by model of a list of version
# strings
ALLOWED_RADIO_TYPES = {'YCM04UV': ['V100']}
Updated by Joe Milbourn over 4 years ago
Fernando Sclavo wrote:
What can I do to get this change included in official Chirp?
You can send a patch to the chirp_devel mailing list - see DevelopersProcess. If you don't fancy that,let me know here and I'll do it.
thanks
J
Updated by Fernando Sclavo over 4 years ago
Joe Milbourn wrote:
Fernando Sclavo wrote:
What can I do to get this change included in official Chirp?
You can send a patch to the chirp_devel mailing list - see DevelopersProcess. If you don't fancy that,let me know here and I'll do it.
thanks
J
I tried to send the patch but I get the following error when tried to send it with Mercurial:
(could not negotiate a common security protocol (tls1.1+) with intrepid.danplanet.com; the likely cause is Mercurial is configured to be more secure than the server can support)
(consider contacting the operator of this server and ask them to support modern TLS protocol versions; or, set hostsecurity.intrepid.danplanet.com:minimumprotocol=tls1.0 to allow use of legacy, less secure protocols when communicating with this server)
(see https://mercurial-scm.org/wiki/SecureConnections for more info)
abort: error: UNSUPPORTED_PROTOCOL
Setting the proposed configuration (both with "hg config -e" or on chirp.hg/.hg/hgrc makes no difference.
Updated by Jim Unroe over 4 years ago
Fernando Sclavo wrote:
I tried to send the patch but I get the following error when tried to send it with Mercurial:
(could not negotiate a common security protocol (tls1.1+) with intrepid.danplanet.com; the likely cause is Mercurial is configured to be more secure than the server can support)
(consider contacting the operator of this server and ask them to support modern TLS protocol versions; or, set hostsecurity.intrepid.danplanet.com:minimumprotocol=tls1.0 to allow use of legacy, less secure protocols when communicating with this server)
(see https://mercurial-scm.org/wiki/SecureConnections for more info)
abort: error: UNSUPPORTED_PROTOCOLSetting the proposed configuration (both with "hg config -e" or on chirp.hg/.hg/hgrc makes no difference.
Hi Fernando,
Don't use TLS. What I did was to put the following in my mecurial.ini
tls = false
Jim KC9HI
Updated by Jim Unroe over 4 years ago
Fernando Sclavo wrote:
Thanks Jim, it works.
Patch sent!
I'm not so sure. Unless something is down on the "CHIRP" end, there should have been an email sent to [chirp_devel] mailing list regarding your submission. I didn't see one.
Jim KC9HI
Updated by Fernando Sclavo over 4 years ago
Jim Unroe wrote:
I'm not so sure. Unless something is down on the "CHIRP" end, there should have been an email sent to [chirp_devel] mailing list regarding your submission. I didn't see one.
Jim KC9HI
Thanks for warning Jim.
I sent it again with CC to my email, and I get a "waiting for moderator approval" message (because I'm not subscribed to the list).
Updated by Luciano Peroni over 4 years ago
Thanks Fernado for your contribution, I also have a Yedro M04VUS radio and I was able to connect it to the PC with windows 10.
Thanks also to the Chirp team for their work.
Updated by Bernhard Hailer about 4 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 90
Hi Fernando, have you been successful submitting your patch? Thanks!
Updated by Fernando Sclavo about 4 years ago
Updated by Joe Milbourn about 4 years ago
- Status changed from In Progress to Closed
- % Done changed from 90 to 100
Applied in changeset commit:1e4d8cbdbafe.