Carel Hecu handleiding
Handleiding
Je bekijkt pagina 58 van 60
58
Hecu +0300023EN rel. 1.2 - 14.12.2021
Fig. 9.j
2. Enter the new value (e.g. 3) and click OK. The new value will appear
in the column marked “scritto” [written]. To write the parameter to
the pCO controller, right-click and select “scrivi selezionate” [write
selected]. The new value will appear in the column marked “scritto”
[written], meaning that the parameter has been written to the
controller.
Fig. 9.k
Click “Salva” [Save] to generate the project’s “.2cw” fi le.
Commissioning: basic concepts
Notice: the following paragraphs are from the pCO Manager
online help; refer to this for further details.
Commissioning is a confi guring and real-time monitoring software that
can be used to supervise the performance of an application program
installed on a pCO, to commission the pCO and to perform debugging
and maintenance.
This software can be used to set the confi guration parameters, edit the
values of volatile and permanent variables, save to fi le the trends of the
unit’s main values, manually manage the unit’s I/Os using simulation
fi les, and monitor/reset the alarms on the unit that the device is installed
on. Before using Commissioning, the work environment needs to be
confi gured, which is typically done by the project designer. The active
project in 1tool is automatically loaded by pCO Manager. The project
designer can use the confi guration functions in Commissioning to
decide which variables are involved in monitoring, logging, trend-
monitoring and event-monitoring, organise variables into categories and
create sets of confi guration parameters. Operators using Commissioning
for maintenance will be able to see the required variables and exploit
pre-set confi guration values.
Support les
Once the design of the application is completed, 1tool generates a
number of fi les in the compiling stage, two of which are required by
Commissioning:
• <applicationName>.2CF (variable descriptor)
• <applicationName>.2CD (category and access profi le descriptor).
In addition to these fi les, the software also manages the applicationName.
DEV fi le, which contains the unit’s pre-set parameters. When the user has
fi nished using Commissioning, whether for confi guration or monitoring
purposes, the following fi les can be generated:
• <applicationName>.2CW (descriptor for categories, access profi les,
monitoring groups);
• <FilenameCommissioningLog>.CSV (fi le used for the commissioning
log, containing data of the variables logged during monitoring).
Therefore, to confi gure Commissioning the following fi les are required:
.2CF, 2CD and possibly the .DEV fi le that can be imported and exported.
For monitoring purposes, in addition to the fi les above, it might also be
necessary to have the .2CW fi le, containing the defi nition of the work
environment.. The commissioning log fi le is a simple output fi le.
pCO Load: basic concepts
pRackLoad is the module that manages:
• uploading to the fl ash memory (of the device or of the ProgKeyX key
installed on the pRack);
• downloading fi les from the NAND memory, if present.
• downloading the log, the .DEV fi le and the P memory (from Flash
memory).
• downloading NAND memory fi les, if present.
The fi les exchanged with the fl ash memories on the pCO controllers are:
• 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, where the .GRP fi le is extracted);
• <applicationName>.IUP;
• <applicationName>.LCT;
• <applicationName>.PVT;
• <pCOlogName>.BIN, <pCOlogName>.CSV, <pCOlogName>.CSV (only
if log fi les have been confi gured, download only).
The fi les exchanged with the NAND memories on the pCO controllers are:
• any fi le that the pCO can independently copy to the fl ash memory
(see above list);
• External fi les (e.g.: PDF, .doc for documentation).
LogEditor: basic concepts
LogEditor is the module used to confi gure the log fi les of pCO devices
(pCO logs). Confi guring pCO logs consists in defi ning a number of sets
of variables in which to specify which variables should be logged, the
logging method (by frequency or by event) and the minimum number
of loggings 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 of the log confi gurations
defi ned in this way 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. The 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 as 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 in a generic format with values
separated by commas;
• a *_GRAPH.CSV containing the same data to be used for creating
graphs.
9.2 Software revision history
New version 3.0.791
Bekijk gratis de handleiding van Carel Hecu, stel vragen en lees de antwoorden op veelvoorkomende problemen, of gebruik onze assistent om sneller informatie in de handleiding te vinden of uitleg te krijgen over specifieke functies.
Productinformatie
| Merk | Carel |
| Model | Hecu |
| Categorie | Niet gecategoriseerd |
| Taal | Nederlands |
| Grootte | 10743 MB |
