Bug #6631

Baofeng BF-T1 exception while reading attribute 'split'

Added by Colin Ashley 6 months ago. Updated 6 months ago.

Status:Feedback Start date:03/21/2019
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:chirp-daily
Chirp Version:daily Platform:Windows
Model affected:BF-T1

Description

[2019-03-21 21:42:57,375] chirp.ui.reporting - DEBUG: Checking for updates
[2019-03-21 21:42:57,828] chirp.ui.reporting - DEBUG: Server reports version daily-20190321 is latest
[2019-03-21 21:43:08,676] chirp.ui.mainapp - DEBUG: User selected Baofeng BF-T1 on port COM3
[2019-03-21 21:43:12,101] chirp.ui.clone - DEBUG: Clone thread started
[2019-03-21 21:43:12,249] chirp.ui.reporting - DEBUG: Reporting exception
[2019-03-21 21:43:12,249] chirp.ui.common - ERROR: -- Exception: --
[2019-03-21 21:43:12,250] chirp.ui.common - ERROR: Traceback (most recent call last):
File "chirp\ui\clone.pyo", line 256, in run
File "chirp\drivers\bf-t1.pyo", line 553, in sync_in
File "chirp\drivers\bf-t1.pyo", line 283, in _download
File "chirp\drivers\bf-t1.pyo", line 242, in _do_ident
File "chirp\drivers\bf-t1.pyo", line 214, in _start_clone_mode
File "chirp\drivers\bf-t1.pyo", line 134, in _rawrecv
RadioError: Error reading data from radio

[2019-03-21 21:43:12,250] chirp.ui.common - ERROR: ----------------
[2019-03-21 21:43:12,250] chirp.ui.clone - ERROR: Clone failed: Error reading data from radio
[2019-03-21 21:43:12,252] chirp.ui.clone - DEBUG: Clone thread ended
[2019-03-21 21:43:12,253] chirp.ui.reporting - DEBUG: Reporting model usage: Baofeng_BF-T1,download,True
[2019-03-21 21:43:12,255] chirp.ui.reporting - DEBUG: Reporting exception
[2019-03-21 21:43:12,255] chirp.ui.inputdialog - ERROR: --- Exception Dialog: Error reading data from radio ---
[2019-03-21 21:43:12,255] chirp.ui.inputdialog - ERROR: Traceback (most recent call last):
File "chirpw", line 68, in <module>
AttributeError: 'NoneType' object has no attribute 'split'

debug.log - Windows 8.1, CH340 Driver (37.6 kB) Colin Ashley, 03/21/2019 03:12 pm

History

Updated by Pavel Milanes 6 months ago

  • Status changed from New to Feedback

This looks like a interface problem...

Can you try to read the radio with your interface and the OEM software, to check that the interface is working?

73 Pavel

Also available in: Atom PDF