Project

General

Profile

Actions

Bug #10433

closed

python exception after cloning TM-D710G

Added by Zach Gray about 1 year ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
03/10/2023
Due date:
% Done:

100%

Estimated time:
Chirp Version:
next
Model affected:
TM-D710G
Platform:
MacOS
I read the instructions above:

Description

using latest build of chirp (from today!) as well as a previous build from a few days ago I get a python exception after downloading from my TMD710G

  • cable is plugged into main unit (not display)
  • Radio->Download From Radio->TM-D710G_CloneMode
  • download appears to run (radio front panel display clone mode graphic)
  • after download appears to complete radio beeps twice and returns to normal mode
  • download dialog box disappears, but I am left with a nearly blank screen with some small UI artifact in the upper left

Reviewing the developer log (attached) suggests that the download has completed but there was a python exception, possibly when trying to render a row the UI (see below)

grepping the source it looks like the implicated key is in the D710 driver and relates to 'special memories' for this device:

# Put Special memory channels after normal ones
SPECIAL_MEMORIES = {"Scan-0Lo": 1000, "Scan-0Hi": 1001,

Python exception stack:
Traceback (most recent call last):
File "chirp/wxui/main.py", line 1174, in menu_download
File "chirp/wxui/main.py", line 132, in __init
_
File "chirp/wxui/memedit.py", line 774, in refresh
File "chirp/wxui/memedit.py", line 710, in refresh_memory
File "chirp/wxui/common.py", line 192, in do_radio
File "chirp/wxui/memedit.py", line 706, in get_cb
File "chirp/wxui/common.py", line 192, in do_radio
File "chirp/wxui/memedit.py", line 689, in extra_cb
File "chirp/wxui/memedit.py", line 623, in _refresh_memory
File "chirp/wxui/memedit.py", line 612, in mem2row
KeyError: 'Scan-0Lo'


Files

tmd710.py (74.2 KB) tmd710.py Dan Smith, 03/10/2023 05:44 AM
Actions #1

Updated by Dan Smith about 1 year ago

  • Status changed from New to In Progress
  • Assignee set to Dan Smith
  • Target version set to chirp-py3

Yeah, confirmed here, I'll look at this tomorrow.

Actions #2

Updated by Dan Smith about 1 year ago

Actually, this was easy, a long-latent issue in that driver that became relevant recently. Here's the module you can load via LoadingTestModules but it'll be in tomorrow's build regardless.

Actions #3

Updated by Dan Smith about 1 year ago

  • Status changed from In Progress to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF