42
AVOIDING PROGRAMMING CONFLICTS
This section explains how to avoid conflicts that will result in
programming errors.
If there is a conflict in the parameters, a programming error will be generated and
an two-tone alarm will be
sounded
. If this should occur, check the parameters for any possible conflicts and then make corrections as necessary.
This section provides a few basics guidelines to avoid programming conflicts.
(See page 66 for a chart of parameter error codes.)
<PROGRAMMING GUIDELINES AND RULES>
The following examples are designed as representative examples of conflict related errors commonly encountered
during the programming the MX-300, but this section is no way intended to serve as an exhaustive guide to dealing
with all possible programming errors.
■
Basic Programming Rules for Both Regular Employee and Hourly Worker Parameters
* A single work day is defined by the Day Change Time parameter. Therefore, it is critical that all other time zone
parameters are configured within the threshold of the Day Change Time. Failure to abide by this basic rule is to
open the doors to programming error after programming error.
Example of This Kind of Conflict:
Break Beginning Time17:30
Break End Time 18:15
Day Change Time 18:00
* When configuring multiple breaks, it is absolutely vital to avoid overlapping. Failure to do so will result in a
programming error.
Example of This Kind of Conflict:
# 1 Break Beginning Time12:00
# 1 Break End Time 13:00
# 2 Break Beginning Time 12:30
# 1 Break End Time 13:30
■
Basic Programming Rules for Regular Employee Parameters
* Configuring a Break Time Zone between the Shift End Time and the Overtime Beginning Time will result in a
programming error.
Likewise, configuring Break Time Zone that extends over a Shift Beginning Time or Shift End Time will result
in a programming error.
Also, configuring the Shift End Time to the same time as a given Break Beginning or End Time will result in a
programming error.
Example of This Kind of Conflict:
Shift End Time 17:00
Overtime Beginning Time 17:30
Break Beginning Time 16:45
Break End Time 17:15
* Configuring the Overtime Beginning Time earlier than the Shift End Time will result in a programming error.
(However, configuring them to the same time is okay.)
Example of This Kind of Conflict:
Overtime Beginning Time 17:00
←
Shift End Time 17:30
* Configuring the Shift End Time or Overtime Beginning Time to the same time as the Day Change Time will
result in a programming error.
Example of This Kind of Conflict:
Shift End Time
20:00
Day Change Time
20:00
Overtime
Beginning
Time
20:00