Foxboro™ DCS

FDC280 OPC UA Client Driver

User’s Guide

*B0700WJ* *A*

B0700WJ, Rev A

February 2022

https://www.se.com
Legal Information
The Schneider Electric brand and any trademarks of Schneider Electric SE and its
subsidiaries referred to in this guide are the property of Schneider Electric SE or its
subsidiaries. All other brands may be trademarks of their respective owners.
This guide and its content are protected under applicable copyright laws and furnished
for informational use only. No part of this guide may be reproduced or transmitted in
any form or by any means (electronic, mechanical, photocopying, recording, or
otherwise), for any purpose, without the prior written permission of Schneider Electric.
Schneider Electric does not grant any right or license for commercial use of the guide
or its content, except for a non-exclusive and personal license to consult it on an "as is"
basis. Schneider Electric products and equipment should be installed, operated,
serviced, and maintained only by qualified personnel.
As standards, specifications, and designs change from time to time, information
contained in this guide may be subject to change without notice.
To the extent permitted by applicable law, no responsibility or liability is assumed by
Schneider Electric and its subsidiaries for any errors or omissions in the informational
content of this material or consequences arising out of or resulting from the use of the
information contained herein.

High Performance OPC UA Client Server SDK Bundle © Unified Automation. Used by
Schneider Electric under license.

This document contains standardized industry terms that some customers might find
sensitive or offensive. These terms do not reflect the official policy or position of
Schneider Electric.
 FDC280 OPC UA Client Driver User’s Guide

Table of Contents
Preface ...............................................................................................................7
Revision Information.........................................................................................7
Related Documents..........................................................................................7
Schneider Electric Products Mentioned in this Document ....................................7
Global Customer Support .................................................................................7
We Welcome Your Comments...........................................................................8
Chapter 1: Getting Started ..............................................................................9
Understanding the Installation and Configuration Process ...................................9
Features........................................................................................................10
Supported OPC Foundation Profiles and Services ......................................10
Security Features .....................................................................................10
Additional Features................................................................................... 11
Brief Overview of OPC UA Realtime Data Access and Terminology.................... 11
Supported Hardware Configurations ................................................................12
System Requirements ....................................................................................13
Hardware Requirements ...........................................................................13
Software Requirements ............................................................................13
Chapter 2: Installation ....................................................................................15
Installing on a Foxboro DCS Using the ICC and CCS FDC280 Configurator to
Configure the Driver .......................................................................................15
Installing on a Foxboro DCS Using the Control Software Configurator to
Configure the Driver .......................................................................................17
Using Separate Workstations for Control Software Configurator and
Hosting the FDC280 .................................................................................17
Using a Single Station for the Control Software Configurator and Hosting
the FDC280 .............................................................................................23
Downloading the OPC UA Client Driver to the FDC280 .....................................23
Chapter 3: Configuring OPC UA Client Driver Using Control
Software ...........................................................................................................25
Using OPC UA with Security Features .............................................................25
Using OPC UA without Security Features.........................................................25
Configuring an ECB200 Block .........................................................................26
Configuring a Device ECB (ECB201) for Self-signed Certificate .........................26
Configuring a Device ECB (ECB201) for the OPC UA Server.............................30
Configuring the Device Options Parameter .................................................30
Configuring Groups and I/O Point Aliases for ECB201 Server ECB ....................33
Group Configuration for Server ECB ................................................................34
Group for Configuring Security Features ....................................................34
Configuring I/O Point Groups for Server ECB201 ........................................37
I/O Points Aliases Configuration for Server ECB201 .........................................38
Points/Nodes from Multiple Namespace URI ..............................................38
Multiple Publish Intervals for Same Namespace URI ...................................39
Multiple Sample Intervals for Same Namespace URI and Publish
Intervals...................................................................................................40

B0700WJ, Rev A 3
FDC280 OPC UA Client Driver User’s Guide

Bulk Creation of Groups and I/O Point Aliases from a Spreadsheet ..............40
Configure and Deploy DCI Blocks....................................................................44
Bulk Creation of DCI Block Configuration of I/O points from a
Spreadsheet File with OPC UA Server Tags ...............................................45
Chapter 4: Configuring OPC UA Client Driver Using CCS .......................52
Preliminary Considerations .............................................................................52
Overview of Configuration...............................................................................52
Configuring an ECB200 Block .........................................................................52
Configuring an ECB201 Block .........................................................................53
Adding a Group for Configuring Security Policy and Message Security Mode
as None.........................................................................................................54
Chapter 5: Principles of Operation ...............................................................55
OPC UA Client Driver Operation......................................................................55
Redundant Operation .....................................................................................55
ECB201 Operation for Certificate Data.............................................................56
ECB201 Operation for Connection to an OPC UA Server ..................................56
Configuring DCI Blocks for OPC UA Points/Nodes............................................60
Configuring Additional Block Types..................................................................62
BOUT – Binary Output Block .....................................................................62
PAKOUT – Packed Output Block ...............................................................63
IOUT – Integer Output Block......................................................................63
ROUT – Real Output Block........................................................................64
BIN/BINR – Binary Input and Redundant Binary Input Blocks.......................64
IIN/IINR – Integer Input Block ....................................................................64
RIN/RINR – Real Input and Redundant Real Input Blocks............................65
PAKIN/PAKINR – Packed Input Block ........................................................65
STRIN – String Input Block........................................................................66
Diagnostic Data .............................................................................................66
Reset Counters ........................................................................................66
Bad Timestamp Points ..............................................................................67
Response Timeout Counter.......................................................................67
Last Detected Error Message ....................................................................68
Support of Arrays ...........................................................................................68
Write-Only Points ...........................................................................................70
DCI Input/Output Blocks – Data Types .............................................................70
Output Blocks – Support Data Types ...............................................................71
OPC UA Server Data Types to DCI Block Type Mapping ...................................72
OPC UA Value Status .....................................................................................73
Enabling Communication with the Server with OPC UA Security
Features........................................................................................................74
Enabling Communication to the Server without OPC UA Security
Features........................................................................................................76
Chapter 6: System Messages ......................................................................77
Detecting Lost Connection with the OPC UA Server..........................................79
DCI Blocks Status ..........................................................................................80
Appendix A: FDC280 System Monitor Log (smon_log)
Messages ........................................................................................................81
4 B0700WJ, Rev A
 FDC280 OPC UA Client Driver User’s Guide

Appendix B: FDC280 Diagnostic Driver Support .......................................83

Glossary ...........................................................................................................85
Index .................................................................................................................87

B0700WJ, Rev A 5
 n k
Bla
e f t
y L
a ll
i on
n t
n t e
e I
a g
s P
h i
T
Preface FDC280 OPC UA Client Driver User’s Guide

Preface
The Field Device Controller (FDC280) OPC UA Client Driver (OPC UA Client Driver)
integrates real-time data from third-party lant-floor devices via OPC UA Server into the
EcoStruxure™ Foxboro™ DCS. The driver supports communication on both simplex
and fault-tolerant (redundant) Foxboro DCS FDC280 configurations.
Before using this driver, be familiar with the:
• Foxboro DCS
• Standard and Compact 200 Series Subsystem User’s Guide (B0400FA)
• OPC UA interface that you will use to interface with the Foxboro DCS

Revision Information
This is the first release of this document.

Related Documents
• Standard and Compact 200 Series Subsystem User’s Guide (B0400FA)
• Field Device Controller 280 (FDC280) User's Guide (B0700GQ)
• Integrated Control Block Descriptions (B0193AX)
• Hardware Configuration User's Guide (B0750BB)
• Bulk Data Editor User's Guide (B0750AF)
• Block Configurator User's Guide (B0750AH)
• FDC280 Sizing Tool and Excel® Workbook User’s Guide (B0700GS)
• Strategy Editor User's Guide (B0750AN)
• Control Database Deployment User's Guide (B0750AJ)
• System Manager User’s Guide (B0750AP)

Schneider Electric Products Mentioned in this Document

Ecostruxure™ Foxboro™ DCS FDC280
Ecostruxure™ Foxboro™ DCS
EcoStruxure™ Foxboro™ DCS Control Core Services
EcoStruxure™ Foxboro™ DCS Control Editors
EcoStruxure™ Foxboro™ DCS Control HMI
EcoStruxure™ Foxboro™ DCS Control Network
EcoStruxure™ Foxboro™ System Manager

Global Customer Support

For support, visit https://pasupport.schneider-electric.com (registration required).

B0700WJ, Rev A 7
FDC280 OPC UA Client Driver User’s Guide Preface

We Welcome Your Comments

To help us improve documentation, we want to know about any corrections,
clarifications, or further information you would find useful. Send us an email at
[email protected].
This email address is only for documentation feedback. If you have a technical
problem or question, contact Global Customer Support.

8 B0700WJ, Rev A
Chapter 1: Getting Started FDC280 OPC UA Client Driver User’s Guide

Chapter 1: Getting Started

The OPC UA Client Driver integrates plant-floor third-party devices via the OPC UA
Server with Foxboro DCS for real-time data.
Analog and digital values can be read from or written to any OPC UA Server that
supports these data types. Communication is performed via an Ethernet connection
between the FDC280 and an OPC UA Server. The OPC UA Client Driver supports
only binary protocol.
The FDC280 supports connection with one OPC UA Server and up to 8000 points
mapped to tags/nodes.
The OPC UA Server manages all the intricacies of device-specific communication
protocols. The OPC UA Server packages the data in generic OPC UA form so that the
OPC UA Client Driver can have read/ write access to the data in the devices.
OPC UA communication between the OPC UA Client Driver and the OPC UA Server
must be remote. The OPC UA Server must reside on a Windows 10 or Windows
Server 2016 workstation that is connected to the OPC UA Client Driver by an Ethernet
network
The OPC UA Client Driver is a standalone driver. The OPC UA Client Driver image
provided as part of the installation package provides support only for this driver.

Understanding the Installation and Configuration Process

These are the main steps to install, configure, and use the driver.

Table 1 - Driver Installation

1 Install the driver. Chapter 2: Installation, page 15

2 Download the OPC UA Chapter 2: Installation, page 15
Client Driver image to
the simplex or fault-
tolerant FDC280.
3 Configure blocks.
Configuring FDC280 Chapter 3: Configuring OPC UA Client Driver Using
Using CS. Control Software, page 25
Configuring FDC280 Chapter 4: Configuring OPC UA Client Driver Using
Using CCS. CCS, page 52
Configure DCI blocks Configuring DCI Blocks for OPC UA Points/Nodes,
and Diagnostic blocks. page 60
4 Turn on the driver and Enabling Communication with the Server with OPC
enable communication UA Security Features, page 74
with the client.
5 Enable diagnostic Appendix B: FDC280 Diagnostic Driver Support,
driver support. page 83

See Brief Overview of OPC UA Realtime Data Access and Terminology, page 11 for a
brief overview of OPC UA terminology.

B0700WJ, Rev A 9
FDC280 OPC UA Client Driver User’s Guide Chapter 1: Getting Started

Features
Supported OPC Foundation Profiles and Services
The OPC UA Client Driver supports these profiles:
• 6.5.107 UA TCP UA SC UA Binary
• 6.5.123 SecurityPolicy – None
• 6.6.162 SecurityPolicy – Basic128Rsa15
• 6.6.163 SecurityPolicy – Basic256
• 6.6.164 SecurityPolicy - Aes128-Sha256-RsaOaep
• 6.6.165 SecurityPolicy – Basic256Sha256
• 6.6.166 SecurityPolicy - Aes256-Sha256-RsaPss
• 6.6.167 User Token – Anonymous Facet
• 6.6.167 User Token – User Name Password Server Facet
The OPC UA Client Driver supports these services:

Table 2 - Supported Services

OPC UA Service Sets Supported Services Comments

All N/A
• Secure Channel
Service
• Session Service Set
Attribute Service Set Read Reading of OPC UA
Server Namespace, OPC
UA Server Status
Write N/A
Subscription Service Set • CreateSubscription Monitoring Mode:
Reporting only
• SetPublishingMode
• Publish
• RePublish
• DeleteSubscription
• TransferSubscription
MonitoredItem Service • CreateMonitoredI- • “data” only
Set tems • “Value” attribute only
• DeleteMonitoredI-
tems

Security Features
Table 3 - User Authentication

User Identity Token Description

Anonymous No user credentials
Username Identity Username/password credentials

10 B0700WJ, Rev A
Chapter 1: Getting Started FDC280 OPC UA Client Driver User’s Guide

Table 4 - Security Policies

Security Policy Description

None Not Recommended
Basic128Rsa15 Deprecated
Basic256 Deprecated
Basic256Sha256 Recommended
Aes128-Sha256– Recommended — Fastest
RsaOaep
Aes128-Sha256- Recommended — Most Secure
RsaPss

Table 5 - Message Security Modes

Message Security Description

Mode
None Allow communication with no security
Sign Allow secure communication without data privacy
Sign and Encrypt Allow secure communication with data privacy

Additional Features
These profiles and services are as described in OPC Unified Architecture Release
1.04 from the OPC Foundation.
• Up to one OPC UA server and up to 8000 I/O points, as long as the total number
of ECB blocks, DCI blocks, station blocks, and compounds it runs does not
exceed 8262.
• Up to 8000 DCI blocks.
See the Field Device Controller 280 (FDC280) User's Guide (B0700GQ) for more
information on the number of points the FDC280 supports.
• Up to 9 subscriptions.
• Up to 128 characters for a Namespace URI in OPC UA Server.
• Up to 128 characters for a point or NodeID in the OPC UA Server.
• Security mode as None, Sign, and Sign & Encrypt.
• VTQ (Value, Timestamp, Quality) for each tag or I/O point.
• Accessing of any element of a single dimensional array.
• Setting of OPC UA value status (Quality) for all DCI blocks except the STRIN
block.
• Self-signed certificate for encryption and authentication.

Brief Overview of OPC UA Realtime Data Access and Terminology

• An I/O point in the DCS maps to a node in OPC UA.
Each node has a name (Identifier). The Identifier can be a string (most common),
integer, or other data type as defined in the OPC UA standard. The point tag
name maps to the Node Identifier.

B0700WJ, Rev A 11
FDC280 OPC UA Client Driver User’s Guide Chapter 1: Getting Started

• The collection of Nodes the OPC UA Server exposes to clients is called an

Address Space. An Address Space can have subsets of Nodes called
Namespaces. A Namespace is specified by a Namespace URI (Uniform
Resource Identifier).
To configure a point in an OPC UA client, you need to specify the Identifier,
Identifier data type, point data type, and the Namespace URI.
• For real-time data access of points in an OPC UA Server, you need to subscribe
to the OPC UA Server using subscription lists.
A subscription list is a group of points in one or more Namespaces that the client
provides to the OPC UA Server with a publish rate. The client sends a publish
request to the OPC UA Server at the publish rate and the OPC UA Server
responds with any data updates to the points in the list. The points in a
subscription list are also referred to as “monitored items”.
To get updates for points at different rates, configure multiple subscription lists,
each with a different publish rate.
• Each data update for a point provided by the OPC UA Server consists of the
Value, Timestamp, and Quality attributes. Quality is also referred to as Value
Status.
The timestamp can be applied at the OPC UA Server or at the data source (for
example, a sensor connecting to the OPC UA Server). Depending on where the
timestamp is applied, it is called the OPC UA Server timestamp or the Source
timestamp.
The Server timestamp can be done in two ways: either at the time the OPC UA
Server receives the publish request or when the OPC UA Server knows the data
has changed. You can configure the OPC UA Server to sample the source at a
set rate. This is called the Sampling Interval.

Supported Hardware Configurations

Figure 1 - Simplex (Single) FDC280 to OPC UA Server Network Configuration

12 B0700WJ, Rev A
Chapter 1: Getting Started FDC280 OPC UA Client Driver User’s Guide

Figure 2 - Fault-Tolerant FDC280 to OPC UA Server Network Configuration

System Requirements
The FDC280 interfaces with the other hardware and software elements of the Foxboro
DCS to provide control, alarming, trending, and display capabilities. Software residing
in the FDC280 and Foxboro DCS workstations provide full support of the OPC UA
Client Driver functionality.
To support the FDC280 image that introduces OPC UA Client Driver support, you
require:
• Foxboro DCS Control Core Services v9.3 or later
On stations running Control Core Services v9.3 – 9.4, install Maintenance Pack
MP47481162B.
On stations running Control Core Services v9.5, install Maintenance Pack
MP59953075.
These Maintenance Packs are available from Global Customer Support at https://
pasupport.schneider-electric.com (registration required).
• Foxboro DCS Control Software (CS) 7.1.1 or later
• Foxboro DCS System Manager 2.13 or later

Hardware Requirements
See the Field Device Controller 280 (FDC280) User's Guide (B0700GQ).

Software Requirements
• Workstation Software
The workstation software required for the FDC280 includes:
◦ Foxboro DCS Control Editors

B0700WJ, Rev A 13
FDC280 OPC UA Client Driver User’s Guide Chapter 1: Getting Started

These editors are part of Control Software and provide for configuration of the
FDC280 in the Control Network. The software prepares configuration files that
contain information needed by the FDC280s to communicate with the devices
they are connected to. This software executes in a Foxboro DCS workstation
and includes the necessary user interface. Software in the FDC280 supports
run-time use of the configured information.
◦ Foxboro DCS Control Core Services (CCS)
This software integrates the FDC280 and connected devices into the overall
Foxboro DCS equipment configuration. Control Core Services includes the
CCS FDC280 Configurator, which allows you to configure additional data for
the FDC280’s operation, including archival capabilities. This product is
discussed in Field Device Controller 280 (FDC280) User's Guide (B0700GQ).
NOTE: There are limitations to configuration when using CCS. See
Chapter 4: Configuring OPC UA Client Driver Using CCS, page 52.
◦ FDC280 OPC UA Client Driver License
The license file is required to select OPC UA Client as a driver to run in
FDC280, in the configuration steps. The license file is also included in the
FDC280 OPC UA Client Driver media.
◦ OPCUACertGen.bat
To create Self Signed certificate for OPC UA Client Driver and deploy its
configuration to an FDC280 and save in Galaxy Database. This application is
available on the OPC UA Client Driver media.
• FDC280 Firmware
The FDC280 firmware for the OPC UA Client Driver is provided as an image file.
This image is included in the OPC UA Client Driver media. This firmware image
includes:
◦ OPC UA Client Driver: Part of the FDC280 image with highly flexible
configuration facilitating interfacing to OPC UA Server.
◦ Run-Time Software: Supports the reading and writing of data from and to the
connected client device’s field I/O values in the Foxboro DCS. This software
includes Distributed Control Interface (DCI) control blocks that interface to I/O
signals from the device.
◦ Diagnostics: Provide startup and maintenance fault detection and diagnosis
for the FDC280.

14 B0700WJ, Rev A
Chapter 2: Installation FDC280 OPC UA Client Driver User’s Guide

Chapter 2: Installation
The installation provides Complete and Custom installation types. Use Complete to
install all components on one workstation. Use Custom to select the components to
be installed on a workstation.
The installation media includes:
• FDC280 OPC UA Client Driver Image (OPCUA Client_1.0.fdc280)
Provides the OPC UA Client Driver functionality.
It is installed to path \usr\fox\sp\files.
• OPC UA Client Driver Licenses
Enables you to configure the OPC UA Client Driver on the FDC280. This
component installs the required entries on the workstation to enable configuration
of OPC UA Client Driver using the CCS Configurator or Control Software Editors.
If you are using ICC and the CCS FDC280 Configurator to configure the FDC280,
install this component on the workstation with Control Core Services hosting the
FDC280.
If you are using the Control Software Editors to configure the FDC280, install this
media on the Control Software Client workstation hosting the FDC280.
• OPCUACertGen.bat
Enables you to create self-signed certificate for the OPC UA Client Driver, deploy
its configuration to an FDC280, and save it in the Galaxy Database It is installed
in the path C:\ProgramData \SchneiderElectric\OPCUAClientCertGen\. Run
OPCUACertGen.bat file only on the CS Host Machine.

Installing on a Foxboro DCS Using the ICC and CCS FDC280

Configurator to Configure the Driver
1. Insert the CD-ROM with the OPC UA Client Driver in the host workstation's media
drive or mount the installation media to a network location accessible by the host
workstation.
2. In File Explorer, go to the root directory of the CD-ROM or installation.
3. Double-click the installer package.
The FDC280 OPC UA Client Driver Setup window opens.

B0700WJ, Rev A 15
FDC280 OPC UA Client Driver User’s Guide Chapter 2: Installation

4. Click Next.

5. Click Complete to install the required components.

The window displays the components that will be installed.

16 B0700WJ, Rev A
Chapter 2: Installation FDC280 OPC UA Client Driver User’s Guide

6. When installation is complete, click Finish.

Installing on a Foxboro DCS Using the Control Software

Configurator to Configure the Driver
Using Separate Workstations for Control Software Configurator and Hosting the FDC280
To complete this installation, perform both of these steps:

B0700WJ, Rev A 17
FDC280 OPC UA Client Driver User’s Guide Chapter 2: Installation

• Install the OPC UA Client Driver Image on the workstation hosting the FDC280.
For more information, see On a Workstation Hosting FDC280, page 18.
• Install the OPC UA Client Driver Licenses on the workstation with the Control
Software Configurator. For more information, see On a Workstation with Control
Software Configurator, page 20.

On a Workstation Hosting FDC280

1. Insert the CD-ROM with the OPC UA Client Driver in the host workstation's media
drive or mount the installation media to a network location accessible by the host
workstation.
2. In File Explorer, go to the root directory of the CD-ROM or installation.
3. Double-click the installer package. The FDC280 OPC UA Client Driver Setup
window opens.
4. Click Next.

18 B0700WJ, Rev A
Chapter 2: Installation FDC280 OPC UA Client Driver User’s Guide

5. In Choose Setup Type, click Custom.

6. Clear OPC UA Client Driver Key, then click Next.

B0700WJ, Rev A 19
FDC280 OPC UA Client Driver User’s Guide Chapter 2: Installation

7. In the Installation Summary window, click Install.

8. When installation is complete, click Finish.

On a Workstation with Control Software Configurator

1. Insert the CD-ROM with the FDC280 OPC UA Client Driver in the host
workstation's media drive or mount the installation media to a network location
accessible by the host workstation.
2. In File Explorer, go to the root directory of the CD-ROM or installation.

20 B0700WJ, Rev A
Chapter 2: Installation FDC280 OPC UA Client Driver User’s Guide

3. Double-click the installer package. The FDC280 OPC UA Client Driver Setup
window opens.
4. Click Next.

5. In Choose Setup Type, click Custom.

B0700WJ, Rev A 21
FDC280 OPC UA Client Driver User’s Guide Chapter 2: Installation

6. Clear OPC UA Client Driver Image, then click Next.

7. In the Installation Summary window, click Install.

22 B0700WJ, Rev A
Chapter 2: Installation FDC280 OPC UA Client Driver User’s Guide

8. When installation is complete, click Finish.

9. Import the FDC driver file (DriverDefinition.xml) into the Galaxy database.
This needs to be done only one time. The driver definition file allows you to
configure the OPC UA Client Driver using the Control Software.
10. In the Control Editors, select Galaxy > Import > FDC Driver. The Import FDC
Driver dialog box appears.
11. Click the “...” beside the text field at the top of the dialog box, then browse to the
location where the OPC UA Client Driver file was installed on the Control
Software client workstation. The location depends on where ArchestrA is
installed. Typically, this file is stored in D:\Program Files \ArchestrA
\Framework\Bin\Invensys\FDC Drivers\OPCUA Client/OPCUA_
Client_1.0 \ DriverDefinition.xml folder.
12. Select the FDC driver file, then click Validate.
The station is ready to configure the OPC UA Client Driver on FDC280.

Using a Single Station for the Control Software Configurator and Hosting the FDC280
Install the driver media and import the driver definition file to enable configuration of
OPC UA Client Driver using Control Software Editors. See Installing on a Foxboro
DCS Using the Control Software Configurator to Configure the Driver, page 17.

Downloading the OPC UA Client Driver to the FDC280

NOTE: This procedure is applicable for both Simplex and Fault Tolerant FDC280
configurations.
After installing the OPC UA Client Driver image (OPC UA Client_1.0.FDC280) on the
host station, download the image to the FDC280:
1. Install the FDC280 Modules as described in "Installing the Field Device Controller
280" in the Field Device Controller 280 (FDC280) User's Guide (B0700GQ).

B0700WJ, Rev A 23
FDC280 OPC UA Client Driver User’s Guide Chapter 2: Installation

2. Initialize the FDC280s.

3. Verify the presence of the FDC280 OPC UA Client driver image file "OPC UA
Client_1.0.FDC280" in the .../usr/fox/sp/files relative folder path, respective to the
IA Root path.
4. Run the batch script RenameOPCUAClient.BAT. The script file renames the
existing OS3I80 file to OS3I80.SBY and the OPC UA Client_1.0.FDC280 file to
OS3I80.
5. Perform a Major Image update operation as described in the Field Device
Controller 280 (FDC280) User's Guide (B0700GQ).
NOTE: Confirm you are performing an Image update on the correct FDC280
by checking the letterbug of the FDC280.
6. After the image update process successfully completes, run the batch script
RestoreOPCUAClient.BAT. The script file renames the OS3I80 file to OPC UA
Client_1.0.FDC280 and OS3I80.SBY file to OS3I80.

24 B0700WJ, Rev A
Chapter 3: Configuring OPC UA Client Driver Using Control
Software FDC280 OPC UA Client Driver User’s Guide

Chapter 3: Configuring OPC UA Client Driver Using

Control Software
OPC UA Client Driver uses specific terminology. For definitions of these terms, see
the Glossary.
After you have installed the software, you need to configure the FDC280 Ethernet port
as well as create Equipment Control Blocks (ECBs) and connection blocks that define
the devices and data accessed through the OPC UA Client Driver.

Using OPC UA with Security Features

1. Configure FDC280 I/O Ethernet port.
See Field Device Controller 280 (FDC280) User's Guide (B0700GQ).
2. Configure ECB200 and perform Go Online.
For information, see Configuring an ECB200 Block, page 26.
3. Configure ECB201 for self-signed certificate and deploy to FDC280.
For information, see Configuring a Device ECB (ECB201) for Self-signed
Certificate, page 26.
4. Configure ECB201 for Server Communication and deploy to FDC280.
For information, see Configuring a Device ECB (ECB201) for the OPC UA
Server, page 30.
5. Configure Groups for Security Features.
For information, see Configuring Security Settings in Custom Parameters of
Security Group for Server ECB201, page 37.
6. Configure Groups for I/O points and deploy the configuration to an FDC280.
For information, see Configuring I/O Point Groups for Server ECB201, page 37.
7. Configure and deploy DCI blocks.
For information, see Configure and Deploy DCI Blocks, page 44.
8. Enable communication of ECB201 for Server communication.
For information, See Field Device Controller 280 (FDC280) User's Guide
(B0700GQ).
9. Trust the Client certificate at Server Side (By Server Administrator).
For information, see Enabling Communication with the Server with OPC UA
Security Features, page 74.

Using OPC UA without Security Features

1. Configure FDC280 I/O Ethernet port.
See the Field Device Controller 280 (FDC280) User's Guide (B0700GQ).
2. Configure ECB200 and perform Go Online.
For information, see Configuring an ECB200 Block, page 26.

B0700WJ, Rev A 25
 Chapter 3: Configuring OPC UA Client Driver Using Control
FDC280 OPC UA Client Driver User’s Guide Software

3. Configure ECB201 for Server Communication.

For information, see .Configuring a Device ECB (ECB201) for the OPC UA
Server, page 30.
4. Configure Groups for I/O points and deploy its configuration to an FDC280.
For information, see Configuring I/O Point Groups for Server ECB201, page 37.
5. Configure DCI blocks.
For information, see Configure and Deploy DCI Blocks, page 44.
6. Enable communication of ECB201 for Server communication.
For information, see Enabling Communication to the Server without OPC UA
Security Features, page 76.

Configuring an ECB200 Block

ECB200 is the equipment control block for the OPC UA Client Driver. This driver
supports Ethernet communication.

Table 6 - ECB200 Parameters

Editor Subtab Parameter/ Value Description

N/A ECB200 Block Type
FBM * 6-character ID of the
FDC280
1 Hardware Type for
FDC280 (Automatically
filled in)
200 Software Type for
FDC280 (Automatically
filled in)
ENETPORT1 Block name of parent
Primary ECB
(Automatically filled in)
Driver Custom Parameter1 to 6 Not used by OPC UA
Client Driver
N/A Driver Driver and version:
-1 for Diagnostic Driver
7 for OPC UA Client
Driver (Automatically filled
in based on the selection
of the Driver)

Configuring a Device ECB (ECB201) for Self-signed Certificate

For the OPC UA Server to interface to the FDC280, two child ECB201s must be
configured and linked to the parent ECB200.
This ECB201 is mandatory when OPC UA Security features are used.
Follow these steps to create Device ECB201 and deploy a certificate and privatekey:

26 B0700WJ, Rev A
Chapter 3: Configuring OPC UA Client Driver Using Control
Software FDC280 OPC UA Client Driver User’s Guide

1. Deploy the ECB200 and set it to the online state.

2. Run the OPCUACertGen.bat available in the path C:\ProgramData
\Schneider Electric \OPCUAClientCertGen.
The OPC UA certificate generator script file creates a self-signed certificate and
thumbprint information of certificate, and deploys the configuration of certificate
and privatekey to FDC280.
The OPCUACertGenTool window appears.

3. Fill in the details as shown.

• You must fill in all fields to generate a valid certificate.
• Each field can hold a maximum of 64 characters.

Table 7 - Certificate Generation Fields

Field Value
Select an FDC280 Choose the letter bug of the FDC280 to use for the running the OPC UA Client
driver.
Common Name The fully qualified domain Name (FQDN), such as your company email
address.
Organization Your company’s legally registered name, such as YourCompany, Inc.
Organizational Unit Name of your department or section within the organization.
Locality City where your company is legally located.
State The state or province where your company is legally located.

B0700WJ, Rev A 27
 Chapter 3: Configuring OPC UA Client Driver Using Control
FDC280 OPC UA Client Driver User’s Guide Software

Table 7 - Certificate Generation Fields (Continued)

Field Value
Email Address Your email address
RSA Key Length Length of the public key used for certificate. Default is 2048. See the server
specification for key length.
Signature Algorithm Hash algorithm for generating self signed certificates. Default is SHA256. See
the server specification for the signature algorithm.

4. Click Generate Certificate.

The Script prompts you to enter DEV_ID of ECB200.

The Script invokes DirectAccess.exe to generate device ECB201 for certificate

and deploy it in OPC UA Client Driver.

28 B0700WJ, Rev A
Chapter 3: Configuring OPC UA Client Driver Using Control
Software FDC280 OPC UA Client Driver User’s Guide

5. Enter this information.

Table 8 - Direct Access Fields

Field Value
Node Name of your platform. To access a Galaxy running on another node:
1. Click Browse next to the Node field.
2. Select the desired domain and Galaxy server.
You can also enter the name of the remote Galaxy node and press Enter, or
press Tab to navigate to the next field. You are informed if the node you entered
is not reachable, or if there are no Galaxies found on that platform.
Galaxy Name of the Galaxy repository on your platform.
File Click Browse and select OPCUACertGen.XML from C:\ProgramData
\Schneider Electric \OPCUAClientCertGen.
Username and password If the security feature is enabled on within the Galaxy, provide a username and
password in the UserName and Password fields.

6. Click Execute.
If an error occurs, such as incorrect username/password, fix it and click Execute
again. For error information, see Scripting with Direct Access User’s Guide
(B0750BM, Rev AJ).
NOTE: If the error is related to the ECB200 Name, restart the script file again
and provide the correct input.

7. Click Close.
After a few minutes, the script closes automatically.
The certificate generator creates Thumbprint.txt in the path C:\ProgramData
\Schneider Electric \OPCUAClientCertGen. The length of the thumbprint
information is 62 bytes.

At a later time, the server administrator reviews this thumbprint information along
with FDC280 letterbug in the client certificate for inclusion in the Trusted list.

B0700WJ, Rev A 29
 Chapter 3: Configuring OPC UA Client Driver Using Control
FDC280 OPC UA Client Driver User’s Guide Software

Configuring a Device ECB (ECB201) for the OPC UA Server

This ECB is referred to as Server ECB in this user guide.

Table 9 - ECB201 Parameters

Editor Subtab Parameter Description

General * Contains the name used by the
FDC280 to access this ECB.
General Block Description Description
Block Sample Time (PERIOD) The block’s execution time base, 1 =
0.5 second. This is the scan period
at which the Control Processor
scans DCI blocks. The scan rate of
the device is independent of this
scan period.
Block Phase Number Block phase number
FBM Device Identifier A unique 6-character ID. This is the
device identifier shown in the
System Manager.
Device Name The IP Address and Port number of
OPC UA Server must be configured,
or device is marked as INVALID and
an appropriate Smon_log message
is logged.
Using the configured IP Address and
Port No the OPC UA Client Driver
creates OPC UA Server Endpoint
URL of Binary protocol. The format
is ‘opc.tcp://IPAddress:PortNo’
An OPC UA Server Endpoint URL is
a physical address available on a
network that allows OPC UA Client
Driver to access one or more
services provided by an OPC UA
Server.
Device Options See Configuring the Device Options
Parameter, page 30.

Configuring the Device Options Parameter

Options that Can Be Configured in the DVOPTs Parameter, page 32 and Options that
Must Be Configured in the DVOPTs Parameter, page 30 list the options that are
configured in the Device Options (DVOPTS) parameter of the Server ECB201. Some
of the options must be configured in the DVOPTS parameter only. Other options can
be configured in DVOPTS parameter only under certain cases. These options can be
appended in any order or combination, unless explicitly stated otherwise.

Options that Must Be Configured in the DVOPTs Parameter

The options shown in this table must be configured in the Device Options (DVOPTS)
parameter of the Server ECB201.

30 B0700WJ, Rev A
Chapter 3: Configuring OPC UA Client Driver Using Control
Software FDC280 OPC UA Client Driver User’s Guide

Table 10 - Device Options that Must Be Configured in the DVOPTs Parameter

Option Description
+TO Enables option to configure time out (in seconds) for OPC UA Server communication to mark
device to failure detection.
If TO option is not configured, a default timeout value, i.e. 10 seconds, is applied.
Timeout option can be configured between range of 10 sec to 100 seconds.
Example +TO= 50, means 50 Seconds
+MS Enables configuration of Maximum Subscriptions.
If this option is not configured, the default subscriptions supported by the OPC UA Client
Driver is 9.
To change the number of subscriptions, add (+MS=X) valid values of X must be in the range of
1-9.
OPC UA Source When the OPC UA Server subscribes to a value from another OPC UA Server / Device (that is
Timestamp an aggregating OPC UA Server), the timestamp of the originator of the data source is defined
as OPC UA Source Timestamp. The Source Timestamp received for the data value during
initial connect/ reconnect might be older than the current timestamp of FDC280.
NOTE: By default, the timestamps from the control processor (FDC280 Timestamp) are
set to the DCI blocks. Set the CFGOPT bit 13 of Station block to “1” for enabling OPC UA
Source Timestamp options.
• +SRCTS: Enables the OPCUA Source Timestamp for DCI Blocks. If this option is
configured, the driver sets the OPCUA Source Timestamp received from the OPC UA
Server.
• +FTS: Enables the FDC280 Timestamp for DCI blocks during initial connect/ reconnect to
OPC UA Server. Enables the FDC280 Timestamp for DCI blocks during initial connect/
reconnect to OPC UA Server. This option must be used with the +SRCTS option.

B0700WJ, Rev A 31
 Chapter 3: Configuring OPC UA Client Driver Using Control
FDC280 OPC UA Client Driver User’s Guide Software

Table 10 - Device Options that Must Be Configured in the DVOPTs Parameter (Continued)

Option Description
OPC UA Server The time that the OPC UA Server received a variable value or knew it to be accurate from the
Timestamp connected data source. If the OPC UA Server subscribes to the value from another OPC UA
Server and value changes once in every ten seconds, the OPC UA Server timestamp is
updated each time a new value is received. When the value does not change, new values are
not received on the Subscription. However, in the absence of error detection, the receiving
OPC UA Server applies a new OPC UA Server timestamp every ten seconds because not
receiving a value means that the value has not changed. Thus, the OPC UA Server timestamp
reflects the time at which the OPC UA Server knew the value to be accurate.
For example, suppose that a OPC UA Server is receiving values from an exception-based
device, and that these conditions apply.
• The device checks values every 500 milliseconds.
• The connection to the device is good.
• The device sent an update 3 minutes ago with a value of 1234.
In this case, the OPC UA Server value would be 1234 and the OPC UA Server timestamp
would be updated every 500 milliseconds after the receipt of the value.
NOTE: By default, the timestamps from the control processor (FDC280 Timestamp) is set
to the DCI blocks. Set the CFGOPT bit 13 of Station block to “1” for enabling OPC UA
Server Timestamp options.
• +SRVTS: Enables the OPCUA Server Timestamp for DCI Blocks. If this option is
configured, the driver sets the OPCUA Server Timestamp received from the OPC UA
Server.
• +VDT: Enables the driver to validate the OPC UA Server timestamp. This option must be
used in conjunction with +SRVTS option. After receiving the OPC UA Server Timestamp,
the driver verifies the received timestamp to be not later than the FDC280 time by X (in
milliseconds) value. Example +VDT=2000 means 2 Seconds. This option should be
configured only if the OPC UA Server and OPC UAClient Driver clocks are in sync.
If the validation is:
• Successful, the driver updates the OPC UA Server timestamp to the DCI Blocks.
• Not successful, the driver updates the FDC280 timestamp to the DCI Blocks and the block
status is set to ERR/Uncertain (green color) and 'Timestamp Error' alarm message
appears on System Manager and diagnostic counter is updated.
+TSTAMP Use this option when the OPC UA Server does not support timestamp with the data updates.
When you use this option, the server timestamps data value updates received from the Serve
with the FDC280 time.
If the OPC UA Server does not support timestamp with data updates, by default the timestamp
parameter of the corresponding DCI block is updated with the FDC280 time when the DCI
block is processed after receiving a value update form the OPC UA Server.
Using the +TSTAMP option provides increased accuracy with timestamp where driver publish
rate is faster than the DCI block period.
NOTE: By default, the timestamps from the control processor (FDC280 Timestamp) is set
to the DCI blocks. Set the CFGOPT bit 13 of Station block to “1” for enabling this
Timestamp option.

Options that Can Be Configured in the DVOPTs Parameter

The options shown in the table titled Device Options that Can Be Configured in the
DVOPTs Parameter, page 33 can be configured in the Device Options (DVOPTS)
parameter of the Server ECB201 if certain conditions are met. Keep these
considerations in mind:

32 B0700WJ, Rev A
Chapter 3: Configuring OPC UA Client Driver Using Control
Software FDC280 OPC UA Client Driver User’s Guide

• Some options are needed only for certain use cases, as noted in the Description
field.
• The total number of characters in the DVOPTS parameter cannot exceed 64.
• If the total number of characters exceeds 64, for instructions on configuring the
options in this table, see Configuring Groups and I/O Point Aliases for ECB201
Server ECB, page 33.

Table 11 - Device Options that Can Be Configured in the DVOPTs Parameter

Option Description
+URI Enables access of Points/Nodes from Namespace URI of the OPC UA Server address
space. Example: +URI =urn:MESH02:UnifiedAutomation: UaServerCpp
identifies the Namespace URI in OPC UA Server.
This option must be configured, or the device is marked as INVALID and an appropriate
Smon_log message is logged.
NOTE: Configure this option in DVOPTS parameter only when the driver needs to
access points or nodes from a single Namespace URI in the OPC UA Server. If
points need to be accessed from multiple name space URIs, configure those in
Groups as described in Configuring Groups and I/O Point Aliases for ECB201
Server ECB, page 33.
+PI Enables configuration of publish interval. The rate at which OPC UA Server sends the
notification messages to the OPC UA Client Driver.
If this option is not configured, the default publish Interval that is 500ms is applied.
To change the default, publish interval add +PI = X (where X is the time in units of
100ms), valid values of X must be in the range of 1-100.
NOTE: Configure this option in the DVOPTS parameter only when the publish
interval is the same for all the points to be accessed from the Server. If multiple
publish intervals need to be configured, use Groups as described in Configuring
Groups and I/O Point Aliases for ECB201 Server ECB, page 33.
+SI Enables configuration of sampling interval. The rate at which the OPC UA Server
checks the data source for changes.
If this option is not configured, the default Sampling Interval is same as publish interval.
To change the sampling interval, add +SI = X (where X is the time in units of 100ms,
valid values of X must be in the range of 0-100.
NOTE:
• Sampling Interval of 0 (SI=0) indicates that the OPC UA Server should use the
fastest practical rate. It is expected that OPC UA Server supports only a limited
set of sampling intervals to optimize their operation. If the exact interval
requested by the Client is not supported by the OPC UA Server, the OPC UA
Server assigns to the Monitored Items the most appropriate interval as
determined by the OPC UA Server.
• Configure this option in the DVOPTS parameter only when the sampling
interval is the same for all the points to be accessed from the Server. If multiple
Sample Intervals need to be configured, use Groups as described in
Configuring Groups and I/O Point Aliases for ECB201 Server ECB, page 33.

Configuring Groups and I/O Point Aliases for ECB201 Server ECB
Groups are sets of points that can be accessed from the OPC UA Server. Points in a
group belong to a single NameSpace URI and have the same publish interval.
Configuring groups and I/O point aliases is required only if any of these apply:

B0700WJ, Rev A 33
 Chapter 3: Configuring OPC UA Client Driver Using Control
FDC280 OPC UA Client Driver User’s Guide Software

• Identifier (point name in the OPC UA Server) is greater than 31 characters

• Identifier names are case sensitive
• More than one subscription is required (configuring multiple publish intervals for
multiple sets of points/nodes in a single NameSpace URI)
• Driver must access Points/Nodes from Multiple Namespace URIs in OPC UA
Server
• Security policy and message security mode are set with an option other than
None.
1. To configure the Groups and Point Aliases, double-click the device object to open
the Editor.

2. In the Control Editor, click the Groups tab and configure the Groups table. For
more information, see the examples provided in Group Configuration for Server
ECB, page 34.

Group Configuration for Server ECB

Two types of groups can be configured:
• Group for configuring security features
• Group for configuring I/O point groups

Group for Configuring Security Features

1. In Group Name, enter SecGroup.

2. Leave Scan Rate blank.
3. Leave Phase blank.

Security Policy
A Security Policy specifies which security mechanisms are to be used for the Secure
Channel between OPC UA Client driver and OPC UA Server. A Security Policy

34 B0700WJ, Rev A
Chapter 3: Configuring OPC UA Client Driver Using Control
Software FDC280 OPC UA Client Driver User’s Guide

defines the algorithms for signing and encryption, the algorithm for key derivation and
the key lengths used in the algorithms.

Table 12 - Security Policy Options

Security Policy Option to be Configured in Custom Parameter 1

None SP=0
Basic128Rsa15 SP=1
(Deprecated)
Basic256(Deprecated) SP=2
Basic256Sha256 SP=3
Aes128_sha256_Rsaoaep SP=4
Aes256_Sha256_RsaPss SP=5

Message Security Mode

The Message Security Mode configures the general level of security applied to
messages exchanged between client and server.

Table 13 - Message Security Modes

Message Security Mode Option to Be Configured in Custom Parameter 1

None +MSM=0
Sign +MSM=1
Sign and Encrypt +MSM=2

Table 14 - Supported Options for Security Policies and Message Security Modes

Security Policy Message Security Mode

None None
Any policy other than None Sign or Sign and Encrypt
in Security Policy table

Table 15 - Options Not Supported for Security Policies and Message Security
Modes

Security Policy Message Security Mode

None Any mode other than None
Any policy other than None None
in Security Policy table

SP=0 and MSM =0. The Security policy and Message Security Mode are configured
as None in Custom Parameter 1, as shown in this screenshot.

B0700WJ, Rev A 35
 Chapter 3: Configuring OPC UA Client Driver Using Control
FDC280 OPC UA Client Driver User’s Guide Software

SP=3 and MSM=2 The Security Policy is configured as Basic256Sha256 and the
Message Security Mode is configured as SignAndEncrpt, as shown in this screenshot.

If both security policy and message security mode options are not configured, driver
considers the default options i.e. SP= 3( BASIC256Sha256) and MSM=2(Sign and
Encrypt).
If either security policy or message security mode is configured, the driver displays the
error message “Invalid option SP/MSM not configured” and marks the device to
invalid.
If security policy is configured as None(SP=0), message security mode should also be
configured as none(MSM=0) and vice versa. Otherwise, the driver displays the error
message indicating “INVALID SP/MSM combination configured” and marks the device
to invalid.

User Authentication
User authentication allows the OPC UA server to verify the identity of the OPC UA
client driver user credentials.
The driver supports following User Identity Token Types and this option is configured
in CPARAM2 of SecGroup.

Table 16 - User Identity Token Types

User Identity Options to be Configured in Custom Parameter 2

Anonymous Not applicable
Username Identity EN = xxx (where xxx is the username)
+PV = yyy (yyy is the password).

For Anonymous Login support leave option as blank.

For Username Identity support configure both EN and +PV values. Otherwise the
driver displays an error “Invalid option Username/Password not configured” and
marks the device to invalid.
For Username Identity configure username and password in Custom Parameter 2 as
shown in this screenshot.

For Anonymous Login leave Custom Parameter 2 blank.

36 B0700WJ, Rev A
Chapter 3: Configuring OPC UA Client Driver Using Control
Software FDC280 OPC UA Client Driver User’s Guide

Configuring Security Settings in Custom Parameters of Security

Group for Server ECB201

1. Custom Parameter 1 – Configure security policy (SP=) and message security

modes (+MSM=).For more information, see Security Policy, page 34and
Message Security Mode, page 35.
2. Custom Parameter 2 – Configure username and password. For more
information, see User Authentication, page 36.
3. Leave the Custom Parameter 3 and Custom Parameter 4 fields blank.
NOTE: If the SecGroup is not configured, the OPC UA Client Driver sets the
default option for security policy as SP=3, Message security mode as MSM=
2, and User Authentication as Anonymous.

Configuring I/O Point Groups for Server ECB201

1. In Group Name, provide any unique alphanumeric name for the group.
The Group Name must not exceed 128 characters. This image shows a sample
OPC UA Client Driver.

2. In Scan Rate, specify the Publish interval in 100 milliseconds resolution.

3. Leave Phase blank.

Configuring Sample Interval and Namespace URI in I/O Point

Groups in Custom Parameters

1. Custom Parameter 1 – Configure Sample Interval in 100 milliseconds resolution.

2. Custom Parameter 2 – Specify the Namespace URI. When the Namespace URI
is equal or less than 64 characters, leave the Custom Parameter 3 blank.

3. Custom Parameter 3 – When the Namespace URI is larger than 64 characters,

enter the first 64 characters in Custom Parameter 2 and remaining characters in
Custom Parameter 3.
4. Leave Custom Parameter 4 blank.

5. Click a blank row to save the configuration. If you do not click outside the current
row, the configuration is not saved.

B0700WJ, Rev A 37
 Chapter 3: Configuring OPC UA Client Driver Using Control
FDC280 OPC UA Client Driver User’s Guide Software

I/O Points Aliases Configuration for Server ECB201

In the Control Editor, click the I/O Point Aliases tab, configure the table I/O Point
Aliases as shown in this image.
• Name: It is the PNT_NO parameter of the associated DCI block. This is also what
you see in the HMI. It is an alias name of the point in the OPC UA Server. It
should be of the format Alias Name:x, where “x “is the data type of real name of
the point in the OPC UA Server in the Address column. The various options for
“X” are listed in the first table in Configuring DCI Blocks for OPC UA Points/
Nodes, page 60. The Alias Name length must not exceed 32 characters. For
Write Only points, configure : NR option to the PNT_NO of DCI Output Block as
shown in this image. The FDC280 OPC UA Client Driver does not subscribe to
the Write Only Points, so Sampling and Publish intervals are ignored by the OPC
UA Driver.
• Address: Name or ID of the point in the OPC UA Server. The Address must not
exceed 128 characters.
• Group: Select the Group Name for which this Point belongs to i.e. Publish Rate,
NamespaceURI, Sampling Interval
• DataType: Data type of the point in the OPC UA Server. (See the table in OPC
UA Server Data Types to DCI Block Type Mapping, page 72).

Points/Nodes from Multiple Namespace URI

Configure separate group for each Namespace URI, and link Points/Nodes to the
corresponding group.
Group Configuration:

• Group Name - Any unique alphanumeric name for the group, for example:
Group1, Group2
• Scan Rate – Specify the Publish interval (in 100 milliseconds resolution), for
example: 10
• Phase – Leave the field blank (Default value is 0)
• Custom Parameter 1 – Configure Sample Interval (in 100 milliseconds
resolution), for example: SI=10
• Custom Parameter 2 – Specify the Namespace URI, for example: URI=urn:
MESH02:UnifiedAutomation:UaServerCpp for Group1 and URI = http://www.
unifiedautomation. com/DemoServer/ for Group2

38 B0700WJ, Rev A
Chapter 3: Configuring OPC UA Client Driver Using Control
Software FDC280 OPC UA Client Driver User’s Guide

Point Configuration:

• Name - It is the PNT_NO parameter of the associated DCI block. This is also
what you see in the HMI. It is an alias name of the point in the OPC UA Server. It
should of the format Alias Name:x where “x “is the data type of real name of the
point in the OPC UA Server in the Address column. The various options for “X”
are listed in the first table in Configuring DCI Blocks for OPC UA Points/Nodes,
page 60. The Alias Name length must not exceed 32 characters. For example,
Node1:S , Node2:S.
• Address - Name or ID of the point in the OPC UA Server, for example, Demo.
Massfolder_Dynamic.Variable0000, Demo. Massfolder_Dynamic.Variable0001
• Group – Select the Group Name for which this Point belongs, for example:
Group1, Group2
• DataType - Data type of the point in the OPC UA Server, for example, UINT32.
(See the table in OPC UA Server Data Types to DCI Block Type Mapping, page
72).

Multiple Publish Intervals for Same Namespace URI

Configure separate group for each publish interval, and link Points/Nodes to the
corresponding group.
Group Configuration:

Point Configuration:

The number of subscriptions created by OPC UA Client Driver depends on Publish

Interval. For example, in this figure, the Points/Nodes are configured with two different
publish intervals that is, 10 and 20. In this case the driver creates two subscriptions,
one with publish interval 10 and another with publish interval 20.
NOTE: The Maximum Subscriptions supported by OPC UA Client Driver is 9. If
the OPC UA Server supports less than 9 subscriptions, reduce the number of
publish intervals configured for subscription to match the OPC UA Server
limitation.

B0700WJ, Rev A 39
 Chapter 3: Configuring OPC UA Client Driver Using Control
FDC280 OPC UA Client Driver User’s Guide Software

Multiple Sample Intervals for Same Namespace URI and Publish Intervals
Configure a separate group for each sample interval, and link points/nodes to the
corresponding group.
Group Configuration:

Point Configuration:

Bulk Creation of Groups and I/O Point Aliases from a Spreadsheet

Groups and Points information can be generated efficiently by importing data from
spread sheet with the format in sample excel file into CS configurator using CS Bulk
Data Editor. Perform these steps for generating Groups and Points information using
Bulk Data Editor tool of the CS:
1. Open the sample OPC UA_Config.XLS file located in the path: D:\Program
Files \ArchestrA\Framework\Bin\Invensys\FDC Drivers\OPCUA
Client/OPCUA_ Client_1.0\.
2. Configure only these parameters for Groups and I/O Points Aliases:
• Group Name or Point Name – For GroupName: Any unique alphanumeric
name for the group. Point Name: Specify the PNT_NO of the DCI block the
PNT_NO should be of format PNTNO:IdentifierType
• Point Name – Specify the PNT_NO of the DCI block the PNT_NO should be
of format PNTNO:IdentifierType
• Item Type – Specify the type is Group or Point
• Device Name – Leave the field blank
• Publish Interval – Specify the Publish interval (in 100 milliseconds
resolution), for Example: 10
• Namespace URI – Specify the Namespace URI, for example, URI=http://
opcfoundation.org/UA/
• Namespace URI 2 – When the Namespace URI is greater than 64
characters, enter the first 64 characters in the Namespace URI and
remaining characters in Namespace URI 2
• Sampling Interval – Configure Sample Interval (in 100 milliseconds
resolution), for Example: SI=10
• Point/Node Identifier – Node in the OPC UA Server address space is called
as name or ID of the point in the OPC UA Server
• Group Name – Specify the Group Name (only for the Point)
• Data Type of Node – Specify the data type of point in the OPC UA Server

40 B0700WJ, Rev A
Chapter 3: Configuring OPC UA Client Driver Using Control
Software FDC280 OPC UA Client Driver User’s Guide

3. Save the file.

4. Expand InFusion Support in the Template Toolbox to display the base template
($BulkData) and the objects already derived from it.
5. Right-click $BulkData and select New > Derived Template.
6. The newly created object appears in the InFusion Support folder (and in the
Derivation View) with a default name consisting of a number appended to the
base template name, such as $BulkData_003. The name is enclosed in an edit
box in the Template Toolbox indicating that you can change the name to
something that better represents the data to be contained in the object.

B0700WJ, Rev A 41
 Chapter 3: Configuring OPC UA Client Driver Using Control
FDC280 OPC UA Client Driver User’s Guide Software

7. Select the Hardware tab and in Hardware Components select FDC Data. Click
Import.
The Import Bulk Data Wizard appears

8. Select the input source as Excel Spreadsheet (*.xls, *.xlsx) (HW only), select the
file name as OPC UA_Config.xlsx, enter the sheet Name as FDC280 and select
the option Clear all Hardware Tables before Importing.
9. Click Next until the Map FDC data Wizard (step 9 of 9) window appears.

Perform Mappings as shown in the Mappings field shown in the FDC Data
Wizard.

42 B0700WJ, Rev A
Chapter 3: Configuring OPC UA Client Driver Using Control
Software FDC280 OPC UA Client Driver User’s Guide

10. Click Finish.

This dialog box appears.

11. Click Don’t Save.

The bulk data appears with Groups and Points information.

12. From the Hardware Components menu, select Modules and enter the Module
of the Device Identifier, select the type as FDC_Device from the Menu, select the
driver from the list for which this Module belongs to in Parent option.

13. Save the configuration. From the Hardware Components menu, select FDC
Data.

14. From the Device option, select the Device identifier for all the Groups and Points.

B0700WJ, Rev A 43
 Chapter 3: Configuring OPC UA Client Driver Using Control
FDC280 OPC UA Client Driver User’s Guide Software

15. Click Generate.

The Bulk Generation Wizard appears.

16. Select the Modules [Tag Name] and click the Generate option.
After successful generation, the groups and points appear in Groups tab and I/O
Point Aliases tab of Device object as shown:

Set up the device’s I/O connections. See Block Configurator User's Guide
(B0750AH) and Strategy Editor User's Guide (B0750AN).

Configure and Deploy DCI Blocks

• Configure compounds, strategies, and DCI blocks manually as discussed in the
Block Configurator User's Guide (B0750AH). Connect these other blocks to the
device as discussed in “Other Field I/O Connection Methods” in B0750AH.
• The Compounds, strategies and DCI blocks can be configured using bulk data
editor.

44 B0700WJ, Rev A
Chapter 3: Configuring OPC UA Client Driver Using Control
Software FDC280 OPC UA Client Driver User’s Guide

Bulk Creation of DCI Block Configuration of I/O points from a Spreadsheet File with OPC
UA Server Tags
DCI block configuration of I/O points can be generated efficiently by importing the tags
spread sheet with the format in sample excel file into CS configurator using CS Bulk
Data Editor. Perform these steps for generating Compounds and strategies using Bulk
Data Editor tool of the CS:
1. Open the sample OPC UA_Config.xlsx file located in the path: C:\program
files (x86)\schneider-electric\FDC280\OPCUA\.
2. Configure these parameters for the “ItemType (Group or Point)” is of type Point:
• Name: Name of the DCI block
• Strategy: Name of the strategy
• Type: Type of the DCI block (BIN, RIN, STRIN, PAKIN, IOUT), should be
prefix with $. For Example $IIN
• Base: Type of the DCI block. Example IIN
• Compound: Name of the compound
• PNT_NO: Any unique alphanumeric name for the group.
• Point Name: Specify the PNT_NO of the DCI block. The PNT_NO should be
of format PNTNO:IdentiferType and should be the same as in Group Name
or Point Name field.

3. Save the file.

4. Expand InFusion Support in the Template Toolbox to display the base template
($BulkData) and the objects already derived from it.
5. Right-click $BulkData and select New > Derived Template.
6. The newly created object appears in the InFusion Support folder (and in the
Derivation View) with a default name consisting of a number appended to the
base template name, such as $BulkData_001. The name is enclosed in an edit
box in the Template Toolbox indicating that you can change the name to
something that better represents the data to be contained in the object.

B0700WJ, Rev A 45
 Chapter 3: Configuring OPC UA Client Driver Using Control
FDC280 OPC UA Client Driver User’s Guide Software

7. Select the Control tab and in Control Components, select Blocks. Click
Import. The Import Bulk Data Wizard window appears.

8. Select the input source type Excel Spreadsheet (*.xls, *.xlsx) (Control only),
select the File Name as OPC UA_Config.xlsx, enter the sheet Name as FDC280,
select Clear all Control Tables before Importing, and click Next. The Define
Data page appears.

46 B0700WJ, Rev A
Chapter 3: Configuring OPC UA Client Driver Using Control
Software FDC280 OPC UA Client Driver User’s Guide

9. Click Next. The Map Compound Data page appears.

10. Map Compound > Compound as shown in the wizard and click Next. The Map
Strategy Data page appears.

B0700WJ, Rev A 47
 Chapter 3: Configuring OPC UA Client Driver Using Control
FDC280 OPC UA Client Driver User’s Guide Software

11. In Map Strategy Data Wizard, map Strategy to Strategy and Compound to
Compound. Click Next. The Map Block Data page appears.

12. In Map Block Data Wizard screen, map Name to Block, Strategy to Strategy,
Type to Type, Base to Base, Compound to Compound.
13. For PNT_NO, select from Map Imported Column and click Add & Map as
shown in the image.
14. Click Next. The Map Strategy Input/Output Data page appears.

Map Strategy to Strategy and Compound to Compound as shown in the

image.

48 B0700WJ, Rev A
Chapter 3: Configuring OPC UA Client Driver Using Control
Software FDC280 OPC UA Client Driver User’s Guide

15. Click Finish. The Save Mapping window appears:

16. Click Don’t Save.

The bulk data editor displays the Compounds and Strategies information.

17. Select the Device identifier from the menu in IOM_ID field..

B0700WJ, Rev A 49
 Chapter 3: Configuring OPC UA Client Driver Using Control
FDC280 OPC UA Client Driver User’s Guide Software

18. Select compounds from Control Components menu, select the CP name from
the menu, save the changes, and click Generate. The Bulk Generation Wizard
window appears:

19. Select the CPs for control Generation and click Next. The Compound Selection
page appears.

50 B0700WJ, Rev A
Chapter 3: Configuring OPC UA Client Driver Using Control
Software FDC280 OPC UA Client Driver User’s Guide

20. Select the compound Instances to Generate and click Next. The Strategy
Selection page appears.

21. Select the Strategy Instances to Generate and click Next.

22. Click Next until the Map Block Data page appears.

23. Click the Generate option in the Map Block Data page. After successful
generation, the Compounds and Strategies are created.
Deploy the control configuration as discussed in Control Database Deployment
User's Guide (B0750AJ) and System Manager (B0750AP).

B0700WJ, Rev A 51
FDC280 OPC UA Client Driver User’s Guide Chapter 4: Configuring OPC UA Client Driver Using CCS

Chapter 4: Configuring OPC UA Client Driver Using

CCS
Preliminary Considerations
If any of these criteria are true, do not use Control Core Services. Instead use the CS
for Configuration. See Chapter 3: Configuring OPC UA Client Driver Using Control
Software, page 25.
• Identifier is greater than 31 characters
• Points/Nodes are case sensitive
• Requires more than one subscription (Configuring different values for options
such Publish Interval for a single Namespace URI)
• Driver must access Points/Nodes from Multiple Namespace URIs in OPC UA
Server
• Security policy and message security mode are set with an option other than
“None”.

Overview of Configuration
After you have installed the software, you need to configure the FDC280 Ethernet port
as well as create Equipment Control Blocks (ECBs) and connection blocks that define
the devices and data accessed through the OPC UA Client Driver.
To configure the OPC UA Client Driver, you must configure these items:
• FDC280 I/O Ethernet port
• Driver ECB200
• Device ECB201 for each OPC UA Server
• Group for configuring Security Policy and Message Security Mode as None.
• DCI blocks that map to Points/Nodes in the OPC UA Server
Ethernet port connections are configured in ICC with the CCS FDC280 Configurator.
For configuration of these objects, follow the general instructions in the Field Device
Controller 280 (FDC280) User's Guide (B0700GQ). This document provides
configuration instructions that are specific only to the OPC UA Client Driver.
To be operational, the system ECBs must be online and in a good state. System
Management controls the ONLINE/OFFLINE status. For the OPC UA Server
controller to communicate with the OPC UA Client Driver, the Driver ECB200 and the
Device ECB201s must be online.

Configuring an ECB200 Block

For each OPC UA Client Driver, you must configure an ECB200 block. For information
on how to configure the ECB200 block, see the Field Device Controller 280 (FDC280)
User’s Guide (B0700GQ).

Table 17 - ECB200 Configuration

Parameter Value Definition

NAME * Name the block
TYPE ECB200 Type of block

52 B0700WJ, Rev A
Chapter 4: Configuring OPC UA Client Driver Using CCS FDC280 OPC UA Client Driver User’s Guide

Table 17 - ECB200 Configuration (Continued)

Parameter Value Definition

DEV_ID * Device ID
HWTYPE 1 Hardware Type for
FDC280
SWTYPE 200 Software type for FDC280
PARENT ENETPORT PORT
1 1
Block name of parent
Primary ECB
DRVRID 7 Driver ID for OPC UA 1.0
CPARM1-3 * N/A

Configuring an ECB201 Block

For each OPC UA Server to be connected, configure an ECB201 block. For
information on how to configure an ECB201 block, see the Field Device Controller 280
(FDC280) User’s Guide (B0700GQ).

Table 18 - ECB201 Configuration

Parameter Value Definition

NAME * Name the block
TYPE ECB201 Type of block
DEV_ID * Device ID
HWTYPE 1 Hardware Type for FDC280
SWTYPE 200 Software type for FDC280
PARENT * Compound Name: Block
Name of parent ECB200
DVNAME * Server IP address: Port Number
Example:
192.168.1.10:48010
The IP Address and Port number of OPC UA Server
must be configured, or the device is marked as INVALID
and an appropriate Smon_log message is logged.
Using the configured IP Address and Port No the OPC
UA Client Driver creates OPC UA Server Endpoint URL
of Binary protocol. The format is ‘opc.tcp://IPAddress:
PortNo’
An OPC UA Server Endpoint URL is a physical address
available on a network that allows OPC UA Client Driver
to access one or more services provided by an OPC UA
Server.
DVOPTS * See Configuring the Device Options Parameter, page
30.

B0700WJ, Rev A 53
FDC280 OPC UA Client Driver User’s Guide Chapter 4: Configuring OPC UA Client Driver Using CCS

Adding a Group for Configuring Security Policy and Message

Security Mode as None
1. Set the ECB200 to the online state.
2. Open the CCS FDC280 Configurator and choose an FDC280 from the list.

3. In the navigation pane, select ECB201 Dev1 that is configured as a child of the
OPCUA Driver ECB200 DRVR01.

4. Click Add Group and enter these details:

Table 19 - Group Details

Field Description
Group Name Enter SecGroup.
Scan Rate Leave blank.
Phase Leave blank.
Custom Parameter 1 Configure security policy (SP=) and
message security modes (+MSM=) as
None. Example: SP=0+MSM=0.
Custom Parameter 2 Leave blank.
Custom Parameter 3 Leave blank.
Custom Parameter 4 Leave blank.

5. Click Deploy to download the configuration to the FDC280.

54 B0700WJ, Rev A
Chapter 5: Principles of Operation FDC280 OPC UA Client Driver User’s Guide

Chapter 5: Principles of Operation

After you configure the appropriate DCI blocks and ECBs as described in Field Device
Controller 280 (FDC280) User's Guide (B0700GQ), enable device communication in
the Foxboro System Manager. The OPC UA Client Driver sends publish request
messages to the OPC UA Server. The FDC280 waits for responses from the OPC UA
Server, processes the responses, and updates DCI blocks mapped to the OPC UA
Points/Nodes.
For a description of the operation of fault-tolerant FDC280s interfacing to an OPC UA
Server using redundant connections, see the Field Device Controller 280 (FDC280)
User's Guide (B0700GQ).

OPC UA Client Driver Operation

An OPC UA Client Driver represents a connection to one specific OPC UA Server. A
device ECB201 represents OPC UA Server. However, the device ECB201 does not
have to represent a specific physical device such as a PLC. It can represent one
connection to an OPC UA Server and connections to multiple Namespace URI (and
multiple Points/Nodes) in the OPC UA Server. The DCI blocks represent the individual
Points/Nodes. Each Points/Nodes is associated with an ECB201 via the DCI blocks
IOM_ID parameter.
NOTE: OPC UA Client Driver subscribes to all the DCI blocks except the blocks
configured with Write Only Option (‘:NR’ in PNT_NO parameter of DCI blocks).
Configuring Groups and Points is required in the OPC UA Client Driver if any of these
criteria apply:
NOTE: The CCS configurator can be used for configuring DCI blocks, for a simple
configuration where none of these criteria are met.
• Identifier (point name in the OPC UA Server) is greater than 31 characters.
• Identifier names are case sensitive.
• Requires more than one subscription (Configuring different values for options
such Publish Interval, Sampling Interval for a single Namespace URI).
• Driver must access Points/Nodes from Multiple Namespace URIs in OPC UA
Server.
• Security policy and message security mode are set with an option other than
None.

Redundant Operation
The fault-tolerant version of the FDC280 consists of two modules (primary and
shadow) operating in parallel, with redundant connections to the control network. Both
modules communicate with the OPC UA Server and receive and process information
simultaneously, but only the Primary Module performs writes to OPC UA Server.
During every BPC, the value and status of all I/O points are copied from the Primary
FDC280 to the Shadow FDC280 so that when a role switch occurs, the point value
and status is preserved. When a role switch takes place, the Shadow FDC280 is in
position to take over as the new Primary because it already has all the required
configuration information, including current input/output data values, and it is
communicating with the same OPC UA Server.
On every BPC, the connections status of the device (OPC UA Server) on the Shadow
FDC280 is monitored by the Primary FDC280 and the device status reported to the
System Manager is updated. A device with “good” connection status with both the
modules is marked “good”. If connection status is good (it appears white in the System
Manager) from the Primary FDC280 and unavailable/bad from the Shadow FDC280,

B0700WJ, Rev A 55
FDC280 OPC UA Client Driver User’s Guide Chapter 5: Principles of Operation

the device status is set to yellow condition and an alarm is raised. If the device
connection is unavailable or bad from both the FDC280s, the device is marked
unavailable (red) and an alarm is raised.
The Primary FDC280 constantly runs a redundancy algorithm to verify if a switchover
to the Shadow module is required in case of loss of link to the I/O Ethernet network or
loss of connection to OPC UA Server.
If the loss of a link to the customer-supplied Ethernet I/O network is detected via the
Primary FDC280, the redundancy algorithm running on the Primary FDC280 affects
an automatic role switch, with the Primary FDC280 rebooting to become a Shadow
module and Shadow FDC280 switching to the role of Primary module.
If the Primary FDC280 loses connection to the OPC UA Server and Shadow FDC280
is having good connection with OPC UA Server, the primary initiates the role switch to
complete the failover.
The Equipment Information pages in the System Manager indicate Primary and
Shadow connection status for OPC UA Server. If the ECB display as yellow, you can
use these displays to determine which side of the connection has stopped working.
For example, if the device ECB is yellow and the ECB201 display shows the status
“Left active, Right failed”, it implies that the FDC280 is acquiring data from the device
through the Ethernet I/O network connected to the left Ethernet I/O port on the
baseplate, and that the left FDC280 is the Primary module. If the device ECB is shown
as red and the ECB201 display shows the status “Left active, Right failed”, this implies
that the FDC280 is acquiring data from the OPC UA Server through the left Ethernet I/
O port on the baseplate, and that the right FDC280 is the Primary module.

ECB201 Operation for Certificate Data

This ECB201 is mandatory when both security policy and message security mode are
set with an option other than None.
Verify that the Driver ECB200 is in online state and run OPCUACertGen.bat script file,
to create ECB201 for certificate and deploy its configuration to CS. For more
information, see Configuring a Device ECB (ECB201) for Self-signed Certificate, page
26.

ECB201 Operation for Connection to an OPC UA Server

This ECB201 is used to define the connection to an OPC UA server/URI. Because the
ECB201’s initial state is unavailable, the ECB must be enabled before communication
can take place with a connected OPC UA Server. To enable the device, click the
ENABLE COMMUNICATIONS field in the ECB201 Equipment Change action display.
After the DCI blocks are entered and device communication is enabled in the System
Manager, the OPC UA Client Driver creates a transport connection by sending the first
message as “Hello”. This specifies the buffer sizes that the client supports. The OPC
UA Server responds with an “Acknowledge” message. This completes the buffer
negotiation.
Subsequently, the OPC UA Client Driver sends the “OpenSecureChannel Request”. it
receives the “OpenSecureChannel Response” from the OPC UA Server, the OPC UA
Client driver sends a GetEndpoints request to the OPC UA Server, the OPC UA
Server returns a list security policies, including the security configuration as well as its
certificate (including the server’s public key).

56 B0700WJ, Rev A
Chapter 5: Principles of Operation FDC280 OPC UA Client Driver User’s Guide

Follow this procedure when the Security policy and Message security Modes are
configured with any option other than None.
1. The OPC UA Client driver checks if the Security policy configured for the Client
exists in the list of Security modes and policies received from the Server. If
Security policy and message security mode configured in Security Group
(SecGroup) is not supported by the OPC UA Server, the driver displays the error
message in smon_log and marks the device to failed state.
2. If the configured security policy and message security mode is supported by the
OPC UA server, OPC UA Client driver trusts the server certificate and stores it in
trusted folder in the FDC280. The OPC UA Client driver attempts to create a
secure channel with the server, sending along its Self- Signed Certificate
(including the public key).

The server accepts the secure channel connection only if the Client certificate is
in its Trusted list. The server administrator reviews the certificate and manually
moves it to the Trusted list at the Server.
The server administrator reviews the thumbprint information of “thumbprint.txt” file
available in the FDC hosting station path C:\ProgramData\Schneider
Electric \OPCUAClientCertGen for inclusion in Trusted list. This image
shows an example.

B0700WJ, Rev A 57
FDC280 OPC UA Client Driver User’s Guide Chapter 5: Principles of Operation

The server administrator reviews the FDC280 letterbug information in the client
certificate for inclusion in Trusted list. This image shows an example.

58 B0700WJ, Rev A
Chapter 5: Principles of Operation FDC280 OPC UA Client Driver User’s Guide

The connection is successful once the OPC UA server administrator trusts the
OPC UA Client Driver certificate (part of Trusted list).

3. Once the Server Administrator validates the certificate and moves it to trust list,
the OPCUA Client Driver receives the success message. Next, the driver initiates
the create session request followed by the activate session with the configured
usertoken ID.
The OPC UA Client Driver sends the read service to obtain the OPC UA Server
namespace table. The driver compares the Namespace URI configured in the
Custom Parameter 2 and Custom Parameter 3 of the Control Editor Groups tab
or DVOPTS and updates the Namespace indexes accordingly. Next, the OPC UA
Client Driver creates the subscription request with publish interval and
MonitoredItems (Points/ Nodes). On successful subscription response, the OPC
UA Client driver sends the Publish Request. On receiving a response from the
OPC UA Server, the OPC UA Client driver updates the DCI blocks mapped to the
I/O points.
If PNT_NO of DCI blocks is configured as Write Only option, the driver does not
subscribe for these points in OPC UA Server.
This image shows an example of the sequence of messages between FDC280
OPC UA Client and OPC UA Server.

B0700WJ, Rev A 59
FDC280 OPC UA Client Driver User’s Guide Chapter 5: Principles of Operation

Figure 3 - Sample Sequence of Messages between FDC280 and the OPC UA

Server

Configuring DCI Blocks for OPC UA Points/Nodes

The Point/Node can be entered in the PNT_NO parameter of the DCI block.
• Namespace URI: The namespace URI identifies the naming authority defining
the identifiers of Points/Nodes, e.g. the OPC Foundation, other standard bodies
and consortia, the underlying system, the local OPC UA Server. They are stored
in the so-called namespace array (also referred to as namespace table).
Namespace indexes are numeric values used to identify namespaces to optimize
transfer and processing. The namespace index is the index of the namespace
URI in the Server_NamespaceArray.
• IdentifierType: The format and data type of the identifier. It can be a numeric
value, a string, a globally unique identifier (GUID), or an opaque value (a
namespace specific format in a ByteString).
• Identifier: The identifier for a node in the address space of an OPC UA Server.
For example:
◦ Namespace URI: “http://www.ua.com/OPC UAServer/”
◦ Identifier Type: Numeric

60 B0700WJ, Rev A
Chapter 5: Principles of Operation FDC280 OPC UA Client Driver User’s Guide

◦ Identifier: 21000

Table 20 - Point/Node Parameter Identifier Types

Identifier Type Identifier PNT_NO for DCI Description

BLOCK
NUMERIC 21000 21000:N Numeric value
STRING My_Temperature My_Temperature: String value
S
Static.Scalar. Static.Scalar. DateTime value
DateTime DateTime: S
GUID 5ce9dbce-5d79- 5ce9dbce-5d79- Globally Unique
434c-9ac3- 434c-9ac3- Identifier
1cfba9a6e92c 1cfba9a6e92:G
OPAQUE YWJjZA== YWJjZA==:O Namespace
specific format

To configure DCI block as described in the table, configure PNT_NO= 21000:N

(where N is Identifier type Numeric) and specify namespace Uri in DVOPTS field of
ECB201. This configuration is supported only if the driver has to access Points/Nodes
from a single Namespace URI in OPC UA Server, the Identifier is less than 31
characters, not case sensitive in OPC UA Server and requires single publish interval
for all the Points/Nodes.
Example of DCI block mapping with Point/Node in OPC UA server:

Table 21 - DCI Block Mapping with Point/Node

DCI Block DCI Block OPC UA OPC UA Description

Parameters Value Server Value
Parameters
NAME * N/A N/A Block name of
the point
Block Type IIN DataType Int16 IIN Block
mapped to
Int16 Data
Type of OPC
UA Server
IOM_ID # N/A N/A The name of
the associated
ECB201
PNT_NO 20001:N Identifier 20001 20001
represents
'Identifier' for
Point/Node in
OPC UA
Server
Address
space
N/A N/A Identifier Type Numeric :N represents
'Identifier
Type' Numeric
for Point/Node
in OPC UA
Server
Address
space

B0700WJ, Rev A 61
FDC280 OPC UA Client Driver User’s Guide Chapter 5: Principles of Operation

To configure DCI block as described in the table, configure PNT_NO= 21000:N

(where N is Identifier type Numeric) and specify namespace Uri in DVOPTS field of
ECB201. This configuration is supported only if the Driver has to access Points/Nodes
from a single Namespace URI in OPC UA Server, the Identifier is less than 31
characters, not case sensitive in OPC UA Server and requires single publish interval
for all the Points/Nodes.
Example of DCI block mapping with Point/Node of DateTime Datatype in OPC UA
Server:

Table 22 - DCI Block Mapping with Point/Node DateTime Datatype

DCI Block DCI Block OPC UA OPC UA Description

Parameters Value Server Value
Parameters
NAME * N/A N/A Block name of
the point
Block Type STRIN DataType DateTime STRING Block
mapped to
DateTime
Data Type of
OPC UA
Server
IOM_ID # N/A N/A The name of
the associated
ECB201
PNT_NO 20001:N Identifier 20001 20001
represents
'Identifier' for
Point/Node in
OPC UA
Server
Address
space
N/A N/A Identifier Type STRING :S represents
'Identifier
Type' STRING
for Point/Node
in OPC UA
Server
Address
space

Configuring Additional Block Types

The block types that the FDC280 supports are discussed here as well as their
parameter configurations.

BOUT – Binary Output Block

Block parameters of the BOUT block can be set as:

62 B0700WJ, Rev A
Chapter 5: Principles of Operation FDC280 OPC UA Client Driver User’s Guide

Table 23 - BOUT Block

Parameter Name Setting Description

NAME * Block name of the point
Block Type BOUT Defines the block as a single
binary output block
IOM_ID * The name of the associated
ECB201
PNT_NO * Point/Node of the OPC UA
Server address space as
described in Configuring DCI
Blocks for OPC UA Points/
Nodes, page 60.

PAKOUT – Packed Output Block

Block parameters of the PAKOUT block can be set as:

Table 24 - Pakout Block

Parameter Name Setting Description

NAME * Block name of the point
Block Type PAKOUT Defines the block as a packed
boolean output block
IOM_ID * The name of the associated
ECB201
PKCOGP * Point/Node of the OPC UA
Server address space as
described in Configuring DCI
Blocks for OPC UA Points/
Nodes, page 60.

IOUT – Integer Output Block

Block parameters of the IOUT block can be set as:

Table 25 - IOUT Block

Parameter Name Setting Description

NAME * Block name of the point
Block Type IOUT Defines the block as an integer
output block
IOM_ID * The name of the associated
ECB201
PNT_NO * Point/Node of the OPC UA
Server address space as
described in Configuring DCI
Blocks for OPC UA Points/
Nodes, page 60.

B0700WJ, Rev A 63
FDC280 OPC UA Client Driver User’s Guide Chapter 5: Principles of Operation

ROUT – Real Output Block

Block parameters of the ROUT block can be set as:

Table 26 - ROUT Block

Parameter Name Setting Description

NAME * Block name of the point
Block Type ROUT Defines the block as a single real
output block
IOM_ID * The name of the associated
ECB201
PNT_NO * Point/Node of the OPC UA
Server address space as
described in Configuring DCI
Blocks for OPC UA Points/
Nodes, page 60
HSCO1 * The maximum value that the
point can have
LSCO1 * The minimum value that the point
can have

BIN/BINR – Binary Input and Redundant Binary Input Blocks

Block parameters of the BIN and BINR blocks can be set as:

Table 27 - RIN Block

Parameter Name Setting Description

NAME * Block name of the point
Block Type BIN(R) Defines the block as a single
(BIN) or redundant (BINR) binary
input block
IOM_ID * The name of the associated
ECB201
PNT_NO (BIN) * Point/Node of the OPC UA
Server address space as
BI1_PT (BINR) described in Configuring DCI
Blocks for OPC UA Points/
BI2_PT (BINR)
Nodes, page 60.

IIN/IINR – Integer Input Block

Block parameters of the IIN block can be set as:

Table 28 - IIN Block

Parameter Name Setting Description

NAME * Block name of the point
Block Type IIN Defines the block as an integer
input block

64 B0700WJ, Rev A
Chapter 5: Principles of Operation FDC280 OPC UA Client Driver User’s Guide

Table 28 - IIN Block (Continued)

Parameter Name Setting Description

IOM_ID * The name of the associated
ECB201
PNT_NO (IIN) * Point/Node of a tag in the OPC
UA Server address space as
II1_PT (IINR) described in Configuring DCI
Blocks for OPC UA Points/
II2_PT (IINR)
Nodes, page 60.

RIN/RINR – Real Input and Redundant Real Input Blocks

Block parameters of the RIN and RINR blocks can be set as:

Table 29 - IIN Block

Parameter Name Setting Description

NAME * Block name of the point
Block Type RIN(R) Defines the block as a single
(RIN) or redundant (RINR) binary
input block
IOM_ID * The name of the associated
ECB201
PNT_NO (RIN) * Point/Node of the OPC UA
Server address space as
RI1_PT (RINR) described in Configuring DCI
Blocks for OPC UA Points/
RI2_PT (RINR)
Nodes, page 60.

PAKIN/PAKINR – Packed Input Block

Block parameters of the PAKIN block can be set as:

Table 30 - PAKIN Block

Parameter Name Setting Description

NAME * Block name of the point
Block Type PAKIN Defines the block as a packed
boolean input block
IOM_ID * The name of the associated
ECB201
PKINGP (PAKIN) * Point/Node of a tag in the OPC
UA Server address space as
PK1_PT(PAKINR) described in Configuring DCI
Blocks for OPC UA Points/
PK2_PT (PAKINR)
Nodes, page 60.

B0700WJ, Rev A 65
FDC280 OPC UA Client Driver User’s Guide Chapter 5: Principles of Operation

STRIN – String Input Block

Block parameters of the STRIN block can be set as:

Table 31 - STRIN Block

Parameter Name Setting Description

NAME * Block name of the point
Block Type STRIN Defines the block as a pulse
output block
IOM_ID * The name of the associated
ECB201
PNT_NO * Point/Node of the OPC UA
Server address space as
described in Configuring DCI
Blocks for OPC UA Points/
Nodes, page 60.

Diagnostic Data
Create DCI blocks to get the timestamp diagnostic information at the device level.
The available diagnostic blocks are:
• Reset counters
• Bad Timestamp Points
• Response timeout counter
• Last detected error message

Reset Counters
All counter blocks are reset to zero when you toggle the value in this block.

Table 32 - RESET Counters

Parameter Name Setting Description

NAME * Block name of the point
Block Type BOUT Defines the block as a boolean
output block
IOM_ID * The name of the associated
ECB201
PNT_NO * FDC280 Single: $L_ RESET_
CNTRS
FDC280 fault-tolerant: $L_
RESET_CNTRS $R_ RESET_
CNTRS
Prefix ‘$L’ corresponds to counter
value on the FDC280 installed in
the left baseplate slot, while the
prefix ‘$R’ corresponds to counter
value on the FDC280 installed in
the right baseplate slot

66 B0700WJ, Rev A
Chapter 5: Principles of Operation FDC280 OPC UA Client Driver User’s Guide

Bad Timestamp Points

You can monitor the total number of points that have bad timestamp under the device.
When the FDC receives a bad stamp for a point, the DCI block status is set to “bad”
and an alarm is generated. In addition, you can monitor the total number of such
points by configuring “Total Number of Bad Timestamp points”.

Table 33 - Bad Timestamp Points

Parameter Name Setting Description

NAME * Block name of the point
Block Type IIN Defines the block as an Integer
input block
IOM_ID * The name of the associated
ECB201
PNT_NO * FDC280 Single: $L_MISC1_
ERRS
FDC280 fault-tolerant: $L_
MISC1_ERRS
$R_MISC1_ERRS
Prefix ‘$L’ corresponds to counter
value on the FDC280 installed in
the left baseplate slot, while ‘$R’
corresponds to counter value on
the FDC280 installed in the right
baseplate slot.

Response Timeout Counter

You can monitor the number of response timeouts, that is, service call (such as
channel, session, read, write, subscribe, monitored items, publish) is sent but no reply
received by OPC UA Client Driver. The value that appears in this block is updated
ONLY for the block corresponding to the current master Primary FDC280 module. In
other words, when the Left FDC280 module is running as Primary, the “$L” block is
updated, and when the Right FDC280 module is running as Primary, the “$R” block is
updated.

Table 34 - Response Timeout Counter

Parameter Name Setting Description

NAME * Block name of the point
Block Type IIN Defines the block as an Integer
input block

B0700WJ, Rev A 67
FDC280 OPC UA Client Driver User’s Guide Chapter 5: Principles of Operation

Table 34 - Response Timeout Counter (Continued)

Parameter Name Setting Description

IOM_ID * The name of the associated
ECB201
PNT_NO * FDC280 Single: $L_RESP_
TIMEOUTS
FDC280 fault-tolerant:
$L_RESP_TIMEOUTS
$R_RESP_TIMEOUTS
Prefix ‘$L’ corresponds to counter
value on the FDC280 installed in
the left baseplate slot, while ‘$R’
corresponds to counter value on
the FDC280 installed in the right
baseplate slot.

Last Detected Error Message

The exception code and short text description of the last detected error received for
OPC UA Server; the details of the exceptions are described in Chapter 6: System
Messages, page 77.

Table 35 - Last Detected Error Message

Parameter Name Setting Description

NAME * Block name of the point
Block Type STRIN Defines the block as a string input
block
IOM_ID * The name of the associated
ECB201
PNT_NO * FDC280 Single: $L_LAST_ERR_
MSG
FDC280 fault-tolerant: $L_LAST_
ERR_MSG
$R_LAST_ERR_MSG
Prefix ‘$L’ corresponds to counter
value on the FDC280 installed in
the left baseplate slot, while the
prefix ‘$R’ corresponds to counter
value on the FDC280 installed in
the right baseplate slot

Support of Arrays
The OPC UA Client Driver allows accessing an element of a single dimensional array
for read, write, and subscribe operations.
The supported data types of the elements are described in the table in OPC UA
Server Data Types to DCI Block Type Mapping, page 72.

68 B0700WJ, Rev A
Chapter 5: Principles of Operation FDC280 OPC UA Client Driver User’s Guide

To access the array data in OPCUA Server, each element of the array needs to be
mapped to a single DCI block. The format of PNT_NO parameter to access an array
element is: Point/Node[index] where index is Zero based.
To access the third element of array ‘MyArray’, configure the DCI block as shown in
the table.

Table 36 - DCI Block Configuration for Third Element of MyArray

DCI Block DCI Block OPC UA OPC UA Description

Parameters Value Server Value
Parameters
NAME * N/A N/A Block name of
the point
Block name of IIN DataType Int32 IIN Block
the point mapped to
Int32 array
date type of
OPC UA
Server
IOM_ID # N/A N/A The name of
the associated
ECB201
PNT_NO MyArray[2]:S Identifier Type String S represents
'Identifier
Type' String
for Point/Node
in OPC UA
Server
Address
space.
N/A N/A Identifier Demo.Static. Demo.Static.
Arrays.Int32 Arrays.Int32 is
a single
dimensional
array of type
integer

Here is an example of accessing the third element of ‘MyArray’ in DCI block using
Groups and Points Tab in Control Editor:
Group Tab Configuration:
• Group Name – Any unique alphanumeric name for the group, for example,
“Group1”
• Scan Rate – Specify the Publish interval (in 100 milliseconds resolution), for
example,, 10
• Phase – Leave the field blank
• Custom Parameter 1 – Configure Sample Interval (in 100 milliseconds
resolution), for example, SI=10
• Custom Parameter 2 – Specify the Namespace URI, for example, URI=http://
opcfoundation.org/UA/

B0700WJ, Rev A 69
FDC280 OPC UA Client Driver User’s Guide Chapter 5: Principles of Operation

Point Tab Configuration:

• Name – It is the PNT_NO parameter of the associated DCI block. This is also
what you see in the HMI. It is an alias name of the point in the OPC UA Server. It
should be of the format Alias Name:x, where “x “is the data type of real name of
the point in the OPC UA Server in the Address column. The various options for
“X” are listed in the first table in Configuring DCI Blocks for OPC UA Points/
Nodes, page 60. The Alias Name length must not exceed 32 characters. For
example, NODE1:N
• Address - Name or ID of the point in the OPC UA Server, for example, Demo.
static.Arrays.Int32
• Group – Select the Group Name for which this Point, for example, Group1
• DataType - Data type of the point in the OPC UA Server, for example, INT32.
(See the table in OPC UA Server Data Types to DCI Block Type Mapping, page
72).

Write-Only Points
You can specify that an individual output block is write-only. This specification instructs
the OPC UA Client Driver to not include it in the list of monitored points. This
modification is configured in each output block where write-only is desired.

Table 37 - Specifying “Write-Only” for DCI Output Blocks

Field Setting Description

PNT_NO Add “:NR” to any existing Adding this option causes
options the OPC UA Client Driver
to disable read requests
for this point.
NOTE: The colon (':')
is required when
specifying/adding a
point option.

Configuring output blocks as write-only stops the corresponding read-back for those
OPC UA Points/Nodes. When the number of these write-only output blocks is large,
the number of read messages is reduced.

DCI Input/Output Blocks – Data Types

For Input blocks (IIN, RIN, PAKIN, BIN) data conversions between the OPC UA
Server and the FDC280 is done automatically by the OPC UA Client Driver.
The operational behavior of the OPC UA Client Driver is such that if an IIN block (a
32-bit signed integer) is connected to a 16-bit OPC UA Server Point/Node, the OPC
UA Client Driver makes the conversion automatically. The same holds true for single
precision (32-bit float) RINs connecting to double precision reals in the OPC UA
Server.

70 B0700WJ, Rev A
Chapter 5: Principles of Operation FDC280 OPC UA Client Driver User’s Guide

The table in Output Blocks – Support Data Types, page 71 shows the DCI blocks and
the corresponding data types for the I/O points.
When configuring output blocks (IOUT, ROUT, PAKOUT) using CCS, the matching
OPC UA Server data type such as U2, S2, U4, or S4 must be specified along with
PNT_NO as shown in this table:

Table 38 - Example for U2 Option

Field Setting Description

PNT_NO Add “:U2” to any existing Adding this option causes
options the OPC UA Client Driver
to write the value of
corresponding output
block to the Point/Node of
type 2-byte unsigned
integer in OPC UA Server.
NOTE: The colon (':')
is required when
specifying/adding a
point option.

NOTE: When configuring output blocks (IOUT, ROUT, PAKOUT) using CS, the
matching OPC UA Server data type such as U2, S2, U4, or S4 is not required to
be specified along with PNT_NO as data type of each Point/Node of OPC UA
Server is specified in I/O Point Aliases tab of Control Editor.

Output Blocks – Support Data Types

The compatible data type connection options in the OPC UA Client Driver are:

Table 39 - Compatible Data Type Connection Options

DCI Block Default Data Compatible Data Ranges

Type Types
IOUT 32-bit signed S2 (2-byte signed -32768 to 32767
integer (S4) integer)
U2 (2-byte unsigned 0 to 65535
integer)
S4 (4-byte signed -2147483647 to
integer) +2147483646
U4 (4-byte unsigned 0 to 4294967295
integer)
ROUT 32-bit float 4-byte floating point N/A
value
PAKOUT 32-bit S2 (2-byte signed -32768 to 32767
Unsigned integer)
integer (U4)
U2 (2-byte unsigned 0 to 65535
integer)
S4 (4-byte signed -2147483647 to
integer) +2147483646
U4 (4-byte unsigned 0 to 4294967295
integer)

B0700WJ, Rev A 71
FDC280 OPC UA Client Driver User’s Guide Chapter 5: Principles of Operation

OPC UA Server Data Types to DCI Block Type Mapping

Table 40 - OPC UA Server Data Types to DCI Block Type Mapping

OPC UA Server Data DCI Block Data Type Comments

Type
16-bit signed integer 32-bit signed integer N/A
(INT16)
16-bit unsigned integer 32-bit signed integer N/A
(UINT16)
32-bit signed integer 32-bit signed integer N/A
(INT32)
32-bit unsigned integer 32-bit signed integer The range supported by
(UINT32) the IIN/IOUT block is
limited to 32 signed
integer. Even though a
IIN/IOUT block can
connect to a 32-bit
unsigned OPC UA Server
data type, the value must
be within the range
supported by the 32-bit
signed integer. If it is not
in that range, non-
deterministic results can
occur.
32-bit float 32-bit float N/A
64-bit float 32-bit float The range supported by
the RIN/ROUT block is
limited to 32 bits. Even
though a RIN/ROUT block
can connect to a 64-bit
float OPC UA Server data
type, the value must be
within the range
supported by the 32-bit
float. If it is not in that
range, non-deterministic
results can occur.
32-bit signed integer 32-bit unsigned integer N/A
(INT32)
32-bit unsigned integer 32-bit unsigned integer N/A
(UINT32)
16-bit signed integer 32-bit unsigned integer N/A
(INT16) (low 16 bits)
16-bit unsigned integer 32-bit unsigned integer N/A
(UINT16) (low 16 bits)
Single contact Boolean Single contact Boolean N/A
type (Boolean) type
Null terminated String String (80 characters, N/A
type including NULL)

72 B0700WJ, Rev A
Chapter 5: Principles of Operation FDC280 OPC UA Client Driver User’s Guide

Table 40 - OPC UA Server Data Types to DCI Block Type Mapping (Continued)

OPC UA Server Data DCI Block Data Type Comments

Type
DateTime String (80 characters, The OPC UA Server
including NULL) sends the DateTime in the
format of 64-Bit signed
integer, which represents
the number of 100
nanosecond intervals
since January 1, 1601
(UTC).
The OPC UA Client Driver
converts the nano
seconds interval to the
DateTime format:” YYYY-
MM-DDTHH:MM:SS.
MSECZ”.
GUID String (80 characters, N/A
including NULL)

OPC UA Value Status

OPC UA Server provides a status code associated with each input/output point. Each
value received from an OPC UA Server has its own status code associated with it. If a
point is declared “BAD” by the OPC UA Server, a “BAD” status is sent along with the
current value of the point.
The OPC UA Client Driver passes this “BAD” (or “GOOD”) status along to the host
control station with the value. In the Block Detail display, the value has the RED
background and the value record status field for that point is set BAD. OPC UA Client
Driver supports setting of OPC UA value status (Quality) for all the DCI blocks except
STRIN block.
Additionally, smon_log message is logged for error condition that is detected and
detailed information about this detected error appears in the FDC280 diagnostic tool.
The StatusCode is a 32-bit unsigned integer. The top 16 bits represent the numeric
value of the code that shall be used for detecting specific errors or conditions. The
bottom 16 bits are bit flags that contain additional information but do not affect the
meaning of the StatusCode.

Table 41 - OPC UA Value Status

OPC UA Value Value Returned Equivalent DCI Description

Status Returned by OPC UA Block Status
by Server Server
Good/Success 00 Good (White color Indicates the
in Background) operation is
successful
Uncertain / 01 Bad (Red color in Indicates that the
Warning Background) operation was
partially successful

B0700WJ, Rev A 73
FDC280 OPC UA Client Driver User’s Guide Chapter 5: Principles of Operation

Table 41 - OPC UA Value Status (Continued)

OPC UA Value Value Returned Equivalent DCI Description

Status Returned by OPC UA Block Status
by Server Server
Bad/ Failure 10 Bad (Red color in Indicates that the
Background) operation was not
successful.
Reserved 11 Bad (Red color in Reserved for
Background) future use, client
should treat it as
bad

Enabling Communication with the Server with OPC UA Security

Features
After configuring the database, follow these steps to interface with the OPC UA Client
Driver:
1. Set the Device ECB201 for Server communication to Enabled.
The OPC UA Driver sends its self-signed certificate (including the public key) to
the server.
The Driver displays this System Monitor Log (smon_log) message: Client
Certificate needs to be moved to trusted list, then the Device
ECB201 changes to a Failed state.
2. Compare thumbprint information from the FDC280 hosting station to the
thumbprint information from the certificate received by the FDC280:
a. Navigate to C:\ProgramData\Schneider Electric
\OPCUAClientCertGen, open thumbprint.txt.

b. Open the certificate received by the FDC280, then click Details >
Thumbprint.

74 B0700WJ, Rev A
Chapter 5: Principles of Operation FDC280 OPC UA Client Driver User’s Guide

c. Verify that the information in thumbprint.txt and in the certificate are the
same.

B0700WJ, Rev A 75
FDC280 OPC UA Client Driver User’s Guide Chapter 5: Principles of Operation

3. In the certificate, click Details > Subject Alternative Name, then verify that the
DNS Name value is the same as the FDC280 letterbug.

4. Move certificate to the trusted list on the server.

5. Change the compounds to the Online state.
6. Verify that all points are in a good state.

Enabling Communication to the Server without OPC UA Security

Features
After configuring the database, follow these steps to interface with the OPC UA Client
Driver:
1. Set the Device ECB201 communication to Enabled.
2. Change the compounds to the Online state.
3. Verify that all points are in a good state.

76 B0700WJ, Rev A
Chapter 6: System Messages FDC280 OPC UA Client Driver User’s Guide

Chapter 6: System Messages

The OPC UA Client Driver must wait for a response for each request it sends to the
OPC UA Server. If no reply is received or if a system message is received for the
configured timeout interval, the device state is changed to not successful and the
color changes from White to Red in System Manager.
The recommended wait time for replies is 10 seconds or 10000 milliseconds. To
change the wait time in milliseconds, modify the DVOPTS parameter of the ECB201
block by adding +TO=X, where X is the number of seconds to wait. For example, to
run the OPC UA Client Driver with an 11 seconds timeout, enter the syntax as:
DVOPTS= +TO=11
See Configuring the Device Options Parameter, page 30 for additional information.
Detected errors are logged in the smon_log. This table lists the detected system
messages, possible causes, and suggested corrective actions.

Table 42 - System Messages

LAST_ERR_MSG Smon_log Possible Problem Corrective Action

diagnostic block
BAD REQUEST “Timeout -No This message Verify that the
TIMEOUT Response from indicates that OPC UA Server is
OPC UA Server” either the OPC UA Up and running.
Server is Increase the
disconnected / configured timeout
OPC UA Server is interval in +TO
busy and not option.
responding to
services in the
configured time out
interval.
BAD SERVICE “The OPC UA This message Verify that the
UNSUPPORTED Server does not indicates that OPC OPC UA Server
support the UA Server does supports these
requested service- not support services:
xxx” services requested
• Read
by OPC UA Client
Driver. • Write
• Create
subscription
• Delete
Subscription
• Publish
• Republish
• Session
Create /
Session Open
• Anonymous
login
BAD TIMESTAMP “The OPC UA This message Remove the +VDT
NOTSUPPORTED Server does not indicates that OPC option from the
support request for UA Server DVOPTS
sending supports only parameter.
ServerTimestamp” SourceTimestamp
and not Verify with the
ServerTimestamp. OPC UA Server
vendor for

B0700WJ, Rev A 77
FDC280 OPC UA Client Driver User’s Guide Chapter 6: System Messages

Table 42 - System Messages (Continued)

LAST_ERR_MSG Smon_log Possible Problem Corrective Action

diagnostic block
ServerTimestamp
support.
BAD TOO OPC UA Server This message See the OPC UA
MANYMONITOR- could not process indicates that the Server vendor
EDITEMS all the configured number of Points/ specification and
Points/Nodes for Nodes configured reduce the number
subscription. for subscription of Points/Nodes
cannot be configured for
supported by the subscription.
OPC UA Server.
BAD INVALID “The OPC UA This message As per the OPC
TIMESTAMP Driver timestamp indicates that OPC UA specification
is outside the UA Server time the OPC UA Client
range allowed by and OPC UA Driver and OPC
the OPC UA Client Driver time UA Server clocks
Server” are not in sync. should be in sync.
Verify that both
OPC UA Server
and FDC280 OPC
UA Client clock are
in sync.
BAD TOO MANY “The OPC UA The OPC UA OPC UA Client
SUBSCRIPTIONS Server has Server has Driver creates
Reached Max reached its multiple
Subscriptions maximum number subscriptions
Limit” of subscriptions. based on different
publish interval.
N/A “Could not This message Verify all network
establish a indicates a connections and
connection to OPC network cabling
UA Server” connection
• Verify the IP
problem. Possible
address and
problems could be:
Port number
• Incorrect IP
• “Ping” the
address
OPC UA
configured in
Server
DVNAME
machine and
parameter
FDC280 from
• Incorrect Port another
Number station on the
configured in same link.
DVOPTS
parameter
• Bad cable
• Bad hub/
switch/router
N/A Client Certificate This message Server
needs to be moved indicates that Administrator has
to trusted list server to trust the client
administrator certificate
needs to trust the
client certificate

78 B0700WJ, Rev A
Chapter 6: System Messages FDC280 OPC UA Client Driver User’s Guide

Table 42 - System Messages (Continued)

LAST_ERR_MSG Smon_log Possible Problem Corrective Action

diagnostic block
N/A Client certificate This message The I/A machine
has expired or is indicates client and FDC280 time
not yet valid certificate is not should be in sync.
valid or expired
N/A ECB for certificate This message Refer Appendix C,
must be deployed indicates that ECB to generate and
if SP is not 0 for certificate is not deploy the ECB for
configured Certificate
N/A OPC UA Server This message Username identity
does not support indicates that token or
the configured Anonymous or anonymous token
user token type username identity is not supported by
token is not OPC UA Server
supported by OPC
UA server
N/A OPC UA Server This message Security policy or
does not support indicates the message security
the configured security policy and mode configured is
security policy message security not supported by
modes are not OPCUA Server
supported by OPC
UA Server
N/A “The OPC UA This message Verify that the
Server unable to indicates that OPC OPC UA Server
recognize the End UA Server does supports binary
Point URL not support binary protocol.
specified” protocol.
Verify the vendor
specifications.
N/A “OPC UA Server is This message Disconnect other
not accepting new indicates that OPC clients connected
connection” UA Server does to OPC UA Server.
not accept any
new connection to If possible, restart
OPC UA Client the OPC UA
Driver. Server.

Detecting Lost Connection with the OPC UA Server

When the OPC UA Client Driver loses the connection to the OPC UA Server, the goal
is to reconnect without losing information. To do this, the OPC UA Client Driver
detects the connection lost to the OPC UA Server and re-establishes the connection.
The OPC UA Client Driver identifies the connection loss to the OPC UA Server when
either of these conditions occurs:
• DCI blocks are configured with write only option (:NR) or DCI blocks are not
configured for the device. The OPC UA Client Driver sends Read service of OPC
UA Server Status at every 10 seconds (default value). If the Read Response is
not received, the driver indicates that communication is not successful.
• One or more DCI Blocks are not configured with write only option. The OPC UA
Client Driver subscribes to these points for data change notification. If the
notification message is not received within the configured time out period, the
driver marks the device to detected failure state.

B0700WJ, Rev A 79
FDC280 OPC UA Client Driver User’s Guide Chapter 6: System Messages

When the device ECB201 state is changed to not successful, the color changes from
White to Red in System Manager. When communication to the device is restored, the
device ECB201 status is set to Good and the color changes to White in System
Manager.

DCI Blocks Status

When communication to the ECB201 is enabled, the OPC UA Client Driver sends a
read service to get the OPC UA Server Namespace Array and compares it with the
Namespace URI configured in the DVOPTS of ECB201 or in Custom Parameter 2
and Custom Parameter 3 of the Groups tab in Control Editor. If the URI is not found,
all DCI blocks under that group appears in OOS and a Smon_log message appears.
After successful comparison of namespace URI, the OPC UA Client Driver subscribes
to the Points/Nodes configured in the Points tab in the Control Editor, if all the Points/
Nodes are subscribed successfully to the OPC UA Server the DCI blocks appears in
good status and point values are updated in HMI.
If the Points/Nodes are not subscribed successfully, the DCI blocks appears in OOS
and an Error Detection Code is reported in the smon_log. The details of the detected
ERROR code are defined in this table:

Table 43 - Error Code Details

Smon_log Possible Problem Corrective Action

“Invalid Point/Node This message indicates See the Point/Node
configured- does not exist that Point/Node information in the OPC UA
in OPC UA Server” configured in the OPC UA Server and configure the
Client Driver is not exact name in the PNT_
available in OPC UA NO field or in Address
Server address space. field of Points tab in
Control Editor.
If the Point/Node is case
sensitive configure the
Point/Node in Points tab
in CS.
“The Point/Node This message indicates Verify with the OPC UA
configured does not have that the OPC UA Server Server configuration that
access for reading/ is not allowing access node has access
subscribing” permissions for reading or permission for reading /
subscribing to that Point/ subscribing.
Node.
“The Point/Node This message indicates Verify with the OPC UA
configured does not have that the OPC UA Server Server configuration that
Write access” does not provide access node has access the
permissions for writing to access permission for
the specific Point/Node. writing.
“DataType Mismatch-write This message indicates See the datatype
operation is unsuccessful” that the Dataype of Point/ information in the OPC UA
Node configured in OPC Server and configure the
UA Server and Data Type exact type in the Data
field of Points tab. Type field of Points tab in
Control Editor.
“The attribute is not The message indicates Verify with the OPC UA
supported for the that the OPC UA Server Server configuration that
specified Node.” does not support “value” node has access
as an attribute. permission for getting the
attribute “value”.

80 B0700WJ, Rev A
Appendix A: FDC280 System Monitor Log (smon_log) Messages FDC280 OPC UA Client Driver User’s Guide

Appendix A: FDC280 System Monitor Log (smon_log)

Messages
These are the smon_log messages that can be issued when using the OPC UA Client
Driver. For smon_log messages that are applicable to all drivers, see the Field Device
Controller 280 (FDC280) User's Guide (B0700GQ).

Table 44 - smon_log Message Text

smon_log Message Text Description

Invalid options configured in DVOPTS Invalid/unknown options were detected
parameter in Device Options (DVOPTS) parameter.
Timeout configured in DVOPTS is not a The Timeout option (“+TO=X”) has been
valid number incorrectly configured.
OPC UA Server namespace URI not The OPC UA Server Namespace URI is
configured in DVOPTS a mandatory field that must be
configured.
Configure the Namespace URI at
DVOPTS parameter of ECB201, when
fields in Groups tab is not used in the
Control Editor.
Publish Interval configured in DVOPTS The PI option (“+PI=X”) has been
is not a valid number incorrectly configured.
Sampling Interval configured in The SI option (“+SI=X”) has been
DVOPTS is not a valid number incorrectly configured.
Valid Timestamp configured in DVOPTS The VDT option (“+VDT=X”) has been
is not a valid number incorrectly configured.
Identifier is not specified/Invalid for Point Address field in I/O Point Aliases tab
of Control Editor is configured
incorrectly.
PNT_NO is not specified/Invalid for Name field in I/O Point Aliases tab of
Point Control Editor is configured incorrectly.
OPC UA Server Datatype is not valid for Data Type field in I/O Point Aliases tab
point of Control Editor is configured
incorrectly.
Exceeded Maximum number of The OPC UA Client Driver creates
subscriptions multiple subscriptions based on different
publish intervals.
Reduce the Publish Intervals configured
in the ScanRate parameter of Groups
tab.
Exceeding maximum number of points Maximum number of I/O point Aliases
allowed 8000 configured cannot be more than 8000.
Reduce the I/O point aliases configured
in I/O point Aliases tab.
Msg Sec Mode(MSM) configured in The MSM option (MSM=X) has been
CPARAM1 is not a valid range configured incorrectly. Valid ranges are
(0 to 2).

B0700WJ, Rev A 81
 Appendix A: FDC280 System Monitor Log (smon_log)
FDC280 OPC UA Client Driver User’s Guide Messages

Table 44 - smon_log Message Text (Continued)

smon_log Message Text Description

Security Policy configured in CPARAM1 The SP option (SP=X) has been
is not a valid range configured incorrectly. Valid ranges are
(0 to 5).
Invalid SP/MSM combination configured The combination SP and +MSM options
are configured in correctly.
Invalid option Username/Password not The EN or +PV option is configured
configured incorrectly or not configured correctly.
Namespace URI configured in The Namespace URI configured in
CPARAM2 should be prefix with URI= CPARAM2 should be prefix with URI= .

82 B0700WJ, Rev A
Appendix B: FDC280 Diagnostic Driver Support FDC280 OPC UA Client Driver User’s Guide

Appendix B: FDC280 Diagnostic Driver Support

The OPC UA Client Driver includes support for the FDC280 Diagnostic Driver, which
can be used to help diagnose communication between the OPC UA Client Driver and
the OPC UA Server. The Diagnostic Driver sends communication echo messages to
the FDC280 IO diagnostic tool, which is a Windows®-based user interface application
that logs the echo messages.
To enable the diagnostic feature, use System Manager to create an ECB200 block
and set it to online.
For information, see the Field Device Controller 280 (FDC280) User's Guide
(B0700GQ).

B0700WJ, Rev A 83
 n k
Bla
e f t
y L
a ll
i on
n t
n t e
e I
a g
s P
h i
T
 FDC280 OPC UA Client Driver User’s Guide

Glossary
N
NodeId: To uniquely identify a node, each node has a NodeId, that is always
composed of these elements:
• NamespaceIndex: The index an OPC UA server uses for a namespace URI.
The namespace URI identifies the naming authority defining the identifiers of
NodeIds. For example; the OPC Foundation, other standard bodies and
consortia, the underlying system, the local server. They are stored in namespace
array (also referred to as namespace table). Namespace indexes are numeric
values used to identify namespaces to optimize transfer and processing. The
namespace index is the index of the namespace URI in the namespace array.
• IdentifierType: The format and data type of the identifier. It can be a numeric
value, a string, a globally unique identifier (GUID), or an opaque value (a
namespace specific format in a ByteString). Which type is preferred depends on
the use case. If it is important to save memory or bandwidth, it makes sense to
use numeric NodeIds which are smaller and faster to resolve. The OPC UA
namespace as defined by the OPC Foundation uses numeric NodeIds. system-
wide and globally unique identifiers allow clients to track Nodes. For example;
work orders moving between OPC UA servers as they progress through the
system.
• Identifier: The identifier for a node in the address space of an OPC UA server

O
OPC (Unified Architecture): OLE for Process Control Unified Architecture, the next
generation OPC standard that provides a cohesive, secure, and reliable cross-
platform framework for access to real time data and events.

P
Parameter: Named element in the data structure of a device function block,
Equipment Control Block (ECB), or other control block.

Publish: After successful Subscription the OPC UA Client Driver sends publish
requests based on the configured publish interval and OPC UA Server sends data
Notifications as part of Publish Response.

R
Right FDC280: For an FDC280 pair, the FDC280 installed in the right slot in the two-
slot FDC280 baseplate, when facing a horizontally aligned FDC280 baseplate from
the front.

S
Sample Interval: Indicates the fastest rate at which the server should sample its
underlying source for data changes.

Session: A session is the authorized connection between the OPC UA Client Driver
and the OPC UA Server’s address space.

Subscription: In contrast to permanently reading information (polling), OPC UA

provides a more elegant functionality, called Subscription. An OPC UA Client Driver
can subscribe to a selection of Nodes of interest and let the OPC UA Server monitor
these items. Only in case of changes, example: to their values, the server notifies the
OPC UA Client Driver about such changes.

B0700WJ, Rev A 85
FDC280 OPC UA Client Driver User’s Guide

U
URI: Uniform resource identifier

86 B0700WJ, Rev A
 FDC280 OPC UA Client Driver User’s Guide

Index L
last detected
error message ......................................................68
B
bulk creation N
groups and I/O point aliases
spreadsheet......................................................40 namespace URI
multiple
intervals............................................................40
C points/nodes .....................................................38
publish intervals ................................................39
configuration
hardware..............................................................12
I/O point aliases....................................................38 O
configuring
additional block types............................................62 operation
DCI Blocks ECB201 ...............................................................56
OPC UA points/nodes........................................60 OPC UA client driver .............................................55
device options parameter ......................................30 principles .............................................................55
ECB200 Block ......................................................52 redundant ............................................................55
ECB201 block ......................................................53 output block
FDC280 BOUT ..................................................................62
CCS .................................................................52 IOUT....................................................................63
FDC280 using CS.................................................25 PAKOUT ..............................................................63
ROUT ..................................................................64
overview
D setup .....................................................................9
data types
DCI input/output blocks .........................................70 P
mapping of OPC UA server
DCI block type...................................................72 points
detecting write-only .............................................................70
lost connection Procedure
OPC UA server .................................................79 separate workstations
diagnostic hosting the FDC280...........................................17
data .....................................................................66

R
F requirements
FDC280 hardware..............................................................13
diagnostic driver software ...............................................................13
support .............................................................83 reset
system monitor log (smon_log) counters...............................................................66
messages .........................................................81 response
timeout counter.....................................................67

G
getting
S
started ...................................................................9 status
DCI blocks ...........................................................80
OPC UA value ......................................................73
I support
arrays ..................................................................68
input block support data types
BIN/BINR .............................................................64 output blocks ........................................................71
IIN/IINR................................................................64 system
PAKIN/PAKINR.....................................................65 compatibility .........................................................13
RIN/RINR.............................................................65 messages ............................................................77
STRIN .................................................................66
Installing
configure the driver ...............................................17 T
Control Software Configurator................................17
total number

B0700WJ, Rev A 87
FDC280 OPC UA Client Driver User’s Guide

bad timestamp points ............................................67

turning on
driver
enabling communication .............................. 74, 76

88 B0700WJ, Rev A
Schneider Electric Systems USA, Inc.
70 Mechanic Street
Foxboro, Massachusetts 02035–2037
United States of America

Global Customer Support: https://pasupport.schneider-electric.com

As standards, specifications, and design change from time to time,

please ask for confirmation of the information given in this publication.

© 2022 Schneider Electric. All rights reserved.

B0700WJ, Rev A