27
SYSTEM ERROR MESSAGES
DATABASE EMPTY
Reason:
An attempt was made to edit or delete a user when the database was empty.
Solution:
These functions do not apply when the database is empty.
DATABASE FULL
Reason:
An attempt was made to add a user to the database and there is no more room. The maximum number
of user aliases of 128 cannot be exceeded.
Solution:
Remove any old user names that are no longer in service. If this is not possible, contact Midian to learn
about our Computer Aided Dispatch (CAD) fleet management systems which can handle many more users.
DATABASE ERROR
Reason:
One or more entries in the user database has been corrupted. This can happen if power is lost at the
exact time the database is being updated. Any corrupted records will be blanked-out and must be re-entered.
Solution:
Cycle power to the unit. This should clear the error. If the error message continues to come up, contact
Midian technical support.
DUPLICATE ID
Reason:
An attempt was made to add a user ID to the database which is already in the database. Each user ID in
the database must be unique.
Solution:
Choose a unique user ID for each user. If it is necessary to edit the user record, use the edit menu.
EE CHKSUM ERR
Reason:
The configuration settings stored in EEPROM have been corrupted. This can happen if power is lost at
the exact time a parameter is being updated. All configuration settings will be set back to defaults. The user
database should not be affected.
Solution:
Cycle power to the unit. This should clear the error. If the error message continues to come up, contact
Midian technical support.
EE WRITE FAIL
Reason:
The EEPROM chip or connections to it have failed.
Solution:
Contact Midian for instructions on getting the unit repaired.
FIELD IS BLANK
Reason:
An attempt was made to place a call, but the user ID or name was blank. An attempt was made to spy
or kill and the respective field in the database is blank.
Solution:
When placing a call, be sure an ID number or user name is displayed before pressing SEND. The spy
and kill functions require there be an entry in the respective field of the user database.
COPRO TIMEOUT
Reason:
This message indicates that the coprocessor is not responding to commands from the main processor.
Generally, this message should never be seen.
Solution:
If this message is displayed, press the CLR key several times, three seconds apart, until the unit
returns to normal. If it does not, try turning the power off and back on again. If this message continues to be
displayed, or is displayed frequently, contact Midian technical support.
