Hi Joe - WSJT-X has been running for several hours now, and the day/sunset transition seemed to work just as it should.
Regarding the user_hardware issue, would it make sense to send the band and the mode as command-line arguments to user_command and put the onus on the user-supplied script to “do the right thing” when called with a particular band/mode? In many cases, the right thing to do might be “nothing”. This would allow considering the user_hardware call to be an atomic part of a band change sequence. I just noticed that if EnableTX is pressed during a “TX” interval, then transmission will start immediately. Would it be better to set a flag that would cause transmission to start at the beginning of the next TX interval rather than jumping in mid-transmission? With transmission percentage set to 40%, and hopping over 4 bands, I’ve seen the rig transmit three times in a row. Is there any limit to the number of contiguous transmissions? Finally (for tonight) - I have wide-band interference on 10m and 15m that raises the noise floor by several dB whenever the computer is polling the radio. Yes, I know that this is really my problem and not WSJT-X’s problem! — but I’ve been able to avoid fixing the noise issue until now by writing my control program to use single rigctl commands to change bands. Since there really isn’t a need to poll the rig in WSPR mode, would it be easy to turn polling off when in WSPR mode? Steve > On May 21, 2015, at 7:52 PM, Joe Taylor <j...@princeton.edu> wrote: > > Hi Steve, > > I'm just back from dinner and the movies. Bill set you right on > deleting the "Frequencies" line in the *ini file. I had thought that > those using WSPR in WSJT-X would already have dealt with this one-time > issue. > > As for calling the "user_hardware" script: as presently coded, this > happens only for automatic changes. If we decide that it should happen > also for manual changes, that should be fairly easy to do. I did not do > it, so far, because my script understands only the WSPR bands -- and > more bands are available of the manual pull-down list. > > -- Joe > > On 5/21/2015 7:44 PM, Steven Franke wrote: >> Thanks Bill! >> >> After deleting the “frequencies” line from the .INI file I now see >> the WSPR frequencies (as well as the WSJT frequencies). Now, band >> hopping appears to be working. It still looks like the user_hardware >> script is not being called after a manual band change. >> >> 73 Steve k9an > > ------------------------------------------------------------------------------ > One dashboard for servers and applications across Physical-Virtual-Cloud > Widest out-of-the-box monitoring support with 50+ applications > Performance metrics, stats and reports that give you Actionable Insights > Deep dive visibility with transaction tracing using APM Insight. > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
