Automation Studio User Manual - UA 500 - MAP3100b

UA 500 MAP3100b
ASID13000042, Rev. 2.0, September 13
The content of this manual has been carefully revised, however, the full compliance of its
content with the technical and functional characteristics of the product it is referred to
cannot be assured, as typing or other errors cannot be completely ruled out. The
information given is regularly reviewed and any necessary correction or additional
explanation will be included in future revisions of this document.
Due to continuous development, the content of this manual can be changed without
notice.
We appreciate any correction or improvement suggestion.
ii
- UA 500 MAP3100b, N. ASID13000042, Rev. 2.0, September 13
Manual Revisions
Revision
Date
Changes
1.0
2013-03-01
Initial Version of Automation Studio with UA 500 - MAP3100b support
2.0
2013-08-08
Version corresponding to Automation Studio 2.6 Rev.4 or later.
iii
INDEX
1
INTRODUCTION ................................................................................................................................ 1-1

1.1 PURPOSE .................................................................................................................................................. 1-3
1.2 SCOPE AND AUDIENCE ................................................................................................................................ 1-4
1.3 REFERENCES.............................................................................................................................................. 1-5
1.4 INTRODUCTION .......................................................................................................................................... 1-6
1.5 HOW TO GET STARTED?............................................................................................................................... 1-7
ADOPTING A CONFIGURATION PROCESS ......................................................................................... 2-1

2.1 ITERATIVE CONFIGURATION AND MODIFICATION ............................................................................................... 2-3
2.2 MANAGING CONFIGURATION VERSIONS .......................................................................................................... 2-4
ADDING DEVICES TO PROJECTS ........................................................................................................ 3-1

3.1 NEW DEVICES ............................................................................................................................................ 3-3
3.2 EXISTING DEVICES....................................................................................................................................... 3-4
SETTING UP SOFTWARE AND HARDWARE MODULES ....................................................................... 4-1

4.1 LOCAL AREA NETWORK INTERFACES .............................................................................................................. 4-3
4.2 SERIAL PORTS ............................................................................................................................................ 4-4
CONFIGURING THE DATA MODEL ..................................................................................................... 5-1

5.1 RESOURCES............................................................................................................................................... 5-3
5.2 CONTROL CENTER COMUNICATIONS .............................................................................................................. 5-8
5.3 NETWORK .............................................................................................................................................. 5-10
5.4 DEVICE CONNECTION ................................................................................................................................ 5-11
BUILD AND DEPLOY OPERATIONS .................................................................................................... 6-1

6.1 SAVE PROCESS ........................................................................................................................................... 6-3
6.2 VALIDATE PROCESS ..................................................................................................................................... 6-4
6.3 BUILD PROCESS .......................................................................................................................................... 6-5
6.4 DEPLOY CONFIGURATION ............................................................................................................................ 6-6
iv
LIST OF FIGURES
Figure 2.1 Iterative activity cycle .................................................................................................................... 2-3
Figure 3.1 UA 500 - MAP3100b new device wizard ........................................................................................ 3-3
Figure 4.1 UA 500 - MAP3100b with network interface ................................................................................. 4-3
Figure 5.1 Diagnostic Entities access .............................................................................................................. 5-6
Figure 5.2 Diagnostic Entities list .................................................................................................................... 5-6
Figure 5.3 UA 500 - MAP3100b network parameters ................................................................................... 5-10
Figure 5.4 UA 500 - MAP3100b connection parameter ................................................................................ 5-11
LIST OF TABLES
Table 3.1 Available options to add existing UA 500 - MAP3100b devices ...................................................... 3-4
Table 5.1 Generic Local Digital Entity properties ............................................................................................ 5-3
Table 5.2 Generic Local Analog Entity properties ........................................................................................... 5-3
Table 5.3 Generic Local Counter Entity properties ......................................................................................... 5-3
Table 5.4 Generic Local Control Entity properties .......................................................................................... 5-4
Table 5.5 Generic Local Digital Entity properties ............................................................................................ 5-4
Table 5.6 Generic Local Analog Entity properties ........................................................................................... 5-5
Table 5.7 Generic Local Counter Entity properties ......................................................................................... 5-5
Table 5.8 Generic Local Control Entity properties .......................................................................................... 5-5
Table 5.9 Diagnostic Entities ........................................................................................................................... 5-7
Table 5.10 Generic Digital map properties ..................................................................................................... 5-8
Table 5.11 Generic Analogue map properties ................................................................................................ 5-8
Table 5.12 Generic Counter map properties .................................................................................................. 5-8
Table 5.13 Generic Digital Control map properties ........................................................................................ 5-9
vi
1
Chapter
INTRODUCTION
Chapter 1 - Introduction
INDEX
1.1 PURPOSE .................................................................................................................................................. 1-3
1.2 SCOPE AND AUDIENCE ................................................................................................................................ 1-4
1.3 REFERENCES.............................................................................................................................................. 1-5
1.4 INTRODUCTION .......................................................................................................................................... 1-6
1.5 HOW TO GET STARTED?............................................................................................................................... 1-7
Total pages of the chapter 7
1-2
1.1- Purpose
1.1 PURPOSE
1
To help Automation Studio users configure and manage Efacec UA 500 devices, more specifically the
MAP3100b. For device hardware and software installation and maintenance procedures other
documentation is need, please refer to the specific IED product documentation.
1-3
1.2 SCOPE AND AUDIENCE

This guide targets the Efacec UA 500 MAP3100b device and Automation Studio Engineer Edition 2.6 Rev.3
or Designer Edition 2.6 Rev.3, or later versions of these editions.
The reader of this document and user of the tool is an automation engineer who has basic knowledge of
automation and industrial communications.
1-4
1.3- References
1.3 REFERENCES
1
[Ref.] Title
1.
Date
Automation Studio User Manual
Rev.
Source
latest
EFACEC
Number
1-5
1.4 INTRODUCTION
The Efacec UA 500 Devices Configuration Editor is an Automation Studio Designer IDE module designed
specifically for managing and editing the configuration of the MAP 3100b. It includes several editors,
productivity tools, a device builder and a communications driver.
This document describes user features and provides hints on how to use them in a productive way. Please
note however that this guide does not cover IDE-wide features such as windowing, device management,
loading, saving and backing up device configurations, project and build system, etc. Before going through
this guide the user is advised to read the Automation Studio User Manual [2] .
1-6
1.5- How to get started?
1.5 HOW TO GET STARTED?

1
For the experienced engineer the tool is intuitive and provides built-in descriptions of all configuration
parameters so that minimum documentation reference is required during use.
An automation engineer which is inexperienced with this device model will, in most scenarios, need to read
this document1 to get started and be able to handle most configuration activities. If you already know how
to use the IDE you can skip User Manual [2] and go directly to chapter 2.
In chapter 2 the configuration process is described from a general perspective. From there the user is
directed to specific chapters for guidance on each step or on how to properly handle the configuration of
each module. In each specific chapter the reader will find the information which is required but not easily
perceived from the configuration editors and built-in descriptions.
1 This document is comprehensive but note that reading referenced documentation may also be necessary.
This document as well as any other required product documentation is included with the tool and
accessible via Start Page or Help menu.
1-7
2
Chapter
ADOPTING A CONFIGURATION
PROCESS
Chapter 2 - Adopting a configuration Process
INDEX
2.1 ITERATIVE CONFIGURATION AND MODIFICATION ............................................................................................... 2-3
2.2 MANAGING CONFIGURATION VERSIONS .......................................................................................................... 2-4
2-2
2.1- Iterative configuration and modification
2.1 ITERATIVE CONFIGURATION AND MODIFICATION

1
Actual configuration performed by the user is often performed iteratively in small consecutive steps leading
to an incremental process. Although editing, validating and testing are distinct activities for each user
profile and different features or tools of the IDE are employed, the activity cycle is quite similar (see figure
below).
Figure 2.1 Iterative activity cycle

Productive teams or engineers will make use of the reuse features provided, namely copy/paste, libraries
and templates, as described in the User Manual [2] and elsewhere in this document.
2-3
Chapter 2 - Adopting a configuration Process
2.2 MANAGING CONFIGURATION VERSIONS

The UA 500 MAP3100b configuration model does not support version management. This will not allow for
easy identification of configuration changes so it is recommended to maintain external log if such tracking is
required.
2-4
3
Chapter
ADDING DEVICES TO PROJECTS
Chapter 3 - Adding Devices to Projects
INDEX
3.1 NEW DEVICES ............................................................................................................................................ 3-3
3.2 EXISTING DEVICES....................................................................................................................................... 3-4
3-2
3.1- New devices
3.1 NEW DEVICES

1
To add new UA 500 MAP3100b device to a device project the usual IDE template-based approach is
employed (see the User Manual for details on adding devices to device projects). After selecting the specific
UA 500 MAP3100b model and desired template the user is prompted to enter template parameters. The
newly created device configuration is based on the selected template.
Figure 3.1 UA 500 - MAP3100b new device wizard

After creating a new device all basic device configurations are ensured by the tool and you can perform any
additional configurations and/ or deployment at once.
3-3
Chapter 3 - Adding Devices to Projects
3.2 EXISTING DEVICES

To add existing UA500 - MAP3100b devices to a project all the IDE mechanisms are supported:
Source
How-to
Live device on the network
Choose Add Existing Device command from Solution

Explorer context menu, select MAP3100b device
model and enter connection parameters. The newly
created device will extract the current available
configuration on the live device to the project.
Device on the current project or in

another project.
Use copy/paste from within the tool.
Device package
Choose Import / Device Package command from the

File menu.
Table 3.1 Available options to add existing UA 500 - MAP3100b devices
3-4
4
Chapter
SETTING UP SOFTWARE AND

HARDWARE MODULES
Chapter 4 - Setting up Software and Hardware Modules
INDEX
1
4.1 LOCAL AREA NETWORK INTERFACES .............................................................................................................. 4-3

4.2 SERIAL PORTS ............................................................................................................................................ 4-4
4-2
4.1- Local Area Network Interfaces
4.1 LOCAL AREA NETWORK INTERFACES

1
An Efacec UA 500 - MAP3100b device may provide one IP network interfaces, typically Ethernet interfaces.
4.1.1 ETHERNET INTERFACES

This type of UA 500 - MAP3100b Device can only have one Ethernet port which is configured in the
following area.
Figure 4.1 UA 500 - MAP3100b with network interface
4-3
Chapter 4 - Setting up Software and Hardware Modules
4.2 SERIAL PORTS

Although the UA 500 - MAP3100b device has to up 8 serial ports they are not configurable in this version of
Automation Studio.
4-4
5
Chapter
CONFIGURING THE DATA MODEL
The Efacec UA 500 - MAP3100b device data model is available under the Resources item and CC
Communications item of the loaded Configuration Settings and is comprised of a set of data objects, which
are available on the device real-time database.
Chapter 5 - Configuring the Data Model
INDEX
5.1 RESOURCES............................................................................................................................................... 5-3
5.2 CONTROL CENTER COMUNICATIONS .............................................................................................................. 5-8
5.3 NETWORK .............................................................................................................................................. 5-10
5.4 DEVICE CONNECTION ................................................................................................................................ 5-11
5-2
5.1- Resources
5.1 RESOURCES
1
There are 3 types of resources that can be configured in Efacec UA 500 - MAP3100b devices: (1) local
entities, (2) physical entities and (3) diagnostic entities.
5.1.1 LOCAL ENTITIES

Local entities represent data objects that are handled by local automation or control execution.
There are 4 types of local entities that can be configured: (1) digital, (2) analog, (3) counter and (4) control.
The properties for a local digital type entity are:
Properties
Description
Internal Address
Entity internal address value.
Name
Name that can be used to identify the entity.
Description
User-defined textual description that can be used to describe the entity.
Sub Type
Simple, Double Enum 2, 3 or 4 bits.
Status Timer Value
Only used if Status Timer is true (1ms resolution).
Status Timer
Status Timer.
Complementary Filter Time
Complementary Filter Time. Only used for digitals of type double.
Debounce Time
If 0 does not implement debounce functionality.
Maximum Number of Changes
Maximum number of changes allowed.
Table 5.1 Generic Local Digital Entity properties

The properties for a local analog type entity are:
Properties
Description
Internal Address
Name
Description
Table 5.2 Generic Local Analog Entity properties

The properties for a local counter type entity are:
Properties
Description
Internal Address
Name
Description
Table 5.3 Generic Local Counter Entity properties
5-3
The properties for a local control type entity are:
Properties
Description
Internal Address
Name
Description
Duration
Control timeout. If 0 then permanent control
Associated Entity
Digital, analog or counter entity.
Table 5.4 Generic Local Control Entity properties
5.1.2 PHYSICAL ENTITIES

Physical entities represent data objects whose values are acquired by local I/O or may control the state of
the same I/O.
There are 4 types of local entities that can be configured: (1) digital, (2) analog, (3) counter and (4) control.
The properties for a local digital type entity are:
Properties
Description
Internal Address
Physical Address
Physical address value.
Name
Description
Sub Type
Simple, Double Enum 2, 3 or 4 bits.
Status Timer Value
Only used if Status Timer is true (1ms resolution).
Status Timer
Status Timer.
Complementary Filter
Time
Complementary Filter Time. Only used for digitals of type double.
Debounce Time
If 0 does not implement debounce functionality.
Maximum Number of
Changes
Maximum number of changes allowed.
Table 5.5 Generic Local Digital Entity properties

The properties for a local analog type entity are:
Properties
Description
Internal Address
Physical Address
Name
5-4
5.1- Resources
Properties
Description
Description
Is Digital
If true then entity acquired from digital input.
Format
Format of entity when acquired from digital input.
Resolution
Number of digital entities used in this entity.
Sample Rate
Number of samples.
Software Filter
Software filter time.
Table 5.6 Generic Local Analog Entity properties

The properties for a local counter type entity are:
Properties
Description
Internal Address
Physical Address
Name
Description
Resolution
Counter resolution.
Sample Rate
Sample rate.
Software Filter
Filter time.
Flanc
Table 5.7 Generic Local Counter Entity properties
The properties for a local control type entity are:
Properties
Description
Internal Address
Physical Address
Name
Description
Subtype
Control sub type.
Duration
Control duration. If 0 then control is permanent.
Table 5.8 Generic Local Control Entity properties
5.1.3 DIAGNOSTIC ENTITIES

Diagnostic entities represent local state information of the running device such as I/O board health or
communication related information.
5-5
To access diagnostic entities user must right click on Configuration Settings Node and select Tools and
then Diagnostic Entities.
Figure 5.1 Diagnostic Entities access

There are 2 types of Diagnostic Entities. Digital and Counters and each ones have their own internal
address.
Figure 5.2 Diagnostic Entities list

Possible Diagnostic Entities:
Default Name
Internal Address
Type
DISABLE_CONTROLS
255
Digital Entity
DO_RESET
254
Digital Entity
SINDIG_DIGOUT_BOARD7_STATUS
251
Digital Entity
250
Digital Entity
249
Digital Entity
May be modified if required.
Cannot be modified since it is used as an internal identification for the corresponding diagnostic
information.
5-6
5.1- Resources
Default Name
Internal Address
Type
248
Digital Entity
247
Digital Entity
246
Digital Entity
245
Digital Entity
244
Digital Entity
SINDIG_ANAIN_BOARD7_STATUS
243
Digital Entity
242
Digital Entity
241
Digital Entity
240
Digital Entity
239
Digital Entity
238
Digital Entity
237
Digital Entity
236
Digital Entity
SINDIG_DIGIN_BOARD7_STATUS
235
Digital Entity
234
Digital Entity
233
Digital Entity
232
Digital Entity
231
Digital Entity
230
Digital Entity
229
Digital Entity
228
Digital Entity
SINDIG_DIGOUT_MAP3100_STATUS
227
Digital Entity
IEC104_IS_INIT
226
Digital Entity
IEC104_IS_SYNC
225
Digital Entity
IEC104_TCP_STATUS
224
Digital Entity
IEC104_LOST_INFO
223
Digital Entity
IEC104_FAILS_MSG
31
Counter Entity
IEC104_RX_MSG
30
Counter Entity
IEC104_TX_MSG
29
Counter Entity
Table 5.9 Diagnostic Entities
5-7
5.2 CONTROL CENTER COMUNICATIONS

5.2.1 IEC 60870-5-104 CONTROL CENTER
In this version of Automation Studio only this type of control center is supported. There are 4 types of
entities maps that can be configured for one control center:
The properties for a digital type mapping are:
Properties
Description
Name
Mapped entity name.
Description
User-defined textual description that can be used to describe the entity map.
Object Address
Object address
Table 5.10 Generic Digital map properties

The properties for an analogue type mapping are:
Properties
Description
Name
Mapped entity name.
Description
User-defined textual description that can be used to describe the entity map.
Object Address
Object address
Report by High Level
If true entity will be reported by high level.
High Level
High level.
High Level Hysteresys
High Level Hysteresys
Report By Jitter
If true entity will be reported by jitter.
Jitter
Jitter value.
Report by Low Level
If true entity will be reported by low level.
Low Level
Low level.
Low Level Hysteresys
Low Level Hysteresys
Report by Period
If true entity will be reported by period.
Period
Period value.
Table 5.11 Generic Analogue map properties

The properties for a counter type mapping are:
Properties
Description
Object Address
Object address
Name
Entity map name. Usually equals the entity name.
Report By Period
If true entity will be reported by period value.
Period
Counter cyclic period.
Table 5.12 Generic Counter map properties
5-8
5.2- Control Center Comunications
The properties for a control type mapping are:

Properties
Description
Object Address
Object address
Name
Entity map name. Usually equals the entity name.
Table 5.13 Generic Digital Control map properties
5-9
5.3 NETWORK
The network parameters are the needed for the deploy configuration to live device. Its this network
configuration that the device is going to use after resetting.
Figure 5.3 UA 500 - MAP3100b network parameters
5-10
5.4- Device Connection
5.4 DEVICE CONNECTION

1
The Edit Connection Wizard is the place where the user enters the active IP address to the device. This
address is only used for connecting to the device and if in the previous chapter the IP is changed then the
user must change the connection also after resetting.
Figure 5.4 UA 500 - MAP3100b connection parameter
5-11
Chapter
BUILD AND DEPLOY OPERATIONS
Chapter 6 - Build and Deploy Operations
INDEX
Er
or
!
R
ef
er
en
ce
so
ur
ce
no
t
fo
un
d.
6.1 SAVE PROCESS ........................................................................................................................................... 6-3

6.2 VALIDATE PROCESS ..................................................................................................................................... 6-4
6.3 BUILD PROCESS .......................................................................................................................................... 6-5
6.4 DEPLOY CONFIGURATION ............................................................................................................................ 6-6
6-2
6.1- Save process
6.1 SAVE PROCESS

1
When the user loads a configuration, all parameters are edited in memory and no changes are
automatically committed to disk. When the user saves the configuration, the previous configuration file is
backed up and all changes are committed to disk.
6-3
6.2 VALIDATE PROCESS

The validate process can be full or partial. The user may validate the entire device, or one module that
belongs to it.
Er
or
!
R
ef
er
en
ce
so
ur
ce
no
t
fo
un
d.
6-4
6.3- Build process
6.3 BUILD PROCESS

1
The build process can only be full or partial. The user may only build the entire device and generate a new
configuration package to be deployed.
6-5
6.4 DEPLOY CONFIGURATION
Er
or
!
R
ef
er
en
ce
so
ur
ce
no
t
fo
un
d.
Deploy Configuration: The deploy command deploys the device configuration to the device using
the address defined in the default connection.
These commands allow the user to communicate with the device. They all need a defined connection, and
the user will be asked to give a user name and a password, so the user must be authorized to access the
device. This commands run externally. The user can follow the process in the Task Manager pad, and check
for any errors that may occur in the Output Window pad.
6-6

Automation Studio User Manual - UA 500 - MAP3100b

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Automation Studio User Manual - UA 500 - MAP3100b

Caricato da

Copyright:

Formati disponibili

UA 500 MAP3100b

ASID13000042, Rev. 2.0, September 13

- UA 500 MAP3100b, N. ASID13000042, Rev. 2.0, September 13

Initial Version of Automation Studio with UA 500 - MAP3100b support

Version corresponding to Automation Studio 2.6 Rev.4 or later.

- UA 500 MAP3100b, N. ASID13000042, Rev. 2.0, September 13

INTRODUCTION ................................................................................................................................ 1-1

ADOPTING A CONFIGURATION PROCESS ......................................................................................... 2-1

ADDING DEVICES TO PROJECTS ........................................................................................................ 3-1

SETTING UP SOFTWARE AND HARDWARE MODULES ....................................................................... 4-1

CONFIGURING THE DATA MODEL ..................................................................................................... 5-1

BUILD AND DEPLOY OPERATIONS .................................................................................................... 6-1

- UA 500 MAP3100b, N. ASID13000042, Rev. 2.0, September 13

- UA 500 MAP3100b, N. ASID13000042, Rev. 2.0, September 13

- UA 500 MAP3100b, N. ASID13000042, Rev. 2.0, September 13

Total pages of the chapter 7

- UA 500 MAP3100b, N. ASID13000042, Rev. 2.0, September 13

- UA 500 MAP3100b, N. ASID13000042, Rev. 2.0, September 13

1.2 SCOPE AND AUDIENCE

- UA 500 MAP3100b, N. ASID13000042, Rev. 2.0, September 13

- UA 500 MAP3100b, N. ASID13000042, Rev. 2.0, September 13

- UA 500 MAP3100b, N. ASID13000042, Rev. 2.0, September 13

1.5- How to get started?

1.5 HOW TO GET STARTED?

- UA 500 MAP3100b, N. ASID13000042, Rev. 2.0, September 13

Chapter 2 - Adopting a configuration Process

- UA 500 MAP3100b, N. ASID13000042, Rev. 2.0, September 13

2.1- Iterative configuration and modification

2.1 ITERATIVE CONFIGURATION AND MODIFICATION

Figure 2.1 Iterative activity cycle

- UA 500 MAP3100b, N. ASID13000042, Rev. 2.0, September 13

Chapter 2 - Adopting a configuration Process

2.2 MANAGING CONFIGURATION VERSIONS

- UA 500 MAP3100b, N. ASID13000042, Rev. 2.0, September 13

ADDING DEVICES TO PROJECTS

Chapter 3 - Adding Devices to Projects

- UA 500 MAP3100b, N. ASID13000042, Rev. 2.0, September 13

3.1- New devices

3.1 NEW DEVICES

Figure 3.1 UA 500 - MAP3100b new device wizard

- UA 500 MAP3100b, N. ASID13000042, Rev. 2.0, September 13

Chapter 3 - Adding Devices to Projects

3.2 EXISTING DEVICES

Live device on the network

Choose Add Existing Device command from Solution

Device on the current project or in

Use copy/paste from within the tool.

Choose Import / Device Package command from the

Table 3.1 Available options to add existing UA 500 - MAP3100b devices

- UA 500 MAP3100b, N. ASID13000042, Rev. 2.0, September 13

SETTING UP SOFTWARE AND

Chapter 4 - Setting up Software and Hardware Modules

4.1 LOCAL AREA NETWORK INTERFACES .............................................................................................................. 4-3

Total pages of the chapter 4

- UA 500 MAP3100b, N. ASID13000042, Rev. 2.0, September 13

4.1- Local Area Network Interfaces

4.1 LOCAL AREA NETWORK INTERFACES

4.1.1 ETHERNET INTERFACES

Figure 4.1 UA 500 - MAP3100b with network interface

- UA 500 MAP3100b, N. ASID13000042, Rev. 2.0, September 13

Chapter 4 - Setting up Software and Hardware Modules

4.2 SERIAL PORTS

- UA 500 MAP3100b, N. ASID13000042, Rev. 2.0, September 13