On 8/27/21 10:06 AM, Saku via wsjt-devel wrote:
Hi Saku & all,
I have noticed a similar problem when using a GPS mouse as time source
for ntpd. The source of the problem is gpsd, especially when using the
"-n" command line flag, which is necessary here, although this
information is not included in the man page.
The solution was to set the "gpsd.service" as disabled with systemctl:
systemctl disable gpsd.service
At next, I have inserted the following line in
/etc/udev/rules.d/99-hamlib.rules:
SUBSYSTEM=="tty", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60",
ATTRS{serial}=="IC-7300 [0-9]*", TEST!="/dev/rigA", SYMLINK+="rigA"
Now, the IC-7300 appears as /dev/rigA. This was necessary because the
GPS mouse includes the same chip.
Finally, I have created a file "/etc/modprobe.d/my-local.conf" with:
alias pps-ldisc /dev/null
alias tty-ldisc-18 /dev/null
in order to avoid that gpsd try to use any tty device as PPS device.
When beginning, I plug in the XCVR and the GPS mouse on the USB sockets.
Then I start rigctld on /dev/rigA. Then gpsd "systemctl start
gpsd.service". I verify that gpsd is receiving data from the mouse
"gpsmon". After some delay, I verify that ntpd is using the signal from
gpsd via the shared memory: "ntpq -4p 127.0.0.1". Then I can start wsjtx.
Perhaps you have a similar interference with gpsd.
Best wishes,
Claude (DJ0OT)
Now during few days I have noticed that calling cq with FT4 causes PTT
to stay on during RX period. Nearly to end of it. Then small RX gap and
TX starts again to next TX period (at proper time).
This happens at random times after started CQ calling.
When this starts to happen it may also cause error that rig is not
responding. But not always. On other times it may just blink once the
"green dot" besides band selector to yellow and back to green.
After some time of calling cq with these problems TX enable drops away,
no errors, and no receiving any more. Waterfall stays blank while
stations can be heard from speaker I.E. there is traffic.
Stopping and starting WSJTx does not help for long. If PTT problem has
happened it soon continues after program restart. Rebooting PC helps and
gives longer time until the PTT again stays on.
This does not happen with FT8.
It is a random problem, and so hard to reproduce but has happened now
daily when I have started to use FT4 again with these versions of WSJTX
and Hamlib.
I may also be a rigctld problem, it is not the very latest from Git.
Anyway it causes WSJTX to be unstable.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
