This document describes the features planned for each release

Release1

Base System

• The OPC UA ModBus Server is based on the OpcUaServer version 4
• Support Windows and Linux
• Supports Modbus TCP\IP
• Supports the following primitive data types:
  • Bool
  • Int8
  • UInt8
  • Int16
  • UInt16
  • Int32
  • UInt32
  • Int64
  • UInt64
  • Float
  • Double
• Supports arrays
• Supports ModBus functions:
  • (1) Read Coils
  • (2) Read Discrete Inputs
  • (3) Read Holding Registers
  • (4) Read Input Registers
  • (15) Write Multiple Coils
  • (16) Write Multiple Registers
• Works in two direcions:
  • ModBus Client - OPC UA Server
  • OPC UA Server - ModBus Server
• Reads configuration from XML

ModBus Client - OPC UA Server

The mapping ModBus data into OPC UA Information Model must have three hierarchy levels:

• TCP\IP Channel
• ModBus Device
• MosBus Map

TCP\IP Channel

TCP\IP Channel represents the TCP\IP transport layer and must have the following settings:

• IP address
• Port
• Enable

Also, the channel must provide diagnostic variables:

• Enable
• Available

ModBus Deivce

ModBus Device represents the data source and must have the following settings:

• UID
• Max number of registers in functions 3,4 and 16
• Max number of coils in functions 1,2 and 15
• Byte Swapping (ABCD, BADC, etc)
• Enable

Diagnostics:

• Enable
• Available

ModBus Map

ModBus Map is a group of ModBus registers or coils that are read or written in one ModBus request. It must have the following settings:

• Scan rate
• Start address
• List of Nodes with types that are mapped ModBus data.

OPC UA Server - ModBus Server

Build and Test

• The build, test and the deploy are done automatically with Jenkins

Documentation

• Overview
• Installation
• Configuration