Host Link, protocol macro, NT Link, or loopback test can beselected for each port.Unit Ver. 1.2 or later also supports Serial Gateway, no-protocol, and 1:1 Host Link modes. (Note: The Serial Gatewaycan also be executed in protocol macro mode.) *1Unit Ver. 1.3 or later also supports Modbus-RTU slave mode.

Port 2

NumberofmountableUnits

CPU Unit

None

CPU Rack

A total of up to 16 Units, including all otherCPU Bus Units. Norestrictions on the mounting location.However, if an external interrupt task is used,the Unit must be mounted in one of thefollowing slots on the CPU Rack.CJ2H-CPU6[]-EIP CPU Unit: Slots 0 to 3CJ2H-CPU6[], CJ2M-CPU[][] or CJ1G/H-CPU[][]H CPU Unit: Slots 0 to 4CJ1M-CPU[][] CPU Unit: Slots 0 to 2External interrupt tasks will not be started ifthe Unit is mounted to any other slot.

A total of up to 16 Units, including all other CPU Bus Units.No restrictions on the mounting location.

ExpansionRack

Dataexchangewith theCPU Unit

Ordinaryrefreshingof softwareswitchesand status

Allocated 25 words of the 25 words in the CPU Bus Unit CIO Area (constant data exchange with the CPU Unit)

Transferfrom theCPU Unitset by thesystem

Of the CPU Bus Unit DM Area, each serial port is allocated 10 words (total 20 words).Data is transferred from the CPU Unit at the following times:Startup or restartLadder instruction: STUP (237)Port Settings Changing Flag turns ON (Auxiliary Area)

Simple Backup Function

The CPU Unit's Simple Backup Function can be used to backup the Protocol Macro data in the SerialCommunications Unit to the CPU Unit's Memory Card. The backed-up data can be restored or compared.(The Simple Backup Function can be used with the CJ1-H and CJ1M CPU Units only.)

Current consumption*3

280mA+x

400mA

360mA+x

280mA+x

380mA

380mA+x

Weight

160g Max.

120g Max.

140g Max.

110g Max.

110g Max.

110g Max.

General specifications

Conforms to general specifications for CJ Serise.

*1. Serial Gateway: The Serial Gateway can also be executed in protocol macro mode.
*2. No-protocol: An external interrupt task can be executed when data is received in No-protocol Mode. If the CJ2H CPU
Units with unit version 1.1 or later and CJ2M CPU Units is used, the high-speed communications instructions
(DRXDU(261) and DTXDU(262)) can also be used.
*3. The current consumption is for one Serial Communications Unit. When an NT-AL001 Link Adapter is connected to the
Serial Communications Unit, power is supplied to the Link Adapter from the Unit. A current consumption of 0.15A
must be added for each Link Adapter that is connected. In the above specifications, “x” indicates that 0.15A must be
added for each port to which an NT-AL001 Link Adapter is connected to provide the required 5-V power supply.

*1. Confirm the baud rates and communications distance supported by connected devices.
*2. The CJ1W-SCU[]2 is required for communications at 230,400 bps.
*3. The maximum cable length for RS-232C is 15 m. The RS-232C standard, however, does not cover baud rates above
19.2 Kbps. Refer to the manual for the device being connected to confirm support.
*4. The specified frame format must be prepared on the host computer and then sent.
*5. The host computer must interpret the commands and return a response in the correct format.
Connection between the host computer and Controller must be 1:1.

Protocol Macro Function Specifications

Item

Description

Number ofprotocols

20 max.

Can be created and registered with the Protocol Support Tool (CX-Protocol).

Area in which data is exchanged between the CPU Unit and the Serial Communications Unitduring Communications Unit refreshing.Two areas are possible for each device: An area for storing receive data and an area for storingsend data. *3

0.01 to 0.99 s, 0.1 to 9.9 s, 1 to 99 s, or 1 to 99 minutes(Only when the command is SEND or SEND&RECV)

With or withoutresponse write(operand)

When receive processing is completed (when the receive data is stored in the area specified inthe 4th operand of the PMCR(260) instruction), whether or not to store the received messagescan be selected.

Next processing

When a step has ended normally, End (sequence completed), Next (proceed to the next step No.),Goto (go to the specified step No.), or Abort (interrupt the step and terminate that sequence)can be selected.

Error processing

When a step has ended abnormally, End, Next, Goto, or Abort can be selected.

Send message

Data sent to the specified address when thecommand is SEND or SEND&RECV.

Data sent from the specified address when thecommand is RECV or SEND&RECV.

Reception matrix

When the command is RECV or SEND&RECV,sets the expected receive messages (15 max.),and switches to the next processing accordingto the message received.

Specifies the receive messages and the nextprocessing for each of cases No. 00 to No.15. Of the maximum 16 cases, one case mustbe set as "Other" in the receive messages(in addition to the set receive messages).

Messageunitcontents

Header andterminatordataattributes

Constant

ASCII data, hexadecimal data, or control code

Dataattributesofaddressesand data insend/receivemessages

Constant

ASCII data, hexadecimal data, or control code (with an address, no control code is possible)

Variable

No conversion, conversion to ASCII data, or conversion to hexadecimal data(the read/write direction can be specified)

Set leading address+ n (The linearexpression aN + b,including repeatcounter N, is alsopossible for n.)

Specify using a linkword.

I/O memory directdesignation

Word write(receive datato I/O memory)

Specify using the4th operand of thePMCR(260) instruction.

Specify using a linkword.

I/O memory directdesignation

Wild card

*

Any data or address can be received(only in receive messages)

Repeat counter

N

Y

Linear expressionincluding repeatcounter

aN+b

a: 0 to 1000; b: 1 to 1000N: Repeat counter value

Wild card

*

Can be received regardless of the length(only in receive messages)

Word designation

Word read(I/O memoryto send data)

Specify using the3rd operand of thePMCR(260) instruction.

Set leading address+ n (The linearexpression aN + b,including repeatcounter N, is alsopossible for n.)

Specify using a linkword.

I/O memory directdesignation

Error check codes

LRC, LRC2, CRC-CCITT, CRC-16, SUM, SUM1, and SUM2 can be calculated.

Maximum length ofsend/receivemessages

1,000 bytes. (A maximum length between 200 and 1,000 bytes can be set in the Setup Area.)

Maximum number ofdata attributesregistered in onemessage

96 attributes *5

Maximum number ofwrite data attributesregistered in onemessage

30 attributes *6

Trace function *7

A total of up to 1,700 bytes (characters) of time-series data can be traced in send and receivemessages.Changes to the step No. and control signals such as RS and CS can also be traced.

*1. The baud rate and the communications distance sometimes depend on the remote device.
*2. A baud rate of 57,600 bps can be selected when using Unit Ver. 1.2 or later (115,200 bps is not possible). The CJ1W-
SCU[]2 is required for communications at 115,200 or 230,400 bps.
*3. Unit Ver. 1.2 or later supports continuous I/O refreshing in addition to the previous on-request I/O refreshing.
*4. The data size is the number of bytes on the transmission path.
*5. The CX-Protocol can be used to register up to 96 attributes per message.
*6. A macro syntax error will occur when the protocol macro is executed if more than 31 write attributes are registered in
one message.
*7. The CPU Unit is set to the RUN/MONITOR mode. (MONITOR mode is not available with the NJ-series CPU Units.)
Note: When using 2-wire RS-422A/485 communications in Protocol Macro Mode, set only modem controls for the send
control parameters, and do not use RS/CS flow controls.

Serial Gateway Specifications

The received FINS command sent to the Unit's serial port is converted according to the FINS command code as follows:2803 hex: FIN header removed and converted to Compo-Way/F command.2804 hex: FIN header removed and converted to Modbus-RTU command.2805 hex: FIN header removed and converted to Modbus-ASCII command.The converted command is sent to the serial port.When the received FINS command is sent to the Unit (user-specified FINS command code), the FINS command isenclosed in a Host Link header and terminator.

Up to five FINS commands can be converted and then queued for processing.

Protocol macroexecution processing

When a FINS command is received during protocol macro execution, the Serial Gateway is executed using an interrupt between steps in the communications sequence. If the next step is a RECEIVE command, the Serial Gateway will not be executed until the next step. For other conditions, the interrupt is executed immediately. *1

Response timeoutmonitoring

The time is monitored from when the message is converted into the specified protocol using the Serial Gatewayuntil the response is received (in Serial Gateway mode or protocol macro mode).Default: 5 s (setting range: 0.1 to 25.5 s) *2

Send start timeoutmonitoring

The time is monitored from when the FINS command is received until it is converted into the specified protocol andstarts to be sent (in protocol macro mode only).Default: 5 s (setting range: 0.1 to 25.5 s) *3

Send delay

The time can be set from when the message is converted into another protocol using Serial Gateway conversionuntil the data is actually sent. (Serial Gateway or protocol macro mode)Default: 0 s (setting range: 0.01 to 300.00 s)

*1. The reception buffer is cleared during Serial Gateway execution.
The Serial Gateway can be prohibited in protocol macro mode by turning ON the Serial Gateway Prohibit Switch in the
CIO Area.
*2. When a timeout occurs, the FINS end code (0205 hex: Response timeout) is returned to the source of the FINS
command and a response is received after a timeout occurs.
*3. When a timeout occurs, the FINS end code (0204 hex: Remote node busy) is returned to the source of the FINS
command. The send processing will not be executed and the received FINS command will be discarded.

Set either of the following types in the Setup Area in the allocation DM Area.1. Data only (without start code and end code)2. Start code + data3. Data + end code4. Start code + data + end code5. Data + CR + LF6. Start code + data +CR + LF

Set in allocated DM Area(The start code can be included by setting it to between 00 and FF hex, and the end code can be included bysetting it to between 00 and FF hex. To exclude the end code, set the number of receive data bytes.)

Start code

None or 00 to FF hex

End code

None, 00 to FF hex, or CR + LF

Number of receive databytes during reception

Set the number of receive data bytes between 1 and 256 bytes (according to the DMArea settings) when frame structure 1 or 2 above is used.

Sending messages

CJ: TXDU (256) instruction *3

NJ: SerialSend instruction

Receiving messages

CJ: RXDU (255) instruction *3

NJ: SerialRcv or SerialRcvNoClear instruction *4

Maximum messagelength

Sending and receiving: Up to 259 bytes including the start code and end code (up to 256 bytes excludingstart/end codes)

Data conversion

No conversion

Communicationsprotocol

None

Message delay time

CJ:When the TXD (236), TXDU (256) instruction is executed, after the send delay time, the data is sent from theport. *30 to 300 s (0 to 300,000 ms)(Can be set in 10-ms units depending on the DM Area settings)

NJ:When the SerialSend instruction is executed, after the send delay time, the data is sent from the port.0 to 300 s (0 to 300,000 ms)(Can be set in 10-ms units: Set in System Studio or by using a device variable for CJ-series Unit.)

Receive counter

The number of data bytes (0 to 256) received at the port can be counted.

Reception buffer cleartiming

CJ1W-SCU[]1-V1The reception buffer is cleared immediately after executing the RXD(235)/RXDU(255) instructionCJ1W-SCU[]2With the DRXDU (261) instruction, you can specify whether the reception buffers will be cleared or not in a settingin the DM Area words allocated to the Unit. *3NJSerialRcv instruction: After reading the receive dataSerialRcvNoClear instruction: When the receive data size variable (Size) is set to 0 *4

*1. The baud rate and the communications distance sometimes depend on the remote device.
*2. The CJ1W-SCU[]2 is required for communications at 115,200 or 230,400 bps.
*3. The DTXDU (262) and DRXDU (261) instructions can be used only when a CJ1W-SCU[]2 Serial Communications Unit
is connected to the CJ2H CPU Units with unit version 1.1 or later and CJ2M CPU Units.
*4. A Serial Communications Unit with unit version 2.1 or later, a CPU Unit with unit version 1.03 or later, and Sysmac
Studio version 1.04 or higher are required to use the SerialRcvNoClear instruction.