Project

General

Profile

Actions

Bug #4483

closed

Can't download initial file BTech uv 5x3

Added by Bob Evans almost 8 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
02/02/2017
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
BTech UV-5X3
Platform:
MacOS
Debug Log:
I read the instructions above:

Description

I've seen three different versions of this issue with a comment that they got it resolved but never HOW. I'm trying to pull down the initial file for my new BTech UV 5x3 and get the error - Not the amount of data we wanted. I tried on a radio with nothing programmed, and with one channel programmed. I have updated driver for El Capitan, and am trying two different cables that work with multiple Baofeng and Woxoun radios in both MacOS and Windows 10 run under Fusion emulator.

Bob Evans

ps I've tried setting to a channel with no activity, turning volume all the way up etc. no difference. cable is talking to my computer, radio seems to be talking just not saying what Chirp expects to hear


Files

debug.log (22.9 KB) debug.log Bob Evans, 02/03/2017 09:13 AM
debug.log (26.8 KB) debug.log Bob Evans, 02/23/2017 08:53 PM
Actions #1

Updated by Jim Unroe almost 8 years ago

  • Status changed from New to Feedback

The most common mistakes I've seen are..

1 the user selects Baofeng for the vendor instead of BTECH
2 the user selects UV-50X3 instead of UV-5X3

Attach the debug.log file

Jim

Actions #2

Updated by Bob Evans almost 8 years ago

Here is the debug log - forgot to attach first time

Actions #3

Updated by Bob Evans over 7 years ago

I've tried this again with latest daily build. Also tried factory reset of radio, then manually programming several channels (this was what helped our ACS Chief Radio Officer). every attempt gets - "... not the amount of data we wanted). Debug log seems to error out on an index out of range. interesting note for this radio - memory channels go from 0 - 127 rather than the usual 1-128. latest Debuf log attached. This is getting very frustrating as other's I know with this radio are not having a problem. cable used works with every other (baoefung, wouxun) Kenwood plug compatible radio I have so I don't think it is a cable or driver issue

Bob Evans

Actions #4

Updated by Jim Unroe over 7 years ago

Do you have the Baofeng Tech PC03 FTDI programming cable or do you have one of the cheaper programming cables with unauthorized copy of a Prolific USB-to-Serial chip? If the latter, you will probably have to purchase a 3rd party driver (the driver for the Mac available from Prolific is intentionally incompatible).

Jim KC9HI

Actions #5

Updated by Bob Evans over 7 years ago

I have what I believe is an authorized prolific copy (got several years ago for use with my first Wouxun radio). No one is telling me WHY I need to check this stuff when the cable works with several different radios using both CHIRP and company software in both MAC os and Windows 7 and 10 Fusion emulation off same Mac. I use it on three different Wouxun's - UV3D, UV 6DX, UV8E (factory program in Windows), Baofeung UV82. I use a different plug cable but same driver I believe for my BTech Mini 2501*200. Since the cable / driver works on all those radios WHY do you keep insisting I check the cable & driver?

to help debug - at one time when I was asking about my UV8E (Wouxun try band) I read about using a serial port logging program on windows to send a log of a download using the factory software (actual serial port data stream). Is there a compatible tool for Mac OS - I have several serial port /terminal utilities that have logging but can't find the protocol setup for the prolific chip - baud rate, parity, stop bit, cts, dir etc. to connect properly. I'd like to see if there is actual data going through (CHIRP usually says it can't connect if there isn't rather than not the amount of data we expected)

Actions #6

Updated by Bernhard Hailer over 4 years ago

  • Chirp Version changed from 0.4.0 to daily
  • Model affected changed from (All models) to BTech UV-5X3

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?

Actions #7

Updated by Bernhard Hailer about 4 years ago

  • Status changed from Feedback to Closed

No more feedback by submitter.
Bob, if you still have problems, please let us know, and we'll reopen this ticket. Forgive us if we ask seemingly redundant questions, but a) it's not easy to do remote analysis, and b) we have seen it many times that even when a user insists that everything works 100%, something still doesn't. Getting impatient helps nobody. Plus: you could ask on the "mailing list":http://intrepid.danplanet.com/mailman/listinfo/chirp_users - a lot of people with similar issues might be listening.

Actions

Also available in: Atom PDF