Discussion:
Issue and Fix for USB Rig Control for fldigi with Kenwood TS-590
Richard Kriss aa5vu-fOdFMYwuEsI@public.gmane.org [linuxham]
2014-08-29 12:01:57 UTC
Permalink
I posted the following on 27-Aug in hopes someone would respond on the correct procedure to reset the TS-590’s USB sound card chipset. I managed to do it and it worked but I would like to know if there is a better way. I could not find anything TS-590S Users Manual on this but did not check the Service Manual.

73 Dick AA5VU

Subject: Issue and Fix for USB Rig Control for fldigi with Kenwood TS-590S
Posted by: "Richard Kriss" aa5vu-***@public.gmane.org aa5vu
Date: Wed Aug 27, 2014 10:49 am ((PDT))

A few weeks ago I was trying to help a new TS-590S user with fldigi rig control settings. His RigCAT configuration and TS-590S Setting were correct but each time he started fldigi he had no rig control. We messed around with all sorts of things and finally got it working.

This morning I worked the W1AW/1 (ME) on 18 MHz but when checked the log it showed the QSO logged 21 MHz. I did a double-check of fldigi and it was stuck on 21 MHz. I knew something was wrong when the fldigi rig frequency was no longer labeled as RigCAT - TS-590S. I did the normal RigCAT Initialize, save config, restarted fldigi and still had no rig control. I then remembered reading something posted on the TS-590S reflector about resetting the USB port to the sound card chipset in the TS-590S.

Cycling the TS-590S ON and OFF does not reset the chipset. To reset the chipset you have to first turn OFF the TS-590, then turn OFF the Power Supply, and wait a few seconds before turning on the Power Supply. I may have over-killed but I cycled the Power Supply On and Off first, then turned the TS-590S OFF and then cycled the Power Supply with delay between the OFF and ON. Bingo on the first fldigi restart…. I had rig control again.

Keep this tip in mind the next time you lose fldigi Rig Control. The USB port to the sound card chipset on the TS-590S seemed to be the problem child. A simple reset fixed it.

73 Dick AA5VU

Loading...