Should contest rules allow and act upon 599K QRM reports?

Thursday, 5 February 2009

IOTA 2009. Shared serial number pool with Wintest

MM3T will be multi-op for the first time with myself and Simon M0GBK taking up the challenge for IOTA 09. We're off to the isle of Skye this time, but will still be EU-8 for the benifit of SCP files out there. We will have 2 stations operational for 24 hrs and will be operating all bands on both SSB and CW.

One station will be on mults only and the other station running for an hour, then we'll swap over. We will be using Wintest contest logging software, which can keep track of each stns contacts (RSGB requirement) and contribute both to one log (duplicated on both computers for safety). This means the stations will aquire sequential serial numbers from the same pool. The laptops will be linked via a router and if a mobile signal is possible, the cluster will be shared across the network.

The sharing of a serial number pool from Wintest presents some problems. It is possible for both stations to log the same serial number (if enter is hit on both laptops at the same time). It's also possible for the serial number to increment just before you hit enter (due to the other station finishing a contact before you). To avoid this contention for serial numbers, an operating procedure must be in place. I have found it is best to put the onus on the mult station to avoid contention as this station normally has more time to think about it:

Mult Station Operating Procedure:
Wait till the running station has just completed a contact. Dupe it while he is calling CQ, thus reserving the next serial number. This should be done quickly before the running station requires the next serial number. The cursor is then moved onto the dupe ready to edit it with the next station worked. In this way, serial numbers given out never need changed at the last minute and are guaranteed to be unique.

No comments: