Ed Braaten, N7EKB

See my radio and technology web page at https://n7ekb.net. #hamradio #homepage

Public Key

npub13r96f0unz2ejtnngz4p4w5nau3m6ds3cnadac09a24czkpf5kkaqrwapgd

NIP-05 Address

Profile Code

nprofile1qqsg3jayh7f39ve9ee5p2s6h2f77gaaxcguf7k7u8j742uptq56ttwspz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0ds6tudnc

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub13r96f0unz2ejtnngz4p4w5nau3m6ds3cnadac09a24czkpf5kkaqrwapgd

Show more details

Last Notes

2025-06-19 02:43:19 UTC

Added this #BitAxe to the #Hamshack today. It's solo-mining (also known as the "Bitcoin Lottery"). It's a lot quieter than I anticipated. Now it just needs to hit the lottery to help pay for some new #hamradio projects! 😀
https://image.nostr.build/c886cfb68867a471ccb8bed3936f8c1502af3a138f2d626b56a41bd55f822543.jpg

2025-06-09 01:21:48 UTC

- reply

Useful in scenarios where you need instantaneous one-to-many comms in an area where radio doesn't have the coverage.

2025-06-09 00:36:25 UTC

Just getting started with "block 44" in the #hamshack. Are there any other #nostr #hams using a #block44 address?
My #hamradio/#technology web site is still hosted on my VPS with an ordinary IP address, but is now also reachable at www.n7ekb.ampr.org .

2025-05-29 17:33:32 UTC

- reply

Genau richtig. Wird auch gut mit #reticulum funktionieren... 😀

2025-05-28 05:43:06 UTC

- reply

There sure are! 73 DE N7EKB.

2025-05-23 16:02:22 UTC

- reply

I honestly don't know what the rules are for this ham in the Netherlands, but if I was to implement his design here in the US, I'd put the nodes on a commercial band frequency to avoid the encryption mess under Part 97 rules. For #EMCOMM I've been toying with the idea of using one of our town's dedicated public safety frequencies for a UHF band LoRA #reticulum #RNode network. #hamradio is too restrictive with the required individual licensing and rules regarding encryption, etc. For example, in a #disaster we can hand out radios from our town's radio cache to non-technical volunteers who otherwise meet volunteer requirements (background check, etc.), and not worry about a ham license.

2025-05-22 17:59:06 UTC

A 2 watt RNode design. #reticulum #PE1RXF #nomadnet #hamradio #meshtastic #homebrew #esp32
https://www.meezenest.nl/mees/projects/reticulum_design_my_own_rnode/index.html

2025-05-14 14:25:47 UTC

Looking at the below abstract from the #Reticulum manual brings the following ideas/questions to mind: How hard would it be to modify a #nostr relay to allow connections to/from a #Reticulum network? Along the same lines, how hard would it be to modify a #nostr client to utilize a #Reticulum network as a transport?
#asknostr #strfry #nostrrelay #nostrclient #meshnetwork
Pipe Interface
Using this interface, Reticulum can use any program as an interface via stdin and stdout. This can be used to easily create virtual interfaces, or to interface with custom hardware or other systems.
``````
`[[Pipe Interface]]
type = PipeInterface
enabled = yes
# External command to execute
command = netcat -l 5757
# Optional respawn delay, in seconds
respawn_delay = 5
`

2025-05-11 04:10:09 UTC

- reply

I don't quite understand this article. I just finished setting up my own #XMPP / #Jabber messaging server on https://xmpp.n7ekb.net. I don't get the connection between a phone plan and XMPP. Especially the comment "privacy-enhancing phone service using XMPP".
#asknostr

2025-05-11 03:37:24 UTC

- reply

I payed for the life membership when I first got my #amateur #radio license. I had too much money burning a hole in my pocket, and frankly didn't know any better. I'm still waiting on #ARRL to issue my #DXCC which was electronically confirmed within seconds after my 100th validated QSO in #LoTW. For an organization supposedly representing amateurs who 'contribute to the advancement of the radio art' they're woefully behind in technology. It's sad... 😢

2025-05-11 02:51:29 UTC

The installation of my self-hosted Jabber/XMPP modern messaging server on #Debian is done. For the second time. That's right. I had it all up and running on a shiny new VPS a few weeks ago. I had the new installation passing with 100% compliance on https://compliance.conversations.im/server/n7ekb.net/. Then I *deleted* it instead of the old #Rocky #Linux VPS I had on the same hosting service...
Of course I made this swift rookie mistake *before* I'd setup my offsite backup!
Soooo. Guess what? The new re-installation is now backed up three ways to Sunday. My old friends git and rsync are happily guarding the server from this incompetent server admins!
Setup for family and friends and #hamradio, https://xmpp.n7ekb.net is ready for action.

2025-05-10 15:21:37 UTC

https://endof10.org/
#Linux #Windows #Windows10

2025-05-10 05:01:19 UTC

- reply

#WWARA #hamradio

2025-05-07 21:35:30 UTC

- reply

That area looks familiar! My perspective:
https://ed.braaten.net/GraniteDome.php
#GraniteDome #helocrash #Yosemite #NASFallon #hh1n

2025-05-07 05:43:14 UTC

- reply

So you configure your radios to talk into the repeater on one time slot and then listen on the other timeslot?
#dmr #hamradio

2025-05-07 05:26:32 UTC

- reply

I just turned the example whitelist into a blacklist today! I also made some minor tweaks to print an "ACCEPTED" or "REJECTED" line along with the public key hash to the log file. Now I can grep through the logs and see who's being naughty or nice... A simple grep | cut | sort makes a list where large blocks of the same ID are easy to eyeball.
#bash #grep #nostr #spam

2025-05-03 16:24:56 UTC

My self-hosted #Nostr #Relay logs were growing, growING, GROWING!
So I set out yesterday to determine exactly what was going on.
Guess what I found?!? A handful of clients from different IP addresses were causing a continuous stream of error messages where the relay was complaining of a "filter item too small".
So I tweaked the logging settings to get dumps of the requests generating the errors.
Each error entry looked like the following:
[Ingester 0 ]INFO| [21] dumpInReq: ["REQ","6zn9yubmmkm557n78kkta2e7aahjbn",{"since":1746216000,"authors":["00","01","02","03","04","05","06","07","08","09","0a","0b","0c","0d","0e","0f","10","11","12","13","14","15","16","17","18","19","1a","1b","1c","1d","1e","1f","20","21","22","23","24","25","26","27","28","29","2a","2b","2c","2d","2e","2f","30","31","32","33","34","35","36","37","38","39","3a","3b","3c","3d","3e","3f","40","41","42","43","44","45","46","47","48","49","4a","4b","4c","4d","4e","4f","50","51","52","53","54","55","56","57","58","59","5a","5b","5c","5d","5e","5f","60","61","62","63","64","65","66","67","68","69","6a","6b","6c","6d","6e","6f","70","71","72","73","74","75","76","77","78","79","7a","7b","7c","7d","7e","7f","80","81","82","83","84","85","86","87","88","89","8a","8b","8c","8d","8e","8f","90","91","92","93","94","95","96","97","98","99","9a","9b","9c","9d","9e","9f","a0","a1","a2","a3","a4","a5","a6","a7","a8","a9","aa","ab","ac","ad","ae","af","b0","b1","b2","b3","b4","b5","b6","b7","b8","b9","ba","bb","bc","bd","be","bf","c0","c1","c2","c3","c4","c5","c6","c7","c8","c9","ca","cb","cc","cd","ce","cf","d0","d1","d2","d3","d4","d5","d6","d7","d8","d9","da","db","dc","dd","de","df","e0","e1","e2","e3","e4","e5","e6","e7","e8","e9","ea","eb","ec","ed","ee","ef","f0","f1","f2","f3","f4","f5","f6","f7","f8","f9","fa","fb","fc","fd","fe","ff"]}]
2025-05-02 13:12:41.038 ( 198.848s) [Ingester 0 ]INFO| sending error to [21]: bad req: filter item too small
The culprits were trying to request a list of articles with an author list that basically covers every possible Nostr ID... Or something along those lines.
If you're using a nostr relay you aren't paying for, remember to #zap your relay operator. They deserve a little love from time to time!
#sysadmin #admin #linux #cybersecurity
#nostr is not just #bitcoin

2025-04-29 14:00:00 UTC

- reply

Updated the python net report script to generate a better formatted report. Next optimization would be to publish the #nostr note directly from the script.

2025-04-29 07:01:52 UTC

- reply

This still needs some work, but it's a lot better than the #RSS feed version turned out.

2025-04-26 08:21:16 UTC

#reticulum #rncp
https://github.com/markqvist/Reticulum/discussions/804

2025-04-14 23:27:44 UTC

Did some cleanup on the web page today.
https://n7ekb.net
#radio #xmpp #n7ekb #hamradio #nostr #reticulum #meshtastic #shortwave #nomadnet #aprs #opengd77 #jabber #ares #ni4l

2025-04-14 00:49:17 UTC

- reply

There actually is a global public network. I host a #public #reticulum node that you can connect to over the commercial internet: https://reticulum.n7ekb.net. It provides a bridge from my local low power RF-based (#LoRA) nodes to other RF-based networks. I also run a mobile RNode in my car that can use my mobile phone to tie it into the "global" network.

2025-04-14 00:28:05 UTC

- reply

I just posted about this early today:
#nevent1q…zkl2
#reticulum #nostr #development

2025-04-13 14:20:15 UTC

Here's one for #asknostr: Filed in https://github.com/greenart7c3/Citrine/issues/61.
I run #Citrine on my phone (Thank-you!!!) and also run a personal nostr relay (strfry) on my VPS so that I have two locations for all my notes. These are entirely dependent on the commercial internet however. I also run a program called #Sideband which connects to the #Reticulum network using a locally hosted transport router for Reticulum. How feasible/difficult would it be to add support in Citrine to publish/interact with my local Reticulum transport? The Reticulum transport has a lot of options: Reticulum Interfaces. Such a feature would make nostr over Reticulum possible in areas where commercial internet is unavailable (#disaster/#censorship).

2025-04-12 04:58:19 UTC

- reply

I've migrated from #Anytone to #Tytera. I use the MD9600 (a dual band analog/DMR base mobile radio at $220) and the Tytera UV-390 (also dual band analog/DMR at $120) as my handheld. Both radios came shipped with the #OpenGD77 firmware. This common firmware means I use the same #codeplug for all my radios, and the #DMR programming is #ham friendly with the OpenGD77 approach. These radios support #hamradio as well as commercial, so they meet my needs in the #EMCOMM space really well. (Our town's EOC uses DMR). I've found the UV-390 to be more rugged than the Anytone handhelds for daily carry, especially outside in rainy weather.

2025-04-12 04:29:13 UTC

- reply

It's fun indeed! Most #meshtastic devices are easily converted to #RNodes for use in a #reticulum environment as well. Double the fun! https://reticulum.n7ekb.net

2025-04-10 04:37:39 UTC

- reply

A lot of #hams ignore the other radio services which are often better suited for meeting the needs in some parts of a #disaster plan. You're wise in connecting the dots between the experimenting nature of #hamradio and the use of the knowledge gained there to solve real world problems with ALL the tools available.

2025-04-10 04:17:11 UTC

Finally got around to troubleshooting my #NIP-05 setup after the move to a new #Debian #Linux server. In the process I used #Grok to research the needed Apache configuration to allow #nostr client access to the /.well-known/nostr.json file.
Grok did great on the basic research query! But on my subsequent bunny trail queries it determined that I'm the ONLY #hamradio operator known to the interwebs that hosts a nostr relay!
#CQ, CQ all #hams! Tell Grok you use nostr and that you host a relay! 🤪

2025-04-07 20:00:59 UTC

- reply

On #linux you can specify a /dev/serial/by-id that is persistent across reboots. That's unfortunately not a native option in #MacOS. It might be possible to mimic the linux behaviour with a custom Python script using the pyserial library to enumerate the serial ports and create /dev/serial/by-id links for you.

2025-03-26 18:49:08 UTC

- reply

This looks like it be a great platform to run Liam Cottle's #reticulum #MeshChat!

2025-03-24 01:52:12 UTC

- reply

Are you referring to reticulum.n7ekb.net:48086? It doesn't appear to have any issues on this end.

2025-03-20 03:38:50 UTC

- reply

First time booster and regular listener via the AntennaPod app on my GrapheneOS phone. The show keeps me entertained while I drive an 18-wheeler all around the metro area based out of Algona, WA. Thank-you for what you do! You mentioned a network challenge in a recent show. How about taking your meshtastic experience up to another level? There's a far more solid mesh protocol called Reticulum with some interesting apps built on top of it like reticulum-meshchat, Sideband, rnsh, rcp, and nomadnet. So here's the challenge: re-flash those meshtastic devices, turning them into RNode devices. Then build out a test network over LoRa and TCP/I2P/Serial/AX25. Maybe give points for things like sucessful rnsh (like ssh) connections that hop over at least one or more LoRa hops. After you read up a bit on Reticulum, I'm confident the team can come up with a great challenge that will demonstrate how Meshtastic vs Reticulum is sort of like Windows vs Linux. :)
https://fountain.fm/show/dWiuBeqpDSM86AwXRXov

2025-03-15 15:25:27 UTC

- reply

I actually read just the opposite from someone who posted about their test results. Higher SWR with the 90 degree angle versus straight. Antennas, feedlines, and RF are so fickle.

2025-03-11 14:42:05 UTC

- reply

Is anyone working on enabling the #Meshtastic UI to operate over a #Reticulum network?
#asknostr #embeddedworld #hamstr #hamradio #lora #freedomtech

2025-03-09 08:22:42 UTC

- reply

Try Liam Cottles' #Reticulum MeshChat app. You can send audio snippets over #reticulum links.

2025-03-09 08:16:30 UTC

- reply

#Reticulum would be a better suited protocol for this application.

2025-03-08 05:16:39 UTC

- reply

Ugh. Why not build this as a software layer on top of the existing RNode devices? Yet another firmware that's incompatible with any other existing mesh... 😢

2025-03-01 16:03:47 UTC

The #Reticulum Network World #Map Project went live today:
https://rmap.world/index.php
I'd like to see some #EMCOMM minded #hamradio sites show up on this map. In theory #EOC client computers running reticulum-meshchat day-to-day would have transparent fallback to RF-based connectivity when their commercial TCP network goes away in a #disaster event.

2025-02-25 17:32:01 UTC

- reply

2025-02-22 21:36:04 UTC

Has anyone investigated the possibility of building a LoRa-like low-power transceiver for 49.82-49.90 MHz band for use as an #RNode? This might have greater range in rural, tree-covered areas that limit 800/900 MHz signal propagation.
#AskNostr #reticulum #meshnetworking #mesh #LoRa #hamradio #nomadnet
( Quoting from the https://www.hfunderground.com/wiki/index.php/Part_15 )
The 49.82 MHz to 49.90 MHz band allows for personal hobby transmitters up to 100mw output with any modulation as long as the modulation stays within the 49.82-49.9 MHz band. This provision within Part 15 opens up opportunities for 49 MHz beacons, provided an effective antenna is used.
§ 15.235 Operation within the band 49.82–49.90 MHz. (a) The field strength of any emission within this band shall not exceed 10,000 microvolts/meter at 3 meters. The emission limit in this paragraph is based on measurement instrumentation employing an average detector. The provisions in §15.35 for limiting peak emissions apply. (b) The field strength of any emissions appearing between the band edges and up to 10 kHz above and below the band edges shall be attenuated at least 26 dB below the level of the unmodulated carrier or to the general limits in §15.209, whichever permits the higher emission levels. The field strength of any emissions removed by more than 10 kHz from the band edges shall not exceed the general radiated emission limits in §15.209. All signals exceeding 20 microvolts/meter at 3 meters shall be reported in the application for certification. (c) For a home-built intentional radiator, as defined in §15.23(a), operating within the band 49.82–49.90 MHz, the following standards may be employed: (1) The RF carrier and modulation products shall be maintained within the band 49.82–49.90 MHz. (2) The total input power to the device measured at the battery or the power line terminals shall not exceed 100 milliwatts under any condition of modulation. (3) The antenna shall be a single element, one meter or less in length, permanently mounted on the enclosure containing the device. (4) Emissions outside of this band shall be attenuated at least 20 dB below the level of the unmodulated carrier. (5) The regulations contained in §15.23 of this part apply to intentional radiators constructed under the provisions of this paragraph. (d) Cordless telephones are not permitted to operate under the provisions of this section.

2025-02-22 18:18:06 UTC

#reticulum #rns #meshnetworking #mesh https://image.nostr.build/d9750d73719118ffa0bcce9261ae5f267b244433cea442ee5618b2db02ee26be.jpg

2025-02-21 16:51:13 UTC

- reply

Are there plans to support #NOSTR user profiles/login?

2025-02-18 05:09:57 UTC

- reply

Today was the first day I used it portable. It's currently reporting 47% battery level after about 6-8 hours of operation.

2025-02-17 12:58:45 UTC

Update to the #reticulum status page includes a description of my configuration using re-flashed #meshtastic hardware running as #RNodes:
https://reticulum.n7ekb.net/

2025-02-16 20:55:05 UTC

- reply

That's right. #reticulum firmware 1.81 is what I used.

2025-02-16 05:51:15 UTC

- reply

Its a bit early to say. I live in a rural area with lots of Douglas Fir trees, so 900 MHz radio signals don't travel very far - even with the magic of LoRA low-power propagation. The 4 RNodes I currently have on the property are happily meshing together and waiting for more neighbors. If I could just get a node up on a mountaintop... In the meantime I'm using the internet as a stable gateway to other RNode networks.

2025-02-16 03:59:12 UTC

Got this new LilyGo T-Echo device yesterday with #meshtastic firmware. Promptly reflashed it with #reticulum #RNode firmware 1.81. I paired this RNode with my phone running #Sideband. I finally stumbled across the "Popular RNode Settings" page in Mark's wiki on github. Now I have my RNodes operating on 914.875 MHz with a spreading factor of 8 so they'll be more likely to #mesh with other people's RNodes in the 900 MHz #ISM band. Looking forward to #wardriving some of the areas I frequent with this new RNode.
#hamradio #nomadnet
https://image.nostr.build/75b35f276d4a0711291760c7ef6d1684dc35f2ffd3618a40133b35c645ed0dbb.jpg

2025-02-13 05:12:21 UTC

- reply

Have you looked at reticulum-meshchat on GitHub?

2025-02-09 06:36:50 UTC

- reply

N7EKB's RNode Network Node screenshot...
https://image.nostr.build/a9a7eff5871f1ad660fe93ce7fe7b66b2fbf2110ba173f3f1baff08e66077e77.jpg

2025-02-09 06:26:39 UTC

I converted my third #meshtastic node to an #RNode today so I can use it as a future portable/mobile node. My #Linux #hamradio shack PC has both an RNode and high-speed TCP connectivity and is acting as a dedicated bridge between my RNode-based reticulum network and the public internet TCP-based #reticulum network. I tweaked the mode settings on the different interfaces in the ./reticulum/config files to use the #gateway and #boundary modes were appropriate. You can see the modes on the status page at https://reticulum.n7ekb.net.
For #nomadnet I setup a second node so that my rnode-based network has it's own node on the #hamradio shack PC. Look for "N7EKB's RNode Network Node" and "N7EKB's TCP Network Node" in the announce stream on the #Nomad Network.
The screenshot is of Liam Cottle's #MeshChat program running on my #Fedora #Linux laptop connected to the TCP Server interface of my #hamradio shack PC. MeshChat is an AWESOME program Liam!
https://image.nostr.build/8745f0d9112d9462c2ff428dec5a1b5f6de7b787af6c7eb8319f9f10218b9d55.jpg

2025-02-03 02:42:14 UTC

- reply

LOL. The node reticulum.n7ekb.net is indeed only using TCP on the commercial #internet since it's running on a VPS in a data center and also hosting my web pages.
You inspired me to create a couple of scripts to add the output of my hamshackpc #RNode status to the reticulum.n7ekb.net web page. My hamshackpc (computer running #fedora #linux) talks to the greater #reticulum network only via an #RNode based on the RAK4631. Another PC in the home network has both RNode and TCP connections to the reticulum network.
I put the output of the #rnstatus command from the hamshackpc into a file. Then I'm using the #reticulum utilities #rnx and #rncp to move the file from the hamshackpc over the two RNode connected PC's and onto the web server where the #php page can display the contents! The transfer script runs every five minutes via a crontab entry. 😀

2025-02-01 22:14:40 UTC

Got my #reticulum status page up and running:
https://reticulum.n7ekb.net
#meshnetwork #meshtastic #mesh

2025-01-29 05:26:53 UTC

I have my #Reticulum TCP node up and running. You can connect as a TCP Client to reticulum.n7ekb.net using port 48086.
I'd like to build a network with TCP connections to other #hamradio nodes worldwide. Reply to this note with your host:port info and I'll add you to my connections.
I have a couple of #meshtastic devices that I've reflashed as #RNodes that will be joining soon as local RF connections.

2025-01-26 15:25:31 UTC

- reply

Can we safely assume they're easily reflashable to convert to #rnodes for a #reticulum #mesh network?

2025-01-25 22:26:08 UTC

- reply

Reflashed one of my #meshtastic devices to an #RNode - pretty easy to do. Now to wait for some more RNodes to mesh with.
#Sideband on the #graphenos phone and #nomadnet on the #Linux desktops using #i2p seems to work really well so far.
Great potential for #EMCOMM without the restrictions of #amateurradio.

2025-01-21 02:43:45 UTC

- reply

I run Windows 7 Pro in a virtual machine (under QEMU) on my #Fedora laptop to get around this issue. I keep hoping that the developers of #OpenGD77 will port their CPS to Linux so I won't have to do this...

2025-01-21 02:27:32 UTC

- reply

Good evening OM! Welcome to Nostr! 73 DE N7EKB

2025-01-11 20:33:01 UTC

- reply

I usually consider myself DX for them if we're in different DXCC entity locations.

2025-01-11 20:13:28 UTC

Logged my first #JS8 QSO today using #JS8Call on my #Linux laptop remote controlling my #XieguG90 radio. Thanks W9PEM for the great QSO and tips! #hamradio https://image.nostr.build/4b345764722635b1ddb513b0a22db4b26b30f2814befa23b0e943e7d2d1e3efb.jpg

2024-10-06 23:39:02 UTC

I finally got familiar with #Pat, an open source #Winlink client program written in the Go language that runs natively on my #Linux laptop. It supports forms well. I'm quite happy to throw out the clunky Winlink Express running in a #Windoze VM and replace it with #Pat. 🤓 https://image.nostr.build/2c74eeae4774219689e5c5b4736d96c36cce95ed1c40d84ed9611097560ac6fa.jpg

2024-09-17 00:22:10 UTC

- reply

LOL! That's how I got started with #meshtastic. You'll be amazed at how much you can learn talking to yourself! 😜

2024-09-08 01:31:35 UTC

- reply

That looks like a TYT UV-390 running #OpenGD77. Awesome! My UV-390's have become my go-to handheld radio after installing the new firmware. The only downside is that the CPS is still Windows only. My hamshack is #Linux only so I have to run a #Windoze VM on my Linux machines to use the CPS.

2024-09-03 03:17:59 UTC

- reply

It would be awesome if there was an #M17 version of #OpenGD77. Not sure that the hardware would support that, but it's okay to dream, right? 😲

2024-09-02 06:55:52 UTC

- reply

#Linux #Linuxkernel #Rust
#nevent1q…npv2

2024-09-01 04:48:13 UTC

Updated my #OpenGD77 codeplug with all the #Beachnet repeaters. The documentation of the #BeachNet system is outstanding and includes Geo coordinates for each of the repeaters: https://www.qsl.net/nm7r/
I just wish the #OpenGD77 #CPS developers would move to a portable GUI that runs on #Linux.

2024-08-24 01:41:58 UTC

- reply

The #EMCOMM community in some areas rely heavily on this paired with #WinLink which is also closed source. Neither of them run natively on #Linux, so no place for them in my ham shack. #amateurradio

2024-08-20 03:35:03 UTC

- reply

LOL. Apparently connecting the dots? I'm reading your post here on my Android #nostr client.

2024-08-11 04:26:37 UTC

LOL. Who says you can't have an adhoc conversation in an #FT8 #QSO? Tnks K8AGB for making our contact interesting!
040315 -5 0.1 1037 ~ THANK U K8AGB
040330 Tx 1040 ~ K8AGB N7EKB RR73
040345 -5 0.1 1036 ~ TS480 GAP VRT
040415 -5 0.1 1036 ~ GAP 31FT VRT
040430 Tx 1040 ~ TNKS 73 ED
040445 -3 0.1 1035 ~ STA IS BASIC
040500 Tx 1040 ~ XIEGU G90
040530 Tx 1040 ~ 15 WATTS
040600 Tx 1040 ~ OCF DIPOLE
040615 0 0.0 1035 ~ N7EKB K8AGB 73
040630 Tx 1040 ~ K8AGB N7EKB 73

2024-08-02 04:29:56 UTC

- reply

LOL.

2024-07-30 01:05:47 UTC

- reply

Well done!!! What mode and what rig? I run my Xiegu G90 at 12-15 watts into an OCF dipole and I'm only 10 DX contacts away from #DXCC on FT8. It doesn't always take big guns to have fun with #hamradio. 😎

2024-05-25 08:36:10 UTC

Hello nostr world! #newcomer #hamradio