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 > > On Mon, Nov 10, 2014 at 8:15 AM, Bill Somerville <g4...@classdesign.com > <mailto:g4...@classdesign.com>> wrote: > > On 10/11/2014 15:54, john mcleod wrote: >> Hi Greg and Bill : > Hi All, >> >> Yes, I updated the hamrig rig numbers file with the info for the >> ic-7100, which comes to 370 from dipping into the code. >> Running directly from the cmd window results in everything working >> as it should, but from Windows, an error message >> emerges with the rigctl string - the string it complains about >> though, is correct, and if you paste it into a cmd window, it >> works fine. I guess I could try to debug it, but to see the >> problem, it probably needs a debug tool that runs at the Windows >> level. I guess I could insert printf's !!! :-) I have the MS sdk, >> so perhaps that could be persuaded to run with the wspr code. > Is there any more error information about why the rigctl command fails? > > I suspect a PATH issue, all the rigctl.exe commands are invoked > without any path so will be serviced from the current directory or > by a PATH lookup. > > Try with a rig type that is supported by hamlib v2 and see if that > gets any further, that would prove that the wrong rigctl.exe is > being invoked. > >> >> John >> N6RCD > 73 > Bill > G4WJS. >> >> > As you stated, Hamlib3 is unreleased software. I've not tested WSPR >> with >> > hamlib3 at all, though I build it allot for WSJT-X. >> > >> > I suspect, Bill or maybe some others from the HL teams, have to answer >> > your questions. >> >I'm afraid I have helped John to the extent of my knowledge already off >> >list. I don't know the internals of WSPR so I have no idea what is >> >necessary to substitute hamlib 3. I did note that there is a list on >> >hamlib rig numbers in a file that implies that it might need updating >> >but the error John described seemed to say he was passed that. >> > >> >> <snips-footer stuff> ------------------------------------------------------------------------------ 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
