Jump to content
  • 0

Odd TK-840 programming issue



Hello all,


(I posted this to Radio Reference too, today. I'll also cross-post the solution for folks.)

This has to be a common problem, as all four of my 840s exhibit this issue.

I have a set of frequencies ("groups) set up in KPG-25D in two "systems". Software is working great in DosBox. (Need to donate to those guys!) See the attachments.

Problem comes in after I push this config to the radios. The issue isn't in the KPG-25D software, that I can tell, since the config is fine, and it writes to the radios without any issues. The problem shows up when I'm flipping through the "groups" in the TK-840 itself. Once I get up to #12, the TA icon shows up. Everything above entry 11 turns into "Talk about" and doesn't keep the QT/DQT settings. System 2 groups (aka, the second set of frequencies programmed into the interface) don't have any QT/DQT config in the radio...they're all TA.

I looked in all the options and nothing seems obvious, like a "ignore QT/DQT decode and encode after entry 11", but maybe there's something else that is a little less obvious?

I've also tried reducing the number of entries and changing the radio model to Sp, just to see. No differences in the radio behavior.

Any help would be greatly appreciated.




Link to comment
Share on other sites

6 answers to this question

Recommended Posts

  • 0

Ah ha!!! Problem solved!


I had thought, incorrectly, that TA, aka Talk About, is Kenwood's way of saying "no PL", or QT/DQT.


I just checked my programming. I fat fingered the transmit frequency on one of the entries. TA is just Kenwood speak for "simplex". 


I feel a little dumb and humbled, but you learn something every day, right?


Thanks guys for jumping in to help!


Link to comment
Share on other sites

  • 0

EDIT:  Before all that stuff below, try setting the program to just encode, not encode and decode.  The radio may not like the tone squelch combo, even though its a programing option.



That's odd.  Its been a long time since I have used one.  I may be thinking of another model, but IIRC, TA is something that typically has to be manually selected and it is selected on the per group basis.  If you press and hold the the AUX button (or scan. don't remember), and then power on the unit, that puts the radio in FPP mode.  From there you can scan through the menu options to enable or disable TA on a specific group.


If that doesn't help, I would see if you can find someone with a working radio and clone their unit to yours.  From there, make a backup copy on your computer and then try to mod the image again.


Also, what version of Windows are you using?  That software was created for DOS and DOS hasn't existed since 1995.  If you have Windows 7 or older, you can make a dual-boot computer with DOS 6.0 or 6.1.  The command prompt on anything newer than Windows 95a is not true DOS, but rather it emulates DOS.  You may be having a timeout issue while programing it due to the emulator timing out.  I have the same issue on one of my radios.  If I upload the configs once, it fails to set everything.  However, if I upload it 2 or 3 times back to back, it works fine. 


The reasoning behind it is the radio is taking to long to send the kill command, indicating to the software that the programing is done, so the software times out.  When you do multiple writes, one after the other, the second and third attempts don't have to do anything but verify the settings are already present.  If no change is needed, it keeps going and eventually finishes.  The only caveat is, you have to keep it in the programing mode.  If you reset the radio and then try to flash it again, its the same as starting from scratch, and it won't work.


I am a computer systems engineer with over 30 years of experience.  I have been specializing in Microsoft operating systems since 1991.  To this day, I have not figured out how to change the TTL in the CMD DOS emulator... so I just put up with it.


I hope this helps.  If it doesn't, I hope someone is able to get you the support you need.  Looking forward to your follow-up.  Good luck!

Link to comment
Share on other sites

  • 0

Also, what version of Windows are you using?  That software was created for DOS and DOS hasn't existed since 1995.


He said he was running DOSBox.  If you're not familiar with it, see:





It is VERY good emulator software.  I have not had problems, but that is not to say that this particular bug might not exist.  I don't even try to use the built-in to Windows DOS "Command Prompt" boxes anymore, unless I am trying to command something in Windows.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...

Important Information

By using this site, you agree to our Terms of Use and Guidelines.