Feature Articles

A few short years ago, there was a 'falling out' between a couple of the popular radio related software houses, which resulted in a suspension of a couple of programs talking to each other, but quite quickly, a third party coded a solution to fill the void. That's all behind us now, but at the time, it made me curious about how applications, be they from the same suite, or different programs, exchange relevant information. An example of this is WSJT sending a QSO to be logged by your regular station log. One way this is achieved is with UDP.

Wanting to know exactly what was exchanged, I contacted my logbook provider who gave me some good pointers, but as the API part of the software that looked after this data wasn't developed by them, he couldn't elaborate further.

I then happened upon this gentleman Chris Fredericks VK2BYI who had written a paper on the very subject. The article below is in depth and probably beyond a lot of our understandings, but if you are interested, it is a great source of information. I think most of the issues faced at the time have been resolved, so this article should be treated as FYI only!

Steve GJ6WRI

The 'paper' is reproduced with the expressed authority of the author Chris VK2BYI.

Argon One M.2 case for the Raspberry Pi 4 by Argon40

Last week I installed an alternate image on my Raspberry Pi 3 Model B - the recently available SDRPlay image. I have the (rather excellent, in my opinion) RSPdx SDR receiver, and I'm in the process of migrating as many radio-related applications as I can over to the Pi as part of a wider logical reorganisation of my setup.

All went well, but I quickly found the CPU temperature hitting some fairly alarming numbers when using Cubic SDR for more than a few minutes. That was all the excuse I needed to spend some money on an upgrade. I guess I could have just opted for an active cooling solution, but as a new Raspberry Pi is small enough to get past an unsuspecting wife, it was a virtually guilt-free foregone conclusion.

I've always liked the look of the Argon Pi cases as they appear to be really well engineered, so one of the M.2 versions quickly followed an 8GB RPi 4B into the PiHut shopping basket as well as a WD Green 240GB M.2 SATA SSD and an official PSU. Then the difficult bit - waiting for it to arrive.

Now this may seem daft. I know how big a Raspberry Pi is, but I was still surprised to see the size of the Argon case. Somehow, Internet reviews made it literally more of a 'big' deal in my mind. Pleasantly surprised though, as I had partly justified the purchase on the compact and robust nature of the thing with one eye on a transportable setup.

The Pi 4 is what it is, so I won't linger here. It's much faster and more capable than my 3B, so I just want to cover the very straightforward marriage with the Argon One M.2 (which confusingly also carries 'Argon40' branding - it turns out that this is the name of the company).

The Argon basically comes in three parts. The metal 'lid' for want of a better name, the base, which houses the SSD module (which won't take an NVMe SSD by the way, only Key-B and Key B&M) and a daughterboard which relocates two full sized HDMI ports and the audio socket to the back of the unit.

The top half is definitely where most of your £40 goes. It relocates the USB-C power socket to the rear panel, the GPIO pins to the top rear of the case, acts as a sizeable heat sink, and houses a small cooling fan.

Underside of the Argon One Raspberry Pi case lid

Joining the two components together - Raspberry Pi with the Argon One HDMI daughterboard

Assembly (and that's all this is really - a simple, modular project) is guided by a well written and clearly illustrated manual which is worth stepping through as you go. Firstly, the HDMI board plugs into the side of the Pi, and then the inverted assembly drops into the top half of the case, sandwiching two silicon thermal pads (supplied). It's at this point that you realise just how well made this enclosure is - everything lines up just as you would hope, and with nice tight tolerances; GPIO pins, all the PCB-mounted hardware at what is now the rear of the device, and all the screw holes. It's precision-cast alloy and beautiful to work with and handle.

Fitting the Raspberry Pi and HDMI board

It feels heavy and never gives you any concern that you're close to stripping a screw thread. The small detachable metal flap which covers the external GPIO array snicks satisfyingly into place on a couple of magnetic pads. It just puts a smile of contentment on your face. The GPIO pins are all very well labelled and I suspect that the legend won't be rubbing off anytime soon. The pinouts are usefully colour-coded too.

New GPIO pin arrangement

One of the selling points of the Argon is also one of the downsides of the Raspberry Pi itself, and that is the process of powering the device on and off. Yanking a wire out and plugging it back in again is not where I want to be. The Argon has a high quality push-button power switch at the rear, which is subsequently integrated into the completed system via a small software tweak, and it works like you'd expect. Short click to power on, click and hold to power off. Double click also does a soft reboot. Nice touch. There is a jumper on the upper PCB to effectively disable this, so that the Pi will boot as soon as power is applied to the board if you so wish. Based on the use you're putting your Pi to, this could clearly be a distinct advantage, but not for general 'desktop' use I feel. It could of course be very useful if you're running a remote station. An IR sensor/receiver is also added to the Pi's already feature-packed specification, allowing use of Argon's own remote control (an optional extra). I'm sure somebody will have a use for that in the media-center world perhaps.

Finishing up this little project, is the optional M.2 SSD installation. Not required, but I have an irrational fear of future regret, so blowing another £30 on a 240GB SSD in the Argon's basement just sounded like a prudent future-proofing policy.

M.2 SATA SSD baseplate.

Construction of the plastic base was again more than adequate, but didn't have the same metallic sensory titillation as the lid. If it had, I'd probably be criticising it for being unnecessary. Fitting the drive was straightforward, although the securing screw, which was already located where you see it in the photo prior to the memory module being fitted, came away from the PCB with the brass standoff attached. That should clearly go underneath the drive, but I bet a lot get installed incorrectly because of this minor niggle.

Argon One M.2 Rear Panel with Power button, 1 x USB 3, 2 x USB 2, Gigabit Ethernet Port, power, audio and HDMI ports

Final steps are to fit your microSD card of choice (Sandisk Ultra Class 10 all the way here) pre-loaded with your software, fit the remaining screws and rubber feet, and plug in the USB3 plug thing. The what? Yeah, that's what connects the two halves together electronically. It means you effectively lose a USB3 port, but gain a SSD so that's fair enough.

Maybe you also noticed that at no point did we plug anything into the USB-C power port on the Pi itself. Cleverly, the power is now delivered by some internal magic - I'm guessing via the GPIO pins and the previously mentioned USB-C port round the back - so you can still use the factory 3A power supply.

Changing the microSD card just became a screwdriver-based operation, but that's probably the only real drawback with this case. There is a slot in the upper housing to feed through the ribbon cable for the Pi camera, though I've not tried this yet.

The end result is a tough, compact and very capable little machine which would stack up well against Linux laptops of just a few years ago. Ideal for a field day or just a little portable messing around if you can find a suitable monitor solution. I know small touchscreens are available for example. I'll be testing and evaluating the setup over the next couple of weeks, and may write some of that up if I think it's of interest,

Berni M0XYF

Two of us were invited to visit broadcasting house Portland Place to see Radio One in full swing, plus visits to the other studios.

We arrived at the reception where we made contact with our friend Douglas Morgan who worked for the BBC. He invited us to the Langham Hotel for refreshments and explained who would be our guide for the afternoon which started at 2pm.

BBC Broadcasting HouseSure enough when we returned to the reception area we were introduced to Derek Chinnery who was the executive producer of Radio One (Later to become controller of Radio One).

Our first stop would be to visit some Radio Four Studios where we were amazed to walk into a very large area where all around the room were floor to ceiling curtains of very high quality and thickness, with carpet on the floor. It was explained to us about programs made here were high quality and needed good acoustics.

After visiting Radio Four our next stop was to see a program being transmitted live from Radio 3. This was in a small room consisting of reel-to-reel tape players. The one in use at the time we called in, was playing a concert with tapes running at 15rpm. There was just one lady monitoring the tapes.

From Radio 3 we were taken to the Radio 2 Studio where Terry Wogan was presenting his live afternoon show. We were allowed to enter as long as we didn’t make a sound.

When he had a few seconds after setting up his next record, he left his consul and came around to chat to us. He seemed very interested why we were there and explained a few things to us before returning to his seat.

We stayed for a while, and then moved onto the Radio 1 Studio where this time, we were only allowed into the continuity room. The DJ was in full swing with his program in the main studio viewed through a large soundproof window, but operators could hear the live program from a large speaker or headphones.

The continuity team were very alert to sound as I stood in front of one of the speakers. I was requested to step aside as the sound became muffled.

We spent quite a long time watching the DJ working, but then it was time to leave. But before departing we met Emperor Rosco who with Tony Blackburn and Ann Nightingale were just going to start on his Rosco Round Table program for the afternoon.

After chatting it was time to leave after having a very enjoyable and interesting afternoon.

73’s John Blissett & Tony Finch

Written by John Berry, GM8JBJ

Many members will remember the phone patch - the forerunner of mobile phones.

In one example, ships at sea would call Portishead Radio on HF and ask to be connected to a landline number. Once the landline subscriber answered, the ships radio service operator would flick a switch and a husband would talk to his wife, or captain would talk to his or her port agent. It was an essential service.

In another, an Aircall, Securicor or BT - mobile user would selcall their service operator. On answering, the mobile user would request connection to a landline. When the landline subscriber answered, the operator would flick a switch and connect the two. Aircall and Securicor were simplex. BT was duplex and a forerunner of our present mobile networks.

Now, fast forward to today.

In a pre-CoVid world, Scouts could talk to other Scouts via amateur radio on the third weekend in October each year. Jamboree On The Air is an ad-hoc event that stems from cooperation between local Scouts and radio amateurs. During JOTA, amateur operators set up calls and pass the mic to a Beaver, Cub, Scout or Explorer. Those Scouts pass ’greetings messages’ to other Scouts elsewhere in the UK or worldwide.

Then came CoVid.

Jamboree On The Air this year was held from Friday 16th to Sunday 18th October. At the time, and in most areas, Scouts were at what they refer to as Readiness Level Yellow. Small scale face-to-face activities were allowed, but everyone attending had to be socially distanced. These constraints precluded traditional JOTA operation with the amateur operator sitting beside the Scout. New methods of operation needed to be found.

So, Scouts and their radio amateur partners perhaps needed to take a leaf from the days of phone patch.

Here’s the solution using the likes of Zoom that Borders District Scouts used at the special event station GB2SBS run by John, GM8JBJ and Sue, MM3SLB.

... with modern day 'phone patch'...The connection between Zoom and HF is made using an XGGcomms digital interface containing a C-Media CM108 chipset sound card for digital-to-analogue conversion. The interface links the USB socket of a Raspberry Pi running a Zoom session to the HF transceiver 13-pin facilities socket. Normally digital interfaces use a sub-carrier VOX to key the transmitter. An interface was introduced to disable the VOX and add a manual PTT and this box is shown (light grey) in the adjacent picture.

The ’DATA’ position connects the digital interface for digi-modes use and is the pass-through state. The ’PATCH’ position interrupts the VOX and enables the ’TX KEY’. The TX KEY connects Zoom to HF - the ’patch’ state - and keys the transmitter. The interface uses two two-pole on-on switches and a lead and some wiring. On receive, the audio is routed through the interface to the Raspberry Pi audio and on to Zoom.

John, GM8JBJ, was radio operator while Sue, MM3SLB, acted as ‘Zoom’ controller. In fact, GoToMeeting was used (rather than Zoom), but the solution is common to all online meeting platforms. The voice quality of ‘Zoom’ participants was excellent in both directions.

For anyone wanting to set such a system up for JOTA, there are some points to note.

The radio operator must join the Zoom meeting using the PC with the interface. In my case, I used a Raspberry Pi with a camera pointing at the rig so that the young people on Zoom would be able to see the rig and its settings.

Part of JOTA is also generally to work on, and complete, the Communicator Activity Badge when the young people must log 25 stations. Several must therefore be on the Zoom call simultaneously, listening to on-air proceedings for a few hours.

The radio operator must also join the Zoom meeting with a separate PC with headset and mic so that they can talk to the Zoom controller. The Zoom controller can then also hear the on-air proceedings, and hence they know when to tell the young person to go ahead. If this link is missing, the Zoom operator is working blind.

Having three independent on line meeting connections over one broadband circuit does tax the broadband capability, though!

And radio and Zoom operators must of course be in separate rooms to avoid howl round.

Then Scouts join the Zoom call as normal and talk over HF in turn.

Simples! And it worked perfectly.

And the results? 26 QSOs with stations in 18 countries over 10 hours. 10 Scouts participated for about 4 hours each. Another 10 or so stations were heard and logged, including V55JOTA, in Namibia, though conditions faded

before contact could be made. Our Scouts passed 15 ’greetings messages’ or patches. And since all had completed a training session beforehand, all will now get their Communicator Activity Badge. The training session was effectively a slimmed down Foundation Course.

The best DX was KA8OFC, Michigan with second place to VY2GF, Prince Edward Island. Best QSO was LX9S, Scouts World Bureau, in Luxembourg.

And the icing on the cake for one of our Scouts was when CR7ARW videoed her greetings message being received and sent us the recording.

JOTA this year was a much-muted affair. Sole operators lamented that they were unable to have any participation with their Scouts. Unfortunately, GB2BS seemed to be the only station who could put Scouts ‘on-air’. We were the only station who thought ahead to use the phone patch concept.

Perhaps more radio amateurs will make connection possible next year.

John Berry, GM8JBJ

Database collated by Chris G4ZCS

Call sign prefix database

Mid Sussex Amateur Radio Society

Issue 22 - Spring 2020

Please feel free to use and circulate this list. Chris G4ZCS will be pleased to receive corrections and additions as they are noticed. There are over 2000 entries. Additions are continually added, please check for updates. For date and prefix "exceptions" please check with the "Club Log" on-line database, as this is updated daily and is reccomended. Read with care!