OMRON CQM1-AD041 PLC 

OMRON CQM1-AD041 PLC

CJ1-H/CJ1M CPU Unit Ver. 4.0 Upgrades

This section summarizes the upgrades made for CJ1-H/CJ1M CPU Units with

unit version 4.0. CX-Programmer version 7.0 or higher must be used to

enable using the following functions.

Functional Upgrades for Unit Version 4.0

Function

Online Editing of Function Blocks

Section

1-4-1 Online Editing of Function

Blocks

Input-Output Variables in Function Blocks

Text String Support in Function Blocks

1-4-1 Online Editing of Function Blocks

Unit Version 3.0 or Earlier

1-4-2 Input-Output Variables in

Function Blocks

1-4-3 Text String Support in

Function Blocks

CQM1-AD041

Function block definitions could not be changed during operation.

Unit Version 4.0 or Later

Function block definitions can be changed during operation. This allows func

tion block definitions to be quickly corrected during debugging. It also allows

function blocks to be used more easily in systems that operate 24 hours a day.

1-4-2 Input-Output Variables in Function Blocks

Unit Version 3.0 or Earlier

The data size of parameters that could be passed to and from function blocks

was limited to four words maximum. It was thus necessary to separate ele

ments with large data sizes, such as data tables.

1-4-3 Text String Support in Function Blocks

Unit Version 3.0 or Earlier

Unit Version 4.0 or Later

To program text string processing for communications commands and display

data in ladder diagrams, it was necessary to know the ladder string instruc

tions and ASCII codes. Also, several instructions had to be combined to con

verted from numbers to text strings or text strings to numbers.

1-5-1 Function Blocks (FB)

Unit Ver. 2.0 or Earlier

TXDU(256) and RXDU(255) instructions (sup

port no-protocol communications with Serial

Communications Units with unit version 1.2 or

later)

Model conversion instructions: XFERC(565),

DISTC(566), COLLC(567), MOVBC(568), and

BCNTC(621)

Special function block instruction: GETID(286)

TXD(236) and RXD(235) instructions (support

no-protocol communications with Serial Com

munications Boards with unit version 1.2 or

later)

Earlier Units did not support function blocks (FB).

Unit Ver. 3.0 or Later

1-5-6

Function blocks (FB) conforming to IEC 61131-3 are supported. Use of func

tion blocks is determined by the user.

Note IEC 61131-3 is an international standard for programmable logic

controllers (PLC) established by the International Electro-technical

Commission (IEC). This standard is divided into seven parts, of

which Part 3 Programming Languages (IEC 61131-3) provides reg

ulations for programming PLCs.

Function blocks can be created with CX-Programmer Ver. 5.0 or higher by the

user and pasted into normal programs. The standard function blocks provided

by OMRON in the OMRON FB Library can also be pasted into normal pro

grams. Function blocks enable standard processing to be simply inserted into

a program as a single unit. Function blocks provide the following features.

• Function block algorithms can be written using ladder programming or

structured text (see note).

Note Structured text is a high level textual language designed for industrial

control (primarily PLCs) stipulated in IEC 61131-3. The structured

text supported by CX-Programmer Ver. 5.0 conforms to IEC 61131-1.

• A single function block that has been created can be stored in a library for

easy reuse of standard processing.

• Programs that contain function blocks (ladder programming or structured

text), can also be uploaded or downloaded in the same way as normal

programs that do not contain function blocks. Tasks that include function

blocks, however, cannot be downloaded in task units (although they can

be uploaded).

• Array (one-dimensional) variables are supported, making it easier to han

dle data specific to an application.

1-5-2 Serial Gateway (Converting FINS to CompoWay/F Via Serial Port)

Unit Ver. 2.0 or Earlier

Temperature Controllers, Digital Panel Meters, and other CompoWay/F-com

patible OMRON Components previously could be accessed by sending user

specified CompoWay/F commands from the PLC. This required, however, the

use of a Serial Communications Board/Unit protocol macro, execution of the

PMCR(260) instruction in the ladder program of the CPU Unit on the same

PLC, and implementation of the standard system protocol (CompoWay/F

Master). The use of protocol macros prevented access across networks​