Bill,
Yes, the rigctl-wsjtx command is MUCH easier than the other! :-) I did it and
pasted towards the bottom of this message is the result. I have made a
discovery no this one as I've been writing this message. If I give it an even
number for the frequency (i.e. 14076000), it looses that one Hertz and returns
14075999. If I give it an odd number (14077000) it returns the requested
frequency. Dang computers!
Another thing I'm finding is a problem with transmit on JT9 or JT65. If I click
on the Tune button, or call CQ, or answer another CQ, my transmission ends
after anywhere from 8 - 20 seconds. If I then try another transmission, I get
the following error message on the terminal output panel:
16-04-13T16:00:35.268Z: Hamlib: si570xxxusb_get_freq_by_value:
libusb_control_transfer failed: LIBUSB_ERROR_PIPE
I'm thinking that there is some correlation between these two problems, but
that's just a WAG on my part.
Here is the output from the rigctl-wsjtx command:
pi@raspberrypi:~/~wsjtx-1.7 $ rigctl-wsjtx -m 2517 -vvvvv F 14076000 frigctl,
Hamlib 3.1~gitReport bugs to <hamlib-develo...@lists.sourceforge.net>
rig:rig_init called kit: _init calledrig_register (2501)rig_register
(2502)rig_register (2506)rig_register (2508)rig_register (2514)rig_register
(2509)rig_register (2511)rig_register (2516)rig_register (2517)rig_register
(2513)rig_register (2512)rig_register (2515)rig_register (2518)rig_register
(2503)rig_register (2507)rig:rig_open called find_and_open_device: looking for
device 16c0:05dc... 04f2:0939, 046d:c52b, 0d8c:0008, 2001:f103, 16c0:05dc,
vendor >www.obdev.at< product >Peaberry SDR< -> foundsi570xxxusb_open
calledsi570xxxusb_open: detected PE0FKO-like firmwaresi570xxxusb_open: using
Xtall at 114.277 MHzOpened rig model 2517, 'Si570 Peaberry V2'Backend version:
0.2, Status: Betasi570xxxusb_set_freq_by_value: Freq=14.076000 MHz,
Real=56.304000 MHz, buf=5eba0907si570xxxusb_set_freq_by_value: Result
buf=5eba14075999rig:rig_close called rig:rig_cleanup called
pi@raspberrypi:~/~wsjtx-1.7 $
73, Jim / W6JHB
From: Bill Somerville <g4...@classdesign.com>
To: wsjt-devel@lists.sourceforge.net
Sent: Wednesday, April 13, 2016 9:29 AM
Subject: Re: [wsjt-devel] 6616 Frequency "Shift" Issue
On 13/04/2016 17:20, Bill Somerville wrote:
> You can set these using `cmake-gui <build-root>` or edit the
> CMakeCache.txt file in the build root directory. The resulting build
> will create /tmp/WSJT-X_trace.log .
Hi Jim,
there is probably an easier way to do this using the rigctl-wsjtx
program built with WSJT-X. Type the following, assuming the WSJT-X bin
directory is on the PATH or prepend the required path:
rigctl-wsjtx -m 2517 -vvvvv F 7038600 f
You may need some more command line arguments but try the above for
starters.
73
Bill
G4WJS.
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
