Joe - I have it running here now. I’m having a couple of problems: 1. I am not seeing the WSPR frequencies in the Frequencies tab or in the Dropdown menu on the GUI. Do I need to enter these manually somewhere? Perhaps this will explain the next two issues:
2. I can control the radio (TS-480) ok, but I am not getting any rig frequency changes with band-hopping selected. From the sound of my external antenna switch, the user_hardware script is being called according to the requested hopping schedule, but the rig frequency is not changing. 3. If I select a new band from the drop-down menu, then the rig is properly tuned to that band (but not to the WSPR frequency for that band) but in that case the user_hardware script is not called. Thanks in advance for any suggestions, Steve k9an > On May 21, 2015, at 2:06 PM, Joe Taylor <j...@princeton.edu> wrote: > > Hi all, > > WSJT-X v1.6.1 now includes a "Band Hopping" capability for WSPR mode. > It's basically similar to that in the older, Python-based WSPR, but in > addition it allows different choices of active bands for four daily > periods: Sunrise Grayline, Day, Sunset Grayline, and Night. > > You can set up the desired bands on the main window's "Tab 4". Here's > the setup I'm using at present: > > Sunrise: 160 80 40 30 20 > Day: 30 20 17 15 > Sunset: 160 80 40 30 20 > Night: 160 80 40 30 20 > > Tune: 80 60 40 30 17 12 > Duration: 60 > > The first four lines list the bands selected for each of the four daily > periods. > > The "Tune" entries list the bands that require a brief (2.5 s long) > tuneup transmission, so that an automatic ATU can retune a multi-band > antenna. The tuning signal will be emitted during the last few seconds > before the start of a WSPR sequence on one of the listed bands. > > Band-switching is effected by using the standard WSJT-X rig-control > features. The program knows the standard WSPR frequencies on the bands > from 160 through 10 meters. > > Depending on your station and antenna setup, band changes might require > other switching besides retuning your radio. To make this possible in an > automated way, whenever WSJT-X executes a successful band-change command > to a CAT-controlled radio in WSPR mode, it looks for a file named > "user_hardware.bat", "user_hardware.cmd", "user_hardware.exe", or > "user_hardware" in the same directory as wsjtx[.exe]. If one of these > files is found, WSJT-X tries to execute it, passing the band as a single > argument. For example, > > user_hardware.cmd 40 > > for a switch to 40 meters. You will need to write your own program, > script, or batch file to do the necessary switching at your station. I > wrote a simple Python program for this purpose. > > The band-hopping algorithm is as follows. Starting at the top of a UTC > hour, the "designated band" for each 2-minute WSPR interval goes through > a sequence as follows > > Band (m) 160 80 60 40 30 20 17 15 12 10 > -------------------------------------------------- > UTC Minute 00 02 04 06 08 10 12 14 16 18 > 20 22 24 26 28 30 32 34 36 38 > 40 42 44 46 48 50 52 54 56 58 > > Thus, each band is visited 3 times per hour if all 10 bands are active. > If a designated band is not in the active list for the current time of > day, the program makes a random choice among the specified active bands. > Unless there is no other available choice, the same band will not be > selected for two consecutive WSPR sequences. > > Since the setup for WSPR mode is rather different that that for JT65, > JT9, and JT4 I find it convenient to run WSPR mode with the command > > wsjtx -r WSPR > > The WSPR settings will then be kept separate from your normal WSJT-X > settings. Those remain available by starting the program in the usual > way, e.g., > > wsjtx > > at the command prompt (or double-clicking on a WSJT-X screen icon). > > For those interested, I posted two WSPR-mode screen shots at: > > http://www.physics.princeton.edu/pulsar/K1JT/WSPR_Main_Window.png > http://www.physics.princeton.edu/pulsar/K1JT/WSPR_Wide_Graph.png > > There are probably some new bugs in the program, and in various ways it > could use some cleaning up in both code and appearance. However, it > seems to be very usable now (as of revision 5414). Suggested > improvements will be very welcome! > > -- 73, Joe, K1JT > > ------------------------------------------------------------------------------ > 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
