Bill, Thanks for the info. I'm an old CW op at heart, and even with a PhD in EE, I sometimes scratch my head trying to figure out why the software works the way it does.
73, Frank KF6E On Thu, Apr 25, 2019 at 9:54 AM Bill Somerville <g4...@classdesign.com> wrote: > On 25/04/2019 14:15, Frank Kirschner wrote: > > Someone wrote that the software prevented using Hound mode in the > > regular band segments. I was just demonstrating that this was not the > > case. I didn't actually transmit, since I saw no stations in Fox mode. > > Frank, > > WSJT-X tries to prevent *Fox* FT8 DXpedition mode stations from > operating on the "usual" FT8 frequencies. Clearly we cannot stop use of > Fox mode if the DX does not use CAT control. Other programs like MSHV > allow a mode similar to Fox mode on normal FT8 frequencies but AFAIK you > do not need to select WSJT-X Hound mode to work DX using that > application. This causes considerable confusion and when the so-called > multi-threaded mode on MSHV is enabled on normal FT8 frequencies it > causes QRM to other users by using more bandwidth than other stations, > but TBH that's what happens with DXpeditions anyway. WSJT-X Fox & Hound > DXpedition mode was designed to facilitate the larger DXpeditions, i.e. > in the top 100 most wanted lists and able to operate 24/7 for most of > the DXpedition operation. This warrants using a separate pre-published > frequency schedule and there using multiple QSOs in parallel is quite > acceptable for maximum throughput, thereby allowing as many users as > possible to get in the DXpedition log without having to use high gain > aerials and high power levels. > > 73 > Bill > G4WJS. > > > > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel >
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
