Midian DDU-300, Instruction Manual

Page: 14 / 22

P
AGE
14 M
IDIAN
E
LECTRONICS
I
NCORPORATED
DDU-300 Manual Rev. 2006.02.22
6 SYSTEM ERROR MESSAGES
CHANNEL BUSY
Reason: An attempt was made to transmit 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.
MODEM TIMEOUT
Reason: The LTR input is being used and a channel
could not be acquired on the trunking system. The
DDU will wait about 4.5 seconds for the LTR input to
go high before issuing this message and aborting the
command in progress.
Solution: Try issuing the command again.
Reason: The modem (encode/decoder) section of the
DDU is not responding to commands. This could be
the result of a hardware failure.
Solution: Cycle power to the unit, Reset default
parameters via the UTILITIES menu. Cycle power to
the unit once again. If the error message continues to
come up, contact Midian technical support.
NOT FOUND
Reason: There is no entry in the user database that
matches the data entered.
Solution: When selecting a user to edit or delete, 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 is not in the database.