P
AGE
14
M
IDIAN
E
LECTRONICS
I
NCORPORATED
DDU-100/200
Manual
6 SYSTEM
ERROR
MESSAGES
CHANNEL BUSY
Reason:
An attempt was made to transmit or make a
call on a busy channel with busy lockout enabled.
Solution:
Wait until the channel is clear before
transmitting.
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 137 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.
MODEM TIMEOUT
Reason:
The DDU expects a call to be completed
within 4.5 seconds and this time has been exceeded.
This can happen if the total of the key-up delay and
tone widths exceed 4.5 seconds. This can also happen
when used in a trunking system and a channel cannot
be acquired. It is also possible that there could be a
hardware failure.
Solution:
If total time of the key-up delay and signaling
tones exceeds 4.5 seconds, simply press <SEND> to
clear the message from the display. The call will still be
sent. If the timeout is caused by excessive channel
acquisition time in a trunking system, press <SEND> to
clear the error and try placing the call again. In the
event of a hardware failure, contact Midian technical
support to determine if that is the cause.
NOT FOUND
Reason:
There is no entry in the user database that
matches the data entered.
Solution:
When selecting a user to call, the name or
the ID can be entered in whole or in part. When
entering a partial name or ID, press the right
<SCROLL> button to search the database for the first
partial match. Press <SEND> only if the whole ID or
name has been entered. There may be no entry in the
database that matches in whole or in part. In that case,
the user must be added to the database.
