Carel pCO2 Manual

Standard Chiller/HP modulare per compressore a vite con driver CAREL
Cod.: +030221241 Rel. 1.0 dated 25 September 03
46
21 Alarm log
The alarm log can store the standard chiller’s operating state when alarms are generated or at particular times. Each set of data stored is an event
that can be viewed by selecting it from the list of logged events. The log proves useful when troubleshooting because a “snapshot” is taken of
the system when the alarm occurs, which can later be used to help determine possible causes and how to remedy the trouble.
There are two kinds of log in the program, the STANDARD log and ADVANCED log.
21.1 Standard log
The pCO* boards’ considerable buffer space means events can be saved in the STANDARD log, which is always available on the various
boards. If there is no clock card (optional extra on pCO1 and pCOC, built-in feature on pCO2), the STANDARD log just gives the alarm code.
The maximum number of events that can be logged is 100. Once the hundredth alarm is reached, i.e. the last available slot in the memory is
taken, the oldest alarm (00) is erased as it is overwritten with the next alarm, and so on for subsequent events. Logged events cannot be deleted
by the user unless installing factory settings. The STANDARD log screen can be called up by pressing the MAINTENANCE key, and looks
like this:
+--------------------+
¦ Alarm log A2¦
¦Event number 00¦
¦Alarm code 000¦
¦Date 00:00 00/00/00¦
+--------------------+
For each alarm, the following data are stored relating to the standard chiller at the time of the alarm:
• alarm code
• time
• date
• chronological event number (0-99)
The chronological event number indicates the “seniority” of the event with respect to the 100 available storage slots. The alarm with number 00
is the first to occur after the STANDARD logs are enabled, and hence the oldest.
If you move the cursor onto the chronological number, you can run through the alarm log, from 0 to 99, using the arrow keys.
For instance, if you are on position 00, pressing the down arrow will not take you anywhere.
If 15 alarms have been logged, for instance, and you are on position 014, pressing the up arrow will not take you anywhere.
21.2 Advanced log
Events are logged on the 1MB or 2MB memory expansion module, which is a permanent appendix to the board. Advantages and features are
listed below:
• Event-based log: a typical event-based log is the alarm log. When an alarm occurs, the alarm generated is stored along with significant
data (temperatures, pressures, set points etc.).
• Time-based log: a typical event[sic! probably time]-based log is the temperatures/pressure log. Temperature and pressure values are
stored at regular intervals.
• Log log: this is the log of the last alarms/temperatures/pressures stored before a serious alarm. Unlike data stored in the event- and
time-based logs, these data are not overwritten when the memory is full.
• You have the option of choosing the values to be saved at any time as well as the method used to save them. Using the “WinLOAD”
utility program, you can define the values to be saved and the method used to save them with the aid of a practical Wizard. WinLOAD
does not need application software files as it can procure all the information required directly from the pCO1 – pCO2 board’s resident
application software.
• 1MB of dedicated FLASH memory. With this system, data are saved to the 1MB FLASH memory included in the memory expansion
module (code PCO200MEM0). By way of example, 1MB of memory can hold 5,000 alarm events with 5 values for each alarm, and 6
months of recording 2 values - for instance, temperature and pressure - saved every 5 minutes.
• Option of defining up to 7 different log configurations. Usually, each controller will have one alarm log and one log for control values
(temperature/humidity/pressure) configured, in addition to a number of “log logs”.
• Stored data can be consulted either via the (separate or built-in) LCD terminal or via a connected PC.
• “Black box” operating mode. The memory expansion module containing the logs can be removed from the controlled unit’s pCO² and
inserted in another pCO², via which the stored data can be consulted. The host pCO² does not need to contain the same software as the
original.
• Stored data reliability. Data are saved to a FLASH memory that does not need batteries, which are liable to run down. If previously
stored data are not compatible with new software following an upgrade, all data are erased (you are prompted to confirm first).

Carel pCO2 Specifications

General

Brand	Carel
Model	pCO2
Category	Controller
Language	English