Latest posts
-
Got P2000 FLEX reception finally working.

After a couple of hours struggling with the Yaesu FTX-1 internal soundcard, I came to the conclusion that this rig was for some reason not able to deliver ‘discriminated‘ sound output on the USB-soundcard outputs, that works with PDW. For some reason this FLEX (Used for Dutch P2000 pager messages, which is used by Dutch EMS) is really picky in how ‘raw‘ the signal is; slightly processed audio signals are not viable for proper decoding.
Since I do not have the proper DIN CAT-cable, I was also not able to get the 9600-baud stream including audio from the rig, so my hands were tied a bit.
So, I tried to use the HackRF Pro to try to receive and decode FLEX, which did work correctly. I had to install a virtual audio cable (acting like a microphone>speaker tunnel on a Windows machine), but after that I have a near 100% success rate on FLEX decoding.
I wish there was an easy way for the FTX-1 to just dump out unprocessed audio on the USB-soundcard interface, so it could be used for FLEX-decoding. Maybe I missed a crucial step, or it’s simply not possible, I don’t know.
However, it finally works with the HackRF. Yay!
-
Zendamateur reageert: That Handheld Radio Could Get You Killed (Survival Curriculum, Video, NL)
(NL) In onderstaande video reageer ik op een Youtuber die gaat over wat te doen met je portofoon tijdens een SHFT-scenario.
(EN) In the video below I give a reaction to a Youtuber, who’s talking about what to do while holding on to a HT, like a Baofeng, during a SHTF scenario.
-
Reactie op Citizen Survival Plan (Video, NL)
In the video below I did react on YouTuber Citizen Survival Plan on the topic of possible consequences of transmitting on the ham radio bands, without a license.
Languages: Dutch and English -
Python interfaces with Yaesu FTX-1 utilizing UART and USB-audio
I was wondering: How hard would it be to create a proof of concept for myself that indicates how difficult (or easy) it is to use Python 3 for interfacing with my Yaesu FTX-1 radio.
Short answer: it’s quite easy. If you know a little bit about Python programming, how UART works and a bit about tone generation, anyone can do this in an afternoon.
This proof of concept assures me that I can make tools myself that are specialised and optimized for use with my FTX-1. An example would be to be able to run a VARA FM or some Packet soundmodem, but return to the previous state the radio was in, afterwards.
Imagine, you want your Winlink email being checked every 30 minutes. But you also want to sweep the bands or do some scanning on VHF, for example. You have limited equipment and you want to switch fast between both modes, automatically if possible.
Utilizing a small Python script that interfaces between your sound modem and the transceiver would be able to do that:
- A cron-job is active that schedules to check email over Packet radio every 30 mins.
- You are sweeping the bands or just scanning.
- The cron-job fires and runs a Python script that prepares the radio.
- All current settings and VFO-positions are stored in memory
- The radio is now set in the mode and frequency for use with the soundmodem that is required to check the email
- The Winlink is doing the email check and perhaps some other Packet stuff is being performerd, depending on your needs
- After Winlink and such are done doing what they needed to do, the Python script restores the previously stored settings and positions of your radio
- Your radio continues doing whatever it was doing right before the cron-job fired to check emails.
- Different cron-jobs or scheduled events can be chained together, so a lot of different stuff can be combined and automated with the same rig with the same antenna:
- Checking mail
- Sending APRS beacon
- Automated voice or CW call to another frequency or multiple frequencies in sequence
- Act as a digipeater for a brief moment of time
- As a bonus there could be a ‘Not now‘ or ‘skip‘ button to quickly terminate a cron-job triggered radio ‘takeover’ and let you just do whatever you were doing. (If for example you were listening in on something important)
- The Python script can also be used for some really advanced scanning: Scan certain frequencies more often than others, instead of just cyclic, scan hold longer for certain frequencies, and quick sweeps for others. Change RX-treshold (squelch-ish) to sensitive for certain frequencies, to pick up the faintest signals, but make it less sensitive for others, because of congestion, etc.
This is just an idea of what a simple Python script could mean for us hams. At least to me. And I’m glad I know now that interfacing with my radio in this manner is possible.
73
-

Testing DARES ‘DWC’-suite
Last night and this morning I tested the DARES (Wiki | Website) DWC-software, what they call ‘DWS’ (Dutch Winlink System; link).
What it does is stitching together different stand-alone programs, like VARA-FM, Winlink, APRSIS32, a packet monitor, Packet digipeater and a UZ7HO soundmodem for packet radio. The brain of this suite is a KISS-port multiplexer, called the Packet Agent. Which acts as a router for different RX and TX signals and allows former mentioned programs to attach themselves to these ports via TCP routing.
Under the hood, the whole DWC-suite alters some functionality of all attached programs and configurates them to properly work with the Packet Agent. It’s now easier to setup basic station and connectivity settings via one program, instead of adjusting the settings of the different programs themselves. You can also start and stop all attached programs via the DWC main program, which is nice.

The Packet Agent running. Accompanied by the connections list. There are some caveats, though. This software suite is tailored for use with DARES and therefore it preconfigures all attached programs to that use. The digipeater, for example, will broadcast a standarized beacon string to the ‘ARES‘ group, fitting for the DARES context and it filters out routings for packet data that does not have use in a DARES context. Also it uses the -12 postfix (mobile station) to your callsign, even though some who use this suite, are operating from a base station. Some of these settings are hard to adjust by hand and require tinkering in the config files, which can be found in the installation folder.
If there was more customization possible in that regard, this suite would be a really good general purpose one-click off-grid tool for hams. It’s already really good and I can see the years of effort and dedication was put into developing this software suite. However, it would be nice to have an option for non-emergency use.
I had a fun time testing this suite and I will probably be using this when SHTF, not because it does things that former programs couldn’t, but because its a one-click tool, that gets you on the air within a minute, properly set-up for emercency comms and digipeating. That’s worth a lot.
73
-
PA0JCX is in the air…
It took a while for the RDI (= Dutch version of the FCC) to process my new call, but they finally processed it at the 24th of december; an implied Christmas gift indeed…
So, no longer PD2XAN, but PA0JCX from now on.
Why did I choose PA0JCX and not something like PA0XAN?
The answer is simple: It was my grandfathers call. He had this call until he became a silent key (= he died) in 1992. Now, 33 years later, I’ve taken over his call, in the hope to make a lot of new and rememberable QSO’s (= radio contacts).73 (= Greetings)
