On 15/09/2015 16:16, Joe Taylor wrote: > Hi Bill, Hi Joe, > > Some additional info. I found that with the Radio set to Split mode, > starting WSJT-X with "Monitor off at startup" leaves the radio in Split > mode. The radio stays in SPlit mode if Monitor is clicked manually. > > If "Monitor off at startup" was unchecked at the time of previous > program exit, restarting WSJT-X immediately switches the radio out of > split mode. > > Does this make sense? Is there a good reason for the program to do this? Some of this behaviour is rig dependent so nothing is definitive.
Starting with "Monitor" disabled should not change the rig at all although there are a couple of rigs that have to be changed to obtain or be sure of their current status. Starting with "Monitor" enabled should put the rig into the correct state for receiving in the current mode, note not necessarily the correct state for transmitting i.e. the rig may not go into split mode until a Tx is initiated. This last behaviour is limited to very few rigs. One reason for leaving split mode on startup would be that the mode doesn't support split operation, WSPR for example. As far as the code outside of Configuration is concerned there should be no difference between real and fake split mode. OTOH code should not necessarily react to the reported frequency, just let it get displayed and assume it is right is the best policy. All rig feedback comes back through the two signal handlers in MainWindow handle_transceiver_update and handle_transceiver_failure. These should keep the frequency display up to date and deal with errors. Setting the WSJT_TRACE_CAT CMake option to ON should give enough debug trace to determine if any observed rig changes (or lack of them) are initiated by calls (or lack of them) to Configuration member functions or happening inside the rig control code erroneously. Calling Configuration::tranceiver_tx_frequency(0) will disable split and Configuration::transceiver_tx_frequency(<non-zero>) will enable split. The only caveat is that the rig must be "online" i.e. no rig control error has happened and not yet been handled. Sorry, not a great deal of help but if you can reproduce any anomalous behaviour with rig control tracing on, I can usually diagnose it quickly. > -- Joe 73 Bill G4WJS. > > On 9/15/2015 10:47 AM, Joe Taylor wrote: >> Hi Bill, >> >> As you may have noticed, I'm having a devil of a time getting the >> "CQ nnn ..." messaging to work properly. I want to be sure that I >> handle split mode (either "Rig" or "Fake it") in the right way. >> >> I may have some more specific questions about the cod3e for you soon, >> when I finish formulating them. Right now, though, here's one that has >> me perplexed: >> >> I set the radio (in this case an FT-2000) to Split mode, then start >> WSJT-X. Under some startup conditions (I'm in JTMSK mode) , the program >> immediately sets the radio to non-split mode. I haven't been able to >> isolate the setting (presumably in the .ini file) that causes this. >> >> Is there a simple answer to "Under what conditions should WSJT-X switch >> the radio from Split to non-Split mode? >> >> -- Joe, K1JT ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
