We will now utilize Ethernet/IP to connect a Click PLC as remote IO on a Productivity system. The productivity series of controllers can use explicit and implicit messaging techniques of EtherNet/IP to optimize data exchanges across the network.
Explicit messaging means that the data messages that are transmitted will contain everything needed in order to respond or decode the message. It is a normal client/server relationship with instructions explicitly spelled out in the data messages. This communication happens at times that the Client requests the information.
Implicit messaging means the data messages are streamlined. The device is configured ahead of time to know what to do with the data. This is used for time-critical messages and it functions as a typical scanner/adapter relationship. Implicit messaging is real-time. It has the ability to copy data with minimal additional information because both ends already know exactly what each bit and byte.
A Click PLC will be set up as remote distributed inputs and outputs for our Productivity 1000 controller. Implicit Ethernet IP will be set up. The Click will be the Ethernet IP adapter and the Productivity will be the Ethernet IP scanner. Let’s get started. Keep on Reading!
We will now look at P1AM Arduino Modbus TCP communication to the C-More EA9 Series HMI. This will be communicating Ethernet Modbus TCP protocol. The P1AM will be the server (slave) and the EA9-RHMI the client (master).
We will explain how to connect a headless C-more HMI to our P1AM-ETH Industrial Arduino Ethernet Shield.
The P1AM Example from Automation Direct on GitHub will be used.
We will be using the remote android and windows app to connect to the C-More EA9 HMI. This will display the information from our Arduino P1AM on our headless unit. Let’s get started. Continue Reading!
The productivity suite software now contains a plc simulator. The software is a free download and is available from automation direct. This software will now allow you to test or troubleshoot your program without the physical hardware present. The entire family of controllers can use the simulator. P1000, P2000, and P3000 emulation can happen on the following parts of the productivity series hardware:
– P1000 CPU’s and local I/O stack, P2000 and P3000 CPU’s and local bases
– All basic I/O modules, both analog and digital
– Modbus TCP Server/Client connections on external Ethernet port
The simulation mode is available on the Productivity Suite version 3.8.x.x or higher. We will be discussing the PAC (Programmable Automation Controller) PLC Simulator. Testing this simulator will be done using our first program (Start-Stop Circuit) and the PID instruction in our Productivity 1000 series. We will also be connecting to physical hardware after using our simulator to test the program. Let’s get started. Keep on Reading!
We will not look at the productivity 1000 plc modbus ascii protocol to the Solo process temperature controller. This will be done in ladder logic on our productivity 1000 PLC. Modbus ASCII is a communication method used for transmitting information over serial lines between electronic devices. The device requesting the information is called the Modbus Master (Client) and the devices supplying information are Modbus Slaves (Servers). This protocol was originally developed by Modicon systems.
Modbus protocol comes in basically three different types. Ethernet (Modbus TCP) or Serial (Modbus RTU or Modbus ASCII). Modbus TCP and Modbus RTU come as standard protocols in the productivity series of PLCs.
We will connect the Productivity 1000 PLC to a Solo process temperature controller. This will be done using the Modbus ASCII protocol over serial RS485 communication wire. (Media) The present and set values (PV / SV) will be read from the Solo controller and the set value will be written when required. Let’s get started. Keep on Reading!
We will now look at the productivity 1000 plc modbus tcp rtu communication to the BX-MBIO controller.
The Productivity 1000 PLC can communicate to a remote I/O (input and output) controller modules using the Modbus protocol for communications. The BX-MBIO provides both Modbus RTU and Modbus TCP interfaces. Modbus RTU is a serial communication and Modbus TCP is an Ethernet communication. Modbus RTU is supported over an RS-485 serial connection. Modbus TCP is supported over an Ethernet connection. They function as listening/replying devices (slave, server) and can connect with any mastering (master, client) device that communicates using the Modbus protocol.
Previously we looked at the BX-MBIO Modbus RTU TCP Remote IO Controller wiring and configuration.
Modbus RTU TCP Remote IO Controller BX-MBIO
– BX-MBIO Hardware Video
– BX-MBIO Powering and Configuring Video
We will connect the Productivity 1000 PLC to the Modbus remote IO. This will be done using the Modbus TCP and Modbus RTU protocol. Ethernet and serial RS485 communication to the BX-MBIO unit will be the media.
The BX-MBIO remote I/O expansion units feature the following:
• RJ45 Ethernet port for communications via Modbus TCP
• RS485 serial port for communications via Modbus RTU
• Supports up to 8 additional Expansion Modules (Add the discrete or analog I/O you require)
• AC and DC powered units available
• AC powered units include an integral 24VDC auxiliary output power supply
• Power connector and serial port connector included
Let’s get started. Keep on Reading!