Release Notes

IoT Gateway
1.2

Revision: D
The information in this manual is subject to change without notice and should not be construed as a
commitment by ABB. ABB assumes no responsibility for any errors that may appear in this manual.
Except as may be expressly stated anywhere in this manual, nothing herein shall be construed as any kind of
guarantee or warranty by ABB for losses, damages to persons or property, fitness for a specific purpose or the
like.
In no event shall ABB be liable for incidental or consequential damages arising from use of this manual and
products described herein.
This manual and parts thereof must not be reproduced or copied without ABB's written permission, and
contents thereof must not be imparted to a third party nor be used for any unauthorized purpose. Contravention
will be prosecuted.
Additional copies of this document may be obtained from ABB at its then current charge.

© Copyright 2022 ABB All rights reserved.

ABB AB
Robotics Products
SE-721 68 Västerås
Sweden
 Table of Contents

Overview 4

Release Information 5

New Features 6

How to migrate from IRC5 OPC UA Server to IoT Gateway 7

Corrections 9

Known Limitations 10

Installation 11

Product Support 13

© Copyright 2022 ABB All rights reserved 3

 Release Notes
IoT Gateway v1.2

Overview
Description
This document provides information about the new features, corrected problems, and
installation of the latest IoT Gateway.

Product Overview
IoT Gateway is an extendable communication gateway that provide OPC UA Server
and MQTT publisher capabilities for the IRC5 and Omnicore generation of robot
controllers.
The product is implemented as a Windows service that runs the communication
gateway(s) and a Windows application used for configuration and commissioning. The
product is especially suitable for retrofit solutions as it in most cases does not require
an upgrade of RobotWare.
The OPC UA Server exposes information in the Robot controller to OPC UA clients.
The product consists of two components:
 A Windows service that runs in the background and transfers information to and
from the connected controllers.
 A user interface that lets the user configure which controllers that the server shall
connect to.
A 3rd party SCADA or other system with an in-built OPC UA client may be used to
connect with the OPC UA server in the IoT Gateway.
Note: The IoT Gateway does not include any OPC UA clients.

Please read the RobotWare Release Notes and documentation for general information
on your robot and networking the controller.

To get started, or to learn more, visit our Developer Center:

https://developercenter.robotstudio.com

Here you will also find the User Forum, where developers discuss software problems
and solutions online:
https://forums.robotstudio.com

More information about the OPC specification, related tools and libraries, can be found
at the OPC Foundation web site:
http://www.opcfoundation.org

© Copyright 2022 ABB All rights reserved 4

 Release Notes
IoT Gateway v1.2

Release Information
Release Name
The release name is IoT Gateway v1.2 and the build number is IoT.GateWay.1.2.0-143

It is available for download from https://developercenter.robotstudio.com.

Release Date
The release date is March 25, 2022

Configuration
User interface for configuring the IoT Gateway.
It can be launched from the Windows Start Menu.
Programs > ABB > IoT Gateway Config

Server component
IoT Gateway runs as a Windows service in the background. It connects to configured
controllers and allows incoming connections from OPC UA clients.
It can be started and stopped using the IoT Gateway Config Tool.

Robot Communication Runtime

Component used by the server component for communication with controllers over a
network.

Documentation
IoT Gateway Help – Operating Manual.
It can be accessed from Help button in IoT Gateway Config Tool.

© Copyright 2022 ABB All rights reserved 5

 Release Notes
IoT Gateway v1.2

New Features
Overview
This section contains a short description of new features in this release. For detailed
information, see the user manual.

Publish Event log messages after reconnecting with controller

When the IoT Gateway reconnects with a robot controller after being disconnected for a
while, the Event Log Message trigger will try to retrieve all event log messages from the
robot controller that has occurred in the meantime, up to a maximum of 1000
messages. These messages are subsequently processed as defined by the
configuration of the Event Log Message trigger

Extended support for subscription

Implemented a polling mechanism to poll for updates to variables in the robot controller
where RobAPI does not support event-based subscription

MQTT Engineering Tool

MQTT Engineering tool now supports configuring robots, triggers and payloads

Rename Alias
The IoT Gateway config tool now supports renaming alias.

© Copyright 2022 ABB All rights reserved 6

 Release Notes
IoT Gateway v1.2

How to migrate from IRC5 OPC UA Server to IoT

Gateway

1. Stop the IRC5 OPC UA Server

2. Install IoT Gateway

3. Open the IoT Gateway config tool and verify that all alias defnations are imported. If not try
to restart the IoT Gateway and reverify
4. Import the trusted client certificates from Location ((%ProgramData%\ABB\IRC5 OPC
UA\CertificateStores\TrustedCertificates\certs) using IoT Gateway config tool
 Go to IoT Gateway config tool -> Client Certificates

© Copyright 2022 ABB All rights reserved 7

 Release Notes
IoT Gateway v1.2

 Click on Import button to import the trusted client certificates of IRC5 OPC UA
Server from from Location (%ProgramData%\ABB\IRC5 OPC
UA\CertificateStores\TrustedCertificates\certs). Select all the certicates.

 Click on Open in Import Certifcate window. All the trusted client ceritfcates of IRC5
OPC UA Server imported to trusted client list of IoT Gateway

5. Uninstall IRC5 OPC UA Server

© Copyright 2022 ABB All rights reserved 8

 Release Notes
IoT Gateway v1.2

Corrections
Overview
This section describes the corrections in this release of the IoT Gateway.
Defect Title Description
Number
RSI:419424 Install on different drive than C: The IoT Gateway including support tools
fails failed in certain use cases if a non-default
path was chosen during a custom installation.

IoT Gateway Configuration "SET No access to robot controller data when

PDD:14318 IP Address" adding new Alias name in config tool using
“SET IP Address”
PDD:14388 IOT Gateway 1.1-Signals and No access to robot controller data like IO
Variables not visible in OPC UA signals when adding new Alias name in
Client config tool
PDD:54407 PC SDK throws an undocumented Attempting to read any persistent RAPID
exception when accessing array of strings with more than 67 strings in it,
ArrayData cause PC SDK to throw a
System.FormatException.
PDD:14479 Exception in IOT Gateway if using Sometimes the IO Signals and variables are
OPC UA available, sometimes not. Axis Values are not
available at all
BUG:432773 IoT Gateway Config Tool: The The software must be executable in normal
software must be executable in operation with "user rights", i.e. the program
normal operation with "user rights" must not demand administrative rights in
normal operation.
BUG: MQTT Engineering Tool: The The software must be executable in normal
432772 software must be executable in operation with "user rights", i.e. the program
normal operation with "user rights" must not demand administrative rights in
normal operation.

© Copyright 2022 ABB All rights reserved 9

 Release Notes
IoT Gateway v1.2

Known Limitations
Overview
This section describes known limitations in IoT Gateway.

Feature 308167: IoT Gateway: Fast start-up by delayed on demand address space
creation
While start of IoT Gateway, it collects the data required for information model. IoT
Gateway communicate with Controller to fetch the information.
If controller has many signals and rapid variables data collection takes bit of time.
Example : If Configured controller has 1000 signals and 200 RAPID Persistence
variables then IoT Gateway may take nearly 2mins to connect and fetch the
information.
Workaround: This problem will not occur if configured controllers does not have very
many IO-Signals and RAPID Persistence variables. Otherwise problem will not have
impact on startup.

Feature 440288: IoT Gateway: Use Information Stream for high performance (OPC UA)
subscription
Use Information Stream for high performance (OPC UA) subscription

Bug 386278: Alias icon shows as disconnected after reopening the config tool
Alias icon shows as disconnected after reopening the config tool

Bug 349425: IoT Gateway crashes after connecting remote VC running in different PC
of Same subnet
IoT Gateway crashes after connecting remote VC running in different PC of Same
subnet

Bug 440583: No access to robot controller data when adding new alias for virtual
controller
No access to robot controller data when adding new Alias for virtual controller if
'Address' is selected/ticketed in Connection Criteria box.

Bug 440663: Removing alias which is in system failure , saving the configuration and
restarting IoT gateway results in FTL error
Removing alias which is in system failure , saving the configuration and restarting IoT
gateway results in FTL error.

Bug 441269: Controller name is disabled for alias connection criteria

Controller name is disabled for alias connection critirea
IP address does not work as connection critirea for virtual controllers

© Copyright 2022 ABB All rights reserved 10

 Release Notes
IoT Gateway v1.2

Installation
1.1 Prerequisites

Before you install…

• You must have the administrator rights for the computer in order to install and
configure IoT Gateway.

Licensing
IoT Gateway can be used free of charge, but certain RobotWare options are
required to enable communication with the robot controllers. See RobotWare
software requirements chapter below for details on required options.

1.1 System requirements

Hardware
Medium to high-performance industrial or desktop PC, with the following requirements

Part Requirement
CPU 2.0GHz or faster processor, multiple cores recommended
Memory 2 GB minimum. 4GB or more recommended
Disk 2+ GB free space, solid state drive (SSD) recommended.

PC software requirements

Operating System Edition Remark

Microsoft Windows 10 64-bit edition Recommended

RobotWare software requirements

IoT Gateway supports RobotWare 6 and RobotWare 7.2 and newer.

For all RobotWare 6 versions starting from version 6.12.03, both the “616-1 PC
Interface” and the “1582-1 IoT Data Gateway” RoboWare options are required.
Robotware version starting from 6.11 to 6.12.02, both the “616-1 PC Interface” and the
“1582-1 OPC UA Server” RoboWare options are required.
The IoT Gateway may also be used with RobotWare versions prior to 6.11. Please
contact ABB for information on licensing.

For Omnicore controllers from RobotWare 7.2 and newer “3154-1 IoT Data
Gateway” option is required.

© Copyright 2022 ABB All rights reserved 11

 Release Notes
IoT Gateway v1.2

1.2 Installation instructions

Installing on a new PC
NOTE: It is recommended to uninstall the IRC5 OPC UA Server before installing the
IoT Gateway.
Action
1 Download the IoT Gateway to a folder on your computer from
https://developercenter.robotstudio.com
2 Double click setup.exe in the extracted folder to start the IoT Gateway installation
procedure
3 Proceed to install IoT Gateway.
4 IoT Gateway is installed

© Copyright 2022 ABB All rights reserved 12

 Release Notes
IoT Gateway v1.2

Product Support
For product support please turn to your local ABB office.
https://new.abb.com/contact-centers

For help, advice and the latest updates visit the User Forum and Developer Center.
https://forums.robotstudio.com
https://developercenter.robotstudio.com

© Copyright 2022 ABB All rights reserved 13