Hi Greg :
Ok, to clarify :
The rig is actually an IC-7100, and with the new Hamlib 3 from Bill's fork,
rigctl works fine from the cmd prompt.
The problem arises when WSPR invokes rigctl when changing bands. What I see
then is that an error
comes up in the cmd window :
Error attempting to set rig frequency.
rigctl -m 370 -r COM3 -s 19200 -C data_bits=8 -C stop_bits=1 -C
serial_handshake=None F 18104600
Now there's nothing wrong with this invocation of rigctl. If you copy this
string and paste it into a cmd window, it
works fine as before. Nonetheless, when WSPR tries to do it, it doesn't
work.
It also doesn't seem to be just an IC-7100 problem. I tried the IC-7000
(which is in the current Hamlib release),
and faking out my IC-7100 to look like an IC-7000 by changing the ci-v
address to 0x70, it also works fine from the
cmd line, but fails from WSPR.
So now, back to the original problem : WSPR with hamlib 3 works fine with
the IC-7100 if WSPR is launched from a cmd prompt.
On the other hand, if you double-click on WSPR from Windows, it fails in
the way shown above. Bill and I thought it might be a
PATH issue, but this turns out not to be the case. This problem also arises
if you fit up WSPR 2.0 and WSPR 2.12 with Hamlib 3.
Could this be something to do with the different libraries between Hamlib 2
and Hamlib 3 : dynamic vs static ? All I did to get this
working at all was to copy rigctl.exe, two .dll files and
hamlib_rig_numbers into the WSPR directory.
----
On a slightly different tack, I see you mentioned that the file
hamlib_rig_numbers can be obtained by doing : rigctl -l >
hamlib_rig_numbers.
I tried this, but WSPR has problems parsing it, such that when invoking
rigctl from WSPR, it sends :
rigctl -m 3
instead of
rigctl -m 370
I edited the hamlib_rig_numbers file produced by rigctl -l, and replaced
some of the spaces with tabs, and it worked
correctly. There is more to it than that though, although I gave up at that
point :-)
Thanks for all your help !
John
N6RCD
Hi John,
This should be separated from WSPR, though it may also pass through to
WSPR, it does not appear to be a WSPR issue yet.
Until you can connect / test rigctl / rigctld (Hamlib 1.2.15.3 or v3 aka
Bills integration) with the IC-7000 from the command line, there's not
much point in running the command through WSPR, as it will try to do the
same thing you are doing manually, just through a .py script rather than
CMD Window.
You can look at the bottom of wspr.py for the commands that are set in
the Setup screen.
73's
Greg, KI7NMT
On 11/10/2014 18:35, john mcleod wrote:
> Hi Bill :
>
> rigctl fails when trying to set the frequency :
>
> Error attempting to set rig frequency.
> rigctl -m 370 -r COM3 -s 19200 -C data_bits=8 -C stop_bits=1 -C
serial_handshake=None F 18104600
>
> I thought it might be a PATH issue, but a visual check on the PATH shows
> no alternative rigctl, and indeed, if I hide the rigctl.exe from the
> WSPR directory, WSPR will then complain that rigtcl is not recognised as
> an internal, external, program or batch file.
>
> John
> N6RCD
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
