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 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!
The Productivity Series of PLC can use Modbus TCP remote IO (inputs and outputs) from Stride. The Stride Field I/O Modules are simple and compact. They provide an economical means to connect inputs and outputs to an Ethernet Modbus TCP communication network. Every module operates as a standalone Modbus TCP server and can be configured via a built-in web server.
Previously we looked at the Stride Field Remote IO Modules Modbus TCP Ethernet wiring and configuration.
Stride Field Remote IO Modules Modbus TCP Ethernet
– Unboxing SIO MB12CDR and SIO MB04ADS Video
– Powering and Configuring Video
– STRIDE discrete combo module, Input: 8-point, 12-24 VDC, sinking, Output: 4-point, relay, (4) Form C (SPDT) relays, 2A/point, (1) Ethernet (RJ45) port(s), Modbus TCP server.
– STRIDE analog input module, 4-channel, current/voltage, 16-bit, isolated, input current signal range(s) of +/- 20 mA, input voltage signal range(s) of +/- 10 VDC, (1) Ethernet (RJ45) port(s), Modbus TCP server.
We will be reading an analog voltage into the Productivity 1000 PLC from the remote IO unit. We will then set an output to pulse on and off at a time range indicated by this analog signal. The output will be on the other remote IO unit and will trigger the input to signal. We will look at the Frequency, Count, and Status of this input. Our Productivity 10000 PLC program will also take into consideration watchdog (communication time out) and power-up events for the Stride remote input and output units.
Let’s get started. Keep on Reading!
Productivity PLC – PID Ramp Soak Instruction
The purpose of a ramp soak instruction is to make gradual, controlled changes in temperature (Ramp), followed by a temperature hold (Soak) period.
We will be using our Proportional-Integral-Derivative PID Instruction that we looked at last time to apply the ramp/soak instruction.
Using the immersion heater in a cup of water to keep the temperature at a constant value, we will be adjusting the profile of the temperature as we increase the set point (Ramp) and hold that set point for a predetermined time. (Soak)
We will be modifying our existing program from our PID loop instruction. Let’s get started. Continue Reading!