Daikin Hubbard GCU2040PXB1, Инструкция по установке, пусконаладке и обслуживанию

Страница: 138 / 172

89
ENG
pRack PR300T +0300018EN rel. 1.5 - 02.05.2017
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
pRack 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. 10.j
Click on “Salva” [Save] to generate the project’s “.2cw” fi le.
10.2.4 Commissioning: basic concepts
Note: The following paragraphs are from the online help of pRack
Manager, to which the user is referred 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 pRack, to start up the pRack and to perform debugging and
maintenance.
Operators using Commissioning for maintenance will be able to see the
necessary variables and to draw from preset confi guration values.
10.2.5 Support fi 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:
•
<nomeApplicativo>.2CF [<ApplicationName>.2CF] (variable descriptor)
•
<nomeApplicativo>.2CD [<ApplicationName>.2CD] (category and
access profi le descriptor)
In addition to these fi les, the software also manages the <nome
applicativo>.DEV [<Application Name>.DEV] fi le, which contains the unit’s
preset parameters.
When the user has fi nished using Commissioning, whether for confi guration
or monitoring purposes, the following fi les can be generated:
•
<nomeApplicativo>.2CW [<ApplicationName>.2CW] (descriptor for
categories, access profi les, monitoring groups)
•
<nomefi leCommissioningLog>.CSV [<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, if necessary, the.DEV fi le, which can be imported or 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.
10.2.6 pRack 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);
•
uploading to the NAND memory of certain devices;
•
downloading the log fi le,.DEV fi le and P memory (from the fl ash
memory);
•
downloading fi les from the NAND memory, if present.
The fi les exchanged with the Flash memories of pRack controllers are:
•
BOOT.BIN (download reserved, upload enabled from menu)
•
BIOS.BIN (download reserved)
•
<nomeApplicativo>.BLB [<ApplicationName>.BLB] (download reserved)
•
<nomeApplicativo>.BIN [<ApplicationName>.BIN] (download reserved)
•
<nomeApplicativo>.DEV [<ApplicationName>.DEV]
•
<nomeApplicativo>.GRT [<ApplicationName>.GRT] (upload only, from
which the.GRP fi le is extracted)
•
<nomeApplicativo>.IUP [<ApplicationName>.IUP]
•
<nomeApplicativo>.LCT [<ApplicationName>.LCT]
•
<nomeApplicativo>.PVT [<ApplicationName>.PVT]
•
<nomepRacklog>.BIN, <nomepRacklog>.CSV, <nomepRacklog_
GRAPH>.CSV [<pRacklogName>.BIN, <pRacklogName>.CSV,
<pRacklog_GRAPHName>.CSV] (only if log fi les have been confi gured,
download only).
The fi les exchanged with the NAND memories of pRack controllers are:
•
any fi le that the pRack can independently copy to the fl ash memory
(see above list);
•
external fi les (e.g..pdf or.doc fi les for documentation).
10.3 Pendrive: operating instructions
10.3.1 File extensions, names and contents
Various types of fi les can be uploaded and downloaded and are
distinguished by their extension.
F ile names
In order to be recognised, the names of the directories and fi les on the
pendrive must have no more than 8 characters; the controller makes no
distinction between upper-case and lower-case characters. However,
during DOWNLOAD the names of the directories created by the controller
on the pendrive are always in upper-case.
F I LE TYPES F OR UPL O AD
File extension Description
.IUP Contains the defi nitions of the screens on the terminal
.BLB Contains the application
.BIN Contains the application (with pLAN table)
.BLX Contains the Logique of atoms custom in C language
.GRP Contains the graphics
.DEV Contains the preset confi guration parameter values
PVT,.LCT Contains the descriptions of the public variables to be
logged. Generated by 1Tool, this is used by the LogEditor
module and must be loaded together with the.LCT fi le
Downloaded fi les are saved in directories created automatically, with the
following name format:
NAMXY_WZ
Where:
NAM: identifi es the type of data downloaded (LOG for logs, BKP for the
application, DEV for the buff er memory, CPY for all the data from the
controller).
XY: progressive number from 0 to 99
WZ: controller pLAN address.
Example: a directory named LOG00_01 contains the log fi les (LOG)
downloaded from a device whose pLAN address is 1. Since the key
contained no directory of this type before download, it is indicated with 00.
I mportant: No more than 100 fi les of the same type can be
downloaded to the pendrive, as the directories created can only be
numbered with XY=00 to 99.
F I LE TYPES F OR D O WNL O AD ( controller pLAN address = 1 )
File extension Directory name Description
.DWL LOG00_01 Logged data
.DWL,.DEV,.LCT,.
PVT BKP00_01 Application
.DEV DEV00_01 Non-volatile parameters
.DWL,.DEV,.LCT,.
PVT CPY00_01 All data on the controller
Tab. 10.e
The downloaded fi les to have fi xed names. In particular, the application
fi le is called “ppl–pRack.dwl”, the BIOS fi le “bios–pRack.bin”, the fi les
containing the logs and related information are “logs.dwl”, “logs.lot” and
“logs.pvt”, respectively. Finally, the buff er memory is saved to the fi le on
the pendrive.
Page 138 of 172
Copyright HPL March 2021 P4114S Rev 03