Hi Bill, I'm trying to trace problems documented in this previous message to the list:
https://sourceforge.net/p/wsjt/mailman/message/36701791/ I'm happy not to try and compile a debug version if you happen to have any insight there! 73 Phil W1PJE On Sat, Jul 6, 2019 at 6:54 PM Bill Somerville <g4...@classdesign.com> wrote: > On 06/07/2019 23:30, Phil Erickson wrote: > > It made a new executable in /usr/local/bin as expected, but when I ran > > it, there is no sign of the "..trace.log" file in /tmp. > > HI Phil, > > the name of the trace log file is: > > /tmp/WSJT-X_trace.log > > or if you pass a --rig-name=xxx command line argument it will be: > > "/tmp/WSJT-X - xxx_trace.log" > > What CAT problems are you trying to fix? Have you tried using rigctld > (wsjtx-rigctld built with WSJT-X), with that you can get Hamlib CAT > trace information by starting the wsjtx_rigctld daemon with a -vvvvv > option. Connect to wsjtx_rigctld by selecting "Hamlib Net rigctl" as the > rig in WSJT-X "Settings->Radio->Rig". > > 73 > Bill > G4WJS. > > > > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > -- ---- Phil Erickson phil.erick...@gmail.com
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
