Dover Unified Brands Randell BC-10, Руководство оператора

Страница: 18 / 31

18 800-621-8560
b . Overview of Print/Log Operation:
i
. Data logging begins after an Auto or Manual “Timed” chill
mode is initiated, either manually or automatically.
ii . Chill data is acquired periodically and stored into log memory
every five minutes. Data may also be stored immediately upon
detection of specific
Log Events .
iii. “ Live ”chill information can be simultaneously obtained at the
printer output, if enabled (Preset Prnt = On ).
iv . A “
History”
of chill cycle information can also be printed by
depressing the Print Key and selecting one of two history
formats using the Up or Down Key : Last (for last chill cycle) or
24hr (last 24 hours worth of chill cycles). Depressing the Print
Key a second time selects the format and begins the print
process. Pressing the Print Key two times cancels the print log
process.
v. Several Print Log filter options are available that allow
specific log events to be printed. This filter works while printing
Live during a Chill operation or when printing a History of prior
chill information.
c . Log Data Specification
i . The log memory consists of a nonvolatile storage device
capable of holding 1489 records, equivalent to approximately 5
days worth of chill performance history. Each individual record
consists of ten (10) data members:
1. Timestamp - Date, Time, and Time of day
2. Event – The specific incident that results in a log
record to be created.
Further details on the supported Event types are covered
in the Log Events section.
3.
Mode – The type of chill mode in operation: Auto or
Timed.
4.
Cycle
– The cycle in operation for the selected mode:
Chill, Defrost, or Hold.
5.
Probe Temperatures – Temperature values measured
in degrees Fahrenheit for each of the six (6) supported
sensor inputs: Product Probes 1 through 4, the Air probe
and the Defrost Probe.
ii . Log Events
1. Chiller parameters are typically “Sampled” and
recorded into log memory once every five minutes.
However, this process can also be
triggered by specific controller events. These events and
their significance are described below:
a . Start (*START*) – Denotes the start of a chill
cycle.
b. End (*END*) – Denotes the end of a chill
cycle.