Carel PRK300D0E0, User Manual, Page: 79 / 104

79
ENG
pRack +0300025EN rel. 1.3 - 17.12.2015
10. UPDATING THE SOFTWARE
The pRack pR300 boards are supplied with the software already loaded. If
an update is required, the following can be used:
•
pRack Manager
•
SmartKey programming key
Note : The pRack pR300 software is protected by digital signature
and cannot be loaded onto hardware other than pRack pR300 (e.g.
pCO3), otherwise after 5 minutes of operation the software locks up, all
the relays open and the warning “INVALID OEM IDENTIFIER” is shown’.
The update fi les are available at http://ksa.CAREL.com.
Important : each version of the pRack pR300 software is associated
with a specifi c controller fi rmware version (BIOS), therefore if
updating the version, always check and where necessary update the BIOS
on the board. The appropriate BIOS version is supplied together with the
pRack pR300 update fi les.
10.1 Updating using pRack Manager
The software resident in the pRack pR300 boards can be updated from
a PC.
For the connection procedure see Chapter 9, while for further details see
the pRack Manager program online help..
Note : The pCOLoad program can also be used to update the pRack
pR300 software, however Winload cannot be used.
10.2 Updating using SmartKey
The SMARTKEY programming key can copy the contents of one pRack
pR300 board to another identical board, using the telephone connector
on the terminal (the pLAN must be disconnected).
From a PC, with the SmartKey Programmer software running, the key can
be confi gured to perform specifi c operations: acquire log fi les, program
applications, etc.
The SmartKey Programmer software is installed together with pRack
Manager.
The following fi gure shows the connection of the SmartKey to the PC
using the PCOSO0AKY0 converter.
PCOS00AKY0
VWDUW
PRGH
Fig. 10.a
Note : for further details on using the SmartKey, see the
corresponding instruction sheet. For details on the SmartKey
Programmer see the online manual.
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.
File 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.
FILE T Y PES FOR UPLOAD
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.
Important: 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.
FILE T Y PES FOR DOWNLOAD (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.c
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.