Project

General

Profile

Actions

Bug #3635

closed

Can't download from BTech UV-2501+220 in Linux, but can in Windows

Added by Jim MacKenzie over 8 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
05/08/2016
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
BTech UV-2501+220
Platform:
Linux
Debug Log:
I read the instructions above:

Description

Hi,

I'm able to download the configuration from the BTech UV-2501+220 radio using CHIRP-daily (current as of 20160507) under Windows 10, but it fails with "An error has occurred" / "Invalid header for bloxk 0x000:" using Linux Mint.

Salient points:

  • FTDI data cable obtained from BTech
  • /dev/ttyUSB0 in Linux (read-write permissions fine); COM3 in Windows

Contents of ~/.chirp.debug.log:

[2016-05-08 08:24:39,890] chirp.ui.reporting - DEBUG: Server reports version daily-20160507 is latest
[2016-05-08 08:24:47,183] chirp.ui.mainapp - DEBUG: User selected BTECH UV-2501+220 on port /dev/ttyUSB0
[2016-05-08 08:24:47,186] chirp.ui.clone - DEBUG: Clone thread started
[2016-05-08 08:24:47,297] chirp.drivers.btech - INFO: Magic ACK received
[2016-05-08 08:24:47,874] chirp.drivers.btech - WARNING: Short reading 20 bytes from the 21 requested.
[2016-05-08 08:24:47,874] chirp.drivers.btech - INFO: Positive ident, this is a BTECH UV-2501+220
[2016-05-08 08:24:48,084] chirp.drivers.btech - DEBUG: Invalid header for block 0x0000
[2016-05-08 08:24:48,084] chirp.drivers.btech - DEBUG: CMD: 5 ADDR: 5800 SIZE: 00
[2016-05-08 08:24:48,085] chirp.ui.reporting - DEBUG: Reporting exception
[2016-05-08 08:24:48,085] chirp.ui.common - ERROR: -- Exception: --
[2016-05-08 08:24:48,085] chirp.ui.common - ERROR: Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/chirp/ui/clone.py", line 238, in run
self.__radio.sync_in()
File "/usr/lib/python2.7/dist-packages/chirp/drivers/btech.py", line 790, in sync_in
data = _download(self)
File "/usr/lib/python2.7/dist-packages/chirp/drivers/btech.py", line 581, in _download
d = _recv(radio, addr)
File "/usr/lib/python2.7/dist-packages/chirp/drivers/btech.py", line 417, in _recv
raise errors.RadioError("Invalid header for block 0x%04x:" % addr)
RadioError: Invalid header for block 0x0000:

[2016-05-08 08:24:48,086] chirp.ui.common - ERROR: ----------------
[2016-05-08 08:24:48,086] chirp.ui.clone - ERROR: Clone failed: Invalid header for block 0x0000:
[2016-05-08 08:24:48,087] chirp.ui.clone - DEBUG: Clone thread ended
[2016-05-08 08:24:48,087] chirp.ui.reporting - DEBUG: Reporting model usage: BTECH_UV-2501+220,download,True
[2016-05-08 08:24:48,089] chirp.ui.reporting - DEBUG: Reporting exception
[2016-05-08 08:24:48,089] chirp.ui.inputdialog - ERROR: --- Exception Dialog: Invalid header for block 0x0000: ---
[2016-05-08 08:24:48,089] chirp.ui.inputdialog - ERROR: None

[2016-05-08 08:24:48,089] chirp.ui.inputdialog - ERROR: ----------------------------


Related issues 1 (0 open1 closed)

Related to Bug #3993: Error when downloading from QYT KT-8900RClosedPavel Milanes09/05/2016

Actions
Actions #1

Updated by Jim Unroe over 8 years ago

  • Status changed from New to Feedback

This is still a work in progress. I have to try several times (usually 3 or 4 does it) to get a successful download with Linux Mint 17.3.

Jim

Actions #2

Updated by Jim MacKenzie over 8 years ago

I've tried several times (about 15) on two different USB ports on the machine (under Linux) with the same result.

Windows, on the other hand, has been fine every time (3 reads, two writes). So (so far at least) I have 100% consistency.

Actions #3

Updated by Pavel Milanes over 8 years ago

We have possibly found a solution, please take a peek here http://chirp.danplanet.com/issues/3993#note-12 and comment about your results.

73 Pavel CO7WT

Actions #4

Updated by Pavel Milanes about 8 years ago

  • Status changed from Feedback to Resolved

This bug was solved a time ago by Michael Wagner, see issue #3993

73 Pavel CO7WT.

Actions #5

Updated by Pavel Milanes over 7 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF