DXCC 325 : North Cook Islands in the log

Finally, most wanted #68 now in the log.

Never had the possibility to work E5/N but this morning E51MWA was workable in FT8 on 7 Mhz with my OCF @15m.

Flexradio microphone doesn't work

Some days before the biggest SSB contest of the year... some testing ... some issues...

Problem :

- Microphone doesn't work when DAX label is on. DAX must be on to let N1MM+ send audio to the Flexradio.
- Microphone works when DAX is off.

Solution : Go into the Radio Setup screen, Phone/CW, and activate the "PTT override" buttom.

Problem solved.  Easy and logical but you have to know it.

Furthermore, do not forget to correctly configurate N1MM+ in case the output of the voice signal needs to go to the transceiver : 

Config ->  Logger+ audio Setup -> Playback -> "DAX TX" (and not the standard speaker).

Received gift from a good friend

 Wood on wood made by a CW-Guru:  100% craftmanship !

10 Band DXCC formalised

 

ON4CCP back on the air

This comes after years of using OT1A almost exclusively, with ON4CCP only being used to make a few test contacts in FT8 at 1W output power.

Why ON4CCP?

I've noticed that in major contests, using OT1A with low power is not always ideal. In heavy pile-ups, having a longer callsign can also be an advantage. There are many similar callsigns to OT1A (OT2A, OT5A, OP1A, OE1A, OK1A, etc.) that can cause confusion. When someone copies Ox1A, there are simply too many possible interpretations. But when someone copies ONxCCx, there is a reasonable chance that it will eventually lead to ON4CCP.

However, ON4CCP was no longer included in the master list of callsigns frequently used in contests. So I decided to reactivate it. I've already used it in the recent Worked All Germany contest and in the weekly OK1WC Memorial contests. In the meantime, ON4CCP has made it back onto the master list.

The question now is whether I'll use this callsign in this weekend's CQWW SSB contest or stick with OT1A, in the SOSB LP20(A) category.
Last year, I achieved a top result on 10 metres with OT1A. With the Yagi on 20 metres, I should be able to achieve something similar.

So I'm still undecided about what to do this coming weekend...

CQWPX 2026 CW with OP0HQ : First place worldwide and new European record

 

Flexradio 6400 crashes after succesful upgrade due to bandswitch

It has always been my weakness: the fear of updating a working system with a complete lock-up as a possible consequence. For this reason, until this weekend I was still running SmartSDR v3.1.11 on the Flex 6400, while the latest version is now v4.2.20.

Due to the many crashes this weekend during the CQ WW WPX CW contest—crashes that are known bugs when N1MM+ strings are broken down too quickly in CW—it became clear that it was time to change versions.

When the pain of crashing during a contest becomes greater than the fear of no longer getting the transceiver to work, that’s when you end up doing an upgrade.

All the more so because the latest version includes a complete overhaul of the DAX and CAT control software. For those unfamiliar with FlexRadio, this may sound like Greek, but those who do know it understand that these are crucial parts of the system and the interface with external programs.

Since I have never used my Flex via the internet—only locally via Wi-Fi, never remotely over WAN—I wanted to make sure that my details in the central database were correct, to avoid suddenly being forced to purchase a new software version. To be fair, when I opened a trouble ticket with the Flex helpdesk, the response came extremely quickly that everything was in order, and the upgrade instructions were clearly explained again. We are not used to this kind of performant helpdesks in Belgium; perhaps that’s where part of the hesitation came from.

So, following FlexRadio’s recommendation: remove all old software, including all drivers, from the computer and install the new software. To my surprise and relief, this went without any problem. Next, the transceiver itself is upgraded from the PC. That also went remarkably quickly and smoothly.

The software even seemed to run immediately. N1MM+ appeared to work, and WSJT took over without issues.

Until I switched bands from 20m to 40m. Crash! Transceiver rebooting, software disconnected. And this happened repeatedly, with no way to get it running again.

Knowing it was the middle of the night in the USA and therefore no helpdesk available, I searched online and found that this error had occurred before (also to the great frustration of users). The only option seemed to be a factory reset. After looking up how to do this—and accepting that all parameter settings would be lost but the transceiver would at least start again—I performed the reset, and everything is now working as it should.

It remains a rather special concept: a radio packaged as a black box where there is little you can do except press the power button.

But I remain an absolute fan! And you can rely on the helpdesk, because they even replied later to my message about the crash. Now let’s hope everything stays stable, and that we don’t end up in a situation like SteppIR, where FlexRadio suddenly goes in a military or other commercial direction and abandons the amateur radio market.