On 26/07/2014 03:09, Thomas Early wrote: Hi Tom, > On 07/25/2014 01:23 PM, Bill Somerville wrote: >> Note that you must select "CAT" as a PTT method for any of this to >> work. If the change I made and this information doesn't get you up and >> running Tom; I can give you some further information on how to debug >> the CAT connection and see what is being sent to the rig. > Thanks Bill, I now have persistence of the Audio Source, but I still > have a live mic on "Test PTT". I can even select the Data/Pkt mode and > it will turn on the 590s DATA mode, but the mic is still live on PTT and > this suggest that wsjtx is sending TX0 instead of TX1. Can you tell me > how to see what's being sent to the 590s? Oh! Sorry this is getting so extended, clearly there is still a further defect lurking somewhere.
OK, you need to set some CMake options and rebuild of WSJT-X. This can be done with a release build or you can make a debug configuration. I think that the release build version should be OK for now. To set CMake options the simplest way is to use the cmake-gui program. This may not be installed on your system, you can get it by using 'sudo apt-get cmake-qt-gui'. Once you have the tool installed you run it with a single argument which is the path to your build tree, something like: cmake-gui ~/build/wsjtx/Release I like to use it in grouped mode, to get that check the "Grouped" check box to get that. The options you will need to set are: WSJT_QDEBUG_TO_FILE WSJT_QDEBUG_IN_RELEASE WSJT_TRACE_CAT WSJT_HAMLIB_TRACE These are all boolean options which you can set by checking each associated check box. These will turn on diagnostic tracing and all CAT and Hamlib diagnostics. The trace output will go into a file called 'wstx_trace.log' in the same directory as the wsjtx executable. You then need to click the "Configure" and "Generate" buttons to reconfigure the build area and rebuild the application by running the CMake build command again. I'm not sure if the JTSDK has an option to do a minimal rebuild, you don't want to do a complete build tree construction from scratch as that will lose the option changes just made above. The simplest option may be to just use the raw CMake build command directly which is something like: cmake --build ~/build/wsjtx/Release --target install -- -kj the path to your build tree, again, may be different on your system. Once you have the diagnostic version of WSJT-X you then run it taking the actions that demonstrate the issue and exit. Try and do this reasonably quickly and with as few steps as possible otherwise the trace file may become very large. The trace file is relatively self explanatory but feel free to send it to me directly if you want a quick diagnosis. > > Thanks again! > > Tom AC2IE 73 Bill G4WJS. ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
