On 26/11/2014 17:21, Michael Black wrote:
Hi Mike,
I've got the Omni VII working in None, Rig, and Fake mode now. I'm
cleaning up the code now.
OK, I assume it was as simple as turning on and testing that
set_split_vfo() function, at least that's all it should have needed.
But in testing this I noticed that if I have it in Rig mode, then
switch back to None, it doesn't take it out of split mode. Restarting
doesn't do it either. Doesn't appear to me to be a rig driver
problem. HamlibTransceiver queries the curred split mode and the
appears to use that from then on.
I would think that if you switch from rig to none that WSJT-X should
take it out of split mode at least since it puts it in split mode if
you go from None or Fake to Rig.
And should WSJT-X also set the split mode to off for None and Fake it
on startup too? Or is leaving it as-is needed for EME?
This wouldn't normally be switching around much but was just wondering
what the desired behavior might be…I'm a fan of letting the software
do it rather than fat fingering the radio.
That is all deliberate. I don't much like it myself but there were
issues with rigs that don't support split setting correctly. It is
something that needs revisiting but so far I don't have a workable
solution for all cases. It doesn't seem to have caused any complaints or
issues so far so.
P.S. your comment about radios moving to standards reminds me of one
my favorite sayings…."That's the nice thing about standards…there are
so many to choose from". I got that one from my RS232 days when
somebody would say "but it's RS232 so shouldn't it work?"
:)
Mike W9MDB
73
Bill
G4WJS.
*From:*Bill Somerville [mailto:g4...@classdesign.com]
*Sent:* Tuesday, November 25, 2014 1:27 PM
*To:* wsjt-devel@lists.sourceforge.net
*Subject:* Re: [wsjt-devel] Rig control problem with RigBlaster
On 25/11/2014 19:11, Michael Black wrote:
Hi Mike,
Also…I'll take another look at real split mode….I had started but
not finished that.
OK I was just going to check out what is needed myself.
The #if 0'ed code in set_split_vfo() looks OK to me. The only issue I
see is that in get_split_vfo() it should either leave *tx_vfo
untouched or do:
*tx_vfo = RIG_VFO_B;
I assume the Omni VII always Tx's on VFO B in split mode.
I do have issues with the use of cached rig state in the "priv"
structure, I know it was there already but everywhere I've had to deal
with hamlib backends that cache state there has been problems. It gets
out of sync with the rig if the operator changes the rig directly and
makes the backend misbehave. IMHO it is far better to re-read the
state every time, even then there is a possibility of data races but
at least they are limited.
Mike W9MDB
73
Bill
G4WJS.
*From:*Bill Somerville [mailto:g4...@classdesign.com]
*Sent:* Tuesday, November 25, 2014 12:03 PM
*To:* wsjt-devel@lists.sourceforge.net
<mailto:wsjt-devel@lists.sourceforge.net>
*Subject:* Re: [wsjt-devel] Rig control problem with RigBlaster
On 25/11/2014 17:49, Michael Black wrote:
Hi Mike,
The attached omnivii.c and the serial patch you sent me and the resulting
1.5 head version r4635 works on Windows 7, Windows 10 9879, and Bert Hyman
W0RSB reports it works for him too.
OK. We need to work up a pull request for the hamlib developers, I am
happy to do that but would like to see the changes being a bit more
generic. Looking at the code the same problems probably exist for the
other Ten-Tec back ends and the common code in tentec.c & tentec2.c
probably needs some attention rather than putting so much of the
implementation in individual rig back ends.
I'm running the latest Log4OM, JTAlert, and HRD 6 beta on Windows 10 which
I've found runs 98% of all software that I've thrown at it so far. Very
backwards compatible even on device drivers for FTDI and the Prolific 3.2
driver and such.
The only annoyance with wsjt-x on Windows 10 is the "Untested Windows
version 6.4 detected".
That is down to the qt-project.org team, they normally bump their
supported version very soon after its release. I need to revisit Qt
v5.3 on Windows as there was a problem with making deployment packages
the last time I tried it a few months back.
I may try testing a newer QT next and see if I can get that error to go away
and how it works with wsjt-x. I would think we might want to ensure the 1.5
version runs cleanly on Windows 10 without that warning message so is
upgrading QT in the plans?
See above. I have verified WSJT-X with Qt 5.3 and it seems fine apart
for the packaging issue.
I also sent this file to John Nelson G4KLA who is building a Mac version for
a guy he knows who has the Omni VII on a Mac.
So should have some confirmation for Mac in the next few days hopefully.
OK.
I'm running this in fake split mode and with CAT PTT successfully.
We need to test with real split mode too. That might need some more
enhancements to the Ten-Tec back ends as well although the key
functions seem to be supported for the Omini VII and Orion at least.
And on side note I also tested 1.5 with Omnirig and it works with the Omni
VII just fine too...had problems before that I never followed up on.
Mike W9MDB
73
Bill
G4WJS.
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
