Modbus TCP On Opta™ Using PLC IDE

Overview

Opta™ is distinguished by its industrial-grade hardware that ensures durability and consistent performance even in the most challenging environments. A highlight of its design is the inclusion of multiple connectivity options, notably Modbus TCP through the RJ-45 port.

In this tutorial, you will learn how to implement Modbus TCP based communication between two Opta™ devices using Arduino PLC IDE.

Goals

• Learn how to configure the workspace environment to work with Modbus TCP using Arduino PLC IDE.
• Learn how to configure Modbus TCP for Opta™ using Arduino PLC IDE.
• Learn how to verify that Opta™ has been correctly set up using an example that uses Modbus TCP communication.

Required Hardware and Software

Hardware Requirements

• Opta™ (x2)
• USB-C® cable (x2)
• RJ-45 LAN cable (x3)
• Ethernet Switch (Recommended) (x1)

Software Requirements

• Arduino PLC IDE Tools
• Arduino PLC IDE software
• If you have an Opta™, you do not need any license key to activate your product. Go to section License Activation With Pre-Licensed Products (Opta™) to know more.
• Opta™ Modbus TCP PLC IDE Project Example File

Modbus TCP

The Modbus protocol is a messaging service structure using Client/Server communication. It is an application protocol, with its data management being independent of the transmission method.

The Modbus TCP/IP, often simply referred to as Modbus TCP, is a variant of the Modbus RTU protocol that uses the TCP/IP interface over Ethernet to exchange data between compatible devices. Here are some key elements to understand about Modbus TCP:

• The 'Transmission Control Protocol (TCP)' is responsible for the exchange of packets.

• The 'Internet Protocol (IP)' defines the addresses for routing message destinations.

• A distinct feature of Modbus TCP concerns how it maintains data integrity. Since Modbus TCP encapsulates the basic data frame within the TCP frame, the usual checksum field of Modbus isn't utilized. Instead, the checksum method from the Ethernet TCP/IP layer ensures data integrity.

• Modbus TCP/IP adheres to TCP/IP networking standards on Ethernet, using the Modbus messaging service as its data handler. Typically, the connected devices are Modbus TCP/IP Client and Server devices. However, interconnections can also be established through routers, gateways, or bridges, forming a TCP/IP network.

Controller/Peripheral was formerly known as Master/Slave. The Modbus Organization no longer supports the use of this terminology. Devices formerly known as Master are referred to as Controller/Client and devices formerly known as Slaves are referred to as Peripheral/Server.

Modbus TCP & PLC IDE

In this tutorial, we will guide you through setting up two Opta™ devices with Modbus TCP using the Arduino PLC IDE. Understanding the overall process of implementation is crucial for successful deployment.

Refer to the following diagram for a concise visualization of how Opta™ is configured and deployed with Modbus TCP:

The entire procedure is divided into three distinct stages:

• Modbus TCP Configuration is the foundational step where we initialize the Opta™ device with Modbus TCP and other essential properties intrinsic to the device. A pivotal component of this stage is the IP configuration, which is essential for Modbus TCP communication and will be defined within the Arduino sketch.

  During this stage, the Modbus TCP role, either Client or Server, is designated to the Opta™ device. Based on this role within the Modbus TCP, either the 'Status variables' are delineated or the Modbus node is defined to determine the communicating devices using this protocol.

• PLC Program, developed subsequent to device initialization, it is grounded in Modbus TCP and other properties. The beauty of this stage is the absence of a need for detailed configurations or programming related to Modbus TCP settings in the PLC code.

  The process has been simplified for user convenience. By merely referencing predefined variables in your PLC code, the system autonomously manages data exchange via Modbus TCP. This method capitalizes on the device's earlier initialization, thus cutting down on redundant steps and bolstering efficient communication.

• System Operation represents the anticipated outcome post the Modbus TCP configuration and the execution of the PLC program based on the developer's designed logic. Consequently, we can observe the device engaging in communication with other devices through Modbus TCP.

The provided diagram underscores the consistency in the Modbus TCP configuration across Arduino devices using the PLC IDE. A salient feature of this system is its adaptability. Irrespective of the Modbus TCP configurations, the PLC program can operate effectively and reliably. This autonomous nature guarantees its interoperability and versatility in a variety of scenarios.

Furthermore, when it comes to creating or customizing the PLC code, we are not restricted in terms of programming language. The system supports the IEC61131-3 standard, which means it can be designed with preferred language from the suite defined under this standard. This adaptability allows for both ease of use and precision in program development.

Having provided an overview of the entire process, we can now delve into the specifics.

Instructions

Setting Up the Arduino PLC IDE

Access the Arduino PLC IDE software by following Arduino PLC IDE official website. You will have to download two executable files for proper software installation:

• Arduino PLC IDE Tools
• Arduino PLC IDE

The Arduino PLC IDE Tools will provide all the required drivers, libraries, and cores for development while the Arduino PLC IDE will install the IDE software.

Install the Arduino PLC IDE Tools before the Arduino PLC IDE to avoid potential problems related to old libraries and drivers.

For more details regarding Arduino PLC IDE setup, please take a look at Arduino PLC IDE Setup and Board's License Activation tutorial.

Hardware Setup

For Modbus TCP communication, we will use two Opta™ devices and the PLC IDE.

Connection and Ethernet Switch Integration

Set up the connection by attaching the Ethernet LAN (RJ-45) cable to both devices using the

ETH RJ45

The setup incorporates an Ethernet switch that monitors both Opta™ devices using the PLC IDE. This configuration not only links both Opta™ devices using the PLC IDE but also lets you employ a profile to observe information exchanges in real-time. We recommend using the setup with the Ethernet switch for this tutorial to ensure optimal communication between devices.

Field Deployment Setup

Once the Modbus connection is active, you can directly connect the Opta™ devices without the Ethernet switch in the field application. Furthermore, you have the flexibility to add more Modbus TCP compatible devices to the communication line, expanding the setup as needed. Refer to the following image for this configuration:

Workspace Pre-Configuration

There are some considerations that you will need to understand beforehand for proper use of Modbus TCP on Opta™ within PLC IDE. Following subsections will help briefly explain such aspects.

PLC IDE Project Configuration & Licenses Management

In any robust development environment, understanding the intricacies of project configuration and the nuances of license management is essential. The Arduino PLC IDE provides a unique blend of features tailored for industrial automation, but to utilize them effectively, a solid foundation is indispensable.

We highly recommend reviewing this tutorial before delving into the present tutorial.

Opta™ Basic Configuration

To configure the Modbus TCP communication, we need to know the IP address of each Opta™. When Opta™ is connected to a computer using the RJ-45 cable and the Ethernet switch, and the ethernet configuration is left as default, an IP address is automatically provided to Opta™ by the external Dynamic Host Configuration Protocol (DHCP) server. You will need to scan for the address and use that IP address as the device address of Opta™. To find the automatically assigned IP address, it is possible to use this scanner to identify the address.

Opta™ can also be configured manually with a specific IP address using Ethernet.begin() method. This method is viable to assign devices with specific addresses to operate under certain policies if required. For this configuration, the IP setting must be defined by using the sketch found within the

Resources

The Ethernet.begin(ip, dns, gateway, subnet) method postpones initialization for 60 seconds when the RJ45 cable is found to be disconnected or when Ethernet settings, such as the IP address, are improperly configured. The Ethernet.begin(NULL, ip, dns, gateway, subnet, connection_timeout) method can be used to extend initialization process and tweak the

connection_timeout

If the IP address for Opta™ is set manually, it is necessary to configure the Ethernet interface on your computer by introducing a manual IP address setting under IPv4. The information set under the IPv4 configuration follows the gateway setting. A stable connection with Opta™ using the PLC IDE is essential for project development. The following image shows a configuration example on Windows 11 operating system:

The configured IP address for Opta™ also serves to connect and develop within the Arduino PLC IDE environment. The Modbus TCP option must be activated and set with Opta™ device's assigned IP address by going to

On-line -> Set up communication

ping <Opta™ IP Address>

Keep in mind that the correct configuration is key to work with PLC IDE and Opta™. Once the properties of the Opta™ devices are correctly set, we will be able to seamlessly connect to Opta™ and monitor the states of both devices.

Modbus TCP Client and Server Mode

The image below shows the interface we'll encounter when accessing the Modbus TCP configuration panel in the PLC IDE.

There are two options on the Modbus TCP configuration panel:

• Modbus TCP Master
• Modbus TCP Slave always enabled. Unit Identifier: 255

If the "Modbus TCP Master" option remains unchecked, the role of a Modbus TCP Server with its designated Unit Identifier is automatically adopted by the Opta™ device. No attention needs to be given to the Unit Identifier in such cases. It is because communication with the appropriate Opta™ device is ensured by the configured IP address, even when the same Unit Identifier is shared among multiple devices.

When "Modbus TCP Master" is checked, both Client and Server roles are taken on by the Opta™ device. In this mode, precedence is given to the Client role. As a consequence, under the

Ethernet

General Modbus Node Configuration

The General Modbus Node allows to add information regarding the devices compatible with the Modbus messaging service.

It will require you to fill in basic information under the

General

If you have added a General Modbus Node defining Opta™ as a Modbus TCP Master initially and unchecked the Client role later, the Node option will stay. However, the Node's configuration field will change and request for a Modbus address within the

1 ... 247

PLC IDE Modbus Custom Editor

This is an alternative way of adding a Modbus node under the

Ethernet

Tools -> Run Modbus Custom Editor

It will allow to define the device version and information with Modbus functions pre-defined. It can be deployed later by adding it under the

Ethernet

It is a useful feature to have frequently deployed device configuration stored that is compatible with Modbus protocol.

Project Overview

Now that you have the prerequisites ready and the tools for Modbus TCP configuration for Opta™ using PLC IDE, an example project will be introduced. This will showcase how Modbus TCP communication between two Opta™ devices is established.

The example project will make a slight change to its default example code using the counter (

cnt

The status LED and relay of Modbus TCP Master Opta™ will be activated based on the counter information received from the Modbus TCP Slave Opta™. Through specific sections dedicated to roles, the setting of the Modbus TCP role for each Opta™ device will be learned.

For those wishing to skip the step by step procedure, the complete example project can be downloaded here. Every essential configuration and component has been included, ensuring it's ready to be compiled and uploaded to the corresponding Opta™ device.

In the sections that follow, the configuration of each Opta™, based on its designated role in Modbus TCP communication, will be detailed.

Modbus TCP Server Opta™

To set Opta™ as a Modbus TCP Server, navigate to the

Ethernet

Resources

Modbus TCP Slave

When initializing a project file in PLC IDE, Ethernet properties within the sketch are commented out. These lines should be uncommented to activate the configurations. Once this is done, the sketch should be manually downloaded to Opta™ through the

Opta™ Configuration

The Modbus TCP Server Opta™ will employ the following Ethernet properties within the sketch.

Copy
1void setup()
2{
3    // Configure static IP address
4    IPAddress ip(192, 168, 1, 2);
5    IPAddress dns(192, 168, 1, 23);
6    IPAddress gateway(192, 168, 1, 23);
7    IPAddress subnet(255, 255, 255, 0);
8    // If the cable is not connected this will block the start of PLC with about 60s of timeout!
9    Ethernet.begin(ip, dns, gateway, subnet);
10}

These properties —

ip

dns

gateway

subnet

Ethernet.begin()

ip(192, 168, 1, 2)

The following image shows the

Status variables (volatile)

cnt

The

cnt

• Address: 25000 (dec) / 0x61A8 (hex)
• Name: cnt
• PLC type: INT

With these settings ready, you need to go to

Resources -> Opta

Manual sketch download

On-line -> Set up Communication

Proceed with

On-line -> Connect

Symbols

(1)

(2)

Next, the main PLC code, also referred to as the primary code, must be compiled and uploaded to Opta™. To do this, navigate to the

main

Project

Copy
1cnt := cnt + 1;
2
3IF cnt >= 2750 THEN
4    cnt := 0;
5END_IF;

The Opta™ server device's task runs a simple counter and resets whenever the counter reaches

2750

Download PLC code

F7

Upon completing these steps, you will have successfully configured an Opta™ device as a Modbus TCP Server. The next section will guide you through setting up another Opta™ as a Modbus TCP Client.

Modbus TCP Client Opta™

To set Opta™ as a Modbus TCP Client, begin by navigating to the 'Ethernet' tab found under the 'Resources' panel in the PLC IDE. Here, check the 'Modbus TCP Master' option. As previously discussed here, this action will designate Opta™ as a Client. Do not worry about the greyed-out Server option.

To establish communication with the configured Modbus TCP Server Opta™, Modbus node can be added by right-clicking on the 'Ethernet' tab located under the 'Resources' panel. Once done, the 'Add' option will be made visible. This option should be selected to introduce a 'Generic Modbus' node. For this example, the node must be configured with the following parameters:

• Name: Opta_TCP_1
• IP address: 192.168.1.2
• Minimum polling time: 1 ms
• Address type: Modbus

These properties should be set in the same manner as for the Modbus TCP Server Opta™. The most crucial configuration is the IP address. This address must correspond to the one assigned to the server Opta™, or any other compatible device should you add more nodes. The resulting configuration should look similar to the accompanying image:

While the Modbus node for the client Opta™ is defined, the Modbus function that will retrieve the counter (

cnt

Opta_TCP_1

For retrieving counter data from the server Opta™, select the 'Modbus FC-04 (Read Input Registers)' function. The 'General' tab needs to be configured with the following parameters for correct data access:

• Start address: 25000
• Polling time: 0 ms (Continuous Read)
• Timeout: 1000 ms

Next, a variable that will store the counter information from the server Opta™ must be defined. This variable can be added by navigating to the

Input Reg.

counter_rec

The following image shows a visual representation of the expected configuration:

The Modbus TCP Client Opta™ will use the following Ethernet properties.

Copy
1void setup()
2{
3    // Configure static IP address
4    IPAddress ip(192, 168, 1, 1);
5    IPAddress dns(192, 168, 1, 3);
6    IPAddress gateway(192, 168, 1, 3);
7    IPAddress subnet(255, 255, 255, 0);
8    // If the cable is not connected this will block the start of PLC with about 60s of timeout!
9    Ethernet.begin(ip, dns, gateway, subnet);
10}

The

ip(192, 168, 1, 1)

subnet

The client Opta™ employs status LEDs and relays in this tutorial's example. The status LEDs can be defined with variables of your choice. For this example, it could use

LED1

LED4

For instance, to use the

relay_1

LED1

The following image shows how it should look within the PLC IDE interface:

The relays also require designations to be able to call later in the main PLC code. A table with designated variable names for relays is shown below:

The main program below will be used to fetch counter data, control status LEDs, and manage corresponding relays. A successful Modbus TCP communication will process previous tasks accordingly.

Copy
1counter := counter_rec;
2
3IF counter >= 500 THEN
4    relay_1 := TRUE;
5    LED1 := TRUE;
6END_IF;
7
8IF counter >= 1000 THEN 
9    relay_2 := TRUE;
10    LED2 := TRUE;
11END_IF;
12
13IF counter >= 1500 THEN 
14    relay_3 := TRUE;
15    LED3 := TRUE;
16END_IF;
17
18IF counter >= 2000 THEN 
19    relay_4 := TRUE;
20    LED4 := TRUE;
21END_IF;
22
23IF counter >= 2500 THEN
24    relay_1 := FALSE;
25    relay_2 := FALSE;
26    relay_3 := FALSE;
27    relay_4 := FALSE;
28    LED1 := FALSE;
29    LED2 := FALSE;
30    LED3 := FALSE;
31    LED4 := FALSE;
32END_IF;

The

counter

Global_vars

counter_rec

The complete workspace interface for client Opta™ should resemble the following image once the main PLC code has been successfully compiled and downloaded to the client Opta™:

Finally, Opta™ is now ready as a Modbus TCP Client.

Testing Modbus TCP Communication Between Opta™ Devices (PLC IDE)

You can access the complete example project here.

Set both Opta™ devices running with the corresponding main PLC code with the hardware setup explained in this section. You will be able to observe the following results on client Opta™ periodically:

• Counter value =

  500

  : The status LED #1 and relay #1 will turn on
• Counter value =

  1000

  : The status LED #2 and relay #2 will turn on
• Counter value =

  1500

  : The status LED #3 and relay #3 will turn on
• Counter value =

  2000

  : The status LED #4 and relay #4 will turn on
• Counter value =

  2500

  : All status LEDs and relays will turn off

For a visual representation of this behavior, refer to the following clip:

In the clip, the left window represents the Modbus TCP Client Opta™, while the right window shows the Modbus TCP Server Opta™.

Conclusion

In this tutorial, you have learned how to configure the workspace environment for Modbus TCP using the Arduino PLC IDE and Opta™.

Additionally, through a hands-on example project, you have acquired the skills to verify that Opta™ is correctly set up and that Modbus TCP communication is operating effectively. This project showcased the control of Opta™ device's onboard features, such as relays and status LEDs, based on a custom example.

Next Steps

Now that you have learned to implement the Modbus TCP between Opta™ devices using Arduino PLC IDE, try expanding the setup by integrating additional Modbus TCP compatible devices into the communication network.

Additionally, you can explore the possibilities by leveraging the onboard features of the Opta™ device combined with the Modbus TCP communication network. This combination offers a robust enhancement solution for industrial management systems.

For more information regarding the Modbus RTU protocol implementation on an Opta™, it may interest you to check out "Getting Started with Modbus RTU on Opta™" tutorial.