Carel Hecu CO2, Руководство пользователя

Страница: 60 / 64

60
ENG
Hecu
C O
2
+0300085EN rel. 2.2 - 07.05.2019
C
hanging a parameter
Choose the category of parameters and then the parameter to be set: this
is highlighted by a blue line (e.g. recovery.recovery_type).
Fig. 9.i
1.
Double click the mouse on the read column. A window is displayed
for entering the new parameter value.
Fig. 9.j
2.
Write the new value (e.g. 3) and select OK. The new value is displayed
in the written column. To write the parameter to the pCO controller,
click the right mouse button and run the write selected command.
The new value is displayed, confi rm the value in the written column.
Fig. 9.k
Finally, run the Save command to generate the project .2cw fi le.
C
ommissioning tool: basic concepts
Note: the following paragraphs are taken from the pCOmanager
program online help; refer to this for any further details.
The commissioning tool is real-time confi guration and monitoring
software used to check the operation of an application program installed
on a pCO, for commissioning a pCO, debugging and maintenance.
This tool can be used to set the confi guration parameters, modify the
values of volatile and permanent variables, save the trends of the main
unit values to a fi le, manually manage the unit I/Os using simulation fi les,
and monitor/reset the alarms on the unit where the device is installed.
The commissioning operations fi rst require confi guration of the work
environment, typically the task of the designer. The active 1tool project
is automatically loaded by the pCO Manager. The commissioning tool
confi guration functions allow the designer to decide which variables
will be included in the monitoring/log/trend/event monitoring activities,
to organise variables into categories, and to set groups of confi guration
parameter. Users who use the commissioning tool during maintenance
operations will already have access to the required variables, and will be
able to refer to pre-set confi guration values.
S
upport fi les
At the end of the application program design phase, 1tool generates
several fi
les during compilation; two of these are required for
commissioning:
•
<applicationName>.2CF (variable descriptor);
•
<applicationName>.2CD (descriptor of categories and access profi les).
In addition to these fi les, the <applicationName>.DEV fi le can also be
managed, which contains the pre-set unit parameters. After having
completed commissioning, either for confi guration or monitoring, the
user can generate the following fi les:
•
<applicationName>.2CW (descriptor of categories, access profi les,
monitoring groups);
•
<CommissioningLogFileName>.CSV (fi le used for the commissioning
log, with the data of the variables logged during monitoring).
The commissioning confi guration phase thus requires the following fi les:
.2CF, 2CD and where possible the .DEV fi le, which can be imported and
exported.
For the monitoring phase, in addition to the above fi les, the .2CW fi le
may be needed, with the defi nition of the specifi c work environment. The
commissioning log fi le is a simple output fi le.
p
C O
Load: basic concepts
pCOLoad is the module that manages:
•
uploading to fl ash memory (ProgKeyX device or key installed on the
pCO);
•
uploading to NAND memory on certain devices;
•
downloading logs, .DEV fi le and P memory (from fl ash memory).
•
downloading NAND memory fi les, if present.
The following fi les are exchanged with the pCO fl ash memory:
•
Boot.BIN (download reserved, upload enabled from menu);
•
Bios.BIN (download reserved);
•
<applicationName>.BLB (download reserved );
•
<applicationName>.BIN (download reserved );
•
<applicationName>.DEV;
•
<applicationName>.GRT (upload only, from which the .GRP is
extracted);
•
<applicationName>.IUP;
•
<applicationName>.LCT;
•
<applicationName>.PVT;
•
<pCOlogName>.BIN, <pCOlogName>.CSV, <pCOlogName_GRAPH>.
CSV (only if logs have been confi gured, download only).
The following fi les are exchanged with the pcO NAND memory:
•
All of the fi les that the pCO can autonomously copy to the fl ash
memory (see the previous list);
•
External fi les (e.g.: PDF, .doc for documentation).
LogEditor: basic concepts
LogEditor is the module used to confi gure pCO device logs (pCO log).
Confi guring pCO logs involves defi ning a number of sets of variables for
specifying which variables should be logged, the logging method (by
frequency or by event) and the guaranteed minimum number of records
required. Confi guration is based on a binary fi le (.PVT – Public Variable
Table), which is generated by 1Tool and contains the descriptive data of
the variables that can be logged. All the log confi gurations so defi ned
are saved in the .LCT (Log Confi guration Table) binary fi le, which must be
uploaded to the pCO together with the .PVT fi le. Log confi guration data is
also saved in a fi le that can be used only by LogEditor – the .LEF fi le, which
must be saved to be edited with LogEditor when necessary. LogEditor
can be used even when the device is not connected.
Once the fi les for logging are uploaded to the pCO, the pCO saves the
logged data in the following fi les:
•
a .BIN fi le containing all the data in binary format;
•
a .CSV fi le containing the same data but in a generic format with
comma separated values;
•
a *_GRAPH.CSV fi le with the same data, to be used for graphs.