Infinity Client software embeds the necessary libraries to communicate with other devices via the MODBUS TCP/IP protocol, providing exchanged data is restricted to bits.

PivotWare can therefore connect to I/O modules whose Input / Output state is either reported or configured via the Modbus TCP/IP protocol. Furthermore, this can be achieved without the need for any additional driver to be installed on the computer running the Infinity Client software.

2-2 Choosing a MODBUS I/O Asset

Before selecting an asset, check the following:

The asset must be compatible with MODBUS TCP/IP protocol.
The asset must be compatible with the holding register mode of MODBUS protocol.

Please find below a list of assets known as having been successfully used as MODBUS I/O Asset and the links to the article in our support portal (if any) detailing the configuration procedure:

IO Asset Manufacturer	IO Model	Number of Inputs / Number of Outputs	Configuration Article link
PHOENIX	IL ETH BK DI8 DO4 IB IL 24 DI 32 IB IL 24 DO 32	40 / 36	IL ETH BK DI8 DO4 configuration
MOXA	ioLogikE1212	8 / 8 16 / 16	iOLogik E1212 configuration

Note: Infinity Client can only use Booleans with the MODBUS protocol.

3 - Configuring the Asset in PivotWare

A dummy process (MODBUS_IO_Training.zip) can be found attached to this article, alongside a dedicated CSV configuration file. They are provided as a support for this article.
All snapshots taken below are related to said process, so feel free to use it to help you discover the use of MODBUS TCP/IO assets.

3-1 Creating the Modbus Configuration File

A csv file needs to be prepared before setting- up the asset: this file will be loaded to CVIFusion as the I/O description.

The file must list each Input / Output and its corresponding MODBUS registry address.

This file must include a header with the following columns (please refer to file Phoenix_IL_ETH_BK_DI8_DO4.csv as an example):

Name : the variable name. All subsequent row entries must start with I if an input, O for an output and followed by the Input / Output number.
Address: the IO address field for the target Input/Output. The address format is XXXX.YY, XXXX being the Register Address as provided by the device's manufacturer (please refer to the manufacturer datasheets), YY being the field specific address (Hexadecimal range, i.e. from 0 to 15).
Length: always set to 1, Infinity Client only being able to use MODBUS over 1 bit.
Type: must always be set to Bool.
Access: must be set to R (Read) for the Inputs, and to W (Write) for the Outputs.

3-2 Configuring your MODBUS IO Asset in CVIFusion

Open the Asset Manager panel in CVIFusion then select the project you wish your Asset to be included in.

Once you have opened the correct project:

Click on New Asset.
Provide a name then select as an Asset type the IO Module option.
Change the Asset Vendor to Other IO Module.
Change the IO Type to MODBUS TCP/IP then fill in your asset IP address.
Click Load Configuration then choose the Modbus Configuration File previously created.
If the file format is exact and successfully loaded, a check mark should be displayed next to the filename in CVIFusion.
Click Save Asset then Save Asset Project to complete the Asset creation process.

3-3 Attaching then using the asset in a process

The MODBUS TCP IO Asset must be associated to the station it is connected to via CVIFusion's Station Manager panel. Please refer to Desoutter Industrial Tools : Creating and Associating Assets (desouttertools.com) for further details.

Once the Asset has been assigned to the station, it is possible to check the number of Inputs / Outputs created.
To do so, open Process Manager's station panel:

Expand the IO Event Mapping field.
Click IO Event Mapping button.

In the Event Mapping view that opens, you can check whether all Inputs / Outputs have been created as per your configuration file.

The I/O so declared can then be used in Digital In step, Digital Out step, Digital Picking step, Action Monitoring step ..., but also as tool and status monitoring via the IO Event Mapping view at the station level.

3-4 Checking IO asset behaviour via Infinity Client

The IO asset behaviour can be tested via Infinity Client after transferring a process / station.

Ensure the process / station including the MODBUS TCP/IP IO asset has been deployed.
Login to the station with Administrator privileges.
Click the Infinity logo
Click the I/O diagnostics button.

The panel that opens will let you test any IO Assets configured and connected.

Select the IO Asset you wish to test from the Dropdown menu available at the top of the panel.
Activate one or more of your asset's inputs: the corresponding display must be switched on in the Inputs field.
Click on any of the displayed button from the Outputs field. As a result, the corresponding output must be active on your asset.

4 - Further readings

The following articles can provide you with additional information:

MOXA iOLogik E1212 configuration: configuration procedure for using MOXA iOLogik E212 as a MODBUS TCP/IO asset.
Integrating Desoutter IO assets: configuration procedure for using Desoutter provided Nano IO and Micro IO.

csv

Phoenix_IL_E...

(1.6 KB)

zip

MODBUS_IO_Tr...

(7.59 KB)

Integrating with Modbus TCP/IP IO Module

This Article Applies From:

CVI Fusion 6.23

Infinity Client 6.23

Infinity Module 6.23

Core Services 6.23

Introduction

1 - Suggested readings

2 - MODBUS I/O Asset overview

2-1 Generic overview