You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/hardware/07.opta/opta-family/opta/tutorials/10.opta-modbus-tcp-plc-ide/content.md
-8
Original file line number
Diff line number
Diff line change
@@ -105,7 +105,6 @@ The installation wizard will provide all the required drivers, libraries, and co
105
105
For Modbus TCP communication, we will use two Opta™ devices and the PLC IDE.
106
106
107
107
#### Connection and Ethernet Switch Integration
108
-
<br></br>
109
108
110
109
Set up the connection by attaching the Ethernet LAN (RJ-45) cable to both devices using the `ETH RJ45` port. The following image provides a connection diagram for both devices:
111
110
@@ -114,7 +113,6 @@ Set up the connection by attaching the Ethernet LAN (RJ-45) cable to both device
114
113
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.
115
114
116
115
#### Field Deployment Setup
117
-
<br></br>
118
116
119
117
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:
120
118
@@ -132,7 +130,6 @@ In any robust development environment, understanding the intricacies of project
132
130
We highly recommend reviewing [this tutorial](https://docs.arduino.cc/tutorials/portenta-machine-control/plc-ide-setup-license) before delving into the present tutorial.
133
131
134
132
#### Opta™ Basic Configuration
135
-
<br></br>
136
133
137
134
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](https://angryip.org/) to identify the address.
138
135
@@ -153,7 +150,6 @@ The configured IP address for Opta™ also serves to connect and develop within
153
150
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.
154
151
155
152
#### Modbus TCP Client and Server Mode
156
-
<br></br>
157
153
158
154
The image below shows the interface we'll encounter when accessing the Modbus TCP configuration panel in the PLC IDE.
159
155
@@ -169,7 +165,6 @@ If the "Modbus TCP Master" option remains unchecked, the role of a Modbus TCP Se
169
165
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` configuration tab, the introduction of a *General Modbus Node* option can be observed, as will be detailed in the section that follows.
170
166
171
167
#### General Modbus Node Configuration
172
-
<br></br>
173
168
174
169
The General Modbus Node allows to add information regarding the devices compatible with the Modbus messaging service.
175
170
@@ -180,7 +175,6 @@ It will require you to fill in basic information under the `General` tab. The im
180
175
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` range.
181
176
182
177
#### PLC IDE Modbus Custom Editor
183
-
<br></br>
184
178
185
179
This is an alternative way of adding a Modbus node under the `Ethernet` configuration tab. To open the Modbus Custom Editor window, go to `Tools -> Run Modbus Custom Editor` on PLC IDE.
186
180
@@ -203,7 +197,6 @@ For those wishing to skip the step by step procedure, the complete example proje
203
197
In the sections that follow, the configuration of each Opta™, based on its designated role in Modbus TCP communication, will be detailed.
204
198
205
199
#### Modbus TCP Server Opta™
206
-
<br></br>
207
200
208
201
To set Opta™ as a Modbus TCP Server, navigate to the `Ethernet` tab located in the `Resources` panel of the PLC IDE. Since the `Modbus TCP Slave` mode is always enabled, you don't have to change any setting in the current window. Ethernet properties are essential for Opta™ to work properly with Modbus TCP, thus it requires a proper Ethernet configuration.
209
202
@@ -264,7 +257,6 @@ The Opta™ server device's task runs a simple counter and resets whenever the c
264
257
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.
265
258
266
259
#### Modbus TCP Client Opta™
267
-
<br></br>
268
260
269
261
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](#modbus-tcp-client-and-server-mode), this action will designate Opta™ as a Client. Do not worry about the greyed-out Server option.
0 commit comments