Loading ...
Sorry, an error occurred while loading the content.

2821Re: [V4Protocol] V4 1.0.3 bug -- TS-590S memory frequencies not read

Expand Messages
  • Rick Muething
    Jun 19, 2012
      Its almost NEVER as simple as a one variable change!   Reading the displayed memory value using “FA”  breaks the existing and asked for features of Click to tune and following the Tuning knob.  It also makes the frequency readout function require a different command and parsing than all other Kenwood models.
      The only way I can see is offering the user a more complex optional setup that ends up being unique for the TS-590S.
      You can make everything work now as-is with one additional button push on the TS-590S   “M>V”  after you recall a saved memory.
      See my explanation to Ian.
      Sent: Tuesday, June 19, 2012 11:05 AM
      Subject: Re: [V4Protocol] V4 1.0.3 bug -- TS-590S memory frequencies not read

      That is the best explanation of a problem and the solution I have heard in the past 15 years! Perhaps ever! It should be a simple fix, also. Hopefully, only one variable has to be changed in the code.

      Way to go!
      Stan Kozlowitz



      From: Ian Wade G3NRW <g3nrw-radio@...>
      To: V4Protocol@yahoogroups.com
      Sent: Tuesday, June 19, 2012 8:48 AM
      Subject: [V4Protocol] V4 1.0.3 bug -- TS-590S memory frequencies not read
      Hi Rick

      I have just been trying 1.0.3 with the TS-590S. You're nearly there, but
      you still don't get the T-shirt.

      Recall that earlier this year I reported that V4 does not always read
      the TS-590S display frequency. Yes, it does read the radio's frequency
      *if you are not using a memory channel*, but if you set the frequency
      from a memory channel, V4 does not recognize this.

      Well, the bug is still there in 1.0.3. As I mentioned before, this is
      because you are incorrectly reading the *VFO-A* frequency, with the
      "FA;" CAT command. When you select a TS-590S memory channel, the radio's
      *display* frequency will change, but the *VFO-A* frequency does not.

      Instead, you should be using the "IF;" command to read the radio's
      display frequency, not the "FA;" command. Then V4 will always be in step
      with the radio.

      See how Simon's HRD does it -- it uses "IF;" not "FA;" to get the
      display frequency, and it works fine with memory and non-memory channels

      As I said before, V4 needs to display and log the frequency that is
      *actually* in use by the radio, regardless of whether it is a memory
      channel or not.

      Ian, G3NRW

    • Show all 8 messages in this topic