Serial Communication with the CP1L and CP1H PLCs
This tutorial is intended to explain serial communication configuration with the CP1L and CP1H PLCs.
The following serial communication option boards can be used on any available option board slot for the CP1 series PLCs.
Note: The single option board slot on the CP1L-L14/20 and CP1L-EL is designated as serial port 1 in CX-Programmer, but uses the flags usually allocated to port 2 of other CP1L/H types. When using ladder instructions or function blocks, specify port 2. See the CP1L CPU Unit Operation Manual (Cat. No. W462) or CP1H CPU Unit Operation Manual (Cat. No. W450) for more information.
Configuration of front switches
Supported protocols in user configuration
Host Link: Various control commands such as reading and writing I/O memory, changing the operating mode, and force setting/resetting bits can be executed by sending C-mode host link commands or FINS commands from the host computer to the CPU Unit. It is also possible to send FINS commands from the CPU Unit to the host computer to send data or information. Use Host Link communications to monitor data, such as operating status, error information, and quality data in the PLC or send data, such as production planning information to the PLC.
Serial PLC Link: Up to ten words per Unit can be shared by up to nine CPU Units, including one Polling Unit and eight Polled Units. An RS-422A/485 Option Boards (CP1W-CIF11/CIF12) are used to communicate via RS-422A/485, or RS-232C Option Boards (CP1W-CIF01) can be used to communicate between two CPU Units via an RS-232C connection. CJ1M CPU Units can also be included in Serial PLC Links, and the Serial PLC Links can also include PTs as Polled Units via 1:N NT Links. Serial PLC Links can be created on serial port 1 or serial port 2, but not on both ports at the same time.
Serial Gateway: Converts received FINS commands into CompoWay/F or Modbus-RTU commands and transfers them on the serial communications path.
No-Protocol: Communicates with standard devices with an RS-232C or RS-422A/485 port without a command–response format. Instead the TXD(236) and RXD(235) instructions are executed from the program to transmit data from the transmission port or read data in the reception port. The frame headers and end codes can be specified.
1:N NT Link: Data can be exchanged with PTs without using a communications program in the CPU Unit. 1:N NT Links are also used for 1:1 connections.
1:1 NT Link: Enables data exchange with a PT without communications programming in the CPU Unit. (The 1:N NT Link protocol is used for communications even for 1:1 connections.)
1:1 Link Master/Slave: Enables linking data in a 64-word Link Area between two PLCs.
Configuration of communication port via STUP instruction
The STUP instruction changes the communications parameters of a serial port on a Serial Communications Option Board. STUP(237) thus enables the protocol mode to be changed during PLC operation. This instruction is not allowed in interrupt tasks. A CX-Programmer project file (STUP Example.cxp) is attached as an example.
Changing the communication format of the serial ports 1 and 2 is indicated by the system flags A619.01 and A619.02. After switching off and being switched back on, the controller incorporates the values in its communication parameters
Host Link Mode values
See the following manuals for additional information
Additional STUP information can be found in the corresponding CPU Instruction Reference Manual. This article does not detail similar functionality for CJ-series communication units (CPU Bus Units) when mounted to the CP1H
This article is intended to supplement official Omron documentation. The provided configurations and information should be thoroughly tested before implementation and may or may not function in specific applications. The user assumes full responsibility of the configuration, integration, performance and application of the provided configurations. For detailed information on the use and general configuration of Omron products, refer to official Omron manuals or contact your local Omron support representative.
All information contained in this document is current as of November 2012 but is subject to change due to product and/or software improvements.