On 03/09/2014 23:34, Michael Black wrote:
Hi Mike,

I can tell you it sure wasn't intermittent before. All I had to do was startup HRD Logbook and WSJT-X would pop up the error box within minutes. I duplicated the problem numerous times as I was experimenting with some fixes.

So far it hasn't died at all so I think they actually fixed it. I think the idea of their TCP not being thread safe prompted them pretty good and it was probably an easy fix.

OK, well we shall see. Hopefully they have change something.

As for the OMNI VII I'm not sure what all control we are supposed to have from WSJT-X to HRD. All that I know I use is frequency read/write as I do VOX via the Signalink USB.

So I'm not using any other cat control that I know of. I know you mentioned split operation but I've never done that. That's only for contest work, right?

No, split mode allows you to work both JT65 and JT9 in a 4kHz bandwidth despite your TX bandwidth being around 2.6kHz. It also allows WSJT-X to always generate TX tones in the 1.5 - 2kHz range thus causing any harmonics to be above the cut off frequency of your TX filter. You cannot use those with the Omni VII via HRD until they provide a means of setting split mode and setting the TX frequency like they do for many other rigs.

I'm still missing PTT and Split buttons on HRD and the wsjtx_trace.log still shows them missing from the "get buttons" list. Supposed to be on their list to fix.

Mike W9MDB

73
Bill
G4WJS.

*From:*Bill Somerville [mailto:[email protected]]
*Sent:* Wednesday, September 03, 2014 5:05 PM
*To:* [email protected]
*Subject:* Re: [wsjt-devel] TenTec Omni HRD TCP fix

On 03/09/2014 20:32, Michael Black wrote:
Hi Mike,

    HRD just released a new version 6.2.72.292 and I've been running
    it now for about 3 hours with HRD Logbook running and it hasn't
    died yet.

    So me thinkst they fixed their problem. It wasn't mentioned in the
    release notes but it was probably a two-line fix and not worth
    mentioning.

That seems surprisingly fast. I have to wonder if the defect is still there and more intermittent than we thought. I will leave the HRD command retry mechanism in place as you were definitely getting network timeout errors at one time.

So can you summarize the status with WSJT-X controlling an Omni VII via HRD please?

Have we solved all the issues that can be without HRD adding new controls to the Omni VII rig interface?

Mike W9MDB

73
Bill
G4WJS.



------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/


_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to