P
AGE
14
M
IDIAN
E
LECTRONICS
I
NCORPORATED
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 155 cannot be exceeded.
Solution:
Remove any old user names that are no
longer in service. If this is not possible, contact Midian
for possible alternative products.
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 NAME
Reason:
An attempt was made to add a user name to
the database which is already in the database. Each
user name in the database must be unique.
Solution:
Choose a unique user name 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.
ENCODER TIMEOUT
Reason:
The PDE expects a page to be completed
within 20 seconds and this time has been exceeded.
This can happen in the if the total time of the key-up
delay and encoding exceeds 20 seconds. This is not
likely to happen unless non-standard encode timings
and encode lengths are used. It is also possible that
there could be a hardware failure.
Solution:
If total time of the key-up delay and signaling
tones exceeds 20 seconds, simply press <SEND> to
clear the message from the display. The page will still
be sent. In the event of a hardware failure, contact
Midian technical support to determine if that is the
cause.
INVALID CAP CODE
Reason:
The number of digits in the CAP code are
incorrect for the pager format being used.
Solution:
Enter the correct number of digits. Most built-
in 2-tone formats require exactly 3 digits. POCSAG
requires 7 digits, and ‘any 2-tone’ requires 10 digits.
The other formats can accept 1-10 digits.
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 CAP code can be entered in whole or in part. When
entering a partial name or CAP code, press the right
<SCROLL> button to search the database for the first
partial match. Press <SEND> only if the whole CAP
code 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.
NOT NUMERIC MESSAGE
Reason:
You are trying to send a message containing
non-numeric characters (other than those below) to a
POCSAG pager designated as being numeric only.
Solution:
Restrict your entry to POCSAG ‘numeric’
characters only. These are 0123456789?U-][ and
space.
PROFILE IN USE
Reason:
You have selected a pager profile to edit that
is associated with a user in the database. This
message is provided as a warning so that you do not
change a user’s profile unintentionally.
Solution:
You may either press <#> to cancel your
selection, or press <SEND> to proceed to view or edit
the selected profile. Changing an already assigned
profile may cause problems if the profile changes, say,
from POCSAG to 2-Tone because 2-Tone users
cannot have 7-digit CAP codes! Please keep this in
mind if you proceed to do this.
