Tag Archives: power measurement

Measuring the Icom IC-705 RF Power vs DC Input Voltage

Introduction

In the summer of 2024 during a Camb-Hams trip to Friedrichshafen, I was drawn into the world of SOTA (summits on the air). A key requirement for SOTA activations is a compact, lightweight and effective station.

When I got started, I was able to use Rob M0VFC‘s Elecraft KX2 portable transceiver. However, from our third SOTA activation of the holiday I was taking my own Icom IC-705. My CW is not great, and so I was activating on SSB mainly on HF (and some FM on VHF/UHF). The IC-705 was a little easier than the internal microphone on the KX2. Rob M0VFC was kind enough to loan me use of his 3S LiPo battery, but I noted that as soon as the voltage dropped a little from full (4.2V * 3S = 12.6V), the IC-705 power was reduced considerably. This was also apparent on the KX2, but isn’t usually an issue because the SOTA pro’s use CW. Anyway, a challenge to know what I needed to do was born… I needed to understand how the IC-705’s RF output power changed as a function to the DC input voltage. I set up a simple test…

The radio specification states 13.8V ± 15%, which gives us an absolute voltage range of 11.73V (13.8V-15%) to 15.87V (13.8V+15%).

Setup & Method

The test setup was simple. My IC-705 connected to a high quality lab power-supply (Rigol DP821), accurate voltage and current readings for DC input power (two Keysight 34401A multi-meters) and a way to measure RF output power (Keysight N9010B spectrum analyser & 30dB attenuator).

The input voltage and current could be measured and adjusted in real time and the input power would be calculated for each test. The RF output power was measured at the frequency of interest.

During all testing the external battery was removed from the radio so that the battery charging current did not confuse measurement. To generate RF, the radio was set into RTTY mode at 100% power (thus creating a pure tone at full power). Each test was automated, and tested quickly to avoid heating issues in the PA.

Initial Results

I measured things at both ends of HF (160m and 10m), and on 6m, 2m and 70cm. The results were consistent with the drop of output power I had noted. More importantly for the initial results, I could see that the behaviour was consistent across all bands, so I could concentrate testing on a single band, and take more detailed steps without creating extra work.

In every test, the power above 13V was very consistent, likely due to ALC on the PA. The efficiency slowly dropped as the input voltage increased. Below 13V, the power was observed to fall.

Further Testing

After the initial testing, I started digging a bit more into what happens between 11 and 13 Volts input. Working downwards from 13V there is a clear linear drop-off until around 11.8V where the software senses the falling voltage and drops to the 5W mode. At 11.6V the radio alternates between the 5W battery limit and the higher power (about 7.5W). This 11.73V threshold that the specification mentions (13.8V-15%).

For useful purposes, we need to keep the DC IN voltage above 11.8V (and below the maximum of 15.87V).

Battery Choices

Assuming we want to keep with a modern battery technology (so, excluding NiCd and NiMH), we have two obvious choices of lithium-ion battery:

  • Lithium Polymer (LiPo) battery
  • Lithium Iron Phosphate (LiFePO4) battery

For each battery pack, there are different combinations of series (S) and parallel (P) configurations, detailed using this “S” and “P” notation. For example, you may see a “3S4P”, referring to three series sets of four parallel batteries. Parallel-ing the batteries increases current handling and overall power, and the voltage is unchanged. Series-ing the batteries increases the voltage and overall power, but the current is unchanged.

Each battery technology has a different nominal voltage (the assumed cell voltage), charged voltage (the maximum cell voltage) and the discharge voltage (the minimum cell voltage). A battery will often have a BMS (battery management system) to take care of protecting the battery from over-charging, over-discharging, balancing (keeping the voltage across series cells equal), etc., but these are out of scope for this page.

LiPo

Typical Lithium Polymer (LiPo) cells have a nominal voltage of 3.7V. Fully charged, each cell is 4.2V. Fully discharged, each cell is 3.2V.

See more on LiPo cells on Wikipedia.

LiFePO4

Typical Lithium Iron Phosphate (LFP, or more commonly LiFePO4) batteries have a nominal voltage of 3.2V. Fully charged, each cell is 3.65V. Fully discharged, each cell is 2.5V.

They have a higher cycle rating than standard LiPo batteries, meaning they can be charged and discharged more many more (>60% more) times before they start to fail.

See more on LiFePO4 cells on Wikipedia.

Why not use X?

I have tried to limit my choice to batteries that are widely known and in production. I have seen AliExpress selling Sodium-Ion batteries and other similarly novel battery technologies, but without easy access and known reliability, I didn’t include them.

See more experimental battery types on Wikipedia.

Battery Comparison

From the IC-705 testing and the specification as well our two battery choices, we can see what options are available.

Extrapolating from the two battery types above, we can see that configurations in the right kind of area are as follows:

Unfortunately, there is no ideal solution with these battery technologies. It is kind of disappointing that Icom did not consider this when designing the radio – a small design tweak to take 17V would have allowed LiPo 4S battery packs to be used. Instead, the best option is LiFePO4 4S. However, as the battery discharges, the lower voltage becomes an issue.

From the tables above it is possible to see that the only real options are LiPo 3S and LiFePO4 4S since the other combinations have the ability to supply excessive voltage (>15.87V) to the radio. Of these two, the LiFePO4 4S has a higher maximum voltage (14.6V vs LiPo 3S at 12.6V). For this reason, the LiFePO4 4S is my preferred choice. LiFePO4 has the added advantage of a higher cycle count and increased safety too, so those are further marks on the LiFePO4 scorecard.

The voltage decision is made: LiFePO4 4S. Now for the capacity of the battery…

Battery Capacity

The 4S battery fixes the pack voltage to a nominal 12.8V. For the capacity, it’s just a case of estimating how much current the radio will draw and then using this to infer the battery capacity you require in “Amp-Hours”.

The IC-705 draws around 220mA (0.22A) in receive from the external power supply at 12.8V (our nominal LiFePO4 4S voltage). If we would like the radio to run on receive for an evening, say 6 hours, we’d need a battery to run 0.22A * 6h = 1.32Ah.

In reality a SOTA activation will be around 50% transmit (at ~2.1A) and 50% receive (at ~0.22A). However, the activation will probably be quite short, perhaps 30 minutes, perhaps 2 hours. By working out the average current used during an hour, an approximate runtime can be calculated for any battery or a battery capacity specified for a given desired operating period.

The final, and perhaps most important consideration for battery capacity is weight! The typical way to expand the current capability of the battery is to parallelise cells; which in effect means doubling the number of them – in our case, doubling or 4-series-connected cells, thus creating two interconnected strings of 4 cells, totalling 8 cells. This becomes a 4S2P battery pack as we discussed earlier. The capacity is doubled. But, so is the weight!

So, what did I buy?

In the end I bought a LiFePO4 4S1P battery made from 3Ah cells. This gives me a 12.8V nominal, 3Ah battery which will run the IC-705 on receive for around 13 hours, or a mix of SSB TX and receive for around 4 hours.

Feeling Brave? Try a LiPo 4S?

Shortly after writing this, I was on a discussion online and someone told me that they had run their IC-705 on a 4S LiPo pack for years and the radio had been fine. They mentioned that it stops charging the battery when the input voltage was above 16V (already out of spec) but that they had happily used 16.8V inputs (actually in excess of 17V) with no damage to the radio.

In a moment of madness, I tried 17V input and noted that (a) the IC-705 does stop charging the internal battery, (b) the HF noise floor was quieter (likely due to the battery charger powering off) and (c) that the radio didn’t explode and still delivered 10W. The radio’s voltage readout caps at 16V on the meter display and the voltage quick menu shows “Hi Voltage” instead of a number. See the two images below showing the difference at 16.9V input (from my 4S LiPo pack).

Maybe not the best thing to do long term, but it could help get you that that much needed QSO on a wet and windy SOTA…

2.4 GHz TX with LimeSDR & EDUP WiFi PA

Following on from my Receiving Es’Hail-2 GeoSat article, the obvious next thing to write something about transmitting. I created a draft of this article, but it seemed to mix heavily with the specifics of my station and was less generic. So I felt it better to create this page first, detailing my 2.4 GHz transmitting station, which I have just cobbled together in the time since writing the original article.

About the LimeSDR

Let me first start by saying that I’ll be using a LimeSDR USB which has a continuous frequency range of 100 kHz to 3.8 GHz. Clearly acceptable for our requirements of 2.4 GHz. The bandwidth the SDR can support is staggering 61.44 MHz. The SDR is based around an Altera Cyclone IV FPGA with 256 MB of DDR2 RAM and a Rakon RPT7050A reference clock at 30.72 MHz. It has 6 inputs and 4 outputs, and boasts a CW transmitter power of up to +10 dBm (10 mW).

Clearly the LimeSDR is nothing without some fancy software to drive it; and there are plenty of good offerings. I decided to opt for SDRConsole V3 by Simon Brown G4ELI, which at the time of writing was version 3.0.5 (Feb 2019).

SDRConsole with the LimeSDR

The process of setting the LimeSDR up was easy. I had to collect the LimeSDR drivers for Windows and install those. That process is nicely described on the Miriad RF LimeSDR USB Driver Install page, but the crux of it is: (a) download the drivers from their GitHub page [direct link to master here], (b) use Device Manager to find the LimeSDR, and replace the driver with that in the zip.

Once the driver is installed, you’re ready to set up SDRConsole. When the program starts, it will state that you do not have any radios defined, and give you the opportunity to define one. Simply select “Search” and then “LimeSDR” and it will find your radio. Accept the changes you’ve made.

Radio Definitions: Define your LimeSDR

Once you have defined your radio, you should select it from the box that pops up following the definition (and subsequently each time you start SDRConsole). Select the LimeSDR you have just defined, make sure you select a bandwidth that supports transmitting “(TX)” in the “Bandwidth” option, and “Start” will become clickable in the bottom left. You should see the console spring to life.

Select Radio: Make sure you select a bandwidth what supports TX.

From the Receiving Es’Hail-2 GeoSat article, you will recall that the narrowband transponder input is 2400.050 MHz to 2400.300 MHz. Taking the middle of this band to be 2400.175 MHz. The screenshot below shows the radio on this frequency. I have put boxes and tails on some of the important settings.

From the figure above, you can see the receive frequency on the top left box, with the transmit frequency on the top right box. The “Sync RX” options for frequency and mode show that the TX frequency and more are locked to that of the receiver.

The “Drive” control on the top right box controls the RF power on the output and we shall try to characterise that later. Just above it is a “TX” button which causes the transmitter system to be engaged, and the receiver to be muted.

Finally, in the bottom left there are controls which select which of the LimeSDR’s 6 receive sockets and 4 transmit sockets are in use.

LimeSDR Output Power

The next thing to do is measure the LimeSDR’s TX power on the frequency of interest: 2400.175 MHz, the centre of the NB transponder uplink. A CW signal is used to generate a constant power level.

To achieve this, I have used a known calibrated R&S NRP18A, which will measure power from 100 pW to 200 mW. We are expecting a maximum of 10 mW, so we should be easily safe to use this.

The drive level is a percentage, ranging from 0 to 100. My basic plan was to take a reading every 10%, and if there is a large non-linearity, I’ll take further measurements in those areas. At this point, the LimeSDR is only powered via the USB bus, and has no external power source. With drive levels below 50%, the reading was noisy, so I concentrated on the linear part of the curve.

Drive Level (%)Power (dBm)Power (mW)
50-41.620.000069
60-34.350.000367
70-26.50.002239
80-18.310.014757
90-9.690.107399
100-1.620.688652
Graph of LimeSDR output power vs drive level at 2400.175 MHz

EDUP 8W WiFi Power Amplifier

I purchased an EDUP 8W WiFi power amplifier for £35 in February 2019 for use with the LimeSDR and Es’Hail-2 uplink. There had been talk on Twitter of these amplifiers being suitable, so I decided to give one a go.

EDUP 8W WiFi Amplifier cost around £35 delivered

Without getting into details, the amplifier has a system which detects if the WiFi radio is transmitting, and enables the PA’s TX path, or if the radio is receiving, and enables a separate RX path. This is exactly like “VOX” on an amateur radio amplifier. However, since the packets are very short on WiFi, with guard times in the order of 400 nanoseconds, the hang time is very short, and thus not suitable for SSB. We thus need to modify this behaviour, so that the amplifier is in TX all of the time, or, even better, when the LimeSDR is transmitting – perhaps using a GPIO pin to drive the amplifier – but that’s unimportant for now.

PTT Modification: EDUP 8W Amplifier

Here’s a snap of the insides of the amplifier. It’s clear that there is some room for improvement in gain with this amplifier, such as removing the (likely lossy) TX/RX switching, etc., as we don’t need these parts. However, for now, we’ll leave it. Swapping the RF-OUT RP-SMA connector for a standard SMA connector is probably a wise decision for the radio amateur.

Inside the EDUP 8W WiFi Amplifier

The mod, in its basic form, is just a solder bridge across pins 4 (VS) and 5 (+IN2) of the ADA4851-4 quad rail-to-rail op-amp on the opposite corner of the board to the DC power socket. The mod makes it appear that the diode detector is detecting a huge signal (5.787 V, the supply rail). The reference voltage (-IN2) is set at 0.189 V. When the voltage at +IN2 exceeds -IN2, the device enters transmit mode.

If the amplifier is in receive mode, the status LED illuminates red. Conversely, if the amplifier is in transmit mode, the status LED illuminates green.

Measurements with the EDUP Amplifier

In terms of the experiment, the EDUP amplifier input is connected with an SMA barrel to the LimeSDR output, and the EDUP amplifier output is connected (via RP-SMA on the included short RG174 patch cable) to a 20 dB attenuator which in turn connects to the power meter.

Using this configuration, I do not expect that the output power will be come very high, since their is not enough drive level from the LimeSDR at −1.62 dBm. I see about 13 dB of gain, with an output of around +11dB (~10mW) of RF output power.

At this point the EDUP amplifier is drive limited. Working backwards, to achieve a theoretical +39 dBm (8 W) output, we would need to input +26 dBm (0.4 W) input.

The amplifier draws around 170 mA in receive, and about 380 mA in transmit with no RF (just quiescent bias).

More Gain!

Clearly connecting the EDUP directly to the LimeSDR does not provide enough power. There is a need for some more gain. Looking around what options are available cheaply, you quickly come across some options.

Qorvo SPF5189Z

SPF5189Z breakout module available from eBay, AliExpress, etc.

The Qorvo SPF5189Z has a small signal gain of 11.9 dB at 2.2 GHz (the closest listed frequency to the required 2.4 GHz) and an output P1dB of 22.7 dBm. This output power is close to the 26 dBm input required for the EDUP, although it is not recommended to run the system close to the 1 dB compression point (P1dB). With the SPF5189Z in line, we see approximately 20 dBm output (100 mW) from the EDUP.

Adding another SPF5189Z following the first gives around 30 dBm (1 W). Adding another 10 dB of gain early on in the drive chain will get us closer to the goal of 8 W output, but the system was becoming unwieldy and would probably not be suitable for use on air without inter-stage filtering as the parts used are wide-band.

Analog Devices CN0417 Evaluation Board

Analog Devices CN0417 Evaluation Board (bottom side) [source]

Another part brought to my attention by @Manawyrm on Twitter is the Analog Devices CN0417 evaluation board (EVAL-CN0417-EBZ). It is a USB Powered 2.4 GHz RF Power Amplifier, and can be purchased for around £26 ($35 USD).

I have not used this part yet, but I know that others have with some success. The EVAL-CN0417-EBZ is based on the ADL5606 is a broadband, two-stage, 1 W RF driver amplifier which operates over a frequency range of 1800 MHz to 2700 MHz.

Nearly there…

With some tidying of the interconnects, I was able to get to 32.98 dBm (1.95 W). More filtering will be required before letting this loose on air.

Screenshot of SDRConsole with RF Power Meter inset. +32.89 dBm = 1.95 W

Getting it on air!

At this point I was pretty keen to see if I could make it to the Es’Hail-2 satellite. The day I tried, 2 March 2019, followed an announcement by AMSAT that the narrowband transponder gain had been reduced, so I was keen to

AMSAT-DL reduced the transponder gain by several decibels on 28/02/2019

Using a WA5VJB quad-patch antenna purchased from Sam G4DDK, I was able to get going sooner than if I had held out to wait for the dual-feed solution that Mike G0MJW and others had been working on. The patch can be seen connected to the amplifier with a simple SMA barrel connector.

Patch antenna and EDUP PA

Balancing the amplifier and patch antenna on the back of a large reclining chair in the garden, I was able to align the patch antenna to the satellite’s location. Setting the TX frequency of the LimeSDR to the centre of the transponder band (2400.175 MHz), with an output power of around 1W of I was able to hear a single tone through the Es’Hail-2 narrowband transponder, I quickly added a CW paddle and was able to confirm my signal by sending “M1GEO TEST” several times, listening via the BATC NB WebSDR as discussed in my Receiving Es’Hail-2 GeoSat article.

I took a short recording using the BATC WebSDR:

“M1GEO TEST” received at BATC Goonhilly Web SDR

Some filtering?

W1GHZ has a nice study on pipe-cap filters and there are other articles that describe their construction such as KO4BB Pipe Cap Filters construction page. Other options include inter-digital filters and similar.

Not much to report here… I still have some experimentation to do.

Where next?

The next article in this set describes making a dual-band feed. It is still being written…