Bill,
I added another v (making six of 'em) and re-ran. Looks identical to me...!
Here it is:
pi@raspberrypi:~/~wsjtx-1.7 $ rigctl-wsjtx -m 2517 -vvvvvv F 14076000 frigctl,
Hamlib 3.1~gitReport bugs to <[email protected]>
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 $
I'll start working on the trace stuff, but may take some time as I'm doing the
stay-at-home dad thing with my 3-yr old....
Jim
From: Bill Somerville <[email protected]>
To: [email protected]
Sent: Wednesday, April 13, 2016 11:49 AM
Subject: Re: [wsjt-devel] 6616 Frequency "Shift" Issue
On 13/04/2016 19:35, Jim Bennett wrote:
> 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
>
Hi Jim,
I was expecting more trace output from rigctl-wsjtx, can you try again
with another v like:
rigctl-wsjtx -m 2517 -vvvvvv F 14076000 f
The interrupted transmission will probably need the trace from WSJT-X.
Doing the instrumented build is not so hard, just run cmake-gui with one
argument which is the directory that is the build directory. Tick the
"Grouped" check box and then find the options I listed and check them.
The WSJT_HAMLIB_VERBOSE_TRACE one will not show until you have set
WSJT_HAMLIB_TRACE=ON and clicked "Configure". When they are all set
click "Configure" then "Generate" and quit then rebuild:
cmake --build <build-root> --target install -- -j2
or similar. The build will take a while as changing those options will
cause everything to recompile.
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
[email protected]
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
