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
