I've got a TS-2000 handy for testing. I'm able to get the module to load, but there's an issue with the character used for the command message separator. Looks like the Kenwood HT and mobiles use '\r' as the command separator, but the TS-2000 uses ';' as the message separator. Some of the issue appears to be in kenwood_live.py, but I haven't successfully gotten the driver to get the radio ID properly due to this issue.
Ok, I was able to get the TS-2000 to ID as ID019;, but the kenwood_live.py ID parser expects space separated. TS-2000 appears to not have space separated commands at all and depends on message definitions in their manual to determine field spacing in requests/responses. I'll need to make some edits to kenwood_live.py that first detects the type of separator in use while detecting baudrate, and modify the ID response code to handle the TS-2000 special case as well as the no space separated response.
Ok, have the radio IDing to the kenwood_live driver properly, and modified it to correctly detect the command delimiters in use at the time it detects the baud rate. There were some exceptions and cleanups to make, but I'm able to read the memory from my TS-2000 successfully. Unfortunately, I have some characters in the channel names that chirp rejects (notably '-'), so I am not yet able to successfully write the memory bank back to the radio as a test.
df19127ead