Latest posts

  • PA0JCX hosted a DRCO monthly EMCOM exercise

    As a fresh and rookie member of DRCO, the Dutch DARES-derivate and equivalent in the province of Zeeland, The Netherlands, It was my time to host this month’s training exercise.

    DRCO is an abbreviation for Delta Radio Communicatie Ondersteuning, which translates to “Delta-region Radio Comms Support” Whereas the Delta-region comprises of mostly Zeeland in The Netherlands.

    So what does DRCO do? Actually just what (D)ARES does, but more lightweight, more agile and more regionally tied (‘Delta’, or Zeeland). It tries to set up radio EMCOM (emergency communications) between important poi’s and government bodies in case of regional internet and cellular outage.

    Whereas the military and other civil services need time (often up to 72 hours) to set up emergency comms, DRCO and ARES-type of groups in general are able to establish radio comms between government bodies within the first few hours after a regional outage. And that’s exactly where DRCO fills the gap between an outage incident and the government’s contingency, which can take multiple days to set up.

    Nowadays, with Starlink satcom possibilities and a robust network of cellular connectivity with built-in redundancy, the chance where DRCO needs to act is slim. It’s not like 1953 any more, where the Watersnoodramp (Dutch flood of 1953) posed extreme hurdles for communications between rescue teams and government bodies. Nowadays, a Starlink satellite dish pulled out of a waterproof pelicase can be connected and secure, broadband comms will be up within 30 minutes. Glass-fiber will mostly still be functioning and cell-phone antennas will hold on for a little while, because of their redudancy battery, that provides power for hours more after a grid-down situation.

    So, why DRCO in 2026?

    For me there are two valid reasons to have DRCO-like groups still existing:

    • A great way to participate in low-entry EMCOM exercises
    • Radio is the only way to establish fast point to point connections without third parties

    While probably never needed in real-life situations, groups like DRCO or ARES can share valuable skills and knowledge about communications in general. Because of participating in training scene’s (actually larping a simulated grid-down event where EMCOM needs to be established) you find out really quicky what becomes important during communications when only radio is available. Limitations in range, preventing chaos, readability of information, security of information, the availability of radio technology at scene, etc. All of these come together during these exercises. The bottleneck will become visible, whether it’s usable range of used equipment, improper dispatching resulting in chaos or sloppy information integrity; it will come to light during an exercise, where the clock is ticking.

    The other point is that radio is the only way to establish fast point-to-point connections, without the need of third parties. It will perhaps not come to mind to a lot of people, but the fact that Starlink satellites and cellphone towers exist and are generally considered reliable in case of emergency, does not guarantee that the third parties controlling them are reliable at all times. A government or a company, involved in providing the service, albeit satellite or cellular coverage, might become compromised really really fast during grid-down situations and the following civil unrest that might follow. Self-interests are on the rise and that might involve that a decision is made to not provide EMCOM possibilities to the public any longer or only in a way that allows for monitoring or handling by compromised agencies or actors, which can become extremely dangerous in a volatile environment where the rule of law became just random words in some books, instead of an agreed upon social contract enforced by judges. Being able to use simplex radio comms during such situations can be valuable in my opinion. While groups like DRCO are initially meant for EMCOM in addition to and in collaboration with state owned contingency comms, it’s perfectly usable as a stand-alone separate comms system, in cases where the state or third parties controlling regular comms have been compromised.

    For me personally it was a fun time to host last exercise. I’ve learnt a lot by planning and executing it. It’s a great way to see radio equipment, antenna placement, radio etiquette, role assignment and information integrity come together and see where things start to fall apart by doing so and try to improve on that for the next exercise.

    If you like what you just read, please pay them a visit: https://drco.nl/ (Dutch)

  • 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:

    1. A cron-job is active that schedules to check email over Packet radio every 30 mins.
    2. You are sweeping the bands or just scanning.
    3. The cron-job fires and runs a Python script that prepares the radio.
    4. All current settings and VFO-positions are stored in memory
    5. The radio is now set in the mode and frequency for use with the soundmodem that is required to check the email
    6. The Winlink is doing the email check and perhaps some other Packet stuff is being performerd, depending on your needs
    7. 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
    8. Your radio continues doing whatever it was doing right before the cron-job fired to check emails.
    9. 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
    10. 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)
    11. 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

    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)