Xoops | Welcome to JA5FNX's Place.

2018年8月24日

たまにはRed Pitaya Notes見てみよう。

久しぶりに見ると

　良いことを再発見するかもしれません

　https://pavel-demin.github.io/red-pitaya-notes/

田村文史郎　／　ＪＡ５ＦＮＸ　／　Ｂｕｎ

2018年7月28日

This white paper describes a number of important enhancements planned
for WSJT-X Version 2.0. Most of them involve the FT8 and MSK144
protocols, which will be upgraded to use use 77-bit information
payloads rather than the present 72 or 75 bits. This modest increase
in information content will make possible new message types that
support the following special types of QSOs and exchanged information:

1. NA VHF Contest operation with full and transparent support of grid
locators and “/R” (Rover) callsigns

2. EU VHF Contest operation with the exchange of 6-digit locators, QSO
serial numbers, and “/P” (portable) callsigns

3. ARRL Field Day operation with standard Field Day exchanges

4. ARRL RTTY Roundup operation with standard contest exchanges

5. Better and more user-friendly support for compound and nonstandard
callsigns

6. A special “telemetry” message format for exchange of arbitrary
information (up to 71 bits)

Decoding sensitivity for the new messages will be essentially the same
as for the FT8 and MSK144 modes presently in WSJT-X v1.9.1. The
existing FT8 DXpedition mode will still be supported, and a more
powerful DXpedition mode may be offered as well.

In this document we’ll call the new FT8 protocol “FT8+”. It will be a
superset of the FT8 implemented in v1.9.1, providing at least
temporary compatibility and inter-operability with older program
versions. We may decide to remove support for old-style 72- and
75-bit messages after a specified switchover interval.

In contrast, the new MSK144 protocol will replace the old one without
backward compatibility. We believe the smaller and more specialized
group of MSK144 users will upgrade quickly and not find this
restriction to be a problem.

Here are some examples of message formats that will be supported by
FT8+ and MSK144 in WSJT-X v2.0. The list is not exhaustive.
Parameters i3 and n3 (shown in column 1) are used in the software to
define major and minor 77-bit message types.

———————————————————————————-
i3.n3 Example Messages Comments
———————————————————————————-
0.0 TNX BOB 73 GL Free text
0.1 K1ABC RR73; W9XYZ -08 DXpedition Mode (sent only by Fox)
0.2 G4ABC/P R 570007 JO22DB EU VHF Contest
0.2 PA9XYZ 590003 IO91NP EU VHF Contest
0.3 K1ABC W9XYZ 6A WI ARRL Field Day
0.3 W9XYZ K1ABC R 2B EMA ARRL Field Day
0.5 123456789ABCD Telemetry (18 hex digits)
1. W9XYZ Compound call
1. W9XYZ 73
1. CQ FD K1ABC FN42
1. CQ K1ABC FN42
1. CQ TEST K1ABC FN42 NA VHF Contest (“TEST” is optional)
1. CQ TEST K1ABC/R FN42
1. K1ABC W9XYZ EN37
1. K1ABC W9XYZ -09
1. K1ABC W9XYZ R-17
1. K1ABC W9XYZ RRR
1. K1ABC W9XYZ 73
1. K1ABC W9XYZ RR73
1. K1ABC/R W9XYZ EN37
1. K1ABC W9XYZ/R RR73
1. W9XYZ -13 Nonstandard call
1. W9XYZ R+02
1. W9XYZ RRR
1. W9XYZ RR73
2. CQ G4ABC/P IO91
2. G4ABC/P PA9XYZ JO22
2. PA9XYZ G4ABC/P RR73
3. K1ABC KA0DEF 559 MO ARRL RTTY Roundup
3. K1ABC W9XYZ 579 WI ARRL RTTY Roundup
3. KA1ABC G3AAA 529 0013 ARRL RTTY Roundup
3. TU; G3AAA K1ABC R 559 MA ARRL RTTY Roundup
3. TU; KA0DEF K1ABC R 569 MA ARRL RTTY Roundup
3. W9XYZ K1ABC R 589 MA ARRL RTTY Roundup
4. CQ KH1/KH7Z Compound call
4. CQ YW18FIFA Nonstandard call
———————————————————————————-

Here are some examples of minimal QSO sequences that take advantage
(where necessary) of the new protocol capabilities. Model QSOs number
1 and 2 are supported already, with the present FT8 and MSK144
protocols, and number 3 with the existing FT8 DXpedition Mode. Model
QSOs 4-8 (and others not illustrated here) require the new protocols
with 77-bit messages.

———————————————————————————-
1. Standard QSO
———————————————————————————-
CQ K1ABC FN42
K1ABC W9XYZ EN37
W9XYZ K1ABC -11
K1ABC W9XYZ R-09
W9XYZ K1ABC RRR
K1ABC W9XYZ 73

———————————————————————————-
2. Short-cycle QSO
———————————————————————————-
CQ K1ABC FN42
K1ABC W9XYZ -09
W9XYZ K1ABC R-11
K1ABC W9XYZ RR73
W9XYZ K1ABC 73

———————————————————————————-
3. FT8 DXpedition Mode
———————————————————————————-
CQ KH1/KH7Z
KH7Z K1ABC FN42
K1ABC KH7Z -12
KH7Z K1ABC R-14
KH7Z W9XYZ EN37
… possibly other callers …
K1ABC RR73; W9XYZ -08

———————————————————————————-
4. ARRL Field Day
———————————————————————————-
CQ FD K1ABC FN42
K1ABC W9XYZ 6A WI
W9XYZ K1ABC R 2B EMA
K1ABC W9XYZ RR73

———————————————————————————-
5. ARRL VHF Contests
———————————————————————————-
CQ TEST K1ABC/R FN42
K1ABC/R W9XYZ EN37
W9XYZ K1ABC/R R FN42
K1ABC/R W9XYZ RR73

———————————————————————————-
6. ARRL RTTY Contest
———————————————————————————-
CQ TEST K1ABC FN42
K1ABC W9XYZ 579 WI
W9XYZ K1ABC R 589 MA
K1ABC W9XYZ RR73

———————————————————————————-
7. EU VHF Contest
———————————————————————————-
CQ TEST G4ABC/P IO91
G4ABC/P PA9XYZ JO22
PA9XYZ 590003 IO91NP
G4ABC/P R 570007 JO22DB
PA9XYZ G4ABC/P RR73

———————————————————————————-
8. Compound call
———————————————————————————-
CQ PJ4/K1ABC
W9XYZ
W9XYZ K1ABC -11
K1ABC W9XYZ R-09
W9XYZ RRR
W9XYZ 73
———————————————————————————-

To minimize confusion that’s likely to arise during a switchover from
v1.9.1 to v2.0, we propose to follow a well advertised schedule:

“RC1 Date” — perhaps as early as September 15, 2018?
——————————————————-

This will be the first chance for beta testers to try WSJT-X using the
77-bit messages. We may restrict this opportunity to specific
volunteer testers, and we’ll probably include an “upgrade by
xxxx_date” message to remind people that they are using a release
intended only for testing.

FT8+ will support the old (v1.9.1) protocol as well as the new message
types outlined above. To avoid QRMing legacy FT8 users with messages
they can’t decode, we’ll recommend testing FT8+ on frequencies
formerly used for JT9.

MSK144 will be fully functional between any two stations using the RC1
software, but it will not be backward compatible with earlier program
versions.

“RC2, RC3,… Date” — perhaps in October?
——————————————–

As needed, depending on results of testing.

GA Release Date — perhaps in November?
———————————————

Official General Availability release of WSJT-X v2.0.0. The original
MSK144 protocol will be declared obsolete.

For reference: Dates of relevant upcoming ARRL contests
——————————————————-
VHF QSO Party: September 8-10, 2018
RTTY Roundup: January 5-6, 2019
VHF SS: January 19-21, 2019

Our proposed schedule should make WSJT-X Version 2.0 usable for
relevant ARRL operating events in 2019.

2018年7月25日

Version 2.0 of WSJT-X.

Forwarded by Bunshiro Tamura
———————– Original Message ———————–
From: “Joe Taylor joe@Princeton.EDU [wsjtgroup]”
To: wsjtgroup@yahoogroups.com
Date: Tue, 24 Jul 2018 16:37:16 -0400
Subject: [wsjtgroup] Plans for WSJT-X Version 2.0
—-

Hi to all,

Of course we are well aware of the issues many have experienced when
using WSJT modes in North American VHF contests. To summarize, there
are two main problem areas:

– Decoding of messages with two callsigns followed by “R ” and a
4-character grid, and the related auto-sequencing, depend of proper
and coordinated setting of a checkbox at both stations.

– There is a crying need for transparent support of “/R” (Rover)
callsigns in all standard messages, during contests.

Here’s some background information aimed at relative newcomers and
casual users of WSJT, followed by a brief preview of program features we
plan to make available in Version 2.0 of WSJT-X.

Contest Mode
————

Standard JT-style messages (those used in all of the structured WSJT
modes) have 71 information bits: two 28-bit callsigns and a 15-bit grid
locator. The 15-bit field can alternatively convey a signal report
(with optional “R”), or “RRR”, “RR73”, or “73”. One additional bit
re-purposes the 71 bits to carry a 13-character free test message. In a
72-bit packet there are NO free bits available to insert “R ” before a
grid locator, or “/R” after a callsign.

The “NA VHF Contest” checkbox presently in WSJT-X is a stop-gap feature
added in 2016 to the MSK144 mode, and later to FT8. These modes
conventionally use 15-second T/R intervals and offer semi-automated
message sequencing. NA VHF contests require the exchange of 4-character
grid locators. Signal reports are OK, but not required. Contesters
wanted a way to send messages like “K1ABC W9XYZ R EN37”, thereby
increasing their QSO rates by eliminating some transmissions from the
standard minimal-QSO sequence.

Rovers
——
Rovers move from grid to grid and must append “/R” to their callsign
during the contest. These hardworking folks definitely need some help
if they are to use WSJT modes effectively.

All structured modes currently supported in WSJT-X permit messages like
these:

CQ K1ABC/R FN41
DE K1ABC/R 73

…. but you can’t use a second callsign in place of the “CQ” or “DE”.
Once again, there is no room for such information in a 72-bit packet.

Some time ago we created workarounds that enable QSOs using a “/R”
callsign or an “R+grid” message fragment. But these capabilities are
limited and necessarily somewhat clumsy. Users must understand what’s
possible and what’s not, and they must be careful about some necessary
program settings. Decoding “R+grid” messages requires ticking a
checkbox, and if someone else sends you standard signal reports you need
to uncheck the box or manually edit your messages. Also, for reasons
explained in the WSJT-X User Guide, this feature cannot work well when
world-wide propagation is possible — as it has been recently on 6 meters.

All in all, it’s not a happy situation — especially when considering
the typical presence of many casual operators who happen upon a contest
and just want to make a few QSOs.

Recently K9AN, G4WJS, and I have been developing enhanced versions of
the MSK144 and FT8 protocols that extend the message payload to 77 bits.
For a taste of what’s to come, here’s a brief list of things made
possible by the extra bits:

1. NA VHF Contest operation with full support of grid exchanges and
“/R” (Rover) callsigns

2. EU VHF Contest operation with the exchange of 6-digit grids, QSO
serial numbers, and “/P” (portable) callsigns

3. ARRL Field Day operation with standard Field Day exchanges

4. ARRL RTTY Roundup operation with standard contest exchanges

5. Better and more user-friendly support for compound and nonstandard
callsigns

6. A special “telemetry” message format for exchange of arbitrary
information up to 71 bits

7. The existing FT8 DXpedition mode will be supported, and a more
powerful DXpedition mode may be offered as well.

All of these features work seamlessly and automatically. No “contest
mode” checkboxes are needed. In most situations decoding sensitivity
will be slightly better than at present for FT8; for MSK144 it will
sometimes be about 0.5 dB worse. Occupied bandwidths will be the same
as they are now, and false-decode rates will be significantly lower.

Much of the necessary programming is finished. Many of the new features
have been tested on the air, and we find them to work well.

Don’t rush to download something — these capabilities are not yet
publicly available. There is more testing and code optimization to do.
With summer vacation plans, etc., our current plans call for a
beta-testing period probably starting in mid to late September. A full
release should then be possible a couple of months later.

In particular: we are planning to make WSJT-X Version 2.0 available in
time for you to read its new documentation and practice using it before
(for example) the ARRL RTTY Roundup, January 5-6, 2019, and the ARRL VHF
Sweepstakes, January 19-21, 2019.

THIS IS IMPORTANT: The new protocols cannot be backward compatible with
the existing ones. We will probably provide some temporary “bi-lingual”
capability for FT8, but not for MSK144. It will be essential for users
to upgrade to Version 2.0 in order to use the new features and
communicate with others who have made the upgrade.

We will provide plenty of advance notice about a transition interval and
an essential “must upgrade by” date.

— 73, Joe, K1JT

——————— Original Message Ends ——————–

2018年7月9日

雨、雨、雨

　西日本各地での豪雨で被害に見舞われた地域の皆様、心よりお見舞い申し上げます。

　僕の家の前も国道を挟んで千丈川が流れていまして生きた心地がしない数時間ではありましたが、おかげさまで何も被害もなく嵐は通り過ぎました。

　本来ならば後片付けを手伝いに行きたいし行かなければならないのですが失礼をせざるをえませんのでよろしくお願いします。

　熱中症に気をつけて頑張って後片付けしてください。

　本当に、心よりお見舞い申し上げます。

　田村文史郎／ＪＡ５ＦＮＸ／Ｂｕｎ

2018年6月7日

Building an SDR around a Red Pitaya

This page is not about a finished project, but is rather a sort of blog about a work in progress.

https://ludens.cl/Electron/SDR/redpitayasdr.html

2018年6月1日

fw:Release of WSJT-X Version 1.9.1

———- Forwarded message ———-
From: Joe Taylor
Date: 2018-05-31 22:21 GMT+09:00
Subject: [wsjt-devel] Release of WSJT-X Version 1.9.1
To: WSJT software development

WSJT-X Version 1.9.1 is now available for download. This version corrects a flaw in Version 1.9.0 that unintentionally restricted the full use of FT8 DXpedition Mode by “Fox” stations.

New features and enhancements to WSJT-X since Version 1.8.0 are summarized here:
http://physics.princeton.edu/pulsar/k1jt/New_Features_1.9.1.txt

As we have stated before, FT8 DXpedition Mode should be used only in rare-entity circumstances in which sustained QSO rates well above 100/hour are expected. Detailed instructions for FT8 DXpedition Mode can found here:
http://physics.princeton.edu/pulsar/k1jt/FT8_DXpedition_Mode.pdf

Upgrading from earlier versions of WSJT-X will be seamless; there is no need to uninstall a previous version or move any files. Please do not continue using any “release candidate” — that is, any beta release with “-rc#” in the version name.

Links to installation packages for Windows, Linux, Macintosh, and Raspbian Jessie are available here:
http://physics.princeton.edu/pulsar/k1jt/wsjtx.html

You can also download the packages from our SourceForge site:
https://sourceforge.net/projects/wsjt/files/
It may take a short time for the SourceForge site to be updated.

We hope you will enjoy using WSJT-X Version 1.9.1.

— 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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

2018年5月30日

FW:Release of WSJT-X Version 1.9.0

Forwarded by Bunshiro Tamura
———————– Original Message ———————–
From: Joe Taylor
To: WSJT software development
Date: Tue, 29 May 2018 09:27:44 -0400
Subject: [wsjt-devel] Release of WSJT-X Version 1.9.0
—-

The WSJT Development Group is pleased to announce WSJT-X Version 1.9.0. If you have been using version 1.8.0, or a candidate release v1.9.0-rc#, you should upgrade at this time.

New features and enhancements since Version 1.8.0 are summarized here:
http://physics.princeton.edu/pulsar/k1jt/New_Features_1.9.0.txt

A more detailed list of changes since “Release Candidate 4” (wsjtx-1.9.0-rc4) can be found in the Release Notes:
http://physics.princeton.edu/pulsar/k1jt/Release_Notes.txt

WSJT-X Version 1.9.0 permits operation in FT8 DXpedition Mode without callsign restrictions, but not for transmitting in any of the conventional FT8 sub-bands. DXpedition Mode should be used only in rare-entity circumstances in which sustained QSO rates well above 100/hour are expected. Detailed instructions for FT8 DXpedition Mode can found here:
http://physics.princeton.edu/pulsar/k1jt/FT8_DXpedition_Mode.pdf

Links to installation packages for Windows, Linux, Macintosh, and Raspbian Jessie are available here:
http://physics.princeton.edu/pulsar/k1jt/wsjtx.html

You can also download the packages from our SourceForge site:
https://sourceforge.net/projects/wsjt/files/
It may take a short time for the SourceForge site to be updated.

We hope you will enjoy using WSJT-X Version 1.9.0.

— 73, Joe, K1JT, for the WSJT Development Group

——————— Original Message Ends ——————–

2018年5月9日

Fw: [wsjt-devel] Third Public Test of FT8 DXpedition Mode: Early results

Forwarded by Bunshiro Tamura
———————– Original Message ———————–
From: Joe Taylor
To: WSJT software development
Date: Mon, 7 May 2018 15:39:35 -0400
Subject: [wsjt-devel] Third Public Test of FT8 DXpedition Mode: Early results
—-

Hi all,

Hearty thanks to everyone who participated in the Third Public Test of FT8 DXpedition Mode!

A number participants and would-be participants reported that propagation was spotty, at best. Nevertheless, at AA7A, G4WJS, K1JT, and K9AN we copied 405 unique callsigns of stations acting as “Hounds”, and at least one “Fox” was worked by 305 of them. Many Hounds worked two or three of the Foxes.

Details of stations worked and calls copied are given in the attached file “logged_calls.txt”. We’re sorry if we missed you, or if propagation was unfavorable for you.

Hounds who followed advice to monitor the “Ping Jockey Relief” chat page understood before start time (1400 UTC) that we had changed operating frequency from 14.090 to 14.115 to avoid most of the 20m activity in the ARI RTTY contest. Soon after 1400 UTC they also learned that W1/KH7Z had some unexpected setup problems and was unable to continue. Consequently W7/KH7Z took over as Fox at 1425 UTC and continued operating until 1600. K1JT was Fox between 1600 and 1700, and G4WJS stepped in for a short bonus run between 1710 and 1750 UTC.

The three Foxes were configured as shown in the following table. The setup at W7/KH7Z is comparable to what will be used at KH1/KH7Z, the Baker Island DXpedition. We operated in ways expected to provide the most thorough tests of the DXpedition Mode software. The low-power, simple-antenna setup at K1JT may be indicative of what can be done from KH1/KH7Z when band conditions are poor.

Call Grid PEP PerSlot Antenna
—————————————
W7/KH7Z DM43 500 W 20 W 3 el
K1JT FN20 100 W 4-9 W Dipole
G4WJS IO91 400 W 16 W 4 el

The attached plot “QSO_rate.pdf” shows the equivalent hourly QSO rate for each 5-minute interval at W7/KH7Z. The measured rates range from 8 to 33 per 5-minute interval, or 96 to 396 QSOs per hour. Several factors acted to suppress the rate at various times. The dip at t=30 minutes was caused by a restart following a program crash. We have identified the reason, and this bug will be easily fixed. After an hour W7/KH7Z started to run out of available Hounds; by the 90-minute mark he had worked 83% of those copied at least once.

This test run has shown that peak QSO rates with FT8 DXpedition Mode can approach 400/hour, and that sustained rates well above 200/hour will be readily achieved in good conditions.

The test also helped us to identify a few relatively minor software bugs that still need to be fixed. One such bug prevented Hounds calling with compound callsigns (e.g., S5/N1YU, VE3GFW/W6, W1/V47KA, W7/VK2IXC, W7/ZL1NA, W9/K9AN) from working the Fox, through no fault of their own. Unknowingly, the Foxes wasted significant time trying to work these stations, thereby suppressing their QSO rates.

All in all, we consider this test run very successful. We hope to be able to release the General Availability WSJT-X Version 1.9.0 before the end of May.

— 73, Joe, K1JT

——————— Original Message Ends ——————–

2018年5月2日

Fw: [wsjt-devel] WSJT-X v1.9.0-rc4: Third Public Test of FT8 DXpedition Mode

Forwarded by Bunshiro Tamura
———————– Original Message ———————–
From: Joe Taylor
To: WSJT software development
Date: Thu, 26 Apr 2018 08:51:40 -0400
Subject: [wsjt-devel] WSJT-X v1.9.0-rc4: Third Public Test of FT8 DXpedition Mode
—-

The WSJT Development Group is pleased to announce a fourth Release Candidate for WSJT-X Version 1.9.0.

A third beta release, v1.9.0-rc3, has been tested in the field over the past several weeks. These tests included a public test of FT8 DXpedition Mode conducted on April 7. A few additional bugs were identified and corrected, and the -rc4 release also includes some minor enhancements.

A General Availability (GA) release of WSJT-X Version 1.9.0 will be announced at a suitable time, probably in the near future. After that you should stop using any -rc# release candidate.

Short list of changes since WSJT-X Version 1.9.0-rc3:

1. Corrected several flaws in Fox and Hound behavior, FT8 DXpedition Mode

2. Decoded CQ messages where a prefix has been used as a suffix now have the DXCC entity name assigned correctly in almost all cases

3. Improved AFC capability for the wider JT65 sub-modes to help with drifting signals

4. Better support for macOS using hi-DPI Retina displays

5. New UDP message that allows external applications to highlight decoded callsigns

6. Main-screen geometry and state of the “splitter” setting between its two text windows is now properly restored after program restart

7. New simulator jt49sim[.exe] replaces jt4sim and jt9sim

8. Correct S/N measurements for the JT9 slow/wide submodes

9. Other minor bug fixes

10. Updated copy of cty.dat

###############################################################################
*Third Public Test of FT8 DXpedition Mode*
——————————————

If you decide to install v1.9.0-rc4, please help us by participating in the third public test of FT8 DXpedition Mode scheduled for Saturday, May 5. Once again, the goal is to simulate a rare-DXpedition pileup by having many stations (“Hounds”) calling and trying to work a designated pseudo-DXpedition station (“Fox”).

Everyone participating in the test must use WSJT-X v1.9.0-rc4. In addition, you must read, understand, and carefully follow the instructions posted here:
http://physics.princeton.edu/pulsar/k1jt/FT8_DXpedition_Mode.pdf
Please be sure to read this document carefully, again. Some details of the operating procedures are different from previous versions.

If you have legitimate access to more than one callsign (spouse, a club call, or whatever) please feel free to call and work each Fox more than once. The more Hounds, the better: we want the test pileup to be as deep as possible.

The third public test will take place as follows, with each session lasting one hour:

Date UTC Frequency Fox Callsign Operator
—————————————————
May 5 1400 14.090 MHz W1/KH7Z N1DG
May 5 1500 14.090 W7/KH7Z AA7A
May 5 1600 14.090 K1JT K1JT

If last-minute instructions are necessary they will be announced on the “Ping Jockey Relief” chat page:
http://www.pingjockey.net/cgi-bin/pingtalkB

As we have done before, we will plan to publish lists of all Hound callsigns copied and those worked by each Fox.
###############################################################################

Installation packages for WSJT-X v1.9.0-rc4 on Windows, Linux, Macintosh, and Raspian Jessie have been posted on the WSJT web site here:
http://physics.princeton.edu/pulsar/k1jt/wsjtx.html

Scroll down to the bottom of the page to find a link to the installation package for your system.

You can also download the packages from our SourceForge site:
https://sourceforge.net/projects/wsjt/files/

Please report your test results and any problems to one of the email lists wsjt-devel@lists.sourceforge.net or wsjtgroup@yahoogroups.com. You must be a subscriber in order to post to these lists.

— 73 from Joe, K1JT, for the WSJT Development Group

——————— Original Message Ends ——————–

2018年4月10日

Fw: [wsjt-devel] Second Public Test of FT8 DXpedition Mode: early results

Forwarded by Bunshiro Tamura
———————– Original Message ———————–
From: Joe Taylor
To: WSJT software development
Date: Mon, 9 Apr 2018 11:30:32 -0400
Subject: [wsjt-devel] Second Public Test of FT8 DXpedition Mode: early results
—-

Hi all,

Many people have asked for a list of stations heard and worked in the
Second Public Test of FT8 DXpedition Mode, held on April 7. I have attached a brief summary. It’s a plain text file containing four lists of callsigns:

1. 61 logged by W1/KH7Z in 36 minutes: rate = 61*60/36 = 102/hour

2. 55 logged by K1JT in 21 minutes: rate = 55*60/21 = 157/hour

3. 174 logged by W7/KH7Z in 60 minutes: rate = 174/hour

4. 390 unique calls copied by one or more of the three Foxes

It’s worth noting that Ned/AA7A, operator at W7/KH7Z, learned to manage his queues much more effectively as his hour progressed. After a program restart at 1532 UTC he worked 105 additional stations, a rate of 105*60/28 = 225/hour during the remaining part of the hour.

Slowly but surely, we are optimizing the software and improving our “FoxOp” skills. Further progress will definitely be possible!

For this test the three Foxes were configured as follows:

Call Grid PEP PerSlot Antenna
—————————————————-
W1/KH7Z FN42 500 W 20 W SteppIR at 15, az=50
K1JT FN20 100 W 4 W Dipole at 17m
W7/KH7Z DM43 500 W 20 W 3 el at 22m, az=45

— 73, Joe, K1JT

——————— Original Message Ends ——————–