On 17/10/2014 17:33, Michael Black wrote:
Hi Mike,
Running r4524 with Tentec Omni VII through HRD 6.2.72.303 I'm getting
"Ham Radio Deluxe: rig doesn't support mode" every time WSJT-X transmits.
OK, that'll be because I checked in a fairly large change to deal with
some Yaesu vagaries via HRD.
If I click "retry" it does continue transmitting. Perhaps the error
message should say what mode it was trying?
It will be the mode you selected in Settings->Radio and is probably
lying given that it worked before ;)
Was running fine up to r4514 – I update almost daily as I like
bleeding edge technology J
OK, well the failure is of value because that code is in the wsjtx-1.4
branch as well and I certainly didn't intend to destabilize that!
Anything you want me to enable?
I tried turning on some flags to get a CAT trace to see what mode is
being requested but I'm not getting any additional copy info in
wsjtx_trace.log
262c262
< WSJT_HAMLIB_TRACE:BOOL=OFF
---
> WSJT_HAMLIB_TRACE:BOOL=ON
284c284
< WSJT_TRACE_CAT:BOOL=OFF
---
> WSJT_TRACE_CAT:BOOL=ON
That depends if you are running a Release configuration build or not.
The Qt debug trace is compiled away in release builds unless you set the
WSJT_QDEBUG_IN_RELEASE option. Also if you want it to go to a log file
rather than the console you also need to set WSJT_QDEBUG_TO_FILE. The
Windows console doesn't exist in Windows applications so the console
output goes to the bit bucket unless you have a debugger attached to the
process.
Either way, here is a version with trace so I can see where things have
gone wrong:
https://dl.dropboxusercontent.com/u/4192709/wsjtx-1.4.0-rc3-win32-CAT-trace.exe
The trace file location has recently changed, it is now
"%TEMP%\WSJT-X_trace.log".
P.S. I noted that the debug build does not put any of the dlls in the
install\Debug directory so the debug version wouldn't run on my target
machine. After copying all the QT debug dlls I was still unable to
run WSJT-X with "The application has requested the Runtime to
terminate in an unusual way. Please contact….." But I build it on
one machine and run it on a another. WSJT-X does run on the build
machine. I really don't want to put the build system on my radio
laptop due to the space requirements.
That is deliberate, copying around debug libraries on a development
machine was never intended, instead put the relevant paths on the PATH
environment variable when running or debugging non-Release configuration
builds.
If you want to have a package to put on a "production" machine then
either do a Release configuration build (the 'install' target generates
a completely self contained package) or better still, install NSIS and
make the 'package' target in a Release configuration and it will make a
Windows installer for you.
Mike W9MDB
73
Bill
G4WJS.
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
