Dual operator CW POTA script

[mcdanlj]

Shortly before N4NTO Tripp passed, Mark N4MQU did a video of Tripp teaching him to do a dual-operator CW POTA activations. I watched that video, and then combined it with conversations on Mastodon including with Dan KB6NU and actually trying a dual-operator QRP activation with Brantley K4CBW last weekend. We learned some lessons as we experimented from what worked and what didn't, and I thought I'd share the resulting script here.

Screenshot From 2025-11-09 17-11-10.png (149.63 KiB) Viewed 71207 times

Here are https://people.danlj.org/mkj/Dual-OP-CW ... -Sheet.pdf that you can print duplex and cut out as a cheat sheet, and https://people.danlj.org/mkj/Dual-OP-CW ... -Sheet.odt that you can edit in LibreOffice if you want to change anything.

We didn't send "AS" to pass a physical key. We hooked two keys into the same radio using a normal 1/8" stereo audio splitter cable. We still had to agree on the keyer settings in the radio, of course; otherwise we would have needed separate keyers and set the radio to accept straight key input. For our activation, as it happens, I am a single-paddle user, so A or B doesn't make a lot of difference to me. That made it easy to agree on a setting: we just used his preference. We could "pass the key" by just nodding at each other.

Sending CALL1 ES CALL2 in the CQ clues in the hunter that something is different, at least if they are paying attention. Sending CALL1 ES CALL2 with the 72 gives them a chance to double-check their logs if something seemed off, and clues in hunters who didn't hear the CQ because they arrived on frequency in the middle of the QSO. We did alternate who sent the CQ from time to time to give fingers a rest, but kept the responses in the same order as our calls listed in the CQ, which we kept consistent. We both sent "CQ POTA DE KZ4LY ES K4CBW" and I was always the first to respond, even if he sent the CQ.

We had at least one hunter who may have thought that Brantley (the CALL2 for us) was another hunter calling me at the wrong time. Sending THEIRCALL DE CALL1 / THEIRCALL DE CALL2 at the beginning of each exchange is meant to address that confusion, because they should recognize their call and follow along.

You can make it easier for hunters by using Ham2K Polo's https://polo.ham2k.com/docs/polo-features/multiops/ explicit multi-operator support so that at least other Polo users see a combined spot.

This is not the way to make the most contacts fastest. It's a way to activate socially without needing bandpass filters, alternating operating sessions, or moving antennas out of near field and running somewhat obtrusive coax a long way through a park to avoid QRM. (Feels like what golfers have told me that going golfing with a friend is like...)

I think this operating mode should become more common, and the more of us do it, the easier it will be for POTA hunters to recognize the script. So this post is part of my "be the change you wish to see in the world."

[KL7MJ]

What you're proposing isn't wrong or illegal or anything like that, but I would find it very confusing, and I'm not a new operator - which I think is kind of the target audience for POTA. Why not just take turns operating? Have one operator get 10 contacts and then turn it over? Or one of you act as control operator and both log with the same callsign?

[mcdanlj]

Multi-operator POTA is done a lot on SSB, and there's no particular reason not to do it on CW. There is a general script for it on SSB.

Everything new is unfamiliar until it's not new any more. So the fact that trying to do it at all would be relatively unusual but not unheard of isn't ipso facto a reason not to do it.

My goal is to reduce the confusion when it is done.

I'm not the only one interested. As I led with, Tripp N4NTO did this, and Dan KB6NU posted a less detailed procedural suggestion for it as well https://www.kb6nu.com/a-pota-procedural-proposal/ where I jumped into the conversation.

I've seen the question come up repeatedly if not persistently.

When I raised this particular script on the POTA discord's pota-cw channel, it got some interest and wasn't dismissed.

So while I am interested in suggestions for additional tweaks that might improve the script, I feel like "why not just don't do it?" is maybe missing some nuance.