When selling a FLEX-8000/6000, it is desired to completely remove any user-configured data or settings from the radio before transferring the radio to the new owner. The following procedure will outline how to remove all user-configurable data from the radio.
1.) Unregister the FLEX-8000/6000 from your SmartLink Account
- Start SmartSDR for Windows. If you are not logged into your SmartLink account, log in now.
- Highlight your radio and click on SmartLink Setup
- If you see a green check mark and it indicates your radio is "Configured for SmartLink", click on the blue UNREGISTER button.
- You will get a message that the software is trying to connect to the SmartLink server. When a connection is made, you will get the message "Hardware Key the radio now". Press a hardware PTT (foot pedal, mic button, CW paddles).
- The message "Your radio has been unregistered" will be displayed when you have successfully unregistered your radio from your SmartLink account.
There is no need to delete your SmartLink account even if you do not plan to use it ever again.
2.) Reset The FLEX-8000/6000 Callsign and Nickname
- Connect to the radio using SmartSDR for Windows. From the top menu bar select the Settings -> Radio Setup -> Radio tab
- In the CALLSIGN field beside the Callsign button, backspace to delete any information in the box and then enter NOCALL. Press the <ENTER> key when done.
- In the NICKNAME field beside the Nickname button, backspace to delete any information in the box and then enter FLEX-6000. Press the <ENTER> key when done.
- Close the Radio Setup window.
- Shut down SmartSDR for Windows.
3.) Perform a Comprehensive Cold Boot and Factory Reset of the radio
NOTE: Before starting, shut down all programs that may interface with the radio, such as loggers, digital mode programs, and NodeRed devices.
NOTE: If you have anything connected to the REM ON connector on the back of the radio, please remove it before running the reset procedure. Once the reset procedure is finished, it can be reconnected.
Before you get started, please note the "wait times" in the steps listed below. These are important to ensure the radio resets properly.
- Power off the radio by pressing and releasing the power button. Allow it to completely power down before continuing by waiting for the power LED to turn off (or amber if a FLEX-6000 GPSDO is installed). If pressing and releasing the power button does not shut down the radio, press and hold the power button until the radio shuts down. If this does not work, turn off the DC power supply to shut down the radio.
- Once the radio is powered off, wait for 2 minutes to allow for all processors to shut down properly.
- Remove DC power from the radio by disconnecting the DC power cable for at least 30 seconds. Removing the DC power cable rather than turning off the power supply is vital to ensure a complete power down of the radio's processors.
- Reconnect the DC power cable and turn on your power supply.
- Wait 2 minutes after turning on the DC power supply to allow the internal PSoC processor to boot up completely before continuing.
For FLEX-6700 and FLEX-6500:
- Press and hold the OK button while simultaneously pressing and releasing the Power button.
- Release the OK button once the power LED turns white, and allow the radio to continue booting normally. When the Power LED is solid green, the radio has completed the boot-up process.
For FLEX-6300, FLEX-6x00(M), FLEX-8x00(M):
- Press and hold the Power button for approximately 5 seconds until the Power button LED turns white. After the power button turns white, release it and allow the radio to continue booting, indicated by a flashing green power button LED. When the Power button LED is solid green, the radio has completed the boot-up process. Depending on several factors, the radio may take a few minutes to start booting, so please be patient and allow it to boot up completely.
Refrain from loading any previously exported (saved) profiles. Please test for the problem you were experiencing before loading any profiles. The problem you are experiencing may be related to inconsistent or corrupted profiles.