On 06/06/2015 01:33, Joe Taylor wrote: > Hi all, Hi Joe, ...
> I suspect the reason I lost "Tx Enable" last night may be related to the > occasional Hamlib error messages I'm seeing. For example, my qDebug() > output for the past few minutes looks like this: ... > scheduled: "7.038รก600 MHz (40m)" > hop data: period: "Sunset grayline" frequencies index: 5 tune: true tx: > false > Hamlib: kenwood_transaction: Unknown command or rig busy 'FA00007038614' > Hamlib: kenwood_transaction: Retrying shortly Is 40m a band where your auto ATU has to do some work? I suspect that the TS-2000 goes busy on the CAT port while it is tuning. It may be that Hamlib needs to allow for even more retries than it currently does when recovering from this condition. There is a similar situation with older Kenwoods like the TS-440 which goes busy while it generates the audio CW id on mode changes :( > Usually it recovers on the retry, but perhaps not always? A hard rig control error would result in cancelling auto Tx but it should leave a message box on the screen. > > The Hamlib problems are exacerbated when I try to run my > bare-bones-and-incomplete Echo mode. The test cycle with Doppler > corrections enabled means retuning the radio twice every 6 seconds. > Even at 57600 baud, the TS-2000 too often fails to get a message. I would like to see the Hamlib trace from that. Retuning twice in 6 seconds should be no problem at all, there is something going wrong other than timing and CAT baud rates. > > I may need to rethink how I'm doing this ... > > -- Joe, K1JT 73 Bill G4WJS. ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
