On 07/03/2018 17:42, John Zantek wrote:

The OTA tests were a hoot, even with the hound-on-hound nonsense and the unfortunate DQRM from XE.

Did anyone collect and mention the final numbers for the foxes?  I thought N1DG said ~190 for 30M, but I sense the total 40M QSO’s may have been quite significant, since my screen was /REALLY/ scrolling during AA7A’s hour.

73 John KE7B

Hi John,

the total Fox QSO counts mentioned on PJR included many dupes, this is because the Fox mode logs a dupe when a repeated confirmation is received from a Hound. This would be ok but a defect lead to signoff messages not always being sent again by the Fox so the dupe counts were very high. I don't have exact figures but something of the order of 1/5 of the maximum possible unique QSOs for the number of Tx slots being used by the Fox. With the defect found and fixed so that Hounds that have to repeat their confirmation are very likely to get a prompt RR73 response, the throughput should increase significantly.

I would expect that with a suitable sized pileup and reasonably good behaviour, a slick Fox operator may be able to get quite close to optimal rates i.e. <slot-count> x 120 QSOs per hour. There are a few tools in the Foxes bag for pileup management that were not used such as randomized Tx frequencies (helps with DQRM), directional calls (needs thought as currently the Fox has to stop and call CQ to ask), working weak callers first, working furthest distances first, etc..


Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
wsjt-devel mailing list

Reply via email to