1tool Basic Course

Version. 2.7

1tool basic training course

Welcome!
Trainers:

Trainees:

Course targets 1/2

Introduction
Setup 1tool
Licence management (SW/HW)
How to create, edit, test, upload a project into a pCO
Overview of 1tool components

Special functions/features
Overview of special functions: virtual keys, alarms, define the key function, images, multilanguage, etc.

How to exchange variables with other pCO controllers (local network)

pLAN network

How to exchange variables with a generic BMS system

Supervisory system network

How to test/configure the appl. online via Commissioning tool

How to migrate an EasyTools project (optional)
How to get support
e-mail, web site
3

Course targets 2/2

To give the basic knowledge on:
Development tool (1tool editors)

Programming languages

Project management

through a series of exercises.

At the end of the training you will have made a simple application for a simple AC unit.
You will be able to create a new application and open/modify already made ones.
For you is more important to remember that certain functions are available rather than
to remember HOW to use them: for this there are the slides, the user manual,

No details regarding:

hardware, wiring, sales.

1tool
Programming tool
for all programmable controllers/terminals of pCO sistema
PGDtouch
Graphic/TouchScreen

pCO5
pCO5+
pCO compact

pCO1

pCOC

Semi-Graphic

Supernode
pCOXS

Graphic/TouchScreen

PGD1

pCO3
pCO2

PGD3

PGD0
Semi-Graphic

Miscellaneous information

Schedule:

09:00 12:30 (coffee break at mid-morning)

12:30 13:30 Lunch buffet in CAREL
13:30 18:00 (coffee break at mid-afternoon)
Dinner: see list of restaurants

What is departure time? (last day)

Taxi booking needed?

Wi-Fi zone (b/g).

Ask at Reception.
Passport / Identity card required.
(no VPN)
6

Rules
1. If the explanation is not clear or if you have
questions or curiosity feel free to ask
2. If the exercise is unclear, ask immediately
to repeat
3. If you are too in late with exercise ask help

(max 5 min)

4. Dont use objects or concepts that were not explained

(you will be told what to use)

5. Dont read the manual unless you are asked to do so

???

HE

6. Dont make more than you are asked to do

7. Mobile phone not allowed

LP

Topics 1/7

How to create a new Solution/Project (SolutionExplorer)

Overview of editors
How to define the control strategy (StrategyEditor)
How to define the user interface (MaskEditor)
How to compile
How to simulate (Simulator)
How to upload the application into the controller (pCOLOAD)
How to backup a Solution: Use File/Backup.
(just copy the Solution folder, even better is compressed (ZIP))
See slide Project life cycle (slide)
You dont remember?
See video tutorial into DVD, folder \Doc\1t_VideoTutorial
8

Topics 2/7

How to create a parameter (e.g. Setpoint)

Permanent memory (T), default values, DEV file,
(INV management)
How to create a new mask
How to define the function of a key (KeyFunctionEditor)
How to create a Loop of masks (slide)
How to enable a mask (EnableOn property)
Levels: Field, Mask, Global. (slide)
Text association (ResourceUsedOnBool/Int)
Objects properties

Topics 3/7

move field: allows to show the previous/next mask

How to manage the Unit Status (if statement)
System variables (KEY_COUNTER)
Virtual key (slide)
Block Execution Order (Reference): (slide)
Main cycle/task, events (Do_Task atom/statement)
How to create a new StrategyPage

10

Topics 4/7

Standard management of alarms (slide)

Alarm mask: Alarm Status / Alarm memory
System variables: BUZZER, GLOBAL_ALARM, RESET_BUZZER,
RESET_ALARM

Macroblocks Hyst_Dir_Set2Diff, Hyst_Dir_OnOff ,

Hyst_Rev_Set2Diff, Hyst_Rev_OnOff.
GE, GT, LE, LT, NE, (EQ atom),
Limit, Limit_Low, Limit_High
Type of FDB blocks (slide) and FBD blocks libraries (slide)
Unconnected pin (autoconnection of Const/Var) (slide)
How to create a Macroblock (slide)
How to create a Module (slide)

Module mask insertion mode: Linked, Imported, StrategyOnly

11

Topics 5/7

pLAN (pCO LAN) (slide)

Each controller can show its masks into up to 3 terminals

SHared or PRivate + built-in
Send variables among controllers (max 2048 links)
How to configure the pLAN (addresses, terminal configuration)

File system (Binary files folder) (slide)

BMS: how to send/receive variables (slide)
Commissioning tool
How to install/open an existing solution (i.e. a backup)
Time management: system variables CURRENT_HOUR,
NEW_HOUR, SET_HOUR
Field code, macroblock Schedule_Daily
12

Topics 6/7

How to specialize a mask (without the move field)

How to show images (Image object) (slide)
How to set the set of characters (TextFont property)
How to show chinese text (ImageText object)
How to show text in double height (RowZoom property)
How to delete unused objects (Variables, SpecField, Resources).
Default management (slide)
Language management, Multilanguage support (slide)
Complete overview of variable properties (slide)
Field preview (Simulation value field property)
To reduce compilation time: Compile target only
13

Topics 7/7

Project documentation
Menu File/Create solution documentation

Application development GuideLines (slide)

Content of FLASH memory:
BOOT, BIOS, IUP, BLB/BIN, DEV (slide)
Other languages: ST-StructuredText
Next steps (slide)
Starter kit (slide)
Standard application, Project template (slide)
Quick look to a standard application: Chiller Core FLCORMCH0E

1tool support service: [email protected] (slide)

1tool course evaluation form
14

Setup

1.

Start Windows
Login as Administrator

2.

Insert the 1tool DVD-ROM

Open D:\INDEX.HTM

3.

Click English, Setup 1tool

4.

Click 1tool_setup.exe

5.

Select Run (or Save and then Run)

Sometimes the system asks to install the prerequisites: run
\Setup32\1tool_prerequisites_setup.exe.

6.

Select 1tool and USB Driver.

7.

Start 1tool: Start/Programs/Carel/1tool/1tool

Others are not used in this training.

Updates are in http:\\ksa.carel.com.

May be necessary to uninstall previous version.
15

License 1/2

1tool runs without license for 90 days in TRIAL mode.

This is time-limited: all functions are enabled.
After 90 days wont be possible to save/compile
License types:

Software:

1 license for each PC. Cheaper.

Hardware:

1 license for all PC (transportable). A bit more expensive.

16

License 2/2
Hardware license activation procedure:
1.

Make sure your PC is connected to the Internet.

2.

Insert the dongle into a USB port

3.

Start 1tool

4.

Select menu Tools / License Management

5.

Select the Hardware Licence tab

6.

Copy to clipboard the string of character of the Licence Code

7.

Click the button Get Activation Code:

A web page is shown

8.

Click the image 1tool-Ask for activation

9.

Fill in the form

10.

Select option License Hardware

11.

Enter the Serial Number (12 chars string on the holographic label)
and paste the License Code

12.

Click the button

13.

Copy the Activation Code in the window License Registration

14.

Press the Activate Key: The license key is installed permanently in the dongle

: the system calculates the Activation Code

17

1tool components/editors
Solution Explorer

New projects, start editors, add languages,

Strategy Editor FBD/ST

Control strategy

Mask Editor

User interface (content of masks, keys function)

Network Editor

pLAN projects (selection of units/projects, definition of links among units)

Simulator

Simulation on the PC

pCO Manager (pCO Load + Commissioning tool)

Upload of application files into the controller, definition of Logs, commissioning/test functions

Migration Wizard

Conversion of EasyTools projects to 1tool project.

18

Exercise Cool/Heat 1/3

D.Out N.1
Cooling

20.0
(Setpoint)

Room_Temp
A.In. N.1
Type 0 (NTC)

1.0

19

Exercise Cool/Heat 2/3

D.Out N.1
Cooling

Room_Temp

20.0
(Setpoint)

A.In. N.1
Type 0 (NTC)
1.0
3.0

20

Exercise Cool/Heat 3/3

A.Out N.2

A.Out N.1

Heating_Valve

Cooling_Valve

D.Out N.2

D.Out N.1

Heating

Cooling

Room_Temp

Setpoint
(20.0)

(2.0) Heating differential

(4.0) Heating offset

A.In. N.1
Type 0 (NTC)

Cooling differential (1.0)

Cooling offset (3.0)

21

Project life cycle

Create a new solution/project
Edit Control strategy (Strategy Editor)
Edit User interface (Mask Editor)
Edit Network (Network Editor)
Compile
Debug/Simulate (Simulator) Upload (pCOLOAD)
(slide)

(slide)

Backup
22

Upload
1.Connect PC to device using the USB/RS485 converter
2.Compile the project successfully, then click the button

(pCO Manager)

4. Select the folder where application files are saved

5. Select files to be uploaded to the device

3. Set the
pCO address
and
PortNumber
of your converter,
and click
button Connect
in the toolbar.

6. Upload and Check progress

23

Variables
Analog pin

Integer pin

Data Type (main types)

Boolean (0/1)
Integer (-32768 / +32767)
Analog (-3276.8 / +3276.7)
Decimal/Real/Float datatype/values are not supported.
Analog is an Integer but values are shown with . (21.5 = 215)
Analog and Integer are compatible.
emory Type

(main types)

Memory Types

ID letter

permanenT (flash).

auXiliary (RAM) (value is lost in case of blackout)

NOTE: all atoms write in X-Ram memory,

except RA_IN_T / RI_IN_T / RD_IN_T, Move_BT_En, Move_IT_En.
T-Permanent memory has a limited number of write-cycles (>100.000)
24

Variable Wizard

The properties are divided into categories (General Data is the most important)
These are properties that are provided to those who must communicate with
the program (Commissioning, BMS, project documentation, etc.)
Often the value of a property influences the value/visibility of other

Allowed characters: AZ 09 _
Case non sensitive
Simple description
(multilanguage, see on the right)

Languages used in one or more

Terminals
Address in memory of the variable
(see also Compiling options)

Generic: compatible with X and T

Variant: generic data type.
Pin Out of block DCL/ArrayAlloc
or variables without specific
datatype in migrated applications
Default value (file .DEV)
and/or unconnected INPUT pin
Category in Commissioning.
Can be used as filter in the
VariableList.

Allows to create an array without

use of block Array_Alloc
If selected the number of items is
shown. Only Integer/Analog.
Simple text
Used to share an internal variable
of a MB/Module
(that is a NOT Block pin)
between MB/Module/Application
Official Min/Max/Format/Access.
In fact in the MaskEditor is allowed to use the same variable in several FIELD with
different properties.
E.g. Setpoint Input/Output and Output, or limits 15.0/30.0 and 18.0/28.0.
Also used as default values during D&D from VariableList to TerminalEditor.

25

Variable List

Contains all variables used in the current project

How to create a variable:

Right-click the Variable List, Add menu

Add variable button in the toolbar
Connect variable context menu of the pin
Autoconnection function of Modules

Rename variable in the Variable List to rename it in the whole project

Multiple selection is allowed (e.g. to delete several variable)
Clean list using the menu File / Delete unused variables

Allow to modify the properties

in the cell
(only for some properties)

Remove all filters

Right-click for more options

Filter by Variable Name.

Can use wildcard/s *
e.g.: Temp*, Dif*Comp*

Click title to sort A..Z or Z..A

Custom filter
Right-click title bar to select visible
properties and order

Filter by User/System/Module,
Datatype, MemoryType, etc
F12 to export variables (XLS)

26

Unconnected pin
If the pin is unconnected:
Input pins will take the default value as the pin was connected to a constant
Output pins will take a temporary variable automatically.
They are equivalent

Not all pins can be left unconnected.

Example: the atoms Jump_Start and Jump_End, Array_Read, etc.
You can select the behaviour in case of unconnected pin:
Compile/Compiling options

27

Loop of masks

A loop of masks is a group of masks.

If the cursor is in the top-left corner
(in the move field), the UP/DOWN keys
show the PREVIOUS/NEXT (enabled) mask
of the loop.
UP/DOWN keys change mask thanks to the move field
The move field (only Input) is automatically added to the new masks.
If not needed just delete it.
To restore it, just copy it from another mask.
When you enter a mask, the blinking cursor is placed
one the first Input or InputOutput enabled field.
If there are no fields the cursor doesnt appear.
Loop object is optional
Goto_loop(); statement
Corresponds to Goto_mask(first mask of the loop);
28

Level: Field, Mask, Global

(Field)

(Mask)

(Global)

The level is shown in the Key Function Editor

The level is the same for
the Key Function Editor and Property

Field (highest priority)

Mask code
Global (lowest priority)
29

Standard/Special Field
How

A Field consists of two parts: one

indicates WHAT to manage
(variable name) and the other
describes HOW to show it (format)

A Standard Field is a Field

that has nothing special.

What

When you change a property (eg.

EnableOn, ResourceUsed*, )
or the function of a key (eg. Key
ENTER, Key UP, ), the field
becomesa Special Field.

A Special Field is a template of

format that can be reused in the
same mask or in another mask
instead of a Standard Field
30

Virtual keys

Normally a KEY statement is executed

when a physical key (switch) is pressed .

Sometimes is necessary to execute a key according to 1

0
the value of a variables: Its necessary a virtual key.
The virtual key is pressed when the variables changes from 0 to 1.
How to manage a virtual key:
1. Manage the variable that assumes the value 1
when the virtual key has to be pressed

2.

Create a new key name and link it

to the variable
(Unused Keycode: 137-179, 200-254)

3.

Defines the function of the new virtual key

Exercise: Show the main mask after 60s of inactivity of the keyboard
31

Block Execution Order

Define the Block Execution Order of the current page.

The blocks are executed according to the ascending (10, 20, )

The page order depend on its position in the Solution Explorer.

They are executed from top to bottom.

You can change the page order by right-click the

page, then select the Change page order
You can change Block Execution Order by
double-click the block or by right-click the
page background.

Note :
You cant place two blocks with the same number in the same page.
You can use Jump_Start and Jump_End blocks to skip
some blocks during the execution.
32

Alarm management (1/3)

1tool provides a set of system variables for turning the buzzer ON/OFF
(MAN_BUZZER_EN, MAN_BUZZER_ON, MAN_BUZZER_OFF)
Built-in standard management of alarms provides:
to switch the buzzer ON as soon as an alarm starts (Alarm status 01)
to manage the alarm memory variable (Alarm memory)
a set of system variables:

BUZZER

GLOBAL_ALARM

0: buzzer OFF
1: buzzer ON

0: no alarm memories
1: at least 1 alarm memory (logical OR of mAL)

RESET_BUZZER

RESET_ALARMS

1: request to switch the buzzer OFF (autoreset)

1: request to reset all alarm memories

(autoreset)

AL
mAL

This feature is performed through:

Alarm masks
Mask enable:
Properties
ALARM
mask: variable AlarmMemory(mAL)
NORMAL mask: variable EnableOn
mAL*, BUZZER, GLOBAL_ALARM are read-only

33

Alarm management (2/3)

When the ALARM key
If

is pressed:
then

1tool language

Goto mask No_Alarms

if(SysVarList.GLOBAL_ALARM==0)
{
Goto_mask(No_Alarms);
}

At least 1 alarm memory

and
The buzzer is ON

Switch the buzzer OFF

(request)
and
Goto loop Alarm

if(SysVarList.GLOBAL_ALARM==1 &&
SysVarList.BUZZER==1)
{
SysVarList.RESET_BUZZER=1;
Goto_loop(Loop_Alarms);
}

At least 1 alarm memory

and
The buzzer is OFF

Reset all alarm memories

(request)
and
Goto loop Main

No alarms

if(SysVarList.GLOBAL_ALARM==1 &&
SysVarList.BUZZER==0)
{
SysVarList.RESET_ALARMS=1;
Goto_loop(Loop_Main);
}

34

Alarm management (3/3)

How to manage alarms:
1. Manage alarm condition (e.g. variable AL_HT)
2. Add an Alarm Mask
3. Rename the mask (e.g. al1)
4. Define the alarm text (add TEXT objects, etc)
5. Define the properties AlarmStatus and AlarmMemory (this order)
6. Rename the name of the alarm loop (e.g. LOOP_Alarms)
7. Define the function of Alarm key
8. Manage alarm LED and alarm RELAY
How to add a new alarm:
Repeat steps 1-2-3-4-5
Alarm log:
by application (macroblocks STORE_*, application mask).
pCO log (see pCOmanager/LogEditor, system mask).

Download: NO
Download: YES
35

Exercise 15 - Alarms

AL_HT = 0
AL_LT = 1

AL_HT = 0
AL_LT = 0
Heating

AL_HT = 1
AL_LT = 0
Cooling

Room_Temp

Setpoint
(20.0)

15.0 (Low temp. limit)

A.In. N.1
Type 0 (NTC)
(High temp. Limit) 30.0

36

Exercise 15 - Alarms

AL_HT = 0
AL_LT = 1

AL_HT = 0
AL_LT = 0
Heating

1.0
15.0 (Low temp. limit)

AL_HT = 1
AL_LT = 0
Cooling

Setpoint
(20.0)

Room_Temp
1.0

A.In. N.1
Type 0 (NTC)

(High temp. Limit) 30.0

37

Exercise 13-14-15 - Alarms

38

Type of FBD block

Atom block

ST block

Macroblock block (strategy only)

Module block (strategy+mask)

How to open a macroblock/module:

Select block, context menu Open block
Help:
Select block, context menu ?
39

FBD blocks libraries

SCOPE:

OWNER:

All projects (current PC)

CAREL

Current project

User

Library management:

How to Add/Remove reference (dependency) to

an existing library: right click the node Dependencies
How to Create/Add/Remove a new Library:
right click the node Lib
Where is the UserLibrary? Compile/Open user library folder

Note

Compilation is not recursive: the content of a block is the one at the

moment of the creation (Save to library)
Example: the block A contains B, and B contains C.
If C changes, you have to open/save B, then open/save C
Versioning of libraries

40

Macroblocks
How to create a macroblock:
1. Create a temporary New project,
Module/Macroblock type
2. Delete the Terminal node
(macroblocks dont contain mask)

3.

Define the Strategy

4.

Create the pins (select Block pin property).

It is recommended to use the Connect variable menu

5.

Define the shape using the Shape editor

6.

Save the block into library using

the context menu Save to library as

7.

Delete the temporary project

from Solution Explorer
41

Modules (1/4)

Mask insertion mode:

Linked:
- The masks mantain the link with the instance of the block.
- If the block is deleted its masks are deleted too
- It is possible only to add TEXT/IMAGES/ANIM/LINE/RECT, move masks
- If module masks in the LIB change, the module masks in the appl. are automatically
updated

Imported:
- The masks are imported and become project masks
- It is possible to do any kind of modification
- If module masks in the LIB change, the module masks in the appl. are NOT updated

Strategy only:
- The mask are not inserted
42

Modules (2/3)
MODULE

APPLICATION

Module masks are places in the application in the loop with the same name
The position depends on the MaskDefaultPosition property.
43

Modules (3/4)
Both module and application can be designed for several terminals and languages
The masks are inserted in the
original loop according to the
property MaskDefaultPosition:
Default, First mask, Last mask

ModuleApplication

Module

Module

Application

ActiononTERMINAL

PGD1

PGD1

Masks inserted
Masks ignored

PGD0
PGD3
Application

ActiononLANGUAGES

EN

EN

Masks inserted

IT

IT

Masks inserted
Masks ignored

DE

First

First

Default

Default

Last

First

No masks inserted

Module

FR

Application

Masks inserted(only

Default
Last

Imported)
System asks which lang. to use

44

Modules (4/4)

Notes

Modules have a LABEL (example TR1 EVD_Circ1 )

Variables, SpecialFields, TouchSchemas, etc are renamed (Example: TR1.Diff_Lim)

The application has the access to module variables: LABEL.VarName

Only for pin not Visible in shape

Auto connection

Automatic links (EVDEVO, pAD, )

(see specific slide) (slide)
Limits

A module cant contain modules (with masks) but only atoms/macroblocks. The masks
are ignored.

A module cant contain GlobalCode/Events

45

Simulator 1/2

Simulates all controllers and terminals

Doesnt simulate pLAN (you need to change manually system variables PLAN_ADDRESS, PLAN_INFO,
PLAN_STATUS*, etc) and graph in PGD3

How to enable I/O and Terminal Editor windows: menu View/Simulator

How to show (read-only) Strategy/Mask pages: Solution Explorer
How to show runtime values of Variable and Block pin: show pin values
How to go back to editing: stop Simulator, click
How to start simulator without compiling: CTRL+
(be careful!)
How to select Hardware and Terminal/Language: stop Simulator, select
Watch window

How to create a watch window: menu Simulator / New watch window or

How to add variables: rightclick/Add, D&D from VariableList or D&D from StrategyPage
How to change variable: click value cell. Doubleclick name to change bit.
How to change variable order: click+move
You can show Array (only 1 array per watch)
Value blinks when value changes

Watches are saved when you save the application

Terminal Editor simulates the LED under keys. Buzzer is not simulated
46

Simulator 2/2

Simulation control

START: run till next breakpoint

PAUSE: stops on first block

STOP: stops simulation.

RESTART: correspond to STOP+START

The application is initialized (X memory cleared, Timers cleared, etc) when one of the
following conditions occurs:

Before the very first START

Before a START following a STOP/RESTART

Simulation control (active while simulation is in PAUSE)

Run program cycle: run till first block or next breakpoint

Run function block: run block by block (doesnt open macroblock/module)

Run atom/Mask Statement: run atom by atom or statement by statement

(opens macroblock/module automatically).
Breakpoints

You can add breakpoints on a block or statement (KFE/ST)

Breakpoints are fixed and on condition (see Breakpoint window)

The block/statement where the program stops is not yet executed

47

Connectivity (pCO3)

48

pLAN network (1/2)

The BMS and the pLAN network are independent networks

pLAN devices (slide)

(slide pLAN network 1/2)

(slide pLAN network 2/2)
(slide Examples)
(slide Exercises)
(slide Terminal config.)

Any type of pCO, TXT/PGD terminals, Aria/pAD, EVD, FCM

Any combination is allowed
Max 32 units (only terminals can have address=32)

Features of the pLAN network:

Each controller can show its masks into up to 3 external terminals

(Private or Shared)+builtin
Send variables among controllers (max.2048 outgoing links for each controller)

How to manage a pLAN (slide)

Setup pLAN

Info: the pLAN protocol is a multimaster protocol

1.
2.
3.
4.

Compile and Upload application files into pCO

Set pLAN address to pLAN devices (only first time)
Connect pLAN devices (Wiring) (see pCO sistema manual
Configure terminal (only first time) (slide)
49

pLAN network (2/2)

Terminal configuration

(slide pLAN network 1/2)

(slide pLAN network 2/2)
(slide Examples)
(slide Exercises)
(slide Terminal config.)

System mask (press UP+DOWN+ENTER for 5sec) (slide)

System variables PLAN_TERM_CONF*
Network Editor (Terminal property, Setup button) (Default configuration)

The value of the variable is sent every time it changes and

as soon as the communication starts
NOTE: variable form X to T are not sent at start-up

pLAN alarms management (see also Alarm_pLAN macroblock)

pLAN system variables (most important)

PLAN_ADDRESS: pCO address

PLAN_INFO: bit15=pCO is communicating, bit14: request of SH terminal
PLAN_STATUS_01_16, _17_32: each bit specifies the status of a pLAN device
PLAN_TERM_CONF*: terminal configuration

Simulation: only 1 project at a time

You need to set pLAN System Variables

Binary file folder: [solution]\bin\target\planN\unitN (slide)

50

(slide pLAN network 1/2)

(slide pLAN network 2/2)
(slide Examples)
(slide Exercises)
(slide Terminal config.)

pLAN units

pCO3/2/5/5+

LCD4x20

PGD0/1

pLAN

pCO1

pCOXS

PGD2/3

ARIA/PAD

pCOC

FCM

Supernode

EVD Electronic Expansion

Valve Driver

Max 32 units (only terminals can have address=32)

Any combination is allowed
51

(slide pLAN network 1/2)

(slide pLAN network 2/2)
(slide Examples)
(slide Exercises)
(slide Terminal config.)

pLAN/BMS - Examples
pLAN
1

2
1

3
2

pLAN
1

32 SH(1,2,3,4)

pLAN
32 SH(1,2) 1

BMS
2

32 SH(1,2)

BMS

pLAN

AirCon unit

AirCon unit

PR(1)

PR(3)

32
SH(1,3)

31
SH(1,3) 52

pLAN - Exercise
Address: 1

pCO*
COURSE project
Room_Temp

P01: Adr Priv/Shared

Trm1 32 Sh
Trm2 None -Trm3 None -- OK?No

Address: 2

Address: 32

Terminal
pCO*
COURSE project SH(1,2)
Room_Temp

P02: Adr Priv/Shared

Trm1 32 Sh
Trm2 None -Trm3 None -- OK?No

(slide pLAN network 1/2)

(slide pLAN network 2/2)
(slide Examples)
(slide Exercises)
(slide Terminal config.)

Terminal
configuration from
point of view of
TERMINAL
Terminal
configuration from
point of view of
PCO

53

How to manage a pLAN

1.

Create one or more Network Page (*)

2.

Insert in a Network Page the Controllers, Terminals, Parametric pLAN(**)

3.

For each object define the Group and pLAN Address

(slide pLAN network 1/2)

(slide pLAN network 2/2)
(slide Examples)
(slide Exercises)
(slide Terminal config.)

For the Controller objects you have to specify the application project (***)

4.

Define the pLAN links using the pLAN table

The variables used in a link must have the pLAN flag checked
Bidirectional flag create a hidden link with Source/Target reversed

For some Parametric pLAN the pLAN links are created automatically (see specific slide)
You can Copy/Paste links: select links, click Copy button, right-click destination controller, select Paste links
The Source unit of pasted links become the selected unit.
You can insert in a Network Page some graphic objects: Image (e.g. Roof map), Line, Rect, etc
(*) You can create several Network Page. Example: Ground_Floor, First _Floor, Roof
It is irrelevant the order of the pages
P01: Adr Priv/Shared
(**) It is irrelevant in which Network Page you insert the Controller, Terminal, Parametric pLAN Trm1 None -Trm2 None -(***) For the Terminal objects you can define a default configuration.
Trm3 None -- OK?No
It is installed at pCO start-up only if there are no terminals already configured,
that is Trm1/2/3=None.
54

(slide pLAN network 1/2)

(slide pLAN network 2/2)
(slide Examples)
(slide Exercises)
(slide Terminal config.)

pLAN-Terminal config.

Press
Display address
UP+DOWN+ENTER setting..........:32

I/O Board address:01

contemporary
Terminal Config
for 5 seconds
Press ENTER

Terminal ADDRESS (PGD only)

ADDRESS of the contr. to config.
Press ENTER
(ignore buzzer)

to continue

Repeat for all

controllers

Press
NetSTAT 1 8
9 16
UP+DOWN+ENTERT:32
Enter 17 24
To quit 25 32
contemporary
for 5+5 seconds

P01: Adr Priv/Shared

Trm1 32 Sh
Trm2 None -Trm3 None -- OK?No

Warning! Dont install configurations not consistent!

i.e.: P01: Trm1 03 Sh,
P02: Trm1 03 Pr

Controller address
Terminal 1/3 ADDRESS PR/SH
Terminal 2/3 ADDRESS PR/SH
Terminal 3/3 ADDRESS PR/SH

Units ONLINE
: Controller (pCOx, ARIA,
EEV driver, )
: Terminal (TEXT, PGD, LED)
: None

55

Controllers architectures

(slide pLAN network 1/2)

(slide pLAN network 2/2)
(slide Examples)
(slide Exercises)
(slide Terminal config.)

Point-to-Point (stand-alone)
(obsolete)
Only 1 controller (with or without built-in terminal)
Address must be 0

Only 1 optional external terminal (always Private)

Address must be 0

The PGD display in external terminals works in Text display compatibility mode:
1 fixed font (CAREL_TERM), 4rows/20columns, only single-height rows, no images

pLAN (pCO LAN)

Up to 31 controllers (with or without built-in terminal)
Address must NOT be 0 (1-31)

Up to 31 optional external terminals (Private o Shared)

Address must NOT be 0 (1-32)

PGD display fully working:

3 fonts, 4x20(PGD0) or 8x22 (PGD1) rows/columns, double-height rows, images
56

pLAN - Group

Group 1
Group 2

Group 3
Group 4

57

pLAN - Automatic links

58

pLAN - Automatic links 2/2

How to manage Parametric pLAN controllers (EVD400, EVDEDVO, PAD)
Example: EVD EVO
Strategy Editor
1. Place support module Mod_EVD_EVO_Spec,
(one for each driver)
2. Define the label (CIRC1, CIRC2)
Network Editor
3. Place Generic EVDEVO
Parametric pLAN Controller
(one for each driver)
4. Define pLAN address
5. Select the module which manage
the EVD EVO

The links belong to the Parametric pLAN Controller

59

Compilation / Binary files

pCO memory contains binary files (result

of a compilation procedure), not source files
PointToPoint(Stand alone)
..\SolutionName\Bin\Target\ApplicationName

pLAN

}
}

..\SolutionName\Bin\Target\PLANn\address\
UNIT1-2 contain same files suitable for CHILLER units
UNIT3-4 contain same files suitable for AHU units

Same application (e.g. Chiller Unit1&2) Same binary file

You dont need to change folder, just select

the Group/Unit from the dropdown list
60

Compilation / Binary files

pCO memory contains binary files (result

of a compilation procedure), not source files

1tool
2.6.X

PointToPoint(Stand alone)
..\SolutionName\Bin\Target\ApplicationName

pLAN
..\SolutionName\Bin\Target\PLANn\Address_X_Y_NNN
contain files suitable for units address X and Y
running the application NNN

You dont need to change folder, just select

the Group/Unit from the dropdown list
61

Connectivity - BMS 1/2

LOCAL REMOTE
side
side

PlantWatch

HTTP

CAREL Local

PCgate

Analog

Conv.485/USB

max. 207

PlantVisor
DLL

GSM
(SMS)

CAREL Local

max. 15

HTTP / SNMP
WEBgate

CAREL Local

max. 15

ModBus

Gateway
CAREL Local
ModBus RTU
OPC
ModBus TCP/IP Konnex
BACnet MS/TP LonWorks
BACnet IP
HTTP/SNMP (email)

Analog

Serial card

CAREL Remote
GSM
(SMS)

62

Connectivity - BMS 2/2

Card

Protocol

BMS

63

Supervisory system network (BMS)

Important! BMS and the pLAN network are independent networks

The purpose of the BMS network is to exchange variables with a supervisory
system/BMS (PlantVisor, pCOWeb, WebGate, Gateway, Modem, Lon, Trend, DLL etc.)
How to send/receive variables (common for all types of architectures)
1.
2.

Address in the network (system variable BMS_ADDRESS (I,T) )

Communication speed (system variable COM_BAUDRATE_BMS (I,X) )
0: 1200 baud
1: 2400 baud
2: 4800 baud
3: 9600 baud
4: 19200 baud (default)

3.

Communication protocol (system variable COM_PROTOCOL_BMS (I,X) )

1: Carel Slave Local
2: Carel Slave Remote (analog modem)
3: ModBus Slave
4: WinLoad (for Commissioning)

4.

Select variables. 2 alternatives:

1. Variable properties, BMS property (BIOS >=4.29 required)
2. Remote atoms

RD_In_T, RI_In_T, RA_In_T (variables in T memory)

RD_In_X, RI_In_X, RA_In_X (variables inX memory)
RD_Out, RI_Out, RA_Out (variables in T and X memory)
RD_Multiser, RI_Multiser, RA_Multiser

64

Carel Vs Modbus protocols

Maximum number of variables

Carel protocol
Carel Slave
(Normal)
COM_PROTOCOL_BMS=1
BMS_EXTENSION=0
199 Digital variables
127 Analog variables
127 Integer variables

Carel Slave
(Extension)
COM_PROTOCOL_BMS=1
BMS_EXTENSION=1
207 Digital variables
207 Analog variables
207 Integer variables

ModBus protocol
ModBus Slave
(Normal)

ModBus Slave
(Extension)

COM_PROTOCOL_BMS=3
BMS_EXTENSION=0

COM_PROTOCOL_BMS=3
BMS_EXTENSION=1

199 Digital variables

127 Analog variables
127 Integer variables

207 Digital variables

207 Analog variables
207 Integer variables

ModBus Slave
Extended
COM_PROTOCOL_BMS=30
BMS_EXTENSION=ignored
2048 Digital variables
5000 Analog variables
5000 Integer variables

Communication test programs: CAREL protocol, SLAVE SIDE: DTEST (CAREL)

MODBUS protocol, SLAVE side: MODSCAN

The CAREL/MODBUS slave protocols are available for all serial ports:
BMS, BMS2, FIELDBUS,FIELDBUS2
65

Carel Vs Modbus protocols

CAREL

MODBUS

3 Data types: D-igital, A-nalog, I-nteger

2 Data types: C-oils, R-egisters

(No difference between Input and Holding)

The SLAVE unit sends a new value only when

the value changes (optimized)

The SLAVE unit sends a new value even if the

value is not changed

MODBUS

CAREL
1

The application has to manage

CAREL slave protocol (that is
use CAREL datatype and Index)
and select the MODBUS SLAVE
protocol (i.e. CAREL_PROTOCOL_BMS=3):
the BIOS automatically converts
CAREL datatype/index to
MODBUS datatype/index

+1

+1

+1

n
1

+1
+1+offset

+1+offset

Digital

Analog

Coils

Registers

n
1

Integer
n

Registers
66

Carel Vs Modbus protocols

Complete cross table CAREL Vs MODBUS
COM_PROTOCOL_BMS =3
ModBus Slave (normal)

COM_PROTOCOL_BMS = 30,
ModBus Slave Extended

BMS_EXTENSION = 0

BMS_EXTENSION = 1

BMS_EXTENSION ignored

Offset = 128

Offset = 208

Offset = 5001

Carel
protocol

ModBus
protocol

Carel
protocol

ModBus
protocol

Carel
protocol

ModBus
protocol

Digital

199

Coil

200

Digital

207

Coil

208

Digital

2048
(*)

Coil

2049

Analog

127

Register
(Analog)

128

Analog

207

Register
(Analog)

208

Analog

5000
(*)

Register
(Analog)

5001

Integer

127

Register
(Integer)

130

256

Integer

207

Register
(Integer)

210

416

Integer

5000
(*)

Register
(Integer)

5003

10002

(*) Addresses > 207 are available only if ModBus Slave Extended protocol is set.

67

Other protocols
To communicate with protocols different by
CAREL / MODBUS, you must select the
"CAREL Slave Local protocol.
Some further action is required in the application
or configuration files.
Examples:
CAREL Slave Remote: phone number,

CAREL Slave
CAREL Master

LON: LON properties, LONset

BACnet: BACNET properties, BACset

For more information on protocols (features,

compatibility, etc.): see manual pCO sistema

LON, Trend,
Konnex , CANbus,
BACnet, Ethernet,

68

Images
How to insert an image?
Drag & Drop
Image object
Format: standard BMP, black&white (monocrome)
Editor: your preferred one (Paint, Paint.net, Photoshop, CorelDraw, )
Max size: PGD0: 120x32, PGD1: 132x64 (1 character: 6x8 pixel)
Images must be in the Resources node
Create a new image
Import (es. [1tool]\ImageLibrary\PGD)
Images are saves in the .GRT (see pCOload)
Overlap Text & Image reverse effect
ResourceUsedOnBool/Int with images

69

Default management 1/2

Why to install default values? Because at compile time the variables could change
its position (address) in the memory so they could take another value.
Previous
version

T-permanent
memory

Current
version

Setpoint = 0.0

Setpoint = 20.0
0
0

Setpoint

Unit_Status = 200

Setpoint
GENERAL RULE: every
time you200installUnit_Status
a new version it is recommended to install
the default values. It is not necessary0 if you dont change the list of the variables.
0

How to define the default value in the Variable Wizard:

Variables in the T-permanent memory have a default
The value is written in the .DEV file at compile time. It is the map of the values in
the memory (4 o 13KB).
DEV file doesnt contain the name of the variable but the memory address, therefore if the position of the variables change the DEV is no longer
usable..

To fix the position of the variable in the memori you can use the "Maintain
Variable Address" compile flag, but is has limitations.

70

Default management 2/2

How to install defaults values?
1. Commissioning time: pCO manager > pCO LOAD, file .DEV
2. Commissioning time: pCO manager > Commissioning > Device configuration >
Load/Save DEV/TXT (recommended TXT because it contains the name of the var. instead of the memory address)
3. Simulation time: Load .DEV values button (available with simulation OFF)
4. Runtime: MOVE* block (FDB) or = operator (FKE or ST)
NOTE
. The options 1-2-3 re available only at tha moment.
Option n.4 is always available (therefore so it is often preferable to other options)

. After the installation of the default it is recommended to Power OFF / Power ON

(so that the timers use the correct values of "Time")

. The Mod_HWSW_chk module can determinate if the version of the SW is

changed, so it is convenient to use it in combination with the option 4 through a
virtual key.

71

Multilanguage support 1/2

An application can be multiterminal/multilanguage

How to add/clone/remove languages:

Context menu Configure terminals

The list in the toolbar sets the language to show

in the objects/properties (TEXT, ResouceUsedOn*, Font, )

How to translate text?

Modify every text: TEXT, ResourceUsed*,
Export texts in a .XLS format, menu Import / Export dictionary
72

Multilanguage support 2/2

The compiler creates an .IUP for each combination
of terminal/language
You can upload only some languages (IUP)
Language selection
System Variable LANGUAGE_KEY_SWITCH (con un tasto singolo/coppia)
System Variable LANGUAGE
Value in the range 0 / NumberOfUploadedLanguages - 1
In the example: 0=EN, 1=ZH, 2=JA
When the language changes the first mask if shown.

Lock: If CLOSED the object is moved in all languages

It is not possible to delete a mask only in a specific language,
but you can disabel it (dont compile): context menu Disable
73

Development guide lines

Also called Best practice

In the DVD you can find the complete document. The most important keypoints are:
Project management

Start to develop only once the technical specification have been clarified and agreed by the customer

Make a Backup on a server for each official version. Make daily backup (1tool provides a specific function)

Assign to the application a Code/Date/Version

Start to develop starting from a standard application (Project Template, Chiller Core or other standard
application)

Define the architecture of the SW with a TOP > DOWN approach, then develop/test with DOWN > TOP
approach

Strategy pages: create one or more pages for each function / device

Mask pages: idem (create the loops and define the key function, then populate loops and define mask content)
Strategy

Align blocks and variables/constant

Avoid crossing connection. Avoid unnecessary curves

Take care of the Block Execution Order and page order

Use significant variable names

Write comments

Think simple! Avoid tricks, ask yourself if you can do better and easier.

Take care of any possible anomalous working condition (i.e. unit offline, )
Mask

Show the application Code/Date/Version in a mask easy to access (also BOOT/BIOS)

Use significant Mask/Loop/SpecialField/Variable name

Use a consistent style in all masks (align text on the left and field on the right, first letter of the sentence in 74

Content of FLASH memory

BOOT+reserved

Loader for other parts

32KB

Normally is not necessary to update it.

BIOS

Operating system

640KB (current BIOS)

Update for new functions and bug-fixing.

Updates available on KSA web site

T memory+reserved

Permanent memory

32KB

Application files

IUP+BLB/BIN+GRP

1MB FLASH: 320 KB

2MB FLASH: 1344 KB
4MB FLASH: 3392 KB

75

Next steps
1) Buy the Starter Kit (see next slide)
2) Study Language Reference:
atoms/macroblocks/modules, System Variables, KFE statements
3) Study Slide/QuickReference
4) Make practice:
Create a simple project or modify a standard project
5) Need help?

User manual of 1tool (F1) and pCO sistema (www.carel.com)

Slide / QuickReference / F.A.Q.(Frequently Asked Question)

Support

)
76

Starter kit
Description

Part number (example)

1tool program + License

OTSTD00100 (SW license)

OTSTD00U00 (HW license)

(Software or Hardware)
Simulator box
(at least 2 pcs for pLAN applications)

CM00002001 (simulation box pCO1)

CM00002011 (simulation box pCO3)
(includes RS485 card for BMS and FieldBus)

PGD0/1 terminal

PGD0000FZ0 (PGD0 6 keys+buzzer)

PGD1000FZ0 (PGD1 6 keys+buzzer)

USB/RS485 converters

CVSTDUMOR0 (3ways plugin connector)

CVSTDUTLF0 (RJ11 phone connector)
(optional)

Phone cables (2 pcs)

S90CONN000 (cable 1.5m RJ11 connector)

3-wire cables for pLAN/BMS connections

Not available as standard product

(small/big connector)

Ask your sales office for other product (simulator for other pCO, other serial cards, etc)
77

Standard applications
Standard application 1tool
FLCORMCH0E: Chiller Core (this is not a standard but it was meant as template for a custom chiller/hp)
FLSTDMAHUE: Air Handling Unit
FLSTDMHPGE: Heat Pump
FLSTDMCZ0E: pLAN AC+EVD400 driver+integr.humidifier
Standard application EasyTools (need to be migrated)
Chiller/HP, CCU, RoofTop,Seasoning Room, Rack controller,
(See complete list in KSA)
Project Template: starting point for a generic application
Demo application for field device and features (EVD, Belimo,
PowerPlus, ModbusMaster, )
Source file & more Info: ask 1tool Customer Care
78

1tool support
E-mail: [email protected]
(only issues regarding 1tool program
Provides Technical support (i.e. problem during compilation, not
Application support (i.e. how to implement defrost)
Other: [email protected], [email protected])

WEB: KSA area

http://ksa.carel.com
Last release of 1tool
Last release of BIOS/BOOT
News
Forum (preferred)
Ask immediately for your username/password!
Support KSA: [email protected]

79

1tool basic course

The end
Thank you for your attention,
if you have any question please feel free to ask

80