Configuring PT210 Load Data on an Omron CJ2 PLC via RS-232C

After the fix, the CJ2 PLC reads the PT210 weight stream digitally through RXD, eliminating analog conversion and scaling as sources of disagreement with the indicator display. Use RS-232C streaming for the shortest commissioning path. The indicator’s Ethernet port uses Modbus TCP, not EtherNet/IP.

Connection Options and Recommendation

The installation uses an Omron Cj2m_Cpu31 PLC and a PT210 weighing indicator. Three connection paths require different PLC resources and software.

Do not select a protocol from the connector type alone. An Ethernet socket does not imply EtherNet/IP support. The endpoints must implement the same application protocol and agree on how weight data is represented.

Commissioning Prerequisites

Before anything else, confirm the serial settings and message format in the PT210 documentation. Record the baud rate, data bits, parity, stop bits, streaming selection, frame length, field order, sign representation, decimal-point handling, units, and message terminator. Do not move on until each setting has a matching PLC configuration or a defined parsing rule.

1. Confirm that the CJ2 serial interface is electrically RS-232C and available to the application.
2. Identify the indicator transmit, receive, and signal-ground terminals. Determine from the equipment pinouts whether transmit and receive conductors must cross between devices.
3. Configure the PT210 for streaming output.
4. Configure the receiving device for exactly the same serial framing. A baud-rate, parity, or stop-bit mismatch commonly produces missing or corrupted characters.
5. Document the complete frame using the indicator manual. Do not infer byte positions from one displayed weight because signs, leading spaces, overload indications, and decimal placement can change the frame.

If Ethernet remains under consideration, locate the PT210 Modbus TCP register definitions and data encoding. Then verify that the selected CJ2 Ethernet port and PLC program can act as the required Modbus TCP client. EtherNet/IP Network Configurator and an EDS file apply to an EtherNet/IP device; they do not convert a Modbus TCP server into an EtherNet/IP adapter.

PT210 Streaming Test

Prove the indicator output independently before writing PLC receive logic. A PC terminal test separates indicator configuration and cabling faults from PLC programming faults.

1. Connect the PT210 RS-232C interface to a PC serial port or suitable adapter using the pinout required by both devices.
2. Open a serial terminal such as Realterm and enter the indicator’s configured baud rate, data bits, parity, and stop bits.
3. Enable streaming on the indicator and observe several complete transmissions.
4. Apply at least three stable load conditions, including zero and two nonzero values. Save the raw characters for each condition.
5. Identify the start of the weight field, sign, digits, decimal handling, unit characters, status characters, and terminating character or characters from the documented frame definition.
6. Interrupt the cable or stop streaming briefly, then restore it. Confirm that complete frames resume predictably.

Do not connect the PLC until the terminal displays repeatable, correctly delimited frames. Garbled terminal data points to serial-format or wiring errors. Correct-looking but incomplete frames point to termination, receive-buffer, or display-mode problems.

CJ2 Receive Configuration and Logic

Match the CJ2 serial-port settings to the values proven during the PC test. The PLC must know when a message is complete and must allocate enough receive storage for the documented frame. Use RXD to transfer received serial data into PLC memory.

1. Set the CJ2 port mode and serial framing to match the PT210.
2. Allocate a receive buffer longer than the largest documented indicator frame. Keep the raw received data separate from the numeric weight destination.
3. Execute RXD according to the CJ2 serial-port operating method and the selected completion condition.
4. Accept a frame only when its received length and terminator match the PT210 format. If the format defines status or validity characters, test them before using the weight.
5. Copy the weight characters into a parsing buffer, remove only documented separators or unit characters, and process the sign and decimal position explicitly.
6. Update the control-program weight tag only after the entire frame passes validation. Retain the previous valid value or raise a data-invalid state when a frame fails.

Streaming normally removes the need to transmit a request, so TXD is not part of the normal receive cycle unless the selected PT210 mode requires a command. Prevent repeated RXD triggering from overwriting an unprocessed message. Use a receive-complete state, parse the captured frame, clear or re-arm the receive operation, and then wait for the next complete frame.

Weight Conversion and Data Validity

Digital communication removes the analog converter and analog input from the signal path, but it does not remove format errors. Treat the received message as structured data rather than immediately converting every numeric-looking character.

Keep three values visible during commissioning: raw received characters, parsed numeric weight, and a communication-valid flag. If the indicator transmits engineering units, preserve or validate that field so a configuration change cannot silently alter the meaning of the number.

Verification and Recurring Pitfalls

1. Compare the parsed PLC value with the PT210 display at zero and at multiple stable loads across the operating range.
2. Confirm sign and decimal placement with values that exercise both fields.
3. Cycle PLC power and indicator power separately. Verify that the receive sequence restarts without a manual buffer reset.
4. Disconnect the serial cable. Confirm that the program declares the data invalid instead of holding a stale value as live process data.
5. Reconnect the cable and confirm automatic recovery on a complete valid frame.
6. Expose invalid-frame counts or a communications status bit for maintenance diagnostics.

Common commissioning mistakes include treating Ethernet as a universal protocol, using EtherNet/IP configuration for a Modbus TCP device, parsing a partial streaming frame, and validating only one positive load. Do not move the weight into control logic until framing, status, sign, decimal position, freshness, and recovery have all been tested.

FAQ