I’ve had a production unit of the Xiegu X6200 since June of this year and have made several field reports using it for both SSB and CW.
You may have noticed, though, that I haven’t used it much in the field since June.
The reason? I’m primarily a CW operator, and the original firmware had some frustrating CW keyer timing issues.
These keying issues are most noticeable when operating in iambic mode, especially when trying to form letters like C, R, or K by squeezing the paddles. Often, when I try to send a “C,” as in “CQ,” the keyer produces a “B” instead. If you’ve watched any of my previous X6200 videos, you might have seen this happen a few times.
After some time using the radio, I can adapt and reduce the miskeying, but it still happens occasionally. I suspect part of the issue is related to the keyer timing in relation to the transmit/receive switching.
While these keyer issues aren’t severe enough to prevent me from completing an activation, they are certainly annoying.
As I’m reviewing the X6200 (thanks to Radioddity for the extended loan!), I reported the issue to Xiegu back in May and hoped the first firmware update would address it.
The first firmware update, Version 1.0.1, was released in early August. There was an earlier release, but it was retracted due to other issues.
I checked the release notes and didn’t see anything specific about CW keyer timing in the long list of fixes. I had hoped another update would follow soon, but none has been issued yet. Meanwhile, several readers and subscribers have asked me if the keyer issue was resolved.
I decided to update the firmware and take the X6200 out for another field test.
If you follow QRPer.com daily, you may have already seen the spoiler alert: unfortunately, the keyer timing issue was not fixed in this release.
Still, I had a great time squeezing in a quick activation with the X6200, and I thought I’d share the video and a mini field report with you now!
Pisgah National Forest (US-4510)
My wife and I were out while one of our daughters was in Shakespeare rehearsals in Mills River, NC on Friday September 6, 2024. We had a number of errands to run, but my wife kindly worked with me to carve out 30 minutes for a quick activation.
The most convenient POTA location was the Sycamore Flats Picnic Area in Pisgah National Forest.
By mid-afternoon, the park was busy, but most of the picnic areas were open, giving me plenty of options for setting up.
With limited time, I turned on the camera to start my real-time, real-life activation video and got straight to work.
Since the X6200 has a built-in ATU, I decided to use my PackTenna End-Fed Random Wire, as it’s quick to deploy with its 31’ long radiator—any nearby tree would do.
Next, I paired the X6200 with my BaMaKeY TP-III, plugged in the antenna, and found a spot on the band to start operating!
Time to POTA!
Gear
Note: All Amazon, CW Morse, ABR, Chelegance, eBay, and Radioddity links are affiliate links that support QRPer.com at no cost to you.
- Transceiver:
- Xiegu X6200 via Radioddity (Save 5% off purchase amount when you shop with our affiliate link) and via Amazon.com
- Key:
- Antenna system:
- Other accessories:
- Camera:
- DJI OSMO 4 action camera with Joby Telepod Sport Tripod
On The Air
After tuning up on the 20-meter band, I spotted myself and started calling CQ POTA. Fortunately, hunters quickly responded.
In just twelve minutes, I logged thirteen contacts. Thanks to all the hunters!
My activation was brief, and I was so focused on making contacts and packing up that I forgot to take any photos of the radio in action. I’ve included some screen captures from the video instead.
I did manage to take photos of the logs:
QSO Map
Here’s what this five-watt activation looked like when plotted out on a QSO Map:
Activation Video
Here’s my real-time, real-life video of the entire activation. As with all of my videos, I don’t edit out any parts of the on-air activation time. In addition, I have monetization turned off on YouTube, although that doesn’t stop them from inserting ads before and after my videos.
Note that Patreon supporters can watch and even download this video 100% ad-free through Vimeo on my Patreon page:
Click here to view on YouTube.
CW Keyer Timing
As I discovered during this activation, the CW keyer timing issue has not yet been addressed in the firmware update.
After returning home, I made some notes and reached out to Xiegu to confirm that the CW keyer timing is still on their radar. They assured me that it will be addressed in the next firmware update. I’ll definitely test it and let you know once it’s resolved, so stay tuned!
If you’ve already purchased an X6200, I’d love to hear your thoughts about this all-in-one radio in the comments!
Thank you
Thank you for joining me during this short activation!
I hope you enjoyed the field report and my activation video as much as I enjoyed creating them!
Of course, I’d also like to send a special thanks to those of you who have been supporting the site and channel through Patreon, and the Coffee Fund. While not a requirement, as my content will always be free, I really appreciate the support.
As I mentioned before, the Patreon platform connected to Vimeo makes it possible for me to share videos that are not only 100% ad-free but also downloadable for offline viewing. The Vimeo account also serves as a third backup for my video files.
Thanks for spending part of your day with me! Have a brilliant weekend!
Cheers & 72,
Thomas (K4SWL)
Hi Thomas!
Thanks for the report and the video.
Sad that Xiegu have not sorted out the CW keying. They have just released new firmware for the X6100 (1.1.8) and now there is also a CW keying issue. Some of the elements are stretched very long and sometimes dits are dropped.
The problem is in the “base” part of the firmware. Base version 1.1.6 is fine but 1.1.7 and above has the issue. I am now running the latest “APP” version, 1.1.8 with older base of 1.1.6 and that works fine.
As a matter of interest the issue in not just with the internal keyer, it does the same with an external keyer so it is in the operating system timing. Think the process is not running with a high enough priority on the Linux OS.
Thanks for your blog and videos, love them!
72 from dark Africa,
Rudi de ZS6DX/ZS2M/ZS1BT/V51VE
They probably have a backlog of work to get through completing the next firmware release for the X5105……..in my dreams !
It’s terrible that such an expensive radio does not have debugged firmware and that prevents it from being used for basic purposes. The solution would be to use an external keyer or a straight key.
Those of us using old-time single paddle Morse keys might not have had an issue. I am too old to learn a new way to operate CW. How many single paddle users exist?
I do think with a single-lever, keying accuracy would, overall, improve. That said, I think some of the issues stem less from Iambic operation and more from some latency in how the software handles keying. For example, there’s a lag when forming a “c” normally at the beginning of an exchange or message as if the software can’t quite keep up with the Dah-Dit-Dah-Dit.
I love using single lever paddles, I just have so few of them. 🙂 They’re still quite popular!
I agree, the issue is latency. I tried changing the process priority on the X6100 (“nice” value in Linux) and it made a huge difference as more CPU resources are then allocated to the process decreasing the latency to the point where problem was a lot better/almost gone. On the 6100 the problem was there even with a straight key so it was not the internal keyer software causing the issue but rather the process that actually keyed the hardware to form the dots/dashes. This is part of the BASE (operating system + device drivers) system and not the APP that contains the iambic keyer.
I also love single paddles! My favorite is my Kent single lever.
I am delighted to learn that users of single-paddle Morse keys still exist among this great group. My favorite is an Automc (spelling) that was made for a few years in the early 1960s – bought from the factory about 1961 or 2. Used it with a vacuum-tube keyer that I built. Later, built a solid-state keyer using RTL chips! After a long wait, I just received a Kent single paddle – will give it a go as soon as I get a connector on it. James N8TT
Follow up on my post above.
I just installed the latest (1.1.9 APP and 1.1.8 BASE) firmware on the X6100 and the CW keying issues have been sorted out! That along with the improvements on the RX side and more visible colors makes it a worthwhile update.
Hopefully there will be a firmware update for the X6200 soon that solves the CW Keying issue. The code for the 2 radios is very similar.