Year: 2025

PACSystems controllers and Series 90 PLCs equipped with an I/O Link Master Module.

An I/O Link Interface Module occupies one module slot in an

RX3i backplane.  It can be installed in any available backplane slot.

The maximum number of I/O Link Interface Modules that can be

installed in the backplane depends on the power that is available

from the power supply.  To determine the exact number of

modules allowed in your system, see the information on power

supplies in chapter 3.

Usually, when there are multiple I/O Link Interface Modules in the

same RX3i system, they are on separate I/O Links.  However, it

is possible to have more than one I/O Link Interface Module in

the system connected to the same link, if that suits the needs of the application.

Module Description

The module’s front cover is removable. A jumper plug inside the front cover is used to set up the

module as a 32–point or 64–point I/O module.

Serial Ports

The front of the module has two 20–pin connectors that are used to attach the I/O Link cable.

One connector is for the cable to the previous device on the link––either the master or another

slave. The other connector is for the cable to the next slave on the link, if there is one.  See the

RX3i I/O Link Modules User’s Manual, GFK-2358 for more information. Signal levels are

RS422/485 compatible.

The RX3i I/O Link Interface Module operates as a slave on a

Fanuc I/O Link network.  It can exchange either 32 or 64 inputs

and outputs with the master.  Typical masters on the I/O Link

include all modern FANUC CNCs and Power Mates,

PACSystems controllers and Series 90 PLCs equipped with an

I/O Link Master Module.

An I/O Link Interface Module occupies one module slot in an

RX3i backplane.  It can be installed in any available backplane slot.

The maximum number of I/O Link Interface Modules that can be

installed in the backplane depends on the power that is available

from the power supply.  To determine the exact number of

modules allowed in your system, see the information on power

supplies in chapter 3.

Usually, when there are multiple I/O Link Interface Modules in the

same RX3i system, they are on separate I/O Links.  However, it

is possible to have more than one I/O Link Interface Module in

the system connected to the same link, if that suits the needs of

the application.

The PACSystems* RX3i Ethernet IEC 104 Server Module, catalog number

IC695EIS001. implements the IEC 60870-5-104 communications protocol. It

permits a PACSystems RX3i controller to be connected to an Ethernet

network using a standard TCP/IP connection scheme, allowing an IEC 104

Client to poll data from the Server, as well generate unsolicited

communications from the Server back to the Client.

Two auto-sensing 10BaseT/100BaseTX RJ-45 shielded twisted-pair Ethernet

ports permit direct connection to either a 10BaseT or 100BaseTX IEEE 802.3

network without an external transceiver. Line, Star and Daisy Chain topologies are supported.

The RX3i Ethernet IEC 104 Server Module hosts the IEC104 Server side

protocol on a common RX3i ETM001 module hardware platform. Thus, many

of the specifications and behaviors are shared with the ETM001 module

including protocol support. IC695EIS001 is an Ethernet-connected module

that fits in the RX3i backplane and permits the RX3i to behave as a Server on

the IEC104 network. The data exchanges between the EIS001 module and

IEC104 Client(s) are configurable, using a single COMMREQ instruction in the

ladder logic or Structured Text program.

Module Features

• Supports eight client connection to the RX3i Controller data set specified

in the configuration. [RBE supported only on one Client connection

associated with a specified port -Refer to GFK-2949B for details]

• Supports Interrogation and RBE for Single Point and Double Point data.

• Supports Interrogation and RBE for Regulated Step.

• Supports Interrogation and Measured data sets for Scaled, normalized,

and single precision Float.

• Supports 56-bit IEC 60870-5-104 time format, with the default being

56-bit time format.

• Supports Time Set, and query of the RX3i Controller CPU Clock in UTC time.

• Cause of Transmission size is two octets.

RX3i Interface specifications:

• Up to four EIS001 per RX3i, as allowed by available power and slots.

• Module can be installed in any available RX3i main rack I/O slot.

• Module supports insertion into and removal from an RX3i backplane

which is under power.

• Firmware upgrade through RX3i CPU using WinLoader software utility.

DeviceNet Cable

Either DeviceNet thick cable or thin cable can be used.  Thick cable permits greater cable

lengths and higher current levels. Generally, thick cable is used for the trunk cable.  Thin cable

is normally used for shorter distances and is suitable for drop cables and for installations where

more cable flexibility is needed. Both thick cable and thin cable are 5-wire, multi-conductor

copper cable.  Two wires form a transmission line for network communications. A second pair

transmits network power.  The fifth conductor forms an electromagnetic shield. Most cables

have color coded leads which correspond to the color coding on the terminals on the DeviceNet

Master Module.

Power Requirements

The DeviceNet Master module consumes 450mA at 5VDC (typical) from the PLC backplane.

This power is used for module operation, The DeviceNet Master powers its network transceiver

from the 24VDC DeviceNet network power source. Linear power supplies are recommended for

the DeviceNet power source. The DeviceNet power source should not also be used for device

power. Transients caused by  I/O devices can cause communications errors and even create

bus-off conditions.

The DeviceNet specification recommends using a power tap to connect a power supply to the

network. The power tap should be appropriately fused for the current capacity of the bus cables.

The maximum current on the network depends on the cable type.

The DeviceNet network power supply must be grounded, but only at one point.  The V- signal

must be connected to protective earth ground at the power supply only.  If multiple power

supplies are used, only one power supply must have V- connected to earth ground.

Power Requirements

The DeviceNet Master module consumes 450mA at 5VDC (typical) from the PLC backplane.

This power is used for module operation, The DeviceNet Master powers its network transceiver

from the 24VDC DeviceNet network power source. Linear power supplies are recommended for

the DeviceNet power source. The DeviceNet power source should not also be used for device

power. Transients caused by  I/O devices can cause communications errors and even create

bus-off conditions.

The DeviceNet specification recommends using a power tap to connect a power supply to the

network. The power tap should be appropriately fused for the current capacity of the bus cables.

The maximum current on the network depends on the cable type.

The DeviceNet network power supply must be grounded, but only at one point.  The V- signal

must be connected to protective earth ground at the power supply only.  If multiple power

supplies are used, only one power supply must have V- connected to earth ground.

Current Limit for Thick Cable

For thick cable, the maximum current on the network is 16 Amps.  However, only 8 Amps is

permitted on a single network segment. 16 Amps can be drawn from a single power supply by

locating the power supply at the center point of two network segments, supplying 8 Amps to

each segment.

Current Limit for Thin Cable

For thin cable, the maximum current permitted is 3 Amps.

Bus Length

The maximum length of the trunk cable and drops both depend on the cable type and data rate.

Individual drops may not exceed 6 meters and are limited to one network node per drop.

However, the node may have multiple ports.

For each baud rate, the total drop length is the sum of all the drop lines of both cable types in

the network.

In addition, if the distance from a tap to the most distant device on its drop is longer than the

distance from the tap to the nearest terminating resistor, the drop line length also counts as part

of the trunk cable length (as well as the overall drop length).

DeviceNet Cable

Either DeviceNet thick cable or thin cable can be used.  Thick cable permits greater cable

lengths and higher current levels. Generally, thick cable is used for the trunk cable.  Thin cable

is normally used for shorter distances and is suitable for drop cables and for installations where

more cable flexibility is needed. Both thick cable and thin cable are 5-wire, multi-conductor

copper cable.  Two wires form a transmission line for network communications. A second pair

transmits network power.  The fifth conductor forms an electromagnetic shield. Most cables

have color coded leads which correspond to the color coding on the terminals on the DeviceNet

Master Module.

LEDs and Connectors

The module’s three DeviceNet-compliant LEDS show its operating and communications status.

The RS-232 serial port is used for a computer connection during firmware upgrades. The

DeviceNet connector is a removable spring-clamp terminal. It provides bus continuity and can

be removed from the module without disrupting bus operation.

The DeviceNet Bus

Devices can be connected directly to the trunk cable, or to drop lines that are joined to the trunk

cable with taps. Taps can be mounted in junction boxes or panels. Drop lines and daisy-chains

are often used inside control panels where multiple devices are grouped together.  When using

drops with daisy-chains and branches, the maximum length from a tap to its farthest drop is 20 feet.

Current Limit for Thick Cable

For thick cable, the maximum current on the network is 16 Amps.  However, only 8 Amps is

permitted on a single network segment. 16 Amps can be drawn from a single power supply by

locating the power supply at the center point of two network segments, supplying 8 Amps to

each segment.

Current Limit for Thin Cable

For thin cable, the maximum current permitted is 3 Amps.