A 2-KHz shift is good because it allows overlap between segments. If 3 KHz was used there could be spectrum in between segments that would not be reachable.
On Mon, Dec 3, 2018 at 10:12 AM Bill <brightl...@gmail.com> wrote: > I'm glad that I wasn't the only one who noticed the issue with the 2 KHz > band hop. It took me a few minutes to figure out why people weren't > answering me when I tried to call them on the lower portion of the "next" > up segment. I finally realized what was going on when I copied a station on > the upper end of the lower segment then saw them again on the lower end of > the higher segment. I just ignored all decodes below 1000 on the upper > segment. I only needed to do the next segment on 20m. At times 20m was full > of signals with no room to play. It was actually nice to see the open space > on the next segment and see other people playing there too. Having a brand > new playground up 3 KHz seems nice to me. It's easy and quick to change > segments and check out activity if you have all the right frequencies > programmed into your contest configuration file. Right now our useable band > segment is close to 3 KHz so a 3 KHz jump seems to make sense. > > Bill - AK6A > > On Mon, Dec 3, 2018 at 8:27 AM Saku <oh...@sral.fi> wrote: > >> Don AA5AU kirjoitti 3.12.2018 klo 17.56: >> > I haven't put out my post-contest email yet but #1 is on my list. >> > >> > The frequencies should be 3 kHz apart instead of 2. A person >> > transmitting say at 14.132 at 500 Hz will be seen by those using a >> > dial frequency of 14.130 but if you call them using a frequency of >> > 2000 Hz or less while at 14.130, that station will not see you. >> > >> > Don AA5AU >> > >> That's why we need checkbox "answer RANDOM x 60Hz up" for contest >> modes. Where RANDOM is a random integer between 0 - 10. >> It would be better in other ways too as now it was so that several >> stations were answering at 0 at same time. Randomizing would force split >> to happen. >> >> In Ru contest there was plenty of room, but almost everyone (in EU, at >> least) was using the base as dial frequency. That must be changed at >> least when we get more sunspots back again. >> >> Using 3kHz instead of 2kHz is not good idea. Operators can "peek" to >> next dial slice (with most of rigs) if slices are just 2kHz. They just >> have to understand that answering must be 0 or UP, not DN from CQ >> frequency. >> >> But time will learn them ... >> >> -- >> Saku >> OH1KH >> >> >> >> _______________________________________________ >> 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 >
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
