Checking The Software Installed And Other Information - Carel pCO5+ User Manual

NAND fl ash memory
This type di memory is included on all pCO5+ controller versions. pCO
Manager can be used to load any type of fi le to the NAND fl ash memory.
It can be used, for example, to save the source fi les of the application
program being used.
In addition, the IUP, BLB (or BIN) and DEV fi les that represent parameter
fi les, the screens displayed in the various languages and the control
logic can be loaded to the NAND fl ash memory and then selected from
the terminal screen to be used as the current application on the pCO.
Specifi cally, several diff erent applications, or diff erent languages, or
multiple parameter fi les can all be loaded in the NAND fl ash memory,
after which the desired application, language or parameter confi guration
can be selected and loaded to the main fl ash memory. The fi les saved in
the NAND fl ash memory can be selected and copied to the main fl ash
memory on the screen managed directly by the BIOS. The procedure is
described in paragraph 6.6.
Limitations:
•
a maximum of 40 fi les can be saved on the NAND fl ash memory;
•
the memory's total storage capacity is 50 MB.
Pendrive
Some controller models come with two diff erent USB ports (host and
slave) to be used for installation and diagnostics. The host port can be
used to connect USB mass storage peripherals (pendrives, portable hard
disks, etc., having a maximum current consumption of 500 mA) with
which to carry out various operations:
1. upload to the controller fi les contained in the removable peripheral
(e.g. application, parameters in the buff er memory, confi guration fi les
for logs, BIOS);
2. download fi les from the pCO5+ to the removable peripheral (e.g.
application, parameters in the buff er memory, data logs, BIOS).
Note: Using the pendrive to perform the following operations:
•
UPLOAD - copying fi les from the pendrive to the controller;
•
DOWNLOAD - copying fi les from the controller to the pendrive is
possible only when using a terminal, either built-in or connected to
the controller via pLAN.
The controller can be provided with 2 USB ports which can be accessed
by removing the cover (see chap. 2).
The keypad has 6 buttons that, pressed alone or in combination, can be
used to perform all the UPLOAD and DOWNLOAD operations between
the pendrive and the controller.
Important
•
before the pendrive can be used it must be formatted to the FAT32
fi le system;
•
the pendrive can be accessed up to two levels – APPL\CHILLER\PRI.BIN
– but access to fi le \APPL\CHILLER\VER1\PRI.BIN is not allowed;
•
do not use both USB ports at the same time;
•
the maximum pendrive capacity supported is 32 GB.
Manual, automatic and autorun mode
•
manual mode involves selecting the operations to be performed via
the keypad; this off ers maximum fl exibility and the possibility to freely
decide which operations to perform;
•
automatic mode requires creating special fi les called confi guration
fi les. These are text fi les (.txt extension) containing various types of
information on the functions to perform and the fi les to load;
•
autorun mode requires creating a special confi guration fi le called
"autorun.txt". When the pendrive is plugged, in the controller
immediately executes Autorun and upon confi rmation from the
terminal performs the operations contained in the fi le.
Upload and Download
UPLOAD can be performed in three diff erent ways:
1.
manual mode: the user selects manual mode from the keypad, then
the fi les to load, and then confi rms to start the operation;
2. automatic mode: the user selects automatic mode from the keypad
and then the confi guration fi les containing the instructions on the
operations to carry out;
3. autorun mode: after the pendrive is plugged in, a screen is displayed
indicating that Autorun mode has started. After confi rming, the
instructions contained in "autorun.txt" are executed automatically.
The contents of this fi le are similar to the UPLOAD confi guration fi les,
the only diff erence being the name "autorun.txt".
DOWNLOAD can be performed in two diff erent ways:
1. manual mode: the user selects manual mode, then the fi les to
download, and then confi rms to start the operation;
2.
autorun mode: after the pendrive is plugged in, a screen is displayed
indicating that Autorun mode has started. After confi rming, the
instructions contained in "autorun.txt" are executed automatically.
The contents of this fi le are similar to the DOWNLOAD confi guration
fi les, the only diff erence being the name "autorun.txt".
Note: The confi guration and autorun fi les must reside in the main
directory.
The steps to follow are described in par. 9.3.
6.6 Checking the software installed and
other information
Users can at any time check the version of the current program (by CRC
code, expressed in hexadecimal), and also whether it is being used by the
key or by the resident program. To do this, proceed as follows.
Screens managed by BIOS
Press the ALARM and ENTER buttons together for 3 seconds. The following
screen will appear.
> S Y S T E M
L O G D A T A
O T H E R
F L A S H / U S B
Each of the four lines displayed is used to access further screens, managed
by BIOS and consequently always available regardless of the application
loaded. To access the functions, select the line with the cursor ">" using
the UP and DOWN buttons and then press ENTER to confi rm. To exit the
screen press MENU or Esc on the terminal, or wait around 40 seconds for
automatic timeout.
The screens provide the following information.
1. SYSTEM INFORMATION: Selecting this function displays
information on the software loaded and the amount of RAM
and fl ash memory installed. The screen displayed is similar to the
following.
B O O T V
B I O S V
> 2 + 7 M B
A _ C R C : 0 0 0 0 -
The fi rst line displays the BOOT version and date. In the example shown,
the pCO is working with BOOT 4 dated 6 December 2011. The second
line displays the BIOS version and date. In the example shown, the pCO
is working with BOOT 6 dated 13 January 2012. The fourth line displays
the application CRC and the amount of fl ash memory occupied. In the
example, the application's CRC value is 3617. If this line shows 1 MB, a pCO
with 1 MB fl ash is suffi cient. The CRC is a number that summarises the
application contained in the pCO's fl ash memory, but also other system
information. It is therefore recommended to note the version of a specifi c
application by checking the screen on which it is displayed.
39
I N F O R M A T I
I N F O R M A T I O N
M E M O R Y
4 . T E 6 / 1 2 /
6 . T E 1 3 / 0 1 /
<
3 6 1 7
pCO5plus +0300020EN rel. 1.2 - 07.11.2013
ENG
O N
1 1
1 2
M B