Hi Lance I'll leave it others to comment on the first part of your request
It seems from your last point that you suffer a lot from 'blind calling'. This was a real problem during the early days of Superfox mode, and was overcome by code that prevents a 'hound' from transmitting at all until they have managed to decode the signal from the fox. The code for this exists already, and could perhaps be applied to Q65 pileup at some point if you felt this would at least partially alleviate your problem. In the meantime, perhaps you could ask your followers to just adopt the discipline of not calling you unless they have decoded you first, in everybody's interest. 73 Charlie DL3WDG On Tue, 19 Aug 2025 at 00:08, Lance Collister, W7GJ via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > This request is for a feature that would (I think) be primarily of use > during pileup situations during DXpeditions. So Q65 PILEUP makes it the > logical place for it. As I have been suggesting for years, it would be > EXTREMELY HELPFUL and make DXpedition operations so much more > productive, if there could be an indicator when a station is receiving > during the last receive sequence. When multiple stations are calling at > the same time (especially during common moonset windows), a lot of time > can be wasted by cycling through the list of all the callers and trying > to reply to each one to see if there happens to be any reciprocal > propagation with any of them. By the time one tries responding to 10 or > 12 callers, plus delays in running out to aim the antenna, considerable > valuable common moon time has been used up :-( I don't profess to have > any idea how the system works, but here are my suggestions from a > DXpeditioner's point of view: > > 1. In Q65 PILEUP, apparently there is some way to transmit "R" with the > callsigns and grid TX3) and for that information to be received by the > other station. > > 2. If a station could optionally turn on the feature, perhaps they could > send an * (or some other symbol or letter or number) when they receive a > yellow spike (perhaps with some adjustable threshold above the > background noise) during their previous reception period. > > 3. The DXpedition station could receive the new TX3 message with the * > (or whatever instead of the R), and know that he could reply with a > standard TX3 message and have it received by that caller. Of course, > reception of that * message should not engage the AUTO SEQUENCE. If the > caller stops receiving a yellow spike, the program would go back to > automatically sending TX2. > > The HUGE advantage would be that the DXpedition station would be able to > identify stations that have the capability for a reciprocal contact! > Today, for example, I spent a lot time replying to a number of different > stations who never received any decodes from me at all when I tried to > reply to them :-( > > MNI TNX for your kind consideration! VY 73, Lance at H40GJ > > -- > Lance Collister, W7GJ (ex WA3GPL, WA1JXN, WA1JXN/C6A, ZF2OC/ZF8, E51SIX, > 3D2LR, 5W0GJ, E6M, TX5K, KH8/W7GJ, V6M, T8GJ, VK9CGJ, VK9XGJ, C21GJ, CP1GJ, > S79GJ, TX7MB, TO7GJ, 3B9GJ, ZD9GJ, H40GJ) > P.O. Box 73 > Frenchtown, MT 59834-0073 > USA > TEL: (406) 626-5728 > QTH: DN27ub > URL: http://www.bigskyspaces.com/w7gj > Skype: lanceW7GJ > 2m DXCC #11 - 6m DXCC #815 - FFMA #7 > > Interested in 6m EME? Ask me about subscribing to the Magic Band EME > email group, or just fill in the request box at the bottom of my web > page (above)! > > > > _______________________________________________ > 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
