Could you apply that same small patch to 5765 and send a trace log from there 
doing the same thing you did here.  At least PTT is being set off now before 
the freq change.

If 5765 still works then perhaps the difference will tell us something.

 

What I see right now is that it looks like sending RX followed by ID; is not 
good.  But I have no idea why that should expose itself between changes in 
WSJT-X.

 

So the two other things to try in hamlib:

 

#1 Put a usleep(500000) in kenwood.c like this:

int kenwood_set_ptt(RIG *rig, vfo_t vfo, ptt_t ptt)

{

  const char *ptt_cmd;

  int ret=0;

 

  rig_debug(RIG_DEBUG_VERBOSE, "%s called\n", __func__);

 

  if (!rig)

    return -RIG_EINVAL;

 

  switch (ptt) {

    case RIG_PTT_ON:      ptt_cmd = "TX"; break;

    case RIG_PTT_ON_MIC:  ptt_cmd = "TX0"; break;

    case RIG_PTT_ON_DATA: ptt_cmd = "TX1"; break;

    case RIG_PTT_OFF: ptt_cmd = "RX"; break;

    default: return -RIG_EINVAL;

  }

  ret  =  kenwood_transaction(rig, ptt_cmd, NULL, 0);

  usleep(500000);

  return ret;

}

 

Half a second is kind of long but that will ensure plenty of "rest time" if 
that's what it needs.

 

The other thing to try is ignore the ?; return to see if things can continue 
anyways

Inside kenwood_transaction change the end of the "case '?':" section  to this:

      retval = RIG_OK;

      goto transaction_quit;

 

Again…no idea why this should be broken now but it addresses the error you're 
seeing.

 

And one other thought…we should assume the ?; means the rig is busy doing 
something since the command is valid…so perhaps a sleep after any ?; would be 
appropriate

So that test would be the same as above but slightly different:

      retval = RIG_ERJCTED;

      usleep(500000); // big sleep again

      goto transaction_quit;

 

 

Mike W9MDB

 

From: Steven Franke [mailto:[email protected]] 
Sent: Friday, July 10, 2015 6:04 PM
To: WSJT software development
Subject: Re: [wsjt-devel] FW: r5700

 

Hi Mike,

 

The trace is here:

https://dl.dropboxusercontent.com/u/33211132/WSJT-X_trace_6.log

 

This is your patch running on top of r5700. Bill’s patch has not been installed.

 

There are two complete sessions in the trace file. In each case, I started the 
program and immediately pressed Tx Enable. Bandhopping is enabled. If we define 
0:00 to be the start of the first full receive cycle, then at some time near 
1:54 the Tx Enable button goes from red to white. Further, the rig and the 
program fail to hop, i.e. the rig fails to hop to a new frequency. 

 

The error events can be found in the log at 22:41:54 and 22:47:54.

 

I’lll note that there is always a long string of errors produced during the 
shutdown phase after I use Quit to end the program.  The trace file includes 
two examples of this as well.

 

Steve k9an

 

On Jul 10, 2015, at 9:13 PM, Michael Black <[email protected]> wrote:

 

Can you send a trace log?  I can't imagine how this one line could cause any 
problems.

 

From: Steven Franke [ <mailto:[email protected]> 
mailto:[email protected]] 
Sent: Friday, July 10, 2015 2:56 PM
To: WSJT software development
Subject: Re: [wsjt-devel] FW: r5700

 

I should have said “on a clean r5700…”. 

 

On Jul 10, 2015, at 7:52 PM, Steven Franke < <mailto:[email protected]> 
[email protected]> wrote:

 

Mike,

 

I just tried your patch on a clean r5712. I never got to the transmit phase, as 
I now get a critical hamlib error at 1:54 at the end of the receive cycle, 
which kills Tx Enable… Once Tx Enable is disabled by the error, I cannot be 
re-enabled. I did not do a detailed trace, but the bottom line is that this is 
not solution.

 

Steve

 

 

On Jul 10, 2015, at 3:10 PM, Michael Black < <mailto:[email protected]> 
[email protected]> wrote:

 

OK…this WSPR patch is a hack…but I believe this will solve the TS-480 problem.  
The real solution is to only call WSPR_scheduling once instead of twice and 
only do it after ptt is turned off.

For this hack simply ensure ptt=false before calling WSPR_scheduling.

This should at least confirm that this is the problem being experienced on rigs 
that can't change frequency while transmitting.

 

In mainwindow.cpp

 

@@ -1858,6 +1863,7 @@

       m_btxok=false;

     }

     if(m_ntr) {

+      Q_EMIT m_config.transceiver_ptt (false);      //Lower PTT just in case 
we're transmitting

       WSPR_scheduling ();

       m_ntr=0;                                //This WSPR Rx sequence is 
complete

     }

 

73

Mike W9MDB

------------------------------------------------------------------------------
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/_______________________________________________> 
https://www.gigenetcloud.com/_______________________________________________
wsjt-devel mailing list
 <mailto:[email protected]> [email protected]
 <https://lists.sourceforge.net/lists/listinfo/wsjt-devel> 
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/_______________________________________________> 
https://www.gigenetcloud.com/_______________________________________________
wsjt-devel mailing list
 <mailto:[email protected]> [email protected]
 <https://lists.sourceforge.net/lists/listinfo/wsjt-devel> 
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/_______________________________________________> 
https://www.gigenetcloud.com/_______________________________________________
wsjt-devel mailing list
 <mailto:[email protected]> [email protected]
 <https://lists.sourceforge.net/lists/listinfo/wsjt-devel> 
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to