The Click Plus PLC has now been released. This can only be programmed with version 3.00 or higher of the Click Programming Software. Version 3.00 will program all of the Click PLC CPU units and add additional features to the Click Ethernet CPU units.
Features of the new Click PLUS PLC (C2-0xCPU) includes the following:
• Micro USB
• DHCP support
• DNS support
• Wi-Fi (programming and Modbus TCP)
• Bluetooth (Wi-Fi) provisioning
• SD Card (Data Logging)
• Data Logger
• Network Time Service
• MQTT (Publish/Subscribe)
• Required PLC Password
• Disable Ports
• Strong Password Support
• Disable Ping Response
• Encrypted Password Transfer
We will be installing version 3.00 of the Click programming software on our windows 10 computer. After starting the software we will review some of the new features. Let’s get started. Keep on Reading!
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!
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!