Project

General

Profile

Actions

New Model #3279

closed

Kenwood TK-270 (older non G model)

Added by Pavel Milanes over 9 years ago. Updated about 9 years ago.

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

100%

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

Description

This is a request for the older portables in the Series/Family 60 from Kenwood; This will comprise the following radios:

TK-260, 270, 272, 278 (VHF part)
TK-360, 370, 372, 378 (UHF part)

I have borrowed a TK-270 from a friend and received a non functional TK-378 as a gift (CPU works ok, RX kind of "work", TX no go)

With this I hope to map the entire Family. I have figured out the comm process that is similar but different of the mobile ones (TK-760 and others) so this will be a completely different driver. Until now I have mapped 90% of the channel data, remains in TODO list:

  • Finish the mapping.
  • Hack this in hand radios to retrieve the unique ID for each model/variant for the family.
  • Watch for differences in the respective models and handle this.
  • Make the settings part.
  • Validate the driver against PEP8/Chirp's test bed.

Cheers.


Files

Kenwood_TK-270.img (1 KB) Kenwood_TK-270.img Image for the TK-270 Pavel Milanes, 02/06/2016 09:31 AM
Kenwood_TK-378.img (1 KB) Kenwood_TK-378.img Image for the TK-378 Pavel Milanes, 02/06/2016 09:31 AM
Actions #1

Updated by Pavel Milanes over 9 years ago

  • % Done changed from 40 to 70
  • Chirp Version changed from 0.4.0 to daily

Update, last night I completed the following issues:

  • Hack the in hand radios to retrieve the unique ID for each model/variant for the entire family. (Ufff... between 2 and 4 variant for each model...)
  • Make the settings part (with the most ham used ones)

In the TODO remains:

  • I have finished the mapping but there is a problem with new channels not being recognized by the radio beyond CH7, I have to investigate the issue to resolve that.
  • As for now there is no evident difference in the respective models/variants, I will keep an eye on this.
  • Validate the driver against PEP8/Chirp's test bed. (this is the last part)

Cheers.

Actions #2

Updated by Pavel Milanes over 9 years ago

  • % Done changed from 70 to 100

Good news, today I will submit the first working driver.

The problem mentioned about the CH7 and beyond is fixed, no differences was spotted on the different models/variant in the mem layout and the driver is PEP8 compatible now.

I found a bug and fix it, it was about the radio after a hardware reset, some setting appears with 0xFF and that is not a valid value for the get_settings, I make a validation for that with some default values.

Also I put in place a retry procedure for getting the radio in program mode, a lesson learned from the TK-760 one.

I build the driver with a TK-270 and a TK-378 in hand, so there can be some bugs for the other members of the family/series.

The driver is marked as experimental until it is tested to be working and no bugs found in some time.

Enjoy and report back any success/failure.

Actions #4

Updated by Pavel Milanes over 9 years ago

Bug Found!!!

I give a copy of the unreleased driver to a friend ham ho has this radios to test, and he report to me today that the TX freq of channels added or modified by chirp are not on the freq you expect.

I have to investigate this issue at night. That's I marked it as experimental.

Cheers.

Actions #5

Updated by Pavel Milanes over 9 years ago

Done, bug confirmed and fixed, a patch has been send to the devel queue.

A flag in the memmap that I miss to code properly, fixed and tested, it's working as expected now.

Wait for the next release.

Actions #6

Updated by Pavel Milanes about 9 years ago

  • Status changed from New to Resolved

Driver is in Chirp and bug found in the early development resolved.

I have good feedback here from local users about driver working ok, so set it to Resolved and later to Closed if no error arose in a prudent time lapse.

73

Actions #7

Updated by Pavel Milanes about 9 years ago

The driver is working fine, no more error reports, so I close this issue.

New problems must have it's own issue number, 73.

Actions #8

Updated by Pavel Milanes about 9 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF