Many questions come from serial communications using the Click PLC. Most of these questions deal with communication timing when using multiple send and receive instructions. We will show you how to deal with serial communication timing in the Click PLC.
Receive and Send instructions will allow you to send and receive serial data to an external device. The communication method that you set up can be ASCII or Modbus. ASCII (American Standard Communication for Information Interchange) can be used to send to devices such as a printer. Receiving ASCII can be used for connecting barcode scanners to the PLC. The barcode will be read as an ASCII string in the PLC. Modbus serial communication (Modbus RTU) is a standard protocol used in many automation devices.
We will demonstrate the Send and Receive instruction by communicating Modbus RTU to a Solo Temperature Controller. Parameters from the Solo process temperature controller will be read using multiple receive instructions. The send instruction will be used multiple times as well to set the Set Value (SV) and Limits of the SV value entered in the temperature controller. The set values will only be changed when required. Let’s get started. Keep on Reading!
We will now look at the data logging capability using our Click plus PLC.
Data logging is the collection of data over time. This is usually used for data analysis at a later time. The amount of data (System Information) stored and the frequency of the storage will depend on your specific application.
The hardware used to store the data is usually called a data logger. Using the information from our last post, the MQTT information collected (Temperature in Atlanta and Click Analog) will now be logged in two different ways. A micro SD card on the Click Plus will be used to store the data every minute in a CSV (Comma Separated Value) file. Node-RED will also be used to store the same data in a SQL database. Let’s get started on how to use these data loggers. Keep on Reading!
The click plc has a real-time clock that will allow us to control outputs based on a date or time of day. This real-time clock (RTC) can be set from the click programming software or through the program of the controller. Our programs in the click can use the following calendar and clock values:
SD19 – RTC Year – 4 digits (2021)
SD20 – RTC Year – 2 digits (21)
SD21 – RTC Month – (00 to 12)
SD22 – RTC Day – (00 to 31)
SD23 – RTC Day of the Week – 1 Sunday to 7 Saturday
SD24 – RTC Hour – (00 to 23)
SD25 – RTC Minute – (00 to 59)
SD26 – RTC Second – (00 to 59)
We will be using the RTC – Real Time Clock in a sample program. This program will turn on an output Monday to Friday from noon until 1 pm. It will also adjust for daylight savings time. Let’s get started. Keep on Reading!
We will now look at the click plc modbus ascii protocol. This communication will happen in PLC ladder logic and communicate through the serial port (RS485) to a Solo process temperature controller. Modbus ASCII will be the communication protocol.
Modbus 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 Click 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!
The Click 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 for remote IO. 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 Click Ethernet 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!