44
Error Messages (ERR nnn)
Error messages may be displayed on VFO B at power-up or during normal operation. In many cases error
messages are due to a problem with a single option module or incorrect firmware configuration.
If you see an error message on VFO B (ERR nnn): Write down the error message, as well as any associated
error data shown on the VFO A display (e.g. d= 0 05 ). Then tap any switch to clear the error code. Multiple
errors may occur; in this case, write down each of the messages and VFO A data, if any, before you clear them.
See Error Message table below for details on specific ERR messages and associated data values, if any.
KXAT3 module not accessible:
ATC = I/O expander C
ATD = I/O expander D
ATI = I/O address mismatch
If the module is not actually installed, set MENU:ATU
MD to N OT IN ST. If the module is installed, remove it
and re-install it, making sure both connectors are correctly
lined up with their mating connectors on the RF board.
KXAT3 relay failure (on VFO
A, d=nn n identifies the failing
relay, e.g. 001 for relay K1)
Turn power off for 10 seconds, then back on. Remove and
re-install the KXAT3 option module, making sure both of
its connectors are correctly lined up with their mating
connectors on the RF board. If this doesn’t correct the
problem, replace the module.
KXBC3 module error (battery
charger/real-time-clock).
d=nn n is the specific error
code (report to Elecraft).
Turn power off for 10 seconds, then back on. If this
doesn’t correct the problem, re-seat the KXBC3 module
and repeat. If the problem persists, replace the KXBC3.
DSP SPI echo not inverted
DSP, CODEC, or ADC power-
up self-test failed
Extended DSP command
timeout
Turn power off for 10 seconds, then back on. Reload
MCU and DSP firmware. If this doesn’t correct the
problem, save your configuration using KX3 Utility, then
perform an EEINIT (pg. 43). If this corrects the problem,
restore your configuration using KX3 Utility. If error
codes persist, the Control Panel module may have to be
replaced. Write down all error codes and associated data
values (displayed on VFO A) before contacting Customer
Support.
On-chip EEPROM read/write
test failed
The main microcontroller (MCU) may be defective.
Follow the steps shown for ERR DS1.
External EEPROM read/write
test failed
EEPROM may be defective. However, this message may
also appear if power is turned off/on too rapidly, or if the
power supply voltage “bounces” during turn-on due to
inadequate regulation. If the power supply is not at fault,
follow the steps shown for ERR DS1.
General firmware problem.
d=nn n identifies the type of
error (report to Elecraft).
Follow steps shown for ERR DS1.