On 13/04/2016 05:49, Jim Bennett wrote: > Have a small issue that I wanted to mention. When I select a frequency > from the drop-down box, it shows me the one I selected, and then > immediately changes that to one Hertz less. For example, if I want 40 > meter WSPR2, the drop-down shows 7.038600. Within a second after > selecting it, my display in that box shows 7.038599. I believe get the > same result on each band, on WSPR2 and JT65/JT9. Always shifts me down > by one Hertz. > > I'm using Hamlib3, and the radio selected in Preferences is: AE9RB > Si570 Peaberry V2. The OS on the Raspberry Pi is Raspian Jessie. Hi Jim,
looking at the Hamlib driver for the Peaberry V2 and similar Si570 back ends there is quite a bit of math done on the registers read from the device with many opportunities for rounding errors. It would be helpful to see the trace output with the following CMake options set in a WSJT-X build: WSJT_TRACE_CAT=ON WSJT_HAMLIB_TRACE=ON WSJT_HAMLIB_VERBOSE_TRACE=ON WSJT_TRACE_CAT_POLLS=ON WSJT_QDEBUG_TO_FILE=ON if it is a release configuration build you will also need: WSJT_QDEBUG_IN_RELEASE=ON 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 . 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
