I haz the dumb....
011230 -10 0.1 311 ~ WW8RT RR73; WR7Q <...> -02
011230 -12 0.1 371 ~ W8ASA RR73; VE2YTQ <...> -23
011230 -11 0.1 431 ~ K6EU RR73; KX4KU <...> -23
011230 -9 0.1 491 ~ W3SMK RR73; N0TB <...> -09
011300 -11 -0.7 311 ~ KF0QR RR73; W7PP <...> -18
011300 -13 -0.7 371 ~ ND6P RR73; VE1XZ <...> -19
011300 -12 -0.7 431 ~ KC7CS RR73; K1NE <...> -24
011300 -9 -0.7 491 ~ AK1P RR73; W7VXS <...> -14
011330 -11 0.1 311 ~ WB8ART RR73; N5INP <...> -14
011330 -12 0.1 371 ~ AA6OC RR73; VE7KW <...> -18
011330 -12 0.1 431 ~ K7RFW RR73; K4PI <...> -04
011330 -9 0.1 491 ~ K6EU RR73; KB5QR <...> +00
Shouldn't the RR73's correspond to callsigns that were given a report
in the preview sequence?
Is it due to a backlog of callers from who have been called, but from
whom a report has not yet been received?
Why is K5WE getting repeated RR73's ?
011730 -11 -0.7 372 ~ K5WE RR73; W6XK <...> +05
011830 -11 0.1 372 ~ K5WE RR73; WB3DEL <...> -15
011930 -9 0.1 492 ~ K5WE RR73; K4NAB <...> -22
012030 -10 0.1 432 ~ K5WE RR73; NX6D <...> -14
012200 -10 0.1 312 ~ K5WE RR73; N9JJ <...> -12
012230 -9 0.1 492 ~ K5WE RR73; W8TN <...> -23
Seems that someone could do a denial-of-service on the DX by
continually sending a report ;)
73,
~iain / N6ML
On Sun, Mar 4, 2018 at 3:43 PM, Joe Taylor <[email protected]> wrote:
> Hi all,
>
> I write to remind you of the public test of *FT8 DXpedition Mode* scheduled
> for March 6-7. The more participants, the better!
> The main goal is to simulate pileups in which many "Hounds" call and attempt
> to work a desirable rare DX station, the "Fox", and to maximize the
> resulting QSO rate. We hope you can be there and work each of our Foxes on
> each band.
>
> All participating stations must use program version WSJT-X v1.9.0-rc2. If
> you don't yet have it, download links are available here:
> https://physics.princeton.edu/pulsar/k1jt/wsjtx.html
>
> Detailed instructions for Fox and Hound stations are posted here:
> http://physics.princeton.edu/pulsar/k1jt/FT8_DXpedition_Mode.pdf
> It's important to read and follow these instructions carefully! Don't just
> try to wing it.
>
> Each hour during the test has a designated frequency and Fox callsign,
> "Fox_A" in the following table.
>
> Date UTC Freq Fox_A Fox_B NSlots
> -------------------------------------------
> Mar 6 2300 14.080 K1JT W7/KH7Z 3
> Mar 7 0000 10.141 W1/KH7Z K9AN 5
> Mar 7 0100 7.080 W7/KH7Z K1JT 4
> Mar 7 0200 3.585 K9AN W1/KH7Z 3
>
> As you will know after reading the FT8 DXpedition Mode User Guide, Fox can
> conduct up to "NSlots" QSOs simultaneously. W7/KH7Z will be operated by
> AA7A, and W1/KH7Z by N1DG.
>
> Fox_A will operate for the full hour if plenty of Hounds keep calling. Fox_B
> is on standby reserve. If the QSO rate for Fox_A approaches zero at the
> half-hour mark, Fox_A will stop transmitting and Fox_B will call CQ.
>
> If you (as a Hound) can legitimately use more than one callsign -- your
> spouse's call, club call, etc. -- please try to work each Fox multiple
> times. No dupe QSOs with the same call and same band, though.
>
> Real-time liaison will be available via the "Ping Jockey Relief" chat page
> (PJB), https://www.pingjockey.net/cgi-bin/pingtalkB . Everyone should
> monitor this page for possible announcements of frequency changes or
> switch-overs from Fox_A to Fox_B. To ensure that announcements from Fox
> stations are easily visible, Hounds should monitor PJB but not post messages
> there during the test.
>
> The deepest pileups will help us to tune the final-release software version
> for optimum performance on both Fox and Hound sides. After the test, please
> post any comments you feel will be helpful to one of our two email forums,
> [email protected] or [email protected] . You will
> need to be subscribed to the list in order to post there.
>
> We sincerely hope you can join us for this test, working each Fox on each
> band!
>
> -- 73, Joe, K1JT (for the WSJT Development Group)
>
> ------------------------------------------------------------------------------
> 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
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
