Bug #6045

Btech MURS-V1 Radio Read Error

Added by Thomas Palmieri about 2 years ago. Updated about 1 month ago.

Status:Closed Start date:08/19/2018
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:chirp-daily
Chirp Version:daily Platform:Windows
Model affected:BTech MURS-V1

Description

I submitted this problem to Baofeng Tech Support. They asked that I contact Chirp, which is my reason for contacting you. I documented the issue to them as follows:


On August 18, 2018 at 5:08:54 PM, () wrote:

Visitor: Thomas Palmieri

Email Address:

Message: I recently purchased a BTECH MURS-V1 Portable Radio S/N MURSV10001921 and I am very pleased with the radio. I was able to follow the manual and set channel operating parameters such as DCS CTCSS, TOT, etc., using the radio's keypad. I downloaded the latest version of CHIRP and programming cable drivers and my Windows 10 OS recognizes the cable COM Port. So far, so good. When I attempt to read the radio so I can change the channel name, CHIRP returns an error message that says, "An Error Has Occurred. Received and unknown response from the radio." The Left LED on the top of the radio blinks Green for about 1 SEC then the software fails and issues the error code. The Radio Make, Model and COM port are correct to receive the radio download, so I am bewildered. Can you suggest what I can do to read the radio, change the channel names, and upload the changes to the radio please?

Thank you,

Tom


I attached the debug log associated with the error to this message

Thank you,

Tom Palmieri
843-458-0445

debug.log (31.7 kB) Thomas Palmieri, 08/19/2018 07:41 am

History

Updated by Bernhard Hailer 6 months ago

  • Status changed from New to Feedback
  • Priority changed from High to Normal
  • Target version set to chirp-daily
  • Model affected changed from Btech MURS-V1 to BTech MURS-V1

Have you been able to resolve this on your own since you submitted this?
Have you tried with a recent version since you submitted this?

I suspect a cable issue. Please refer to these Wiki articles:
CableGuide
CableGuide FTDI OEM Cables
RTSystemsCablesAndMavericks (if you're running MacOS)

Windows: If you are using a generic cable with a Prolific chip, you will very likely need to downgrade your driver to version 3.2.0.0.
It can be found at http://www.miklor.com/COM/UV_Drivers.php

Updated by Bernhard Hailer about 1 month ago

  • Status changed from Feedback to Closed

No more feedback by submitter.

Also available in: Atom PDF

prevent spam