How about trying a usleep in the get_if function  in kenwood.c.  And change 
your PTT back to CAT control.  If the IF command requires some "rest period" 
this should fix the double-IF problem too.


static int kenwood_get_if(RIG *rig)
{
  rig_debug(RIG_DEBUG_VERBOSE, "%s called\n", __func__);

  if (!rig)
    return -RIG_EINVAL;

  struct kenwood_priv_data *priv = rig->state.priv;
  struct kenwood_priv_caps *caps = kenwood_caps(rig);

  return kenwood_safe_transaction(rig, "IF", priv->info,
          KENWOOD_MAX_BUF_LEN, caps->if_len);
}

Change to
static int kenwood_get_if(RIG *rig)
{
  int ret;
  rig_debug(RIG_DEBUG_VERBOSE, "%s called\n", __func__);

  if (!rig)
    return -RIG_EINVAL;

  struct kenwood_priv_data *priv = rig->state.priv;
  struct kenwood_priv_caps *caps = kenwood_caps(rig);

  ret = kenwood_safe_transaction(rig, "IF", priv->info,
          KENWOOD_MAX_BUF_LEN, caps->if_len);
  usleep(100000); // perhaps increase this -- 100ms may not be enough
  return ret;
}
-----Original Message-----
From: Steven Franke [mailto:s.j.fra...@icloud.com] 
Sent: Wednesday, July 08, 2015 5:10 PM
To: WSJT software development
Subject: Re: [wsjt-devel] r5700


> On Jul 8, 2015, at 4:42 PM, Bill Somerville <g4...@classdesign.com> wrote:
> 
> On 08/07/2015 22:03, Steven Franke wrote:
>> Mike and Bill,
> Hi Steve,
>> I deleted my hamlib directory, downloaded the latest from git, 
>> changed the timeout from 200 to 1000 in ts480.c and recompiled 
>> hamlib. Then I recompiled wsjtx. Same problem - an excerpt from the 
>> trace is included below. I believe that the effect of the increased 
>> timeout is evident in the 1s interval between re-tries…
> This is something more fundamental than timing or numbers of retries. 
> Also replying to your other message about not understanding the change 
> that caused this, I don't think this is a WSJT-X change that has 
> caused this - something else has changed.

I don’t understand what you mean here Bill. Since the problem disappears when I 
go back one revision, isn’t it fair to say that a WSJT-X change has, at least, 
uncovered a problem in hamlib or the TS-480 firmware? I hadn’t updated hamlib 
when I first saw the problem, and I haven’t updated the TS-480.

> I have a hunch that it is something to do with sending two "IF;" 
> commands in succession. It is a bit tricky stopping that happening as 
> we only call Hamlib API functions and several are likely to use the "IF;"
> alone to retrieve the requested state.

> Can you try using "PTT Method" as "VOX" in WSJT-X, that should 
> eliminate one of the double invocations of the "IF;" command that is 
> likely to happen just before trying to change the rig state like changing 
> frequency.
> 

I’m running this way now, and it has now done 5 transmissions without a 
problem. So far, so good!

But why/how does this double “IF” only manifest in r5700 and not in the earlier 
revision?

Steve k9an

> ...
> 
> 73
> Bill
> G4WJS.
> 
> ----------------------------------------------------------------------
> -------- Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that 
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> _______________________________________________
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that you need 
to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to