EU rocks!

I'm currently travelling in Europe. Lifestyle changes after early retirement means I have less time for Ham Radio (especially given a recent argument with another contester). Life is too short for such petty things. Maybe I'll come back when the novelty of retirement wears off.

PS The majority of Scotland voted to stay in the EU (myself included). Unfortunately due to the larger population density in England, the Scottish vote was ignored and the UK left the EU. Now with Trump's and Putin's nonsense, I can see my instincts were correct and that it is important to face despots and tyrants together, in as large a force as possible AKA the EU!

At least I can still get out of the UK temporarily, enjoy!

MM3T ARRL DX CW 2026

Absolutely shocked by the behaviour of a well known, experienced English contester. He sent an email to me during the above contest with all sorts of allegations including LID, poor operator, DQRM etc etc even although he was using a wire doublet and I was using a monoband yagi beaming in the opposite direction on 10m working stateside? He seemed to be suggesting that in no way was it possible that I could not hear him as he could hear me and therefore I was DQRMing him. There was no reasoning with him and I gave up trying to defend myself as he simply was not interested in anything I had to say.

For those of you that understand antennas and propagation, is it more likely that between England/Scotland that accidental same frequency operation (10m band) could happen rather than DQRM? 

The level of abuse and outrageous accusations continued even into his post match contest report. I can only conclude that this man has omitted to take his medication and is in the middle of some kind of life crisis where better judgement would have had him to simply QSY?

When a contest operator selects to use a doublet antenna for 10m he should expect other close in (inter-G) operators not to hear him and immediately QSY when the inevitable QRM occurs. Despite being in the unassisted category, mid-contest, this operator was encouraging me to check the cluster to prove his frequency occupancy rights and was demanding me to QSY via email? Surely this is grounds for disqualification?

I have decided to just forget about the incident and not let this experience deter my interest in contesting or ham radio. However, I hope that the operator in question has now reflected on the incident and his resultant behaviour and feels a twinge of embarrassment.

 

Moonraker Titan CB Review of CW mode (New Version, v2)

Moonraker TITAN CB in CW Mode

Introduction:

There are plenty of reviews written on this tiny transceiver and most of them cover AM/FM/SSB operation etc, so I won't bore you by repeating that easily available information. Instead I'd like to talk about this transceivers CW capabilities. In the past I have bought and tested most multimode CBs with CW mode over the years and in short I have been sorely disappointed. Not only was the rx/tx performance bad (as expected at this price point), but the designers understanding of what is required to make the radio useable in this mode was flawed. I did try and point out all the flaws of the Lincoln II+ in CW mode to President Electronics, but CB radio magazine and most other users seemed to fob this off as "what do you expect from a CB?". My point was that if it advertises CW mode, why shouldn't it be as useable as FM or SSB modes?

Receiver:

So enter the Moonraker TITAN (new version) CB. The receiver isn't as selective as a ham radio receiver (as expected) and on hooking up to an external YAGI antenna blocking was immediately obvious. Any presence of a strong signal would cause a hole of silence in the receiver about 1KHz in both directions. However this radios receiver is sensitive enough and if used with small mobile antennas, should perform satisfactorily enough on non-contest days.

In every other CB until now, one of the major usability failures is that CW mode appears as DSB (Double Side Band) where every CW signal has an upper and lower image signal. This means as you tune around the band you hear every signal twice, which leads to confusion of where you need to tune to actually work a station. In ham radios you can select to hear either sideband (UCW or LCW) but not both at the same time (which would be nuts right? This needs to be explained to most CB manufacturers).

The Moonraker TITAN is the first CB to implement UCW as opposed to DSB. They have managed to suppress the unwanted sideband image, so you only ever hear each station once and its always the upper image of a CW signal. The designer needs to be congratulated on being the first to market with this implementation for CB. Its not perfect as LCW capability is missing and there is a non-adjustable offset of 1KHz between carrier and CW tone (normally 600Hz or so is used dependant on operator). Not having LCW is fine as UCW is predominantly used, but the designer may not have realised that this feature is also used by hams for interference mitigation, where an operator can remove unwanted signals by switching between UCW and LCW to put the unwanted signal outside the filter passband. The 1KHz fixed offset for the CW tone is too high for comfort and easy listening, but it isn't a deal breaker. The TX CW sidetone from the radio is 1KHz, so you tune the wanted RX signal to be the same as your TX sidetone in frequency, then you know that when you transmit, the other station will hear you....easy! 

To help you make that first contact there is another first! This radio has adjustable passband filtering all centred around the +1Khz position away from the carrier frequency. These are as follows: 

CF1 Wide -1.8KHz to +1Khz so 2.8KHz width in total

CF2 Narrow -120Hz to +240Hz so 360Hz width in total

CF3 Mid -300Hz to +340Hz so 640Hz width in total

Note the odd ordering of the above filter width selection.

My advice is to find a station using wide CF1 and tune till it till the audio matches your tx CW sidetone frequency (1Khz), then switch to mid CF3 if you were near 1KHz audio frequency before the signal will be there, if not re-tune, then switch to the narrow CF2 filter position. With a bit of practice you will be able to net correctly onto a stations frequency and the signal will appear in all filter selections. The order of the filter width is a bit unintuitive, but hopefully a firmware upgrade will re-order these filter selections according to passband width and make then a bit easier to access. In narrow CF2 position, if you can hear a 1KHz tone CW signal there is a good chance you can work it!

The radio tuning works in two modes Channelised or VFO.

In Channelised mode, the central large tuning knob is used. The radio jumps around in 5KHz steps with the large tuning knob and the smaller CLA knob can be used for an adjustable offset tuning value. Annoyingly any deviation in frequency from the initial channel frequency caused by using the CLA knob is remembered until the radio is reset (by changing the band 10/12/cb/HF etc). The offset is retained through simple power on/off. This is common to some other CBs and is a pest, but not a problem in my opinion.

CW is best used In VFO mode (10m band only, rotate Band knob until UF displayed above frequency display), the smaller CLA knob is used exclusively (The large tuning knob does nothing). For me this is preferable to channelised mode as the retention of offset frequency is gone. Another marker of a decent radio is that when the frequency is changed by one click of the CLA knob, the audio doesn't momentarily vanish like changing the channel on a conventional CB (President Lincoln II+ take note). The CLA knob works better than the main tuning knob which has the age old problem or random up/down movement in frequency when rotating in one direction (firmware sampling of analogue switch, lack of de-bounce logic). 

Transmitter:

There is a delay between hitting the CW key and the radio going into transmit and the emanation of the sidetone. The result is very confusing for the operators brain who must ignore their ears and independently rely on their hand movement to control sending (I do not have this capability!). One hack may be to use a key with an independent immediate sidetone (not the laggy radios) and try to only listen to the keys sidetone whilst sending.

The time for the radio to unkey is also slow and so in contest situations you would most definitely lose the first second of any response. This isn't a deal breaker in my opinion as most people will use this type of radio for casual operating only.

Looking at the output CW signal on the bandscope of an FTDX101D shows some distortion on the initial sent CW element, but again this isn't unexpected for a CB.

Summary:

This is a massive step forward for the RX implementation on CW mode from any other CB on the market today. Don't get me wrong, the radio still ain't a ham radio by any stretch of the imagination, but for £125 this is now a great deal for CW operators wanting to monitor the bands and make an occasional basic CW contact. The designer needs to be congratulated for the first improvement in CW mode for CBs ever!

Doug (GM0ELP)    

MM3T in Russian DX Contest 2025

 What is it with extreme prejudices against the contest community in the Ham radio hobby? 

The experience from my side: After an hour of calling CQ in the contest I suddenly get QRM'd by an Italian sounding station with no callsign telling me to QSY. I asked for a callsign, but instead I got abuse "change the record" etc. A second station came in and QRM'd me during a Q, stopping me hearing the exchange of a russian station, I asked several times for a callsign and eventually I was given SP7CDG, he gave me his callsign only after me specifying I would not be QSYing for a pirate station. After 5 mins of solid abuse deliberate QRM, insults, including (I am ashamed to say) a Scottish voice who came on accusing me of being rude!? This station gave no callsign, but again wanted me to QSY. After 10 mins of solid deliberate QRM I had to cease operating.

Why didn't I immediately QSY I hear you ask:

1) My frequency for over 1 hour.

2) I am a contester and as such I am now immune to abuse and deliberate QRM.

3) I do not QSY for pirate operators without a callsign.

So later on still angry about the experience, I find out that 3D2TWO decides to do a split operation on 10M SSB on the 16 March 2025. Is he a lunatic? Did he not think of looking up the contest calendar before he started? One of the biggest contests in the contest calendar (only  the Russian DX contest!) is in full swing and this guy guy decides to start up a split operation in one of the busiest segments of 10m 28.488.5MHz (i.e. my frequency).

Although 3D2TWO has every right to start up on my frequency (as we both couldn't hear each other) this does not give frustrated stations who want to work him the right to deliberately QRM me and throw about abuse and insults and demand me to cease my operation. This is a sorry state, where new uneducated operators think that ham radio should stop for dxpeditions.and deliberate QRM and not giving a callsign is justified.

For shame Poland, Italy and Scotland

GM0ELP/MM3T

Yaesu Spectrum Scope Averaging Solution

 Here is the problem:

There is no problem, ICOM users are the problem.

Here is my solution:

ICOM has trained your mind to expect a beautiful (granted), unresponsive, low resolution, slow, piece of garbage that is only suitable for SSB use. You need to realise Yaesu have given the amateur world a functionality upgrade. If you are interested in looks over functionality, buy an ICOM.

Here is the thinking:

Start by correctly adjusting the gain level so it isn't spikey.

If you don't like fast, accurate (spikey) spectrum scope, minimise the spectrum scope and maximise the waterfall.

If you are a CW operator you will enjoy being able to visually decode CW on the Yaesu waterfall.... In the fast 3 setting, you can decode useful CW speeds.

Also, if ICOM truly had the performance of Yaesu's spectrum scope, but chose to average it to make it more "beautiful", why doesn't the "averaging off" button on the ICOM allow you to decode CW visually as well as a Yaesu?

While we are here, please don't think I condone the Yaesu 3D spectrum scope. Those that think that puppy is useful might as well go buy an ICOM. Yaesu 2D spectrum scope rocks if you prefer functionality over looks.

Just sayin

Learning Morse Code

 Never ask anyone that knows morse code how to learn morse code.

They have forgotten and will give you garbage based on theories that presumes you already know the alphabet in morse.

The first thing you must do is  remember the code. All other advice comes after this initial step.

MM3T IOTA Contest 2023

 I had heard that Gordon MM0GOR (MM1E) was off to the Isle of Man as part of MD1U effort, so I thought it would be nice to keep the Isle of Bute activated for the contest.

Unfortunately the RSGB has got involved with politics again, last time they thought they knew better than the CMO and felt they had to play about with the rules for COVID.

Now the RSGB wants to get involved directly with world affairs by disallowing Russian and Belarus radio hams to compete (check logs only). Maybe its just me, but I thought that politics was a no go subject for radio hams to discuss on the air and that an important part of amateur radio was to extend the hand of friendship and break down any perceived differences through communication. This stance seems to have been lost on the men and women that are currently running the show at RSGB HQ especially in the contest committee.

Lets just keep ham radio a friendly place for like minded people despite the crazy world around us.

Anyway, back to the IOTA contest. As I blogged earlier during COVID, I'm always at an alternative location other than my home address for the IOTA contest dates, the RSGB stopped me competing even from my own holiday house (EU5) during COVID. Personally speaking I'm now so disenchanted with the IOTA contest and the way it has been run, I missed last year completely and I was also going to boycott it this year due to its world affairs stance, but in the end I made a last minute decision to go across to Bute and air MM3T.

This year due to lack of enthusiasm, I went light with a QRP entry. This was a mistake. In past years the fun factor was definitely affected due to wire antennas, compromised setup, uncomfy operating  positions (car/tent), poor condx and low power. The less effort I made the less fun I had. Over the last decade I have been looking for that perfect effort to fun ratio and I had learnt that the K2 with 100W and an aerial51 light weight off-centre fed dipole on a 12m spiderpole was the sweet point for me. Verticals are pointless from Bute as DX interest in IOTA is sparse compared to EU and there is hardly any clear sea path to anywhere from any point on Bute. High angle radiation takes advantage of being on EU123 and working back to EU5 for maximum point advantage. This year I forgot all those lessons and went QRP with 5w from an Elecraft KX3 to an EFHW in an inverted L format. The results were very predictable, lots of running with very few answers.

I have a contesting weakness in that I enjoy running and hate search and pounce. The reason for this is when I listen to some other operators whilst enduring S&P, their inefficiency is astounding. I get very impatient and end up shouting at the radio in frustration. These inefficiencies are well documented on this blog so I won't rake over that again. When I'm running, I take great pleasure in rattling through a pile-up in the most efficient manner possible. People in the past have commented on my operating style as "rude", no pleasantries, minimalistic and efficient. When a station goes into the noise, I don't ask for repeats I just drop them and carry on. When a station asks for my call I just call CQ again. When the pile-up intensifies my speed goes up to roll off the slow ops and as it becomes sporadic my speed goes down to aid copy. Its a joy to be in control. Listening to others they will hold a 10 deep pile up asking for repeats and struggling for minutes to complete a Q.... crazy, and I seem to always tune onto them just as they start to work someone playing QRP and running 1mw into a coat hanger.... "again again G8 again". I do understand that search and pounce is necessary for the score, but i find it an absolute chore. This maybe because I am not a dxer, I do not collect QSLs and I don't have a per band DXCC country interest. I'm therefore really poor at search and pounce. Also I hardly ever use the cluster as having someone else point you at the DX kind of makes it too easy, its like going fishing without a rod and someone else handing you their rod after hooking a big fish and letting you reel it in... pointless.

Anyway EU123 was on the air until I worked GM7M who had 5x my Q total after only 4 hours. I decided that EU123 was being well aired by that team and that QRP wasn't for me. I did notice an increase in stations asking for the report again and got the feeling they were expecting EU5 and when they got EU123 they needed to confirm....that's what I get for missing a few years IOTA.

There was an extra incentive to pack up, after struggling for 1.5 hours to get the antenna up on the beach, I slumped (sweating) into the shack/driver seat switched on the radio only to hear "brrr brrr brrr brrrrrrrrrrp" repeating over and over at S9 on every band. And no it wasn't all the clangers on .073 it was some other crappy data nonsense. I then noticed a roadside connection cabinet, so probably some kind of botched cable joint or termination. I seriously considered just accepting this bad luck and working round it, but after coffee I worked up enough energy to swing the top horizontal section of the inverted L round the beach to minimise the interference. I got it down to S3 and tied it off there just in time for the contest start.

Of course I started running first and got very little interest. Its always depressing when a caller comes in on 40m from EU5 (G4IRN) at well over S9 and then nothing.... How can this be, surely there are 1000s of keen EU5 stations searching for elusive IOTA multipliers.... the answer to this today was apparently: NO. If the Radcom "The Last Word" is to be believed and most 80m conversations, most UK operators are anti-contest. The opportunity is there to have a lot of fun collecting all the IOTA offerings round the UK and being extremely competitive, but it seems to be trendy right now to hate contesters and try to insist on have nets and chatting about tomatoes and illnesses through some really cool contest activities. Its frustrating when you go to a lot of effort to activate an island so find the band full of strong signals all disinterested in even giving contesting a chance. The amount of negativity and moaning I hear mostly on 80m SSB from the anti-contest brigade is astounding.... and nothing may I add is being done by the contesters back to this negativity (there exists a gentlemanly silence). It would be nice to hear one of these "all I heard was "CQ contest" and I just reached for the off switch" conversations on 80m and someone to stand up to them and say "well I don't agree, do you know becoming more informed in contesting could better your home station, do you know you can become a better operator, did you know your topics of conversation don't need to be about gardening".

With antenna and radio packed up I headed home through Bute Fest at Ettrick bay to catch an early ferry home. Note to self, never do QRP again with a poor wire antenna in a compromised location. 

No Test? Why?

 Yet again I came across this strange behaviour. A special event station operating in cw during a major contest and taking the time to send "no test". Why do this? Surely the point of running a special event station is to make lots of contacts? Why not just add a 3 digit number to each QSO? You don't need to be interested in the contest and you don't need to register or buy a ticket to enter. You don't need to send in your log, or be super efficient with each qso, but you can make a lot of people happy, and who knows you may even have fun... god forbid? With all that said there will always be the type that feel they need to make a point... "no test".

I have listened and read a lot of real hate towards contesters in recent times and there is very little fight back from contesters. There seems to be no space in the hobby, frequency limited, band limited, weekend limited, it isn't enough for some. The trouble seems to stem from operators who think they "own" a frequency for a regular "net" or bandplans with recommended frequencies for centre of operation for a specific mode like SSTV. When a contest 'intrudes' on these frequencies, non-contest operators feel violated and deliberately QRM the offenders, hardly the ham spirit?

I could be cruel and say I've learned more from an episode of East Enders than I have heard on these "nets". Each to their own, I'm not interested in talking about tomatoes, my health or my audio or how to work my radio (RTFM), am I going to complain about the rubbish these "rag-chewers" talk, no, we are all hams together enjoying our own version of the hobby.

MM3T in CQWW CW 2022

 I soooo much wanted to use the Flexradio 6500 for this contest just to justify its purchase, but in practice sessions before the contest I could not get SO2V, semi SO2R or 2BSIQ to work with N1MM+. The problem was that there are so many guides written for old versions of both SSDR and N1MM+ and the wrong version of radio (ie 6700 or 6600) that only confusion and wasted time results. I tried setting up 2 slices on the same band but annoyingly if I clicked with the mouse on the screen N1MM+ would crazily swap the audio to the wrong VFO meaning I just couldn't use it. After a week of reading every available guide I finally gave in having never been beaten by anything radio/computer related in nearly 40 years.

I packed up the 6500 and instead switched to using my trusty FTDX101D. The difference was instantaneous, I was playing radio rather than fighting interacting software with different authors. The added benefit was that now I had a hope of dealing with ridiculously poor signal quality from the likes of Todor LZ4TX.  Todor hasn't yet realised that with big antennas and big power comes the added responsibility of ensuring a CLEAN TX. On 10m Todor is around 599+30 here but the big problem is the width of his transmission which during the last YO contest reached 25KHz wide on the FTDX101D effectively wiping out 10m. A quick internet search revealed that he uses an Alpin 200 (2.5Kw) linear amplifier and a 7 element yagi on 10m. I guess he hasn't read the manual properly and doesn't know driving it full tilt will cause problems.

Anyway with the 6500 safely packed away , I finally got down to selecting my entry category. I'd have loved to do a 10m mono band entry as 10m was in great shape, but Todor could show up and with the resulting 25KHz of key clicks and QRM I would have just had to pack up. I've always dreamed about activating a rare island and experiencing handling big pile-ups and really enjoy short, snappy efficient Qs and trying to get the run rate up. I would be working right up to Christmas and was involved with trying to deliver a new product in a stressful environment so didn't want to completely knacker myself for Monday morning. The 'classic' category being only 24 hours would help and also would ensure high run rates. I wanted all bands to be able to move according to the conditions. No cluster was allowed, but I intended to RUN RUN RUN anyway to see how many Qs I could make. This doesn't make sense if I was trying to win the contest as you need to S&P to get multipliers, but this wasn't going to happen anyway as there are too many retired contesters who have invested in their properties and antenna farms and can therefore run with substantial pile ups for the full 24 hours no matter their skill level. I've listened in to some of my competition and the amount of inefficiency on show should really relegate them into obscurity, but their station always secures the result. With this is mind and my pip-squeak scaffold pole in the garden, I decided to have fun and train for pile-ups instead.

I would be using an Optibeam OB10-5w wire, 5 band yagi (2-3 element on 10m, 2 element on 15m. moxon on 20m) at 5m over the ground. I live in a residential area of a large town and have close neighbours who have been very patient with me over the years. I want a bigger station, but in reality I'd have to move to larger premises to achieve it. At 5m over the ground, if my antenna were to come down the wrong way it would still land in a neighbours garden, so I'm already pushing the envelope. My garden resembles a long strip of land with the house in the middle, so I can just about shoe horn in a straight 40m length from the back garden over the house roof to the front garden. The antenna used for this location was an 80m doublet fed with 300 ohm ribbon feeder but due to the centre proximity to the house bedrooms, I wouldn't be able to use it late at night.

The back garden support for a doublet leg is a 5m light weight aluminium pole. I decided that this could double as the initial vertical section for a centre loaded  quarter wave inverted L for 160m. I designed a coil that would give me the correct inductance that when coupled to the top of the pole and then extended with a 10m wire section would be resonant on the 160m band. The resulting antenna was a real inefficient mess, but I hoped it would allow me some contacts with some of the bigger stations.

The stage was set for an all band effort and with my category picked and strategy decided for me, I got ready for the contest.

The contest started and Todor was no where to be seen (result!), but 10m wasn't in such good shape as it had been during the week lead up to the contest. I operated for 24 or the 48 hours and made 2430 Qs (around 0.6 Qs per minute), peak rate was around 130 Qs per hour on 20m.

The dirtiest signal encountered belonged to DP9A. They moved onto 14.042 at 08:00 (1KHz above me) and instantly wiped me out. I QSY'd up and asked them to QSY (ignored) then later on I asked them to check their linear amp, but just got ignored again. With my run frequency smashed I had no alternative to give them my frequency. At 6KHz wide key clicks, my radio (FTDX101D) just couldn't do anything to allow me to continue on my frequency. A quick look up of the internet on their callsign (DP9A - Callsign Lookup by QRZ Ham Radio) revealed another superstation. Why oh why do they spend so much money on antennas and ignore their transmit IMD? I think we all know why... they are cheats, plain and simple. It is advantageous to make make your transmit signal as dirty as possible to punch a hole in the band where your receiver can survive all the other stations trying to compete. The result is a lovely clear frequency to pick up rare multipliers. It must be fantastic to operate during CQWW CW within a 6KHz window clear of QRM unheard of to most competitor actually playing by their license conditions. Maybe the Bavarian Contest Club can educate them before they do too much damage to the clubs reputation.

Cw contesting and sending /QRP at the end of your call... just don't do it!

 There is no such thing as /QRP.

In a contest its all about efficiency, why in the world would a contest operator want to know you are running QRP? In my 30+ years of contesting I have never written /QRP into my contest log. When someone sends this, I always send back the proper callsign without /QRP. You would think this would be a good clue that he is regarded as a poor operator when no one ever acknowledges the /QRP he sends.

The type of person that normally does this is always sending slow and will repeat this nonsense twice to ensure you get his pip-squeek signal. The effect is normally to slow the contest operators Q-rate and maybe lose other waiting stations due to the length of time it takes him to complete the Q.

If you want to play games during a contest like turning your power down to mW level, please try to at least be efficient with the exchange:

a) Do not sign /QRP

b) Do not repeat your callsign twice ...ever

c) Do not stick in another TU because you want the other op to know you are very grateful, they will not thank you for it.

IOTA 2022 experience using Flexradio 6300 and v3 SSDR (multiflex)

 After previous years (since inception of IOTA) of hard effort (dxpedition to EU123) and then having the door slammed by the RSGB on any effort during COVID in 2021 (as I was on holiday in EU5 at my own holiday accommodation), I decided not to bother with the contest this year. Instead I would use it test out Flexradio SSDR multiflex capability. For the Flexradio 6300, this allows 2 ops to have apparently separate receivers (using the 2 available slices of the 6300) and also share the transmitter of the 6300.

I used a laptop running N1MM+ and connected to the 6300 using Smart CAT for frequency and mode for the log and also to emulate a winkey for CW transmission of N1MM+ macro messages. I also had a Flexradio Maestro, so I connected that to the 6300 so I didn't need to run SSDR on the laptop (to keep the load on the laptop to a minimum).

My fellow tester (MM0GBK) used a laptop running N1MM+, but this time used Smart CAT and SSDR software as his interface to the 6300.

Both stations were located in the same room and were connected to the 6300 via the same ethernet switch. I was using CW and MM0GBK/P was using SSB

Multiflex is automatically invoked by the 6300 when detecting multiple connections (6300 is capable of having 2 connections: in this case Maestro hardware and SSDR software running on a laptop). Transmission capability is allowed on a first come first served basis and the other connected user is 'locked out' whilst the transmission is in progress.

This type of operation is best suited to S&P which allows both users to search for unworked stations and then take turns at working them sharing the same transmitter. This worked perfectly during the contest and seemed to handle the occasional time we would both try to transmit at the same time (no power out indicated to the loser). Running leads to the other user having too little time between transmissions to find stations.

All in all zero lock ups were observed by both users however, cw generation via Smart CAT emulator wasn't well timed with occasional sidetone audio aberrations (not sure whether they were transmitted or not) even though an Intel i5 8 core was in charge without SSDR running (Maestro doing the heavy lifting). This led to me to think I'd be better off with a real winkey or some other keying method.

I would not recommend Flexradio, SSDR or multiflex to any serious contester due to rx latency, inaccurate cw generation, cost, hardware reliability, complexity, etc, etc, etc. However interesting the concept, it just took too long for the company to get it right and as a result has lost all momentum and user base (especially in CW contesting).

Currently the majority of Flexradio users are digital and SSB mode users. CW has never been implemented well, with the company mainly listening to the American full break-in casual ops instead of world wide serious contesters. Casual CW ops may like the Flexradio offering, but this should not be confused with serious contesting equipment.

FTDX10 headphone receive audio hiss problem and solution

 The FTDX10 is a great radio, but the audio through the front headphones socket is awful. Listening through the headphones, if you turn the volume to minimum there is an annoying hiss within my hearing range (approx 200Hz -> 12KHz). When the volume is turned up slowly you start to hear the real receiver noise come up, but you can still hear the false hiss above the real audio. If you keep turning the volume up the receiver noise then completely overcomes the false hiss, but the volume is now too loud for comfortable listening.

My problem is that I am predominantly a CW operator and am therefore only interested in sound <1KHz in frequency coming from the headphones (normal specification 20Hz to 20KHz). Non music, communication headphones (20Hz to 10KHz) help with this problem, but I couldn't find a pair of communication headphones that would get rid of the annoying false hiss from the FTDX10, suggesting that the false hiss frequency content was below 10KHz.

I thought about audio filtering solutions out there like Timewave DSP-599ZX or MFJ-751B but the last thing I wanted to do was spend more money on another box after shelling out over a grand for the radio. I also wanted to use the radio portable and wanted to keep any solution as simple as possible. I therefore opted to make one myself. I wasn't completely sure what part of the audio spectrum was causing my discomfort, but it was likely that an annoying hiss would be caused by frequencies above 1KHz and as I only needed frequencies below this for CW this seemed like a good target frequency to begin attenuation from.

Remembering that headphone audio is stereo, I would need 2 identical low pass filter circuits, one for the left and one for the right audio channel. Most headphone leads consist of 2 wires for each channel audio (L&R) each of which has an individual screen, but the screen is common from the 'S' part of a TRS (TipRingScreen) audio jack.

I wanted to be able to swap headphones but the keep the low pass filter in line, so the solution was to create a 15cm stub of audio cable terminated at one end with a male TRS audio jack (3.5mm male TRS audio jack in the case of the FTDX10) to go into the radio. The other end of the stub would be open wire for connection into the twin low pass filter circuit, the output of which would then go to a female TRS audio socket which my headphones would plug into. The picture above shows my headphones jack plug on the left hand side, the twin low pass filter circuit in the centre and the open wire end of the stub going to the radio on the right hand side.

The picture has enough detail to get the component values, but the calculation for the cut off frequency goes as follows:

f = 1/2 x pi x R x C

therefore

1/2 x 3.14 x 1500 x 0.1uF

= 1061Hz

Its only a single stage audio filter so the roll off is gentle as the audio frequency goes up, but it achieves total attenuation of the annoying audio hiss without too much wanted audio drop.

Remember, avoid directly grounding either of the audio channels to the screen. Please test with a DVM to make sure you haven't made a mistake before connecting to your expensive radio.

Try it, however you do so at your own risk. I think you will like it! 

FT8 and the death of ham radio as I knew it

If you are an FT8 troll then please just move on, this is not for you.

I've been a Ham radio operator since 1986 so you could say I'm an experienced ham radio operator in comparison to all 'FT8 only' operators. I know that I can get more contacts and get further using FT8.

Q) Why don't I use FT8 all the time then?

There is the potential for an exponential gain in pleasure and satisfaction through using other richer communication modes. I know 'FT8 only' operators will enjoy them more than FT8 because I have experienced FT8 and other modes with all types of setup ranging from simple to contest grade.

Q) Why do I hear other experienced hams using FT8?

They are using them only when conditions necessitate i.e. marginal conditions where you cannot properly hear any desired signals on the band. It's also tempting for an experienced operator to be lazy and switch off the brain and leave the computer to have fun whilst doing something more interesting instead. 

Q) FT8 can hear signals that other modes cannot. I can get further on a very meagre setup due to power, antenna, noise problems. Why therefore wouldn't I use this all the time?

Firstly due to lack of experience 'FT8 only' operators do not understand that if you can hear an FT8 signal with your own ears, you are in the wrong mode. If you can hear FT8, then you will be able to make CW contacts and listen to SSB signals. What percentage of FT8 contacts did you make where you couldn't hear any signal coming back (10%??). Most operators would not use FT8 all the time because compared to other modes its NOT a proper communication mode. A simple report is NOT communication, but 'FT8 only' operators wouldn't know this because most are inexperienced. Believe me an exponential gain is to be had by trying out ANY real communication mode.

Q) When I listen to the SSB or CW portions of the 10m band they are dead, but I can always HEAR FT8.

Join the club. It's frustrating isn't it? If you can HEAR FT8 it means the band is open for all modes. The vast majority of those using FT8 don't know this and through lack of education or shear laziness continue to use a weak signal mode even when conditions are excellent. It's not unusual for me to tune an entire 10m band and hear nothing except a solid 3KHz window of S9 FT8 signals and the entire beacon section bursting S9 with every country in Europe....and for the FT8 smart asses - yes, I did call CQ in both CW and SSB to no avail. Between 1986-2010 this was unheard of. So again take it from experience, FT8 has killed ham radio as I knew it.  

Q) It's a real challenge to get FT8 working correctly and there is a science behind getting good results

Bollocks. Most 'FT8 only' operators don't even understand how to improve the sensitivity/selectivity of their receiver. This is made painfully obvious by the majority of FT8 users who use SSB and 3KHz filters and inject tones into the transmit audio chain. Its odd that you strive for the best your meagre setup can achieve by using FT8, then use the general convenience of an audio based setup and ignore all the available facilities your receiver provides??? There is no way you should be using 3KHz SSB for these marginal contacts. DSP alone won't hack it when FT8 is being as misused as it is today (due to lack of strong signal handling performance). You should be using a mode that can select a narrow filter and the VFO to place the FT8 signal within the passband of the narrowest filter possible i.e. digital mode with 300Hz roofing filter, for increased signal to noise ratio. This is difficult to get right but yields better results in crowded misused FT8 band conditions. Which is it then? Just being lazy/uneducated or striving for the best for you meagre set up???

Q) Why don't you just get on with your hobby and not comment on mine?

Because we have a shared hobby (i.e. communication??? kind of infers more than one person???) and a lack of understanding by a majority of new operators therefore directly affects my hobby.

When a good skier chats to a novice skier and they tell you to stick with it because the hobby comes into its own if you persevere and get past the 'snow plough' technique, do you tell him to mind his own business, as you want to do the snow plough forever because its easier... no, probably because you've seen good skiers on the TV doing parallel turns and can see how awesome it looks you'll realise you would gain by making an effort to get better. Trouble is there is no equivalent in the ham radio world. The nearest we come is education (or elmering), so take it from me, if you are doing nothing but FT8 you are missing out on a lot of fun and also you are not contributing in a positive way to the rest of the hobby.

More and more lazy 'FT8 only' operators are joining the hobby and a lot of good 'all mode' operators are dying of old age. This is causing the death of ham radio as I knew it.

Please contribute to the continuation of ham radio by educating yourself in the use of your receiver and use other modes.

Yaesu FTDX101D FTDX10 Scope averaging solution

Before we start, anyone using the 3D feature of the above radios are beyond help, please just move along and continue to enjoy your radio.

For those who are sentient enough to realise 3D is just a gimmick and 2D is the only real display function, please read on... 

Problem:

Frenetic spectrum-scope? Can't cope?

Solution:

Dead easy! Use the waterfall rather than the spectrum-scope. Tap the waterfall until it covers 3/4 of the screen. The spectrum-scope is now too small to see any frenetic activity, job done!

I now think of this top sliver of LCD panel as a touchscreen for QSY only. There is absolutely nothing gained by looking at the spectrum-scope that isn't reproduced on the waterfall.

Now think of the benefits of having the fastest, most capable, most sensitive waterfall ever produced by the big three!

MM3T in IOTA Contest 2021

 I entered the all band, low, 12hr, cw, dxpedition category again.

The thing I shouted at the radio most:

I ONLY NEED IT ONCE!!!!

Why oh why do people give their callsign and/or report twice without a break in between? Doing this is for data modes only...under no circumstance ever do this in a CW contest....

no you are wrong...UNDER NO CIRCUMSTANCE! EVER! OK?

In CW mode there is a human at the other side and not a dumb computer! Guess what? If the operator didn't get your call correct the first time, he will send back what he got, allowing you to correct it...simple! This process of handing the exchange back and forth to get your call 100% correct is quick, efficient and infallible....unless of course you weaken and decide to send it twice without a break!

another thing...

If you are trying to bust a CW pile-up and the operator gives your partial call, you do not need to give your callsign twice without a break.

no you are wrong...UNDER NO CIRCUMSTANCE! EVER! OK?

Why? 

1) The partial call will cause the pile-up to abate and the operator will have a much better chance of getting your call correction first time.

2) You will lower the operators Q rate.

3) You may cause the operator to lose his frequency, due to having to pause longer than usual.

4) The operator may lose some of his pile-up as it now takes too long for satisfaction.

5) The pile-up starts to misbehave due to boredom as most cannot hear you.

Causing any of the above to happen to a contest operator will cause them to hate you and wish you had never called in....

You are confusing typical CW operator teachings of when to give your call twice like:

If his signal is weak..

If there is QRM

If there is QSB

If he didn't get it right the first time

ALL OF THESE ARE WRONG for contest operation as we now have to take time and efficiency into account.

another thing...

Please use a proper contest logger like N1MM+ and download SCP file and IOTA cross check file, this will save you from asking the operator to repeat the IOTA reference multiple times.

These are small asks compared to uplifting your entire station and temporarily setting it up on an island and doing without comfort and sleep for 24hrs. Please be willing to help that effort by being efficient in your exchange.

Remember, this is a CW contest...never, never, NEVER give your callsign twice without a break in between!

PTT in CW mode for cw contesters (where did it all go wrong for Yaesu, FlexRadio and TenTec?)

 At some point in the dim and distant past a radio designer who knows nothing about CW contesting decided that PTT via RTS over RS232 or a serial emulator cable was unnecessary. This decision was then used for all future radios, worst still other manufacturers then started to copy this mistake and soon a major problem was born.

There are so many usage factors for a ham radio that the manufacturers today have trouble knowing which groups to listen to i.e. casual ops, data ops, dx ops and contest ops.

Casual ops: If the radio kind of functions...what's there to moan about? Its fine.

Data ops: As long as FT8 mode works, and the rx/tx switching times are good, I'm fine.

DX ops: The rx performance needs to be good, I need all modes, as long as I can hear, I'm fine.

Contest ops: The rx performance needs to be good, the tx performance needs to be good, rx/tx switching times needs to be good, I need all modes, the ergonomics need to be good, interfacing needs to be spot on, filtering needs to be good etc etc etc.

In short if you want everyone to be happy, ask a contester as they are striving for the best.

However, serious contest ops are few and far between and there are all sorts of grades of contest ops out there from casual little pistol through to those who own super stations (big guns). Casual contest ops are not that interested in efficiency as they are not really competing, just having fun.

Anyway back to the point in hand PTT via RTS over RS232. Contest ops send macro cw exchange messages from contest logging software to the radio and also 'fill in' messages via the key. TX -> RX time is critical i.e. the release of PTT. The reason for this is that good contest ops are efficient and speed is of the essence, so very little time is wasted in a fast exchange between 2 stations, so much so, a casual listener may not be able to hear a perceivable break between the 2 stations. Serious contest ops use a computer to transmit their side of an exchange (now, now... if you don't agree, I am sorry you are not a serious contest op), this means the computer 'knows' exactly when the exchange message will end ahead of time. No other piece of equipment can know this information before the computer, so it can unkey immediately after sending the message. It therefore stands that the most efficient exchange can only be accomplished by the computer using RTS to signal PTT.

Now enter the radio manufacturer. They are ignorant to the above fact and decide that they will only provide PTT sourced from the radio. The PTT mode relied on here is called break-in which detects cw keying over DTR from the computer and then uses a controllable delay time after the last cw keying action to release the PTT automatically. Unfortunately this causes a delay after every part of the sent exchange where the radio remains in tx for the delay time despite no cw being sent over DTR. The result of this is a really inefficient exchange and many, many unhappy contesters.

It may seem like an little thing, but serious contesters are striving for the best and this kind of PTT implementation is unacceptable, especially when Elecraft, Icom and Kenwood seem capable of getting it right.

It doesn't seem like much to ask for from a £3000 radio and the inclusion of this basic expected functionality hurts no one else's usage case. Hopefully ham radio manufacturers want to be the best?

How to get Yaesu FTDX101, N1MM+ contest logging software and CW Skimmer software working together

My solution:

Hardware:

1) FTDX101D

2) AIRSPY HF+ Discovery

3) PC

Connect the AIRSPY up to a USB port on the PC and connect the antenna to the main IF out port on the rear of the FTDX101D. This will give the AIRSPY access to the 9.005MHz IF of the main receiver in the FTDX101D.

Connect RS232 serial com port of FTDX101D to PC (com 1 in my case).

Software:

1) N1MM+

2) SDR Console

3) CW Skimmer

4) VAC (Virtual Audio Channel, your choice of software)

5) Omnirig

6) Serial Port Splitter (www.fabulatech.com)

In the serial port splitter software, set up a "shared port" for com 1 (allows multiple software apps to connect to the FTDX101D for rig control and status information.

In the Omnirig software setup radio 1 as FTDX101D and use com1.

Setup a VAC for use between SDR Console and the CW Skimmer (ensure windows 10 doesn't grab it).

In the SDR Console software add the external radio feature and use com1 to get rig control from FTDX101D. You also need to add the CW Skimmer menu and select the appropriate VAC audio channel (no need to send on CAT info from SDR Console with this implementation as CW Skimmer will get it via Omnirig). Configure external radio feature by entering 9.005MHz IF details.

In CW Skimmer setup the audio to use the previously created VAC. Also set the CAT (Omnirig) to use radio 1 and com 1. Also setup network to enable telnet server telnet and port to 7300 to send out spot info.

In N1MM+ setup rig control to com 1 and telnet to 127.0.0.1 port 7300

This will allows both ways rig control between N1MM+, SDR Console and CW Skimmer to/from the FTDX101D. Happy skimming!

Doug GM0ELP

Your first HF CW contest

 Here are some handy tips and hints to remember for your first CW contest:

Running (calling cq)

you:    cq your call test

other:    his call

you:    his call 599 exchange

other:    599 exchange

you: tu your call

S&P (search and pounce)

other:    cq his call test

you:    your call

other:    your call 599 exchange

you:    599 exchange

other: tu his call

What could be simpler? Well it would seem the a certain country can't manage it. In S&P they like to do the following:

other:    cq his call test

you:    your call

other:    your call 599 exchange

you:    cfm 599 exchange

other: tu his call

you: tu

The 'cfm' is implicit and unnecessary and wastes the other persons Qs/min rate. During QSB you are guaranteed to hear CFM 599 ......... and nothing else promting you to shout "just give me the exchange!". The final unnecessary "tu" however is the real kicker as this masks the next caller and causes the pile-up to stall, a real f**k you very much for the contact.

These extras are not in the default macros of any contest logger software, so this country operators actually go in and add them!

Some other strange habits, if you get their call wrong due to multiple callers in a pile-up, they are programmed to repeat their call twice, sometimes without even completing the exchange. What they don't realise is when you have called them (even with a slightly wrong callsign), the rest of the pile-up stalls and they are in the clear, the double repeat just hacks everyone off and stalls the pile-up unnecessarily.

Why so pedantic, you try doing many 24 hours straight contests over a period of 30+ years and having to deal with the same stupidity every year...it's about time they were told.

While I have your attention, never, never, never send a '?', just wait patiently for the operator to give their callsign. The reason they don't give their callsign is because they don't want you to call. Sending a '?' is just going to mask the other callers he does want to call and this will cause you to have to wait longer.

The height of stupidity is asking the running station for their call, please just listen for as long as it takes till you are sure you have it right BEFORE calling. Never, never, never expect a station to QRS for you, you have all the the time in the world to decode it BEFORE calling.

A lot of this guide is contrary to what you have been taught, this is because casual operating and dxing is NOT the same as contesting. Please reward contest operators for giving you a contact of a lifetime by being EFFICENT cfm? 

FTDX101D PC CW Keying with DTR

Situation:

Rig FTDX101d. Using N1MM+ to send stored messages (F1 etc) using DTR of the USB port (standard port) to send CW. Setting the radio to CW Setting -> Mode CW -> PC Keying -> DTR to receive the hardware CW keying.

Findings:
Surprisingly this direct method of sending CW from the PC doesn't seem to need PTT? With no transmit CAT command, nothing connected to the PTT input at the rear of the radio and without BK-IN engaged on the front of the radio, the messages from N1MM+ software are transmitted by the radio.

Looking into this a bit more...

In N1MM+, RTS of the USB port (standard port) is set to 'Always Off'. PTT is therefore not being sent to the FTDX101D from N1MM+ on pressing one of the message keys (F1 etc).

How can the radio know when to enagage and disengage PTT at the right times for the message when no PTT signal is sent?

This led me to experiment with the following BK-IN menu setting despite BK-IN being disengaged on the front of the radio:
Changing CW Setting -> CW BK-IN TYPE -> SEMI to FULL

Eureka! Yet more madness from Yaesu! Now when I sent the message from N1MM+, the radio is in Full break-in mode despite BK-IN being disengaged on the front of the radio!

In summary, when using CW Setting -> Mode CW -> PC Keying -> DTR, the FTDX101D uses BK-IN irrespective of the front panel control. Bonkers!

This fact is important to me for contesting as if BK-IN is used, it has an associated CW BK-IN DELAY after the message has completed. This means I will not hear the first CW element of fast return callers. Why Yaesu has done this instead of allowing the PC to control PTT through RTS like the K3 I'll never know. Oh well back to using a Winkey with fully controllable PTT and CW KEY. Buyer beware!

Regards

Doug GM0ELP

Data modes invading cluster CW mode

 

What is happening here? Using the dxspider command "accept/spots on hf/cw" to filter my local cluster, I am getting all sorts of nonsense spots returned with JT65/FT8/FT4 in the comments??? Please can data ops respect the cluster and spot correctly? This is not acceptable and ops doing this should be banned by the cluster sysop.