Uploading/Updating The Software - Carel c.pCO sistema User Manual

ENG
Acquire/ release commands
These commands are used by a controller to acquire / release a terminal.
Procedure:
1. Press Alarm and ENTER together to enter the system menu. Select
"Settings"
INFORMATION
SETTINGS
APPLICATION
UPGRADE
LOGGER
DIAGNOSTICS
2. Select pLAN Settings
PASSWORD
USB SETTINGS
PLAN SETTINGS
CLOCK SETTINGS
TCP/IP SETTINGS
3. The following screen is shown, where the acquire/release
commands can be activated.
pLan pCO Addr: 1
Release Term: No
Acquire Term: No
Update config: No/Yes
Key
pLan pCO addr. Address of c.pCO controller currently connected to the
terminal
Release terminal Release command
Acquire terminal Acquire command
Update configu- Confirm update
ration
Command virtualisation
Whenever a pGD terminal is connected to a c.pCO, the pGD terminal
displays the corresponding user interface. The command is sent from
the terminal, however it is the controller that executes the operation to
release or acquire the terminal.
Example 1
A: the release command on terminal 21 releases c.pCO 3 from terminal
21, and this is then assigned to c.pCO 1;
B: the release command on terminal 21 releases c.pCO 1 from terminal 21,
and this is then assigned to c.pCO 2.
A
Term 21:
Release term
XXXXXXXXXXXX
1 21 1
F d l e i s u B a c d r B S M a c d r
c.pCO pGD
XXXXXXXXXXXX
2 22 2
F d l e i B s u a c d r B M S a c d r
c.pCO pGD
XXXXXXXXXXXX
3 23 3
F e i d l B s u a c d r B M S a c d r
c.pCO pGD
c.pCO sistema +0300057EN rel. 1.2 - 29.05.2017
B
Term 21:
Release term
XXXXXXXXXXXX XXXXXXXXXXXX
21 1
d l F e i s u B a c d r M B S a c d r F d l e i B s u a c d r B M S a c d r
c.pCO pGD c.pCO
XXXXXXXXXXXX XXXXXXXXXXXX
22 2
e i F d l s u B a c d r B M a c S d r F e i d l s u B a c d r B M S d r a c
c.pCO pGD c.pCO
XXXXXXXXXXXX XXXXXXXXXXXX
23 3
e i F d l B s u a c d r B M a c S d r F d l e i B s u a c d r B M S a c d r
c.pCO pGD c.pCO
Example 2
A: the release command on terminal 22 releases c.pCO 3 from terminal
21, and this is then assigned to c.pCO 1;
B: the release command on terminal 22 releases c.pCO 3 from terminal 22,
and this is then assigned to c.pCO 1.
A
XXXXXXXXXXXX
1 21
e i F B d l s u d r a c M B a c S d r
c.pCO pGD
Term 22:
Release term
XXXXXXXXXXXX
2 22
e i F d l B s u d r a c B M a c S d r
c.pCO pGD
XXXXXXXXXXXX
3 23
F e i d l B s u a c d r M B S a c d r
c.pCO pGD
Example 3
A: the acquire command on terminal 22 acquires c.pCO 1 on terminal 21,
and this is thus assigned to c.pCO 1;
B: the acquire command on terminal 22 has no effect, as c.pCO 1 has
already acquired all the terminals
A
XXXXXXXXXXXX
1 21
e i F d l s u B a c d r B M S a c d r
c.pCO pGD
Term 22:
Release term
XXXXXXXXXXXX
2 22
F e i d l B s u a c d r M B S a c d r
c.pCO pGD
XXXXXXXXXXXX
3 23
d l e i F B s u a c d r B M S a c d r
c.pCO
pGD

6.6 Uploading/updating the software

It is possible to load/update the application software of the c.pCO
controllers family with the following methods:
•
Update from computer by using c.factory (via USB or Ethernet
connection
•
Update via USB flash drive
•
Update with file transfer via FTP (see par. FTP commands)
•
Update via tERA cloud service
The c.factory software is part of the "c.suite", but it can be also installed
individually, downloading it from http://ksa.carel.com under "Software &
Support"->"c.suite".
Update from computer using c.factory
On all c.pCO family controllers, the application program can be uploaded
by using the c.factory software, with direct connection to the controller
via USB cable or Ethernet network. To upload the application program,
proceed as follows:
a) Update from computer using c.factory via Ethernet connection:
Configure the computer and the c.pCO controller so that they belong to
the same LAN (see paragraph 9.2).
1.
Open c.factory and select the application program file compiled in
c.strategy tool (".otr" file extension). The tool will list the configurations
defined in c.design. Select the configuration to be loaded on the
controller and click "next".
21
pGD
22
pGD
23
pGD
42
B
XXXXXXXXXXXX XXXXXXXXXXXX
1 21 1
F e i d l B s u d r a c M B S a c d r F e i d l B a c s u d r M B S a c d r
c.pCO pGD c.pCO
Term 22:
Release term
XXXXXXXXXXXX XXXXXXXXXXXX
2 22 2
e i F B d l s u a c d r B M S a c d r e i F d l B s u a c d r B M a c S d r
c.pCO pGD c.pCO
XXXXXXXXXXXX XXXXXXXXXXXX
3 23 3
e i F d l B s u a c d r B M S a c d r e i F d l B a c s u d r M B S a c d r
c.pCO pGD c.pCO
B
XXXXXXXXXXXX XXXXXXXXXXXX
1 21 1
e i F B d l s u a c d r B M S a c d r F e i d l B s u a c d r B S M a c d r
c.pCO pGD c.pCO
Term 22:
Release term
XXXXXXXXXXXX XXXXXXXXXXXX
2 22 2
F e i B d l s u d r a c M B S a c d r F d l e i s u B a c d r B S M a c d r
c.pCO pGD c.pCO
XXXXXXXXXXXX XXXXXXXXXXXX
3 23 3
F e i B d l s u a c d r B M a c S d r e i d l F B s u a c d r B S M a c d r
c.pCO c.pCO
pGD
Fig. 6.f
21
pGD
22
pGD
23
pGD
21
pGD
22
pGD
23
pGD