Skip to main content

POTA K-4516: Project TouCans on Monjeau Peak


Project TouCans did its first somewhat high antenna elevation POTA in Lincoln National Forest over the weekend. The cloud cover was thick at 9,000 feet, so I didn't notice something about the QTH that definitely affected the QSO map. The cloud cover also made for a very quiet forest with the occasional exception of four wheel drive vehicles turning around because the last little bit of Forest Service Road 117 up to Monjeau Lookout was gated closed.

This was the first POTA where TouCans was substantially—meaning more than four feet up—suspended by tarred twine. It turns out that the stuff works spectaculalrly well! 

The area was gorgeous. I grew up in the mountains around here. Both the drive up and the very small hike felt very famililar and very comfortable. The air felt right. I live at sea level these days, so I had to move slow—it's all my body was going to allow me to do—but the space called for slow, easy movements anyway. You'll see.



QSO Maps


You'll probably note that due North just isn't there for the rig. QSOs to Colorado later in the day from Valley of Fires proved out that there were in fact folks listening out that direction. As I mentioned, I couldn't really see where I was setting up in relation to hte rest of the landscape. Here's what I found when I was finally able to look at a map:




I had setup the site in a bit of a bowl. There are two reasons I can see for the lack of QSOs to the North. First, Monjeau Lookout is in the way. 



Second, if you take another look at the antenna and rig that opened the post, you'll see the rig (and therefore the antenna feed point) is situated more towards the side of the ravine that leads out to Monjeau Lookout, so the ravine itself can also block more signal on that side.

QSOs

Callsignrx RSTtx RSTTime (GMT)Frequency
ai6ey5595592024/03/16 18:30:0014057.4
n9msg5395592024/03/16 18:48:0014057.4
kj5w5495992024/03/16 18:50:0014057.4
wm2v5695592024/03/16 18:52:0014057.4
n7wpo5495592024/03/16 18:54:0014057.4
k0yy5495592024/03/16 18:56:0014057.4
ai5in5495592024/03/16 19:00:0014057.4
k0hx5395492024/03/16 19:09:0014057.4
k6pb5395392024/03/16 19:10:0014057.4
w5gw5695592024/03/16 19:13:0014057.4
k0laf5395392024/03/16 19:15:0014057.4
n7xj4395992024/03/16 19:21:0014057.4

Wrapping it all up

I made a useful discovery during this activation: almost all of the digital noise the rig sometimes emanates is coming from the Bluetooh audio transmitter. I switched off the Pico-W and the digital noise was completely unchanged. That leaves the audio transmitter. When the Bluetooth transmitter isn't causing issues, the rig is surprisingly noise free, even in San Francisco.

One of the things I really enjoy about POTA is the chance to get outside and see the world. This activation did not disappoint in that—or any other for that matter—regard. On the way back down the mountain, a large herd of deer made their way across the road in front of me, then started grazing again on the other side.



Comments

Popular posts from this blog

How Many Files Can You Add to a GPT Project? An Interview with GPT-5 on Limits, Context Engineering Tips, and Chats

 Setting the scene: I’m tinkering with Project TouCans, knee-deep in radio logs, SQLite dumps, and Cesium code. Naturally, I’m wondering if shoving all this into one GPT Project is a recipe for brilliance… or for disaster. So I turn to Vril — you know, after Brainy from the Legion of Super-Heroes , because what else do you call your AI sidekick who always has the answers? Time to ask him straight up. [ As an aside, yes, GPT-5 has decided to sometimes call me Vail. I'm not sure why to be honest. Also, I asked Vril, er GPT-5, to write up our interview for me. Apparently, me asking it to 'Bro' up a few stories, just for fun, has convinced Vril that I use 'Like,' more than I actually might. ] Me (Vail): So Vril, how many files can I throw into a GPT Project before it just starts choking? Like, is there some magic number where the context window taps out and everything falls apart? GPT-5 (Vril): Great question. There’s no single hard file limit. What matters is ...

The Alcubierre Warp Drive Tophat Function and Open Science with Sage

I transferred yesterday's Mathematica file with the Alcubierre warp drive[2] line element and space curvature calculations to the  +Sage Mathematical Software System  today, (the files been  added to the public repository [3]).  If you haven't used Sage before, it's a Python based software package that's similar in functionality to Mathematica.  Oh, and it' free.  I also worked a little more on understanding the theory, but frankly, I made far more progress with the software than the theory.  What follows will be a little more of the Alcubierre theory, plus, a cool Sage interactive demo of one of the Alcubierre functions[1], as well as a bit about my first experience with using Sage. Theory The theory is fun, but it's moving slowly.  Here's the chalk board from this morning's discussion Alcubierre setup the derivation using something called the 3+1 formalism which means we consider space to be flat, (in this case), slices that are labelled ...

When Codex CLI Met Port 9 (Debugging WinError 10061 in a Whisper Pipeline)

When Port 9 Ate My Transcript When Port 9 Ate My Transcript A small debugging story about proxies, Codex CLI, and why localhost isn’t always your friend. CopaseticFlow field notes WinError 10061 Codex CLI + Whisper Environment gremlins There’s a particular kind of bug that feels like someone's been messing with your network stack again. You run a script from cmd.exe . It works. You run the exact same script from Codex CLI. It stops with: [WinError 10061] No connection could be made because the target machine actively refused it FFmpeg happily splits the audio. The Whisper API call dies immediately. No 401. No timeout. Just an instant refusal. Translation: that’s not an API error. That’s a socket being rejected. ...