Page History

JTEKT Toyopuc PC10G controllers over Ethernet

Overview

The Toyopuc driver reads and writes controller registers on JTEKT Toyopuc PC10G devices using the Computer Link protocol over the controller built-in Ethernet port. Communication blocks are dynamically created according to the polling cycle defined on the AccessType for each Device Point.

The driver addresses data registers, link registers, present-value and special registers, the relay areas at word granularity, and the expansion data register area. Individual programs on a multi-program controller can be addressed explicitly.

This connector uses the binary command set of the Ethernet port. It is not the ASCII frame used by the RS-422 serial Computer Link, which is a separate protocol on the same controller family.

Controller Configuration

Before connecting, the controller built-in Ethernet port must be configured in PCWin with an IP address and a listening port:

• Own Node IP Address: the IP address the driver will connect to.
• Own Node Port No.: the TCP port the controller listens on.
• Open Protocol: the connection must be set to a TCP passive open so the controller accepts the incoming connection.

A connection configured as a non-specified passive open accepts one client at a time. If another node is already connected on that port, the existing connection is reset.

Channel Configuration

Protocol Options

• BlockSize: maximum bytes per request, two bytes per word. Default is 240, which is 120 words. The protocol limit is 1024 bytes (512 words)1018 bytes on the PC10G built-in Ethernet port. An FL/ET-T-V2 module on a PC3J or PC2J CPU caps at 512 bytes, so lower this value if the controller reports error 0x41.
• TraceFrames: when enabled, every transmitted and received frame is written to the Trace Window as hexadecimal. Intended for diagnostics. Default is false, and it should be left disabled in production.

Node Configuration

Station Configuration

Station syntax: <IP address> ; <Port number>

Where:

• <IP address>: IP address of the controller built-in Ethernet port, matching Own Node IP Address in PCWin.
• <Port number>: TCP port the controller is listening on, matching Own Node Port No. in PCWin.

E.g.: 192.168.1.10; 2000

This protocol carries no station number, so the node requires only the address and port.

Points Configuration

The syntax for the Toyopuc communication points is: <Scope>:<Area>:<Address> <Operand><Address>, written as a single token with no separator.

Where:

• <Scope>: selects which program the address belongs to. Optional. When omitted the point resolves to Own.
• <Area><Operand>: the controller memory area, optionally prefixed with a program number.
• <Address>: the word offset within the area, written in hexadecimal, exactly as displayed in PCWin.

Program Prefix

On a controller running a single program, Own an unprefixed address and the matching program scope prefix return the same data. Scope is ignored when the area is U, which The U area is shared rather than per-program and therefore takes no prefix.

Memory Areas

The relay areas are accessed one word at a time, matching the word-address notation used by PCWin. A relay word address shown as M20W in the programming software is written as M:20 M20 here.

Referencing the Node

In the Devices Points table the Node column takes the fully qualified node reference, Node.<NodeName>, not the bare node name. A node called ToyopucNode1 is referenced as Node.ToyopucNode1. This matters when points are imported from a file rather than picked in the editor.

Examples

Troubleshooting

When a request is rejected, the controller returns an error code that is written to the Trace Window together with its description. The most frequently seen codes are:

If no reply is received at all, confirm the controller port is open and that no other client is holding the connection.

Enable TraceFrames on the channel to capture the exact bytes exchanged when reporting a communication problem.

Driver Revision History

In this section...