F.A.Q. is self-explanatory, we collected frequently asked questions and presented answers to them. In time F.A.Q. will grow bigger.
If you think that some vital information is missing, please let us know via email - This email address is being protected from spambots. You need JavaScript enabled to view it..
ESSENTIALS
1. Make sure you've installed the ExpertSDR2 version for your device. Each device has a special version of the ExpertSDR2, other versions of ExpertSDR2 won't work with your device and may ruin it.
2. Add ExpertSDR2 to the Windows Firewall exceptions list for both Private and Public networks, or just disable Firewall and your antivirus software.
3. Check that AnyDesk doesn't block the ports which are used by the ExpertSDR2/3 – 50001 and 50002. The procedure is explained in the next segment. ExpertSDR2/3 always uses two ports for each radio; one is indicated in the Options-> Device menu-> Expert tab and +1 e.g.: 50001 (indicated) and 50002.
4. Make sure your PC/notebook has a fixed IP address with subnet 16 e.g.: 192.168.16.50. Your PC/notebook should always be in the same subnet with the radio, otherwise you won’t be able to use it.
5. For the first run, you need to connect the radio directly to your PC with Ethernet cable. When you make sure that PC and radio are in the same subnet you can connect your radio to the router.
6. Run ExpertSDR2, open Options-> Device menu-> press the Discover button.
7. In the new SDR radio window, press USE in front of your radio.
8. Start the radio by clicking the red Start button in the ExpertSDR2 window.
9. Double check that transceiver is powered up, LED is solid green and transceiver is connected to PC via RJ45 cable. Open terminal window and type 'ping 192.168.16.200'. Correct result you should get:
Wrong result -> Troubleshoot (see User Manual how).
What to do if you still in "I am Stuck!" mode?
Real examples, which have been observed through the several months:
Issue: Transceiver's power LED is not becoming solid green.
Option: Did you already tried RESET and DEEP RESET procedures? No? Then it is just a time.
Issue: Did RESET and DEEP RESET, but still not solid green.
Option: Try to activate "the bootloader mode" while using ESDR2:
1. Switch off the transceiver with the PWR button;
2. Press and hold the BT button on the rear panel of the transceiver (you will hear a light click);
3. Switch on the transceiver with the PWR button. The LED will blink with a single green light;
4. Release the BT button;
5. Launch ExpertSDR2 software and open Options-> Device menu-> Expert tab and press Firmware update;
6. After the firmware update is finished, the LED will turn to constant green light;
7. Go to section 1 of Step-by-step instruction.
Issue: Cannot ping transceiver
Option: Verify IP settings on PC and transceiver
Issue: Can ping transceiver, but cannot connect to it
Option1: Return PC network adapter to Auto Negotiation mode
Option2: Kill any application (Anydesk, IC9700, etc) which is blocking UDP port 50001 on your PC
Option3: Double check firewall settings
Option4: Reinstall OS
Still in "I am Stuck!" mode?
1. Stop harrassing your PC and transceiver for a while. Go to feed you dog, wife or garden. Wait 1-2 days for the brain cells to cool down (use cold drinks or conditioner if needed).
2. Open this manual and start over
And still in "I am Stuck!" mode after all above done?
Congradulations, your won a nomination of Super Dummie! Contact EE technical support.
Note: The above guide is non-official and applicable to ExpertSDR3 aplha/beta versions.
Here is the short "as is" movie of Downgrading from ESDR3 to ESDR2 and Upgrading back from ESDR2 to ESDR3 in one move (download recommended). Fair warning - you still have to go through the step-by-step procedure, as described above.
For this demostration I am using macbook, however, it is absolutely the same step-by-step in Windows and Linux.
As per "I am Stuck"©™ Series tradition" - fair warning, before we start.
Warning! The below guide will require incredible effort from its follower:
1. Ability to read and understand line by line (not jumping down up, missing the paragrahps, as usual)
2. Follow the instruction step by step (that is hard, we know, but essential)
Prerequisites:
1. You have (accidentaly, of course) installed ESDR3 alpha/beta
2. You are desperate to divert back to ESDR2
3. You have tried everything
4. You are confident to be "Stuck"
5. You have SunSDR2 / SunSDR2 PRO / SunSDR2 DX hardware version (not applicable to MB1)
6. You have compatible Win / Mac / Linux OS
Step-by-step instruction:
1. Read this guide line by line, before even touching anything.
2. Read this guide again. Line by line. Now with attention, yes?
3. Set proper IP address
3.1. Using ExpertSDR3, set the transceiver IP to default: 192.168.16.200:
When you click "Set New Address" button, the ExpertSDR3 will pop up, asking if you really want this - click "Yes". The next two windows will pop up - one is confirming that new IP address is set and next one, just a second after, saying "Failed to read device calibrations!":
Do NOT panic. Do not PANIC as well. The message "Failed to read device calibrations!" is (completely, purely, absolutely) normal. That is how it ment to be. Just press OK and go to next step.
3.2. Completely close ExpertSDR3.
3.3. Power off and power back on the transceiver.
4. Make sure you connect transceiver to PC with direct RJ45 LAN cable. Remember? You have got the working cable somewhere before, when you bravely decided to upgrade, hah? Go get it, you will need it now.
5. Change IP address of your PC to 192.168.16.1 with mask 255.255.255.0 (no default gateway and no DNS required)
Somehow I am sure 95% of readers are still on WiFi, when come to this step ... Hence, here is the hard part - it is time to get direct cable between PC and transceiver.
See? I have only PC-transceiver network active. Shutdown all other networks (WiFi, dual LAN, whatever you may have on your PC) for a moment untill successful downgrade:
6. Make sure, that when PC and transceiver are powered up, the transceiver power LED is solid green. If it is not (flashing or whatever but solid green -> then your network connection is faulty -> troubleshoot and get it working, before you go to next step).
7. Make sure your PC network adapter set to Auto Negotiation.
(When you did the upgrade, you may ask yourself, "why?" Well, if you really think you need that extra knowledge, just read here. And the reason Step 7 is here - just because, by our experience, there are smart users who are already have messed up with Auto Negotiation, resulted in failing upgrade-downgrade Firmware.)
8. Remind yourself the difference between "Device Manager" and "Firmware Manager". If you have Dory-fish-like memory, just see Step 8 in previous issue of our very successful "I am Stuck"©™ Series.
9. Double check that transceiver is powered, LED is solid green and transceiver is connected to PC via RJ45 cable. Open terminal window and type 'ping 192.168.16.200'.
The correct result you should get:
The incorrect result is below, if you get it - troubleshoot:
9.1. Launch ESDR3 and double check if it is seeing the transceiver with correct IP address and port:
9.2. Completely close ExpertSDR3 and double check if there is any of its process (or part of it) still running in background.
10. Launch ExpertSDR2 (you can use any version of 1.3.1, I am using 'update 8').
11. Press On/Off button on ExpertSDR2 - it will pop up, saying you need to update Firmware. Click Yes.
I know that some of you will try to do that different (their own) way. And will get stuck. Well... that is why we have this very successful "I am Stuck"©™ Series, savvy? Just do it as it said: Press On/Off button on ExpertSDR2:
11.1. For SunSDR2 DX users only: The Firmware update (pop-up) process will go through Step 1, then reset and complete in a total of few seconds.
Now you're all set and can start using ExpertSDR2.
11.2. For SunSDR2 / SunSDR2 PRO users only: if the Firmware update (pop-up) process is sitting with no move for more than 30 sec, then:
11.2.1. Do Not close any software window, leave Firmware update (pop-up) untouched.
11.2.2. Power off transceiver by power button, wait 10 sec, power transceiver back on.
11.2.3. When transceiver is back on - watch the Firmware update (pop-up) will go throug step 1, then reset and complete in a total few seconds..
Now you all set and can start using ExpertSDR2.
Here is the short "as is" movie of Downgrading from ESDR3 to ESDR2 and Upgrading back from ESDR2 to ESDR3 in one move (download recommended). Fair warning - you still have to go through the step-by-step procedure, as described above.
With migration from ESDR2 (based on Qt5 framework) to ESDR3 (based on Qt6 framework) it is important for ESDR3 user to understand the fundamentals of default audio drivers and codecs within various OS, alongside with existing cross-dependencies.
This understanding might be able to help the user to set the correct expectations and select the proper (both) ESDR version and computer platform/OS for his needs in HAM radio.
In general, the topic about "audio" should be split in two major parts:
- OS (Linux/OS X/Win) audio, and
- Qt versions (Qt5 and Qt6) differences in delivering audio within ESDR2 and ESDR3
First and foremost: ASIO is a 3rd party (Steinberg) protocol, which is, actually, never was officially supported by Windows. It, actually, works the opposite way: 3rd party ASIO developers are supporting Windows OSes, introducing both: software protocol (which can bypass OS-defined audio path and connect the ASIO-based application directly to the installed audio hardware) and ASIO-capable hardware (sound-cards).
Second: MS, from their side, (and in earlier versions of the OS) was allowing this protocol to bypass in-build audio path. However, with initially introduced (in later versions of Win10, and moved into Win11) new Windows Audio Architecture, MS practically removed from their OS the way of ASIO to work. From the other side, the newest Windows Audio Session API (WASAPI) enables practically the same functionality, which was available earlier only in ASIO: client applications to manage the flow of audio data between the application and an audio endpoint device. Practically, it means that in latest Win10 and all versions of Win11, use of WASAPI (Win default) demonstrates same or better results in terms of low latency audio than use of ASIO.
COMMON KNOWLEDGE
To RX on these frequencies, we'll recommend to us the ADC IN because standard antenna inputs will have low sensitivity.
Maximum allowed signal level on the ADC IN connector is 0.3V of the active voltage (RMS). Do not exceed it, it may result in the transceivers overload and ADC fatal damage.
ADC cannot receive DC, receiving available from 9 kHz and higher, never tested below 9 kHz.
RX below 100 kHz will have low sensitivity, we've never tested our devices on these frequencies.
The S-Meter shows the signal level in the RX filter bandwidth.
When no antenna is connected, the S-Meter shows the level of the radio's internal noises.
The readings depend on the filter bandwidth, if you set SSB mode with 3 kHz bandwidth, the readings will be at the higher level, if you set CW with 100 Hz bandwidth, the S-Meter readings will be lower.
The radio's internal noises also depend on the Preamp level (sensitivity). If you set -20 dB ATT, the sensitivity will be at its worst and S-Meter readings higher, if you set Preamp +10 dB, the sensitivity will be higher and radio's own noises will be at their lowest.
S-Meter in the ExpertSDR2 has two different calibrations for HF (0-30 MHz) and VHF (30-300 MHz).
HF and VHF signals with the same dBm level have different S-scale values.
You can find calibrations tables for HF (Table 3) and VHF (table 4) at the following link http://hamwaves.com/decibel/en/
For example:
29 MHz -127 dBm ~ S0.5 (preamp on)
52 MHz -127 dBm ~ S3.5 (preamp on)
To verify you may connect a signal generator to an antenna port and compare the generator signal with the S-Meter readings for all S-levels, compare to tables from the link above.
Also, you can see the IARU recommendations for HF and VHF S-Meter calibration at the following link https://en.wikipedia.org/wiki/S_meter
For HF S9 = -73 dBm = 50 uV (50 Ohm), for VHF S9 = -93 dBm = 5 uV (50 Ohm).
S-Meter in the ExpertSDR2 corresponds to the IARU recommendations, each device is calibrated at the factory during manufacturing.
S-meter values and audio level have program compensation when you use the attenuator because the signal level on the antenna input is always the same and doesn't depend on the attenuator level. With this solution, a user doesn't need to calculate real values on his own, every time when the -20-dB attenuator is used. Also, he doesn't need to adjust AF or RF level every time when the -20-dB attenuator is used, like in most classic transceivers.
Attenuator influences only receiving dynamic range, S-meter and audio level stay the same. If you disconnect the antenna, you can see how the receiver’s noises are changing when you switch the ATT. The receiver's noise level is lower when you select ATT 0 dB, which means that RX sensitivity is higher. When you select ATT -20 dB, it means that the RX noise level is higher, but RX sensitivity is worse. It is done in the hardware.
ExpertSDR3 SOFTWARE
ExpertSDR2 SOFTWARE
ALL TRANSCEIVERS
ALC is not supported in the ExpertSDR2, we plan to implement it in the ExpertSDR3.
In the meantime, we recommend you to set max output power per band in the power correction menu: Options-> Device-> Expert tab-> power correction. It allows you to send a corrected power level to the PA without overloading the PA itself. ALC system has a small delay, and it's a cause of the short overload. ALC is worse than a fixed (set up) power correction per band.
To use the transceiver with the external PA, you need to adjust the max TX output power per band: When you use the Tune button in ExpertSDR2/3, with the Tune slider at 100%, TRX sends a carrier signal on the air with maximum output power. This carrier has a stable amplitude, and you'll be able to set the max output power of the transceiver for each band. Then you can set the Drive slider to maximum and TRX will send the same output power as in Tune mode.
Note: The Tune slider is a special control of the output power for the carrier signal in tuning mode. For all other modes, for normal operations, you should use the Drive slider. Power correction coefficients are adjustable numbers, they are not equal to real output power e.g., coefficient 50% on 20M does not equal 50W, it can be 60W (in case od MB1 or SunSDR2 DX). Coefficients are not the same for every band, so please be careful and start from lower values. That's how we suggest adjusting output power per band.
MB1 TRANSCEIVER
The Windows gain settings also can be used for gain adjustments, but we recommend to use only ExpertSDR2 gain settings.
1. SDR uses UDP ports and TCI uses TCP ports.
2. MB1 SDR IP address is 192.168.158.1:50001, but MB1 PC should be in a different subnet, something like 192.168.16.50.
3. In your logger (McLoggerDX for example) you should indicate local address 192.168.16.50:40001 or 50001 (default TCI server port depending on the ExpertSDR version).
SunSDR2 PRO TRANSCEIVER
SunSDR2 QRP TRANSCEIVER
LED is stable (NOT blinking) - transceiver is ready for operation and can be connected to the ExpertSDR2.
In the SunSDR2 QRP we used an advanced stack of a local network, so you have 4 options for local operation:
1. DHCP Auto mode is set by default. It works this way: in the beginning, transceiver works in DHCP Client mode and tries to get the IP-address automatically from an external server, if it gets the IP address, LED will stop blinking, becoming stable green color. If transceiver can't get the IP address within ~20 seconds, it will automatically turn to DHCP Server mode and provide IP address, in this mode LED will become stable orange.
2. DHCP Server mode is for direct connection of the transceiver and a PC. In this case, the transceiver will provide a PC with the correct IP address, so you don't have to adjust network card settings. In this mode, LED will become stable orange. in this mode, the transceiver will also have a static IP address 192.168.16.225.
3. DHCP Client is for connection of the transceiver to the home local network, where you have a DHCP-server, which automatically provides IP addresses, for example, router or ADSL-modem. In this mode, LED will become stable green.
4. Static IP, in this mode transceiver, has a static IP address, works the same as in SunSDR2PRO - in this mode LED will become stable orange. By default, IP address is 192.168.16.225. This mode requires to set up PCs network card according to the same instruction as for SunSDR2PRO. We do not recommend to use this mode without special need.
Note: if you have a direct connection, after initialization process you may change a network mode to DHCP Server, this will save you about 20 seconds after switching on.
ColibriNANO RECEIVER
ColibriDDC RECEIVER
3) In the OmniRig settings (in the ESDR2) set the Enable checkbox.
4) Press the Configure button to open the OmniRig SW settings window.
5) All further information you can find in the User Manual-> CAT Menu.
Then you set up the OmniRig to operate with a certain transceiver via a certain COM-port.