Project

General

Profile

Actions

Bug #6831

closed

CHIRP will not download from BTECH GMRS-V1, gives incorrect model number error

Added by Colin Getty almost 5 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
06/01/2019
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
BTech GMRS-V1
Platform:
Windows
Debug Log:
I read the instructions above:

Description

CHIRP will not download from BTEC GMRS-V1. Error message says "An error has occurred. Incorrect 'Model' selected." I don't have a file to write to radio so I don't know if uploading works or not. Programming cable works on other radios like Wouxun with CHIRP. This issue seems to have come up before with this radio. I don't know when the radio was purchased. Sticker inside the radio says "Model NO: GMRS-V1 FCC ID: 2AGND-GMRS-V1" Debug log attached.


Files

debug.log (23.7 KB) debug.log Colin Getty, 06/01/2019 07:59 PM
Actions #1

Updated by Bernhard Hailer over 3 years ago

  • Status changed from New to Feedback
  • Model affected changed from GMRS-1 to BTech GMRS-V1

Actually, the log suggests a cable / driver / connector issue; there is no report about a bad model number. You say that the cable works with other radios, so the best bet is that there's an electrical contact problem with this specific radio and your cable (plug too big or not seated well).
Please refer to these Wiki articles:
CableGuide
CableGuide FTDI OEM Cables
[RTSystemsCablesAndMavericks]
Windows notes: 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
MacOS notes: this OS is apparently very picky about USB to Serial cables. From what I heard, only (genuine) FTDI-based cables can be made work.
You must have the KK7DS Python runtime for Mac OSX installed.
Also see MacOS Tips!
Linux notes: Linux generally is quite good with USB to Serial converter drivers. The most likely cause for grief is a connector which doesn't provide good electrical contact.
Bluetooth notes: connections often suffer from timing issues, please try a cable instead.

Actions #2

Updated by Bernhard Hailer over 3 years ago

  • Status changed from Feedback to Closed

No more feedback by submitter.

Actions

Also available in: Atom PDF