Project

General

Profile

Actions

New Model #2627

closed

Kenwood TS-590

Added by Bas Heijermans over 9 years ago. Updated about 5 years ago.

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

0%

Estimated time:
Equipment Loan/Gift Offered:
No
I read the instructions above:

Description

Hi there,

I changed the Kenwood-live code a bit to accept the TS-590 (ID021) instead of TS_2000 (ID019).
It can read 1 memory channel, I'm unable to read/configure more.

However it does program it when I check it.

Maybe you can add it to the support list? As the TS-2000 and TS-590 are basically the same except the TS-590 doesn't go above 52MHz.

Code I changed/used to read the radio

            # TS-2000
            if "ID019" == resp:
                LAST_BAUD = i
                return "TS-2000"

            # TS-590
            if "ID021" == resp:
                LAST_BAUD = i
                return "TS-2000"

Thanks,

Bas - ON2HB


Related issues 2 (0 open2 closed)

Has duplicate New Model #2863: Kenwood TS-590Closed09/18/2015

Actions
Is duplicate of New Model #895: Kenwood TS-590sClosedDerek Kozel05/31/2013

Actions
Actions #1

Updated by Bas Heijermans over 9 years ago

Correction, it can program all memories but they have to be programmed in the TS-590 first, after that Chirp can take over and program them all.
If you don't do that they will show error and can't be set.

Actions #2

Updated by Tom Hayward over 9 years ago

  • Status changed from New to Feedback

Most of the Kenwood are very similar, so this doesn't surprise me. Keep working on it and when you have a way to flawlessly read and write channels, we will add it to Chirp.

Actions #3

Updated by Bas Heijermans over 9 years ago

I'm sorry I'm not a programmer, just saw the ID in the log as being unknown then searched for the file that contained it and added a bit to get it recognised.
The programming of the memory works without problems once the memory has been programmed before.
It only reads and writes previous programmed memory channels, however, it does work fine.
So if people programmed the memory before, no matter what it contains, Chirp will work fine.

The log is showing this when a memory isn't programmed previously:

[2015-06-03 17:46:43,877] chirp.drivers.kenwood_live - DEBUG: PC->RADIO: MR0008;
[2015-06-03 17:46:43,987] chirp.drivers.kenwood_live - DEBUG: RADIO->PC: MR0 0800000000000000000000000000000000000;
[2015-06-03 17:46:43,987] chirp.ui.common - ERROR: Exception running RadioJob: `?' is not in valid list: ['WFM', 'FM', 'NFM', 'AM', 'NAM', 'DV', 'USB', 'LSB', $
[2015-06-03 17:46:43,988] chirp.ui.reporting - DEBUG: Throttling...
[2015-06-03 17:46:43,988] chirp.ui.common - ERROR: -- Exception: --
[2015-06-03 17:46:43,988] chirp.ui.common - ERROR: Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.7/chirp/ui/common.py", line 116, in _execute
    result = func(*self.args, **self.kwargs)
  File "/usr/lib/pymodules/python2.7/chirp/drivers/ts2000.py", line 111, in get_memory
    mem = self._parse_mem_spec(result)
  File "/usr/lib/pymodules/python2.7/chirp/drivers/ts2000.py", line 147, in _parse_mem_spec
    mem.mode = TS2000_MODES[int(_p5)]
  File "/usr/lib/pymodules/python2.7/chirp/chirp_common.py", line 333, in __setattr__
    (val, self._valid_map[name]))
ValueError: `?' is not in valid list: ['WFM', 'FM', 'NFM', 'AM', 'NAM', 'DV', 'USB', 'LSB', 'CW', 'RTTY', 'DIG', 'PKT', 'NCW', 'NCWR', 'CWR', 'P25', 'Auto']

[2015-06-03 17:46:43,988] chirp.ui.common - ERROR: ----------------
[2015-06-03 17:46:43,989] chirp.ui.common - ERROR: Job Args:   (8,)
[2015-06-03 17:46:43,989] chirp.ui.common - ERROR: Job KWArgs: {}
[2015-06-03 17:46:43,989] chirp.ui.common - ERROR: Job Called from:
  File "/usr/bin/chirpw", line 145, in 
    gtk.main()
  File "/usr/lib/pymodules/python2.7/chirp/ui/mainapp.py", line 1406, in mh
    self.do_download(*args)
  File "/usr/lib/pymodules/python2.7/chirp/ui/mainapp.py", line 687, in do_download
    self.do_open_live(radio)
  File "/usr/lib/pymodules/python2.7/chirp/ui/mainapp.py", line 406, in do_open_live
    eset = editorset.EditorSet(radio, self, tempname=tempname)
  File "/usr/lib/pymodules/python2.7/chirp/ui/editorset.py", line 143, in __init__
    self._make_device_editors(device, devrthread, index)
  File "/usr/lib/pymodules/python2.7/chirp/ui/editorset.py", line 78, in _make_device_editors
    memories = memedit.MemoryEditor(devrthread)
  File "/usr/lib/pymodules/python2.7/chirp/ui/memedit.py", line 1376, in __init__
    self.prefill()
  File "/usr/lib/pymodules/python2.7/chirp/ui/memedit.py", line 1063, in prefill
    job = common.RadioJob(handler, "get_memory", i)

Looks to me it's reading the empty memories perfectly but then thinks the value is wrong.
I hope it helps you to fix it, as for the TS-590 (and simmular) Chrip would be a perfect tool to use memory.
I never used memory before as it's too hard to program with a name in it and I do not run Windows.

Thanks, Bas - ON2HB.

Actions #4

Updated by Tyler Tidman almost 9 years ago

This issue is basically a duplicate of both #895 and #2863.

I'm not sure if anything else has changed since those tickets were raised but, perhaps, you might try combining your efforts with them.

Actions #5

Updated by Tyler Tidman almost 9 years ago

  • Subject changed from TS-590 to Kenwood TS-590
Actions #6

Updated by Rick DeWitt about 5 years ago

  • Status changed from Feedback to Closed
Actions

Also available in: Atom PDF