Copyright: ©2003 CTC Parker Automation  GA-83463-105


Welcome
Interact Cable Dictionary

Welcome to the Interact Cable Dictionary. This dictionary has been provided to organize every cable diagram for every driver included with the Interact software. With this dictionary, we can more easily provide you with up-to-date cable diagrams and more efficient customer support.

To locate the cable diagrams for the driver you are using, first click the driver family name from the list below or in the table of contents. You will then be provided with a list of all drivers within this family supported by Interact. Select your driver from this list.

ACCESS	Galil	NetBIOS	Sutherland-Schultz
Allen-Bradley	GE	Omron	Telemecanique
ASCII	Giddings and Lewis	Opto 22	Texas Instruments
Bristol Babcock	Indramat	Profibus	Yaskawa
Compumotor	Klockner Moeller	Reliance
Delta Tau	Mitsubishi	Siemens
DeviceNet	Modicon	Square D


Allen-Bradley Drivers

Below is a list of all Allen-Bradley drivers supported by Interact.

Data Highway

Ethernet

Remote I/O

SLC-500


ACCESS Drivers

Below is a list of all ACCESS drivers supported by Interact.

4000


ASCII Drivers

Below is a list of all ASCII drivers supported by Interact.

ASCII


Bristol Babcock Drivers

Below is a list of all Bristol Babcock drivers supported by Interact.

Bristol Babcock


Compumotor Drivers

Below is a list of all Compumotor drivers supported by Interact.

Gem6K/6K/6000 Series


Reliance Drivers

Below is a list of all Reliance drivers supported by Interact.

DCSNET

AutoMate

R-NET


DeviceNet Drivers

Below is a list of all DeviceNet drivers supported by Interact.

DeviceNet


Omron Drivers

Below is a list of all Omron drivers supported by Interact.

FINS Host Link

Host Link

SLNK SYSLINK

SMAC SYSMAC Network


Galil Drivers

Below is a list of all Galil drivers supported by Interact.

Galil


GE Drivers

Below is a list of all GE drivers supported by Interact.

Series 6 CCM2

Fanuc Genius I/O

Series 90 SNP

Series 90 SNPX


Giddings and Lewis Drivers

Below is a list of all Giddings and Lewis drivers supported by Interact.

PIC 900


Indramat Drivers

Below is a list of all Indramat drivers supported by Interact.

CLC Motion Control


Klockner Moeller Drivers

Below is a list of all Klockner Moeller drivers supported by Interact.

PS416


Modicon Drivers

Below is a list of all Modicon dirvers supported by Interact.

Modbus Ethernet

Modbus Plus

Modbus


Mitsubishi Drivers

Below is a list of all Mitsubishi drivers supported by Interact.

FX

A

AJ71C24

A7BDE

Q


NetBIOS Drivers

Below is a list of all NetBIOS drivers supported by Interact.

NetBIOS


Square D Drivers

Below is a list of all Square D drivers supported by Interact.

Sy/Link

Serial


Siemens Drivers

Below is a list of all Siemens drivers supported by Interact.

HMI Adapter

S5 Programming Port

RK-512

S7-PPI

Koyo ECOM Ethernet

Koyo Series 205/305/405

TI Ethernet

TIWAY


Sutherland-Schultz Drivers

Below is a list of all Sutherland-Schultz drivers supported by Interact.

SD


Telemecanique Drivers

Below is a list of all Telemecanique drivers supported by Interact.

Uni-Telway


Texas Instruments Drivers

Below is a list of all Texas Instruments drivers supported by Interact.

Series 500

Remote I/O


Yaskawa Drivers

Below is a list of all Yaskawa drivers supported by Interact.

Yaskawa

Memobus


Allen-Bradley Ethernet Connection Information

For the ABEN device driver to communicate with a controller, you must have the following software installed in your computer:

•	MachineShop Shell version 1.0 or higher

•	TCP/IP stack version 1.02 or higher

The diagrams below show the connections required for the ABEN driver to communicate with a controller through the Ethernet port on a PowerStation.

*Note: This driver must be used in conjunction with a HUB or switch.

Ethernet Point-to-Point (Cross Over Cable) 10BaseT/100BaseT Connection

Ethernet Hub Connection (Straight Through)

Ethernet Hub Connection using ENI


ACCESS 4000 Connection Information

Data Link Connectors

The data link is the connection scheme used by the ACCESS4000 network. The data link connectors connect the ACCESS4000 data link to the PCI card.

On the PCI card the connectors are labeled A and B for reference only; either connector may be used for either data link cable.

These connections allow the data link to pass through the PCI card and continue to the next ACCESS4000 module. If the PCI card is the last one in the ACCESS4000 network, you must install a 75 ohm terminator on the unused data link connector.

Data link connections to the PCI card are shown below.

Connect a data link cable to the PCI card by inserting the center conductor of the "F" connector into the hole in the mating PCI card connector.

Screw the "F" connector shell over the PCI card connector and tighten. Make certain the connection is snug; a loose connection will cause erratic system performance.

Caution   Do not let the "F" connectors touch any metal surface.

The ACCESS4000 data link uses 75 ohm coaxial cable and standard "F" type connectors to attach the cable to the PCI card. See the Making Data Link Cables topic in the ACCESS 4000 main help for complete instructions on making data link cables.

Important...To insure that the ACCESS4000 system achieves optimum performance use only BELDEN 9248 cable. Other cables have not been verified to conform to the high performance specifications of the ACCESS4000 system.


Mitsubishi A7BDE Connection Information

A7BDE-A3N Programmable Controller Option Card

The Programmable Controller Option Card (A7BDE-A3N) is actually a system of three cards. Together they enable an on-board A3N PLC CPU and allow access to MELSECNET and MELSECNET/MINI. The following three option cards make up the system.

•	The A7BDE-A3N-A MELSECNET/MINI Interface Card allows the installed A3N CPU Programmable Controller to be configured as the master station of a MELSECNET/MINI network. This card is regarded by the A3N CPU as occupying the second slot of a rack system and operates in the same manner as the A-PLC rack mounted MELSECNET/MINI master unit (AJ71PT32).

•	The A7BDE-A3N-B.C Programmable Controller Option Card is an A3N CPU with an MCPU that is regarded by the A3N CPU as a special function unit occupying the first slot of a rack system.

•	The A7LU1P21/R21 MELSECNET Interface Card allows the installed A3N CPU Programmable Controller to be configured as a master or local station of the MELSECNET network.

The following six switches must be set for proper operation of the Programmable Controller Option Card:

A7BDE-A3N-A MELSECNET/MINI

Mode Number Setting

Switch No.	Switch Name	Contents
0	ON-LINE(A.R.)	System automatically returns to on-line.
1	ON-LINE(U.R.)	System does not automatically return to on-line.
2	ON-LINE(E.S)	System stops when on-line error is detected.
A7BDE-A3N-B.C

Board Number Setting

Dial Number	Memory Area Head Address	I/O Port Number Head Address 100H               300H
0	D0000H	100H               300H
1		1100H           1300H
2	D4000H	2100H           2300H
3		3100H           3300H
4	D8000H	4100H           4300H
5		5100H           5300H
6	DC000H	6100H           6300H
7		7100H           7300H
8		DO NOT SET
9		DO NOT SET
I/O Port Number Offset

The I/O Port Number Offset is specified by means of a "jumper connector" and may be set to either 100H or 300H.

Board IRQ Number Setting

Dial Number	IRQ Number
0	3
1	4
2	5
3	7
4	10
5	11
6	12
7	15
8	DO NOT SET
9	DO NOT SET
A7LU1P21/R21

Station Number Setting

Dial X10: X10 switch sets the "10s" position of the station number.

Dial X1: X1 switch sets the "1s" position of the station number.

Setting for the master station is (00). Settings for local stations are between (01) and (64).

Mode Number Setting

Setting No.	Name	Description
0	On-line	Automatic return to on-line during normal operation.
1	On-line	No automatic return to on-line during normal operation.
2	On-line	Said station is disconnected from line.
Refer to the Mitsubishi Documentation for more information about these settings.

A7BDE-RS4 Serial Port Interface Board

The Serial Port Interface Board (A7BDE-RS4) enables access to the RS422 port of an A-CPU. The board can communicate directly with the CPU to which it is connected. If connected to the master station, the board can also communicate with any station on MELSECNET (or with the master station if connected to a local station).

The following three switches must be set for proper operation of the Serial Port Interface Board:

Board Number Setting

Dial Number	Memory Area Head Address	I/O Port Number 100H offset        300H offset
0	D0000H	100H                   300H
1	D2000H	1100H               1300H
2	D4000H	2100H               2300H
3	D6000H	3100H               3300H
4	D8000H	4100H               4300H
5	DA000H	5100H               5300H
6	DC000H	6100H               6300H
7	DE000H	7100H               7300H
8		DO NOT SET
9		DO NOT SET
I/O Port Number Offset

The I/O Port Number Offset is specified by means of a "jumper connector" and may be set to either 100H or 300H.

Board IRQ Number Setting

Dial Number	IRQ Number
0	3
1	4
2	5
3	7
4	10
5	11
6	12
7	15
8	DO NOT SET
9	DO NOT SET
Refer to the Mitsubishi A7BDE Documentation for more information about these settings.

The Serial Port Interface Board communicates directly with the CPU to which it is serially connected by referencing station number FF hex. The board can only communicate with other local stations on the MELSECNET network (if one exists) if the station to which the board is serially connected is the master station (i.e., station number 0). The local stations are then referenced by their respective station numbers, while the master station is referenced by station number FF.

If the station to which the board is serially connected is a local station, the board cannot communicate with other local stations on the MELSECNET network. It can only communicate with the station to which it is connected, referenced by station number FF, or to the master station, referenced by station number 0.

A7BDE-J71P21/R21 MELSECNET Interface Board

The MELSECNET Interface Board (A7BDE-J71P21/R21) enables access to MELSECNET. The board acts as a station on MELSECNET, either master or local.

The following four switches must be set for proper operation of the MELSECNET Interface Board:

Board Number Setting

Dial Number	Memory Area Head Address	I/O Port Number 100H offset        300H offset
0	D0000H	100H                  300H
1	D2000H	1100H              1300H
2	D4000H	2100H              2300H
3	D6000H	3100H              3300H
4	D8000H	4100H              4300H
5	DA000H	5100H              5300H
6	DC000H	6100H              6300H
7	DE000H	7100H              7300H
8		DO NOT SET
9		DO NOT SET
I/O Port Number Offset

The I/O Port Number Offset is specified by means of a "jumper connector" and may be set to either 100H or 300H.

Board IRQ Number Setting

Dial Number	IRQ Number
0	3
1	4
2	5
3	7
4	10
5	11
6	12
7	15
8	DO NOT SET
9	DO NOT SET
Station Number Setting

Dial X10: X10 switch sets the "10s" position of the station number.

Dial X1: X1 switch sets the "1s" position of the station number.

Setting for the master station is (00). Settings for local stations are between (01) and (64).

Refer to the Mitsubishi A7BDE Documentation for more information about these settings.

If the board is configured as the Master station (i.e., the Station Number is set to 0), the board is responsible for setting the MELSECNET link parameters. In this case, the user must access the board driver before running Interact to set the mode and write the link parameters.

Important    The Set Board Mode check box, located on the Board type property sheet located in the Mitsubishi A7BDE main help, should be cleared to avoid resetting the board and clearing out the link parameters when Interact goes into Run mode.

If the board is configured as a local station (i.e., the Station Number is set to 1 - 64), it is not necessary to write the link parameters to the board, as this is the responsibility of the master station. In this case, the Device Driver will set the mode of the board according to the Mode Setting, located on the Board Type property sheet located in the Mitsubishi A7BDE main help.

Important   The Set Board Mode check box, located on the Board type property sheet located in the Mitsubishi A7BDE main help, should be checked to enable automatic mode setting of the board when it is a local station, unless you wish to set the mode prior to running Interact.

Once the switches on the MELSECNET Interface Board have been set, you must install the board driver by adding a command line to the CONFIG.SYS file on your PC. This command line is described in detail in the topic I/F Board Driver Installation in the Mitsubishi A7BDE main help.

Refer to the Mitsubishi A7BDE Documentation for information about the Board Mode Setting.


NetBIOS Connection Information

NetBIOS Concepts

It is important that you understand the following concepts to use the NBIOS properly:

Remote Driver Access

Multiple Networks

File Transfer

Application Restart

User level change

ASCII Messages

Remote Driver Access

The Remote Driver Access feature provides very powerful capabilities for networked systems. It enables Interact applications running on machines connected to a network, to access data residing in an Interact application running on another network node in real time.

The data can be acquired from or written to a programmable controller. Another source of data could be from any internally generated link variables or reserved references, such as those used to monitor driver status.

The diagram above depicts two networked workstations, each running Interact applications. Node_B is connected to a programmable controller and is capable of reading and writing its memory using the appropriate Interact driver (DVR).

The following diagram illustrates the physical layout:

Data locations in the controller can be referenced by Interact modules running on Node_B, by simply entering an address reference as defined by the controller driver.

For example, a push-button on a PTM panel can be configured to control a bit in the controller by entering an address reference to that bit as follows:

DVR\1:200.15

This fictitious address refers to bit 15 of word 200 at controller station #1, using the Interact driver named "DVR."

Node_A can just as easily reference data locations in the controller connected to Node_B, using an extension of the standard addressing used by Interact modules.

Assuming that a push-button on a PTM panel running on Node_A needs access to the same location described above, the address reference shown below would be used:

NBIOS\NODE_B\DVR\1:200.15

This address reference describes a logical path to the desired data location.

Working from the controller backwards, it configures the push-button to control bit 15 of word 200 in controller station #1. It uses the "DVR" driver which exists on the node named NODE_B, which is accessed via the network using the NBIOS driver, running on Node_A.

This example shows how easy it is to configure Interact applications to access real-time data over the network. Although only two nodes are shown, keep in mind that any node on the network can be similarly configured to access data on any other node, as long as the NBIOS driver is present.

For example, a node could obtain the number of active alarms that exist at a remote "Node_N" running the Interact Alarm Management Module, by referencing the appropriate link variable as shown below:

NBIOS\NODE_N\LINK\ACTIVE_TOTAL

Likewise, the error status from a programmable controller driver running in a remote node named "OPUS" could be referenced as follows:

NBIOS\OPUS\DVR\ERROR_CODE

Refer to the Application Manager Help file and the Interact Reference Guide for an explanation of link variables and to the driver's help file for a listing of reserved address references such as "ERROR_CODE."

Multiple Networks

The Interact Networking NetBIOS Driver is capable of connecting to any network environment which supports a standard NetBIOS interface. With Interact, it is possible to have two or more drivers running simultaneously within a single application.

This feature makes it possible for a single workstation to be connected to two different networks at the same time. This requires the workstation to have two network adapters. Assign one of the networks to the primary adapter number 0 and the other to an alternate adapter number 1 to 255. The diagram below shows Node_A connected to a Novell Network and to a Lantastic Network.

In this scenario, Node_A acts as a "bridge" between the two different networks. The schematic representation below shows the Interact configuration of Node_A to accomplish this.

Since there are two network drivers in Node_A, at least one must be renamed so that they are distinguishable.

For this example, each has been renamed from the default name of "NBIOS" to "NOVL" and "LANT," for the Novell Network and Lantastic Network.

Assume that Node_D has a push-button on its panel which must be configured to connect to a bit in the programmable controller. Its network driver is named "NBIOS." The following address reference would be used:

NBIOS\NODE_A\NOVL\NODE_B\DVR\1:200.15

Node_B could reference the number of active alarms in Node_C, using the following address reference:

NBIOS\NODE_A\LANT\NODE_C\LINK\ACTIVE_TOTAL

File Transfer

Interact applications generate files during Run mode that may be stored on the local node. These files include alarm histories, data logs, activities, reports, etc.

The NBIOS Driver includes file transfer features, making it easy to request copies of these files to be sent across the network to a designated node.

The file transfer functionality for a node is configured using the File Transfer features implemented on the driver configuration dialogs.

The NBIOS Driver is flexible enough to allow the transfer of any file. Files do not necessarily have to be related to the Interact product. Due to this powerful capability, operator access to the various file transfer operations can be limited by assigning required user levels.

Security over file transfers is extended further using parameters in the File Transfer Node List configuration located in the NBIOS main help. These options can be used to limit the type of files which can be transferred from various nodes on the network. Other settings specify whether or not the user level of a remote node can be changed and whether or not applications can be restarted.

When file transfers are performed, the NBIOS Driver will need to know where to store the files when they arrive. The Default Path parameters located on the File Transfer Paths page, located in the NBIOS main help, allow up to four path specifications to be configured for file destinations. During run-time the operator can choose one of these four paths for the transfer destination.

There may be a need to configure a workstation to deny requests for files to be transferred from it, or allow this option to be set by an operator during run-time. The Remote Transfer parameter is used to do this. Check the Remote Transfer topic in the NBIOS main help for more information.

Application Restart

The NBIOS Driver includes a feature that can restart an application after files or new programs are downloaded to a node. This can make updating multiple workstations fast and easy as application requirements change.

Caution   If you intend to use the Allow Restart Application parameter, thoroughly test the application before sending it to a remote node. Check the Allow Restart Application topic in the NBIOS main help for more information.

If an application error occurs on the remote node which inhibits it from re-entering Run mode, the communications between the local and remote nodes will drop. This will require a manual restart at the remote node site.

User Level Change

The Allow User Level Change parameter enables a user to restrict access to designated functions on remote nodes. For example, if two nodes are running the same application, you could change the user level on the other node to restrict access to that application. This would enable you to have complete control of the application and not conflict with input from the other node. Check the Allow User Level Change topic in the NBIOS main help for more information.

ASCII Messages

The Panel Toolkit Module supports a device called the Message Entry Tool. This tool resembles the Local or Remote Message Display. Select this tool to enter ASCII messages from the keyboard to be sent to the address location specified in its configuration.

Use the Message Entry Tool and a Remote Message Display Tool to send messages from one node to another over the network.

REMOTE MESSAGE DISPLAY

MESSAGE ENTRY DISPLAY

Network

In the diagram above, a Message Entry Tool (pictured on the left) on Node_A is configured to send its messages to the link variable called "MSG1" on Node_B. This would be implemented using the following address string; NBIOS\Node_B\LINK\MSG1:A

A Remote Message Display Tool (pictured on the right) on Node_B is configured to display the messages coming from the link variable "MSG1." With this configuration, any messages entered by an operator on Node_A would appear on the Remote Message Display Tool on Node_B. This would be implemented using the following address string; LINK\MSG1:A


Reliance R-NET Connection Information

Connection to the R-NET Network

The PC Link module should be wired with the same cabling and termination as any other R-NET module. Connect the R-NET cable to the BNC connector located on the module. The module may be connected or disconnected without interrupting communications on the rest of the R-NET network.

The PC Link module does not incorporate a terminator on the circuit card. Thus, if the module is at the end of the R-NET coaxial cable, it must be terminated with a 75-ohm terminating load. Refer to the Reliance documentation for further details on connecting the module to the R-NET network.


Opto 22 Drivers

Below is a list of all Opto 22 drivers supported by Interact.

Mistic


Allen-Bradley Remote I/O Connection Information

To connect your new driver to your network, you will need the Belden 9463 twin-axial cable (commonly referred to as the "Blue Hose") and the terminal block included in the A-B Remote I/O installation kit.

1.	Connect the remote I/O cable to the terminal block as shown in the diagram below.

Pin 1 is internally connected to pin 4, pin 2 to pin 5, and pin 3 to pin 6. Therefore, you can make the same connections to pins 1, 2, or 3, that you make to pins 4, 5, or 6.

2.	When connecting to a remote I/O network, wire the A-B Remote I/O adapter in the same fashion as any other remote rack.

Refer to your Allen-Bradley processor documentation for details on remote I/O wiring.Typically, you wire the Remote I/O in a daisy chain configuration using the "Blue Hose."

3.	Insert the terminal block with attached cable into the connector on your card. You will find the connectors as shown below.

Note:	If using a P2 PowerStation, you should connect the cable to the card before replacing the back shell cover. It can be difficult to insert the terminal block correctly through the opening in the cover.

Note:	The A-B Remote I/O adapter has no onboard terminator. If your system requires a terminator, refer to the figure below for proper termination.


Reliance DCS-NET Connection Information

Interact interfaces with the Reliance AutoMax controllers via the DCS-NET local area network. Interact acts like any other drop on the DCS-NET link. Read and write data is automatically transferred between the PC Link Interface Module and the other drops on the network by the master (drop 0).

Interact connected via the DCS-NET network is shown below.


Square D Sy/Link Connection Information

This topic describes configuration of the SY/LINK board memory address DIP switch. Also provided is a description of the board connectors.

The following information is available in this topic:

Card Memory Address Setting

Communications Cable

Card Memory Address Setting

The SY/LINK board is designed for installation in a standard IBM PC slot. A DIP switch is located on the board that requires setting prior to inserting the board in your computer. The SY/LINK board is shown below.

The SY/LINK board requires the use of 4K bytes of I/O space in your computer so that it can be accessed. DIP switch S1 determines the starting address for this I/O space.

The I/O addresses available must start on 4K boundaries ranging from CA000H to D3000H. The computer uses these addresses to exchange data between Interact and the SY/LINK.

Make certain that other equipment in your computer does not conflict with the chosen port address. The default is set to CA000H and for most systems this address is appropriate.

DIP switch 1, shown below, is used to establish the Memory Address.

Setting the DIP switch to the OPEN position corresponds to a logic level 0. Likewise, the CLOSED position corresponds to a logic level 1.

The figure below shows some examples of selecting an appropriate Memory Address.

Record the selected address. This will be used as reference when configuring the SY/LINK driver.

Communications Cable

The SY/LINK board has two connectors, shown below, located on the faceplate of the board. The top connector is the RS-422 port. This 9 pin, D- type female connector allows any compatible device to access the SY/NET network.

Any RS-422 device can be connected to the SY/NET network. Also RS-232 devices can be connected if using RS-232 to RS-422 converters.

The bottom connector on the SY/LINK board is a SY/NET connection. This connection provides access to the SY/NET network just like any network station.


Sutherland Schultz SD Connection Information

This topic provides information on the Port Block selection and connecting the SD card to the Data Highway.

Caution   The SD card contains static sensitive components. Exercise care in handling and installing the card. The handling danger is particularly high on days with low humidity. These basic rules should be followed:

- Touch your hand to the computer case before installing the card to discharge any built up charges.

- Avoid excessive handling of the card in areas susceptible to static electricity such as carpeted floors, low humidity, etc.

The SD card is designed to plug into a standard IBM PC bus slot.

The SD card requires an I/O port block of eight bytes. There is a DIP switch on the card that is used to set the location of the I/O ports used to access the card.

The DIP switch is located and numbered on the card as shown below.

Possible port locations and the corresponding switch settings are listed in your SD card documentation. Do not change the port block from its default setting of 0250 Hex unless there is a conflict with other hardware in your computer.

The factory set port address selection is 0250H as shown in the figure below.

Make certain that other equipment in your computer does not conflict with the chosen port address. Remember that the I/O space required is eight bytes, so a setting of 0250 Hex uses ports 0250-0257.

Record the selected port address. This will be used as reference when configuring the SSSD Device Driver.


Texas Instruments Remote I/O Connection Information

The remote I/O cable is connected to the nine pin connector located on the access cover. The connector is numbered as shown below.

When connecting to a remote I/O network, the TIRIO adapter should be wired in the same fashion as any other remote rack. Refer to your Texas Instruments controller documentation for details on remote I/O wiring.

The insulated wires are attached to pins 3 and 8 of the connector while the non-insulated wire is attached to pin 5. It does not matter which of the two insulated wires are attached to pins 3 or 8.

For remote I/O connection, refer to the figure below.

A terminator is required if the TIRIO adapter is the last node on the link. If this is the case the value of the resistive terminator depends upon the type of cable used as the remote I/O cable.

The table below lists three types of Belden cable commonly used in the I/O link and the associated termination resistor value.

Cable Type	Resistor Value
9860	120 ohms
9271	120 ohms
9182	150 ohms
All cable types are Belden twisted pair cable.

If a terminator is required refer to the figure below for proper termination.

TIRIO adapter installation is now complete.


Opto 22 Mistic Connection Information

You have the choice of connecting your units using either the Serial or ARCNET method. The following features for each method are shown below.

Note   Each method supports the transfer of all data types.

ARCNET Features

•	Single PC connected to multiple Opto 22’s (up to 255).

•	Transfer rate of 2.5 megabits per second.

•	Connect with coaxial cable

•	Host must be set to ARCNET

•	Maximum network connection distance up to 20,000 feet.

•	Any ARCNET card for the PC can be used.

•	Provides better noise immunity than a RS-232 connection.

The ARCNET link connects directly to the Opto 22’s ARCNET connector located on the G4LC32ARC board installed in the controller.

Serial Communication Features

•	Single RS-232 connection from COM port 1 - 4 of the PC to COM0 of the Opto 22 controller.

•	Baud rates of 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200.

•	RS-232 is capable of transmitting up to 50 feet at 9600 baud.

•	When using the RS-422/485 port, as many as 100 devices can be connected.

•	Host must be set to COM0.

•	RS-422/485 connections are capable of transmitting up to 3000 feet.

•	RS-422/485 provides greater noise immunity than RS-232.

Connections and switch settings for all communication methods are shown below. For further information, refer to the Opto 22 Mistic Model 200 Processor User’s Guide. RS-422 and RS-485 cable diagrams only show the connection to a PowerStation from the Opto 22 controller. For any other RS-422 and RS-485 connection, refer to your computer or workstations documentation for specific pin-out information. RS-422 and RS-485 terminator and 2/4 wire settings are dependent on your specific configuration.

RS-232 25-Pin PowerStation to Opto 22 Mistic Controller

RS-232 9-Pin PowerStation to Opto 22 Mistic Controller

RS-422/RS-485 9-Pin PowerStation to Opto 22 Mistic Controller (Four Wire Pin-out)

RS-422/RS-485 25-Pin PowerStation to Opto 22 Mistic Controller (Four Wire Pin-out)

RS-422/RS-485 9-Pin PowerStation to Opto 22 Mistic Controller (Two Wire Pin-out)

RS-422/RS-485 25-Pin PowerStation to Opto 22 Mistic Controller (Two Wire Pin-out)


Allen-Bradley SLC-500 Connection Information

This topic describes the cable connections required for the various controller configurations.

SLC 5/03 and 5/04 controllers communicate with the SLC-500 driver using the RS-232-C standard. All other SLC-500 controllers communicate on a network using the RS-485 standard. Cable and connection diagrams, shown below, will assist you in properly connecting the computer to the controller. For Interact to communicate on an RS-485 network running from a computer, an RS-232 to RS-485 converter is needed. The PowerStation has a built in RS-485 port, if using Interact on a PowerStation, an RS-232 to RS-485 converter is not needed.

Allen-Bradley's Interface Converter (1747-PIC) can be used with AB cable (1747-C10) to connect a computer running Interact to a controller. For a single controller connection, connect the cable as shown below.

Single Controller Connection

Note	The 1747-PIC module does not work on any model of PowerStation. However, other third party converters may be used.

For connection to multiple controllers, you must use the AB Isolated Link Coupler (1747-AIC or 1747-AIC+) attached to a network of SLC-500 controllers as shown below.

Multiple Controller Connection

You can also use a third party RS-232 to RS-485 converter (such as B&B Electronics #485TBLED) with your own cable. If you are using the B&B Electronics RS-232 to RS-485 converter, we suggest setting the CONTROL jumper to SD (JP2).

Cable diagrams, shown below, will assist you in properly connecting a computer or the PowerStation to the controller.

RS-232 25-Pin PowerStation to SLC 5/03, 5/04 Controller

RS-232 9-Pin PowerStation to SLC 5/03, 5/04 Controller

RS-485 9-Pin PowerStation to SLC-500 Cable Diagram

RS-485 25-Pin PowerStation to SLC-500 Cable Diagram


Compumotor Gem6K/6K/6000 Connection Information

The Compumotor Gem6K/6K/6000 Series (CMOT) Device Driver allows you to configure your Interact application to communicate with Compumotor’s Gemini 6K, 6K, and 6000 Series Stand Alone and Bus-Based products. These controllers interface with Interact and Gem6K/6K/6000 Series Stand Alone products through either a point-to-point serial (RS-232-C, RS-422, or RS-485), multi-drop serial RS-422 communication, or through the Ethernet port.

Specific controllers this driver communicates with are; 6K series, Zeta 610N, 6200, 6250, and APEX 615N controllers. In addition, the driver communicates with AT6N00 stepper, and AT6N50 servo devices. Finally, the driver also communicates with Gemini GV6K servo devices and Gemini GT6K stepper devices.

Note   This driver does not support daisy chained RS-232-C communications. Also, the RS-422 connection is referred to as RS-485 4-wire connection in Compumotor documentation.

The CMOT Device Driver communicates with the controller through the computer's serial RS-232-C, RS-422, or RS-485 port, through an AT-Bus card, or using the computer’s Ethernet port. The serial communications port on the computer will vary depending on the type of communications adapter card installed in your computer.

To communicate through the Ethernet port, there are specific versions of software you will need. The software versions you will need are listed in the Ethernet Configuration topic in the Compumotor Gem6K/6K/6000 main help.

The diagrams below show the connections required to interface between a serial port or Ethernet port and the Compumotor Gem6K/6K/6000 Controller.

If you are using an RS-422 or RS-485 connection, you must change the DIP switch or jumper settings on the PowerStation. Refer to the applicable PowerStation User Guide for information on changing the DIP switches or jumpers.

RS-232 9-Pin Connection (Gem6K/6K Serial Controller)

RS-232 25-Pin Connection (Gem6K/6K Serial Controller)

RS-232 9-Pin Connection (6000 Serial Controller)

RS-232 25-Pin Connection (6000 Serial Controller)

RS-422 9-Pin Connection (Gem6K/6K Serial Controller)

RS-485 9-Pin Connection (Gem6K/6K Serial Controller)

Note: This driver must be used in conjunction with a HUB or switch.

Note:  To communicate with a 6000 controller through an RS-422 or RS-485 connection, refer to the label on the controller for pinout information.

Ethernet Point-to-Point (Cross Over Cable) 10BaseT/100BaseT Connection

Ethernet Hub Connection (Straight Through)


ASCII Connection Information

The ASCII device driver communicates with field devices through the serial port. The driver is a master in standard serial communications. The number of supported slave field devices depends on the specific field device and the type of serial communication being used. One device for RS-232-C communications and up to 32 devices for RS-485 communications.

Shown below are PowerStation pinout diagrams for RS-232-C, RS-422, and RS-485 communications. Refer to your PowerStation User Guide for specific DIP switch settings that might be required to communicate using the RS-422 or RS-485 protocol. In addition, refer to the documentation received with your field device for complete system connection information.

RS-232 Pin-out Diagram, 9-Pin PowerStation

RS-232 Pin-out Diagram, 25-Pin PowerStation

RS-422 Pin-out Diagram, 9-Pin PowerStation

RS-422 Pin-out Diagram, 25-Pin PowerStation

RS-485 Pin-out Diagram


Bristol Babcock Connection Information

The RS-232-C port on the computer will vary depending on the type of communications adapter card installed in your computer.

Diagrams showing the connections required to interface with an RS-232-C port are shown below:

RS-232 9-Pin COM Port to Controller

RS-232 25 Pin COM Port to Controller


Square D Serial Connection Information

The Square D Serial (SQRD) Device Driver allows you to configure your Interact application to communicate with ALL SY/MAX controllers that have an RS-422 port.

The SQRD device driver communicates with the controller through the serial port of the computer. Thus, the driver is called a serial driver. No special hardware needs to be installed in the computer to communicate with the controller.

The communication port on the SY/MAX controller is an RS-422 interface. RS-422 communications offer greater noise immunity than RS-232- C. This standard increases the maximum cable length to 4000 feet (1200 meters). RS-422 communications are full-duplex.

The SQRD device driver must communicate to this RS-422 port. There are several methods to accomplish this. Use an RS-232-C to RS-422 converter connected to your computers serial port, or install an RS-422 interface board in your computer.

Refer to the table below for RS-232-C connector signal names and pin-outs.

Signal Name	25 Pin Connector	9 Pin Connector
chassis ground	1	-
transmitted data (TXD)	2	3
received data (RXD)	3	2
request to send (RTS)	4	7
clear to send (CTS)	5	8
data set ready (DSR)	6	6
signal ground (GND)	7	5
data carrier detect (DCD)	8	1
data terminal ready (DTR)	20	4
If using this method, connect to your RS-232-C to RS-422 converter then refer to the converter's documentation for the cabling necessary to connect to the SY/MAX RS-422 port.

If using an RS-422 interface board in your computer refer to the documentation that came with the board for pin-out information.

Note   If using a COMM port that does not have a 16550A UART, the driver may report a Watchdog Time-out error. If connected to a SY/LINK network, the driver may report a Device Inactive error. The use of a 16550A COMM port will help avoid these driver errors.

A standard RS-422 port on a SY/MAX controller is shown below.

SY/MAX RS-422 Port Pinout

Cable diagrams for connecting the PowerStation RS-422 port to the SY/MAX controller are shown below.

RS-422 9-Pin PowerStation COM2 Port to the SY/MAX Controller

RS-422 25-Pin PowerStation COM1/COM2 Port to the SY/MAX Controller


Yaskawa Connection Information

The YASK device driver communicates with the Yaskawa controller through the computer's RS-232-C port. This topic shows the connections required for a standard RS-232-C connection.

The serial connection on the Yaskawa controller is an RS-232 interface. The Yaskawa controller can communicate with the computer using the wiring diagrams below.

RS-232 25-Pin PowerStation to YASK COM1 Port

RS-232 9-Pin PowerStation to YASK COM1 Port


Mitsubishi AJ71C24 Connection Information

RS-232 Cable Connections

The following are the pin outs for the RS-232-C 25-pin and 9-pin D-sub (female) connectors:

RS-232 25-Pin PowerStation to Mitsubishi AJ71C24

RS-232 9-Pin PowerStation to Mitsubishi AJ71C24

The PowerStation incorporates the RS-232-C standard for a 25-pin computer connector. Refer to those diagrams when connecting to a PowerStation.

RS-422 Cable Connections

The following are the specifications for the RS422 connection:

RS-422 9-Pin PowerStation to Mitsubishi AJ71C24

RS-422 25-Pin PowerStation to Mitsubishi AJ71C24


Allen-Bradley Data Highway Connection Information

All the interface modules discussed (KE/KF, KG, KA, KF2 Series B) require similar connections at the module end. The RS-232-C port on the computer will vary depending on the type of communications adapter card installed in your computer. The following table shows the standard pin-out for a 25 and 9 pin DTE connector.

Signal Name	25 Pin Connector	9 Pin Connector
chassis ground	1	-
transmitted data (TXD)	2	3
received data (RXD)	3	2
request to send (RTS)	4	7
clear to send (CTS)	5	8
data set ready (DSR)	6	6
signal ground (GND)	7	5
data carrier detect (DCD)	8	1
data terminal ready (DTR)	20	4
Diagrams showing the connections required to interface with an RS-232-C connector follow.

RS-232 25-Pin PowerStation to 15-Pin Interface Module (KE/KF, KG, KA, KF2 Series B)

RS-232 25-Pin PowerStation to 25-Pin Interface Module

RS-232 9-Pin PowerStation to 15-Pin Interface Module

RS-232 9-Pin PowerStation to 25-Pin Interface Module

RS-232 9-Pin PowerStation to SLC 5/03, 5/04 Cable Diagram


Mitsubishi A Connection Information

RS-232-C Cable Connection

Connect the PC RS-232 port to an RS-232/RS-422 converter.  A cable needs to be wired between the converter and the programming port of the Mitsubishi A PLC.

The following is a pinout for connecting the RS-422 (25-pin) port of the PLC to a B&B RS-232/RS-422 converter (Model # 422CFCR):

*Pin 7 and 8 of the 25-pin PLC RS-422 connector should be short circuited.

RS422 Cable Connections

When using PowerStation Models P3 through P7 RS-422 connection, the pin assignments out of the 25-pin RS-422 port and into the CPU 25-pin connector are as follows:

9-Pin PowerStations do not support direct RS-422 connection to the controller.


Reliance AutoMate Connection Information

The Reliance AutoMate Device Driver (RELN) allows you to configure your Interact application to communicate with Reliance controllers using one of three communication configurations:

Direct Connection - Serial communication directly through the EIA connector port on the front of the AutoMate processor.

Serial Communication Processor - Serial communication through any one of the EIA connector ports on the front of the Serial Comm Processor to any AutoMate processor in the same rack.

R-NET Gateway - Serial communication through the R-NET AutoMate Gateway to an R-NET processor via the Reliance R-NET local area network to any AutoMate processor in the same rack (or to an AutoMate processor with built-in R-NET communications capability).

Since the device driver communicates with the controller, the SCM, or the R-NET Gateway through the serial port of the computer, the driver is called a serial driver. No special hardware needs to be installed in the computer to communicate with the controller.

The serial or RS-232-C port on the computer will vary depending on the type of communications adapter card installed in your computer.

A table listing standard 25 and 9 pin signal names and pin numbers is shown below.

Signal Name	25 Pin Connector	9 Pin Connector
chassis ground	1	-
transmitted data (TXD)	2	3
received data (RXD)	3	2
request to send (RTS)	4	7
clear to send (CTS)	5	8
data set ready (DSR)	6	6
signal ground (GND)	7	5
data carrier detect (DCD)	8	1
data terminal ready (DTR)	20	4
Diagrams showing the connections required to interface with an RS-232-C connector follow.

RS-232 25-Pin PowerStation to 25-Pin Connector

RS-232 9-Pin PowerStation to 25-Pin Connector


Telemecanique Uni-Telway Connection Information

RS-485 Communications Cable

Uni-Telway bus communications use the RS-485 protocol. Connect a cable between the Uni-Telway bus and the PowerStations COM port using the pin out diagrams shown below as a reference. Refer to the Uni-Telway documentation for information on connection to the controller.

RS-485 9-Pin COM2 Port to TSX SCA 62 Connector

RS-485 25-Pin COM Port to TSX SCA 62 Connector


Texas Instruments Series 500 Connection Information

The TICP device driver communicates with the controller through the computer's RS-232-C port. All Texas Instruments Series 500 controllers and communication cards require similar connections at the controller end. The RS-232-C port on the computer will vary depending on the type of communications adapter card installed in your computer.

The following table shows the standard pin-out for a 25 and 9 pin DTE connector.

Signal Name	25 Pin Connector	9 Pin Connector
chassis ground	1	-
transmitted data (TXD)	2	3
received data (RXD)	3	2
request to send (RTS)	4	7
clear to send (CTS)	5	8
data set ready (DSR)	6	6
signal ground (GND)	7	5
data carrier detect (DCD)	8	1
data terminal ready (DTR)	20	4
The following diagrams show the interface to TI controllers.

RS-232 Connections

RS-232 25-Pin PowerStation to TI-525,535 25-Pin Port

RS-232 25-Pin PowerStation to TI-545 Port 1

RS-232 25-Pin PowerStation to TI-545-1102/3/4, TI-555-110 Port 2

RS-232 9-Pin PowerStation to TI-525,535 25-Pin Port

RS-232 9-Pin PowerStation to TI-545 Port 1

RS-232 9-Pin PowerStation to TI-545-1102/3/4, TI 555-110X Port 2

RS-422 Connections

RS-422 25-Pin PowerStation to TI-545-1102/4, TI 555-110X Port 2

RS-422 25-Pin PowerStation to TI-545-1101 Port 2

RS-422 25-Pin PowerStation to TI-525/535

RS-422 9-Pin PowerStation to TI-545-1102/4, TI 555-110X Port 2

RS-422 9-Pin PowerStation to TI-545-1101 Port 2

RS-422 9-Pin PowerStation to TI-525/535


Mitsubishi FX Connection Information

RS-422 9-Pin to 25-Pin Mitsubishi

RS-422 25-Pin to 25-Pin Mitsubishi

9-Pin PowerStation to 8-Pin Mitsubishi MINI-DIN

25-Pin PowerStation to 8-Pin Mitsubishi


Device Net Connection Information

This section provides procedures to install the SS-5136-DN card in your computer.

CAUTION

The SS-5136-DN card contains static sensitive components. Exercise care in handling and installing the card. The handling danger is particularly high on days with low humidity.

These basic rules should be followed:

•	Touch your hand to the computer case before installing the card to discharge any built up charges.

•	Avoid excessive handling of the card in areas susceptible to static electricity such as carpeted floors, low humidity, etc..

The SS-5136-DN card is designed to operate in a standard IBM PC bus. An I/O port address must be set before using the card. There are DIP switches on the card used to set the port address.

I/O Base Address

The port address is set using the DIP switches located on the SS-5136-DN card. The port address DIP switch has six switches with switch number 1 located closest to the faceplate (see diagram below). The port address resides on 8 byte boundaries, so a setting of 250H actually uses addresses 250H to 257H.

You must set the port address before installing the card in your computer. It is suggested that unless there is a conflict with other devices in your computer, you should leave the port address at the default setting (250H).

You can install multiple SS-5136-DN cards in your computer. Each one must have a unique MAC ID, port address and base memory address.

Base Address

The SS-5136-DN card may be placed at any location in PC memory and resides on 16K boundaries. It is recommended you place the card in the segment range of C800H to E000H to prevent overlapping with reserved memory areas. The memory address is configured on the DVNT Device Driver Program mode configuration menu.


Galil Connection Information

The GALI device driver communicates with the Galil controller through the computer's RS-232-C port. This topic shows the connections required for a standard RS-232-C connection.

The serial connection on the Galil controller is an RS-232 interface. The Galil controller can communicate with the computer using the wiring diagrams below.

25-Pin Computer to GALI COM1 Port

9-Pin Computer to GALI COM1 Port


GE Fanuc Genius I/O Connection Information

Connect the GENIUS serial bus cable to the PCIM card terminals. The connector is numbered as shown below.

When connecting to the GENIUS I/O network, the PCIM card should be wired in the same fashion as any other bus device. Refer to your PCIM card documentation for details on bus wiring.

You only require three wires to be connected to the GENIUS I/O bus. The connections required are:

•	Pin 1 to "Serial 1" of the next bus device

•	Pin 2 to "Serial 2" of the next bus device

•	Pin 3 not connected

•	Pin 4 to "Shield in" of the next bus device

A termination resistor is required if the PCIM card is the first or last device on the GENIUS I/O bus. If this is the case the value of the resistive terminator depends upon the type of cable used for the GENIUS I/O bus cable.


GE Series 6 CCM2 Connection Information

The GE CCM2 module can communicate through either port J1 (25 pin) or port J2 (9 pin) of the CCM module. The chosen port must be configured by setting the appropriate dip switches for that port. Port J1 uses the switch bank numbered 9 through 16 and port J2 uses the switch bank labeled 1 through 8.

Both switch banks have switches labeled 1 through 8 on the switch package itself. Refer to these numbers when configuring your module based on the switch information presented in the following topics. A typical CCM2 board with the switches labeled is shown below. Refer to this figure as needed.

The GECM device driver communicates with the CCM2 module through the computer's RS-232-C or RS-422 port. The figures below show the connections required for a standard RS-232-C connection.

For RS-422 connections refer to the GE Series 6 Data Communications Manual.

The PowerStation incorporates the RS-232-C standard for a 25-pin computer connector. Refer to those diagrams when connecting to a PowerStation.

9-Pin PowerStation RS-422 connections to a GE CCM2 controller are shown below.

25-Pin PowerStation RS-422 connections to a GE CCM2 controller are shown below.


GE Series 90 SNP Connection Information

The GE Series 90 SNP (GESN) Device Driver allows you to configure your Interact application to communicate with any GE Series 90 controller using the Series Ninety Protocol (SNP). These controllers interface with Interact through their RS-422 port.

The GESN device driver communicates with the controller through an RS-232 to RS-422 converter. The converter is connected between the serial port of your computer and the RS-422 interface port on the controller. Thus, the driver is called a serial driver.

The GESN device driver communicates with the controller through the computer's RS-232 port or the PowerStation’s RS-422 port. Since GE Series 90 controllers have an RS-422 interface, a converter box is required to connect the controller to the computer's RS-232 port. A converter box is not required when connecting to the PowerStation because the PowerStation has an RS-422 port.

The RS-232 port on the computer will vary depending on the type of communications adapter card installed in your computer.

Diagrams showing the connections required to interface between an RS-232 connector and the GE Series 90 controller follow.

Connections are shown for the GE RS-232 to RS-422 Converter (part no: IC690ACC900) and for a generic converter box.

Notice when installing a PLC at the end of a multidrop configuration, pin 9 of the PLC interface should be connected to pin 10.

25-Pin Connection (GE Converter)

9-Pin Connection (GE Converter)

The two following figures illustrate connecting a generic converter to your computer. These diagrams are shown here only as a reference. Refer to your converter documentation for specific details.

Some points to keep in mind when connecting your converter box are:

•	Ensure your configuration uses twisted pairs.

•	Ensure your cable shielding has only single point grounds.

•	Because RTS and CTS signals are not supported by the driver, they should be jumpered together for the controller.

25-Pin Connection (Generic Controller)

9-Pin Connection (Generic Controller)

9-Pin PowerStation RS-422 COM Port to 15 Pin GE Series 90 Controller

25-Pin PowerStation RS-422 COM Port to 15-Pin GE Series 90 Controller

** Pin 9 of the controller connector is only connected to pin 10 if the controller is at the end of a multidrop line. Exception: For Series 90-70 PLCs Cat. #’s IC697CPU731 and IC697CPU771 the termination for RD is implemented by a jumper between pins 9 and 11.

The following diagrams illustrate connections through a WYE cable or direct from the PowerStation to the CMM module.

9-Pin PowerStation to CMM Module, RS-232

9-Pin PowerStation to CMM Module, RS-422


GE Series 90 SNPX Connection Information

The GE Series 90 SNPX (GSNX) Device Driver allows you to configure your Interact application to communicate with any GE Series 90 controller using the Series Ninety Protocol (SNPX). These controllers interface with Interact through their RS-422 port.

The GSNX device driver communicates with the controller through an RS-232 to RS-422 converter. The converter is connected between the serial port of your computer and the RS-422 interface port on the controller. Thus, the driver is called a serial driver.

The GSNX device driver communicates with the controller through the computer's RS-232 port or the PowerStations RS-422 port. Since GE Series 90 controllers have an RS-422 interface, a converter box is required to connect the controller to the computer's RS-232 port. A converter box is not required when connecting to the PowerStation because the PowerStation has an RS-422 port.

The RS-232 port on the computer will vary depending on the type of communications adapter card installed in your computer.

Diagrams showing the connections required to interface between an RS-232 connector and the GE Series 90 controller follow.

Connections are shown for the GE RS-232 to RS-422 Converter (part no.: IC690ACC900) and for a generic converter box.

Notice when installing a PLC at the end of a multidrop configuration, pin 9 of the PLC interface should be connected to pin 10.

25-Pin Connection (GE Converter)

9-Pin Connection (GE Converter)

The following two figures illustrate connecting a generic converter to your computer. These diagrams are shown here only as a reference. Refer to your converter documentation for specific details.

Some points to keep in mind when connecting your converter box are:

•	Ensure your configuration uses twisted pairs.

•	Ensure your cable shielding has only single point grounds.

•	Because RTS and CTS signals are not supported by the driver, they should be jumpered together for the controller.

25-Pin Connection (Generic Controller)

9-Pin Connection (Generic Controller)

9-Pin PowerStation RS-422 COM Port to 15-Pin GE Series 90 Controller

25-Pin PowerStation RS-422 COM Port to 15-Pin GE Series 90 Controller

** Pin 9 of the controller connector is only connected to pin 10 if the controller is at the end of a multidrop line. Exception: For Series 90-70 PLCs Cat. #’s IC697CPU731 and IC697CPU771 the termination for RD is implemented by a jumper between pins 9 and 11.

The following diagrams illustrate connections through a WYE cable or direct from the PowerStation to the CMM module.

9-Pin PowerStation to CMM Module, RS-232

9-Pin PowerStation to CMM Module, RS-422


Giddings and Lewis PIC 900 (GLP9) Connection Information

You have the choice of connecting your units using either the LNK900 or NET900 method. The requirements for each method are listed below.

Note   Each method supports the transfer of all data types.

NET900 Features

•	Single PC connected to multiple PIC900s (up to 254).

•	Transfer rate of 2.5 megabits per second.

•	Connection options:  twisted pair; coaxial cable; fiber optics.

•	Maximum network connection distance up to 4 miles.

•	An ARCNET card for the PC and a NEXNET daughter board in the PIC900 CPU.

•	Better noise immunity than an RS-232 connection.

Refer to the PIC900 Hardware File for wiring the NEXNET/ARCNET for communications daughter board in the PIC900 CPU Module.

Refer to your ARCNET card documentation for the board settings. The ARCNET pc130e/pc270e Network Controller Boards are used as an example.

LNK900 Features

•	Single or Multiple (up to 254) RS-232, RS-422, and RS-485 connections to/from COM port 1 - 4 of the PC to USER PORT 2 or a Serial Communications Module port of the PIC900.

•	Baud rates of 1200, 2400, 4800, 9600, 19200 (use hardware handshaking at 19200).

•	Limited wire length of RS-232 (typically 50 feet at 9600 baud). Wire length extends to 4000 feet if using RS-422 or RS-485 connections.

You can use a standard three wire null modem cable to connect a PIC900 to the PC, when using communication baud rates up to 9600.

Pinouts for 9-pin or 25-pin connection, from an RS-232/RS-422/or RS-485 port, to a 10-pin screw terminal connector are shown below.

Note   If you use the hardware handshaking option, connect the PIC900’s RTS to the PC’s CTS and the PIC900’s CTS to the PC’s RTS.

9-Pin RS-232 Connection

25-Pin RS-232 Connection

9-Pin PowerStation COM2 RS-422 Connection

25-Pin PowerStation COM2 RS-422 Connection

9-Pin PowerStation COM2 RS-485 Connection


Indramat CLC Motion Control Connection Information

The serial connection on the CLC-P01 card can communicate with either RS-232, RS-422, or RS-485 through the X27 port. The connection on the CLC-P02 card can communicate only RS-232 or RS-422 through the X27 port. The X27 port is configured to respond to the VisualMotion ASCII Host Protocol.

The diagrams below show the pinouts for the various connections.

RS-232-C 9-Pin Connection

RS-232-C 25-Pin Connection

RS-422 9-Pin Connection

RS-422 25-Pin Connection

RS-485 9-Pin Connection


Klockner Moeller PS416 Connection Information

The standard cabling between the computer's 9-Pin RS-232 port and the controller is shown below.

The standard cabling between the computer’s 25-Pin RS-232 port and the controller is shown below.

Refer to your Klockner Moeller PS416 controller documentation for more information.


Modem Device Driver Connection Information

The modem driver is used when connecting an Interact station to a controller interface (PLC Link) or when connecting an Interact station to Interact station communications (Network Link).

Both methods are shown in the figure below.

PLC Link

Using the IMD in a direct controller connection allows an Interact serial driver to connect with a controller via a modem. This modem connection is transparent to the Interact application. It will appear that the application is connected directly to the controller instead of via a modem.

This configuration requires only the use of an Interact serial driver to communicate with the controller. The NetBIOS and LANtastic Z software are not needed in this configuration.

Network Link

Using the IMD in a station to station configuration allows one Interact station to connect with another one via modems. This allows the Interact station to have access to data located in the other station by using the Interact NetBIOS Driver. Either node can read or write data locations in controllers connected to the other node.

In this configuration, you must use the following drivers:

•	NetBIOS driver

•	IMD driver

•	LANtastic Z network software

LANtastic Z is a two-node network used to connect two computers via the serial ports. LANtastic Z is a zero-slot network that needs no network adapters.

The IMD driver was designed to work exclusively with the LANtastic Z product from ARTISOFT corporation. Refer to your Interact supplier for information, pricing, and availability of the LANtastic Z product.

To use the IMD driver in a network link, read the documentation that came with that package. Read the LANtastic Z product user’s manual in addition to this Help file.


Modicon Modbus Connection Information

The Modicon Modbus Device Driver (MBUS) allows you to configure your Interact application to communicate with Modicon controllers using the Modbus protocol. This driver communicates with the following controllers:

Micro - 84	- 584	-HIWORD *
- 184	- 884	-EMERSON *
- 384	- 984
- 484	-LOWORD *
* The LOWORD and HIWORD controllers provide the same functionality as the Micro-984, with the exception of how Interact handles 32-bit data.  Because Modbus controllers do not contain 32-bit registers, Interact needs to know how to interpret two consecutive Modbus registers as 32-bit data.

Selecting LOWORD specifies first word low.  This means that the starting 16-bit register will be the low word in the 32-bit long word.

Selecting HIWORD specifies first word high.  The starting 16-bit register for this model will be the high word in the 32-bit long word.

Selecting EMERSON controller provides the basic functionality of the Micro-984 with a few exceptions.  This model is intended for use with Emerson controllers.  Therefore, BIT types, 32-Bit signed integer, and 32-Bit floating point types for address references are allowed.  By using EMERSON, the driver interprets 32-bit data identical to the Emerson controller software.

All other models use the LOWORD convention.

The Modbus Device Driver communicates with the controller through the serial port of the computer. Thus, the driver is called a serial driver. No special hardware needs to be installed in the computer to communicate with the controller.

The driver communicates with the controller through the computer's serial port. All Modicon controllers require similar connections at the controller end. The serial port on the computer will vary depending on the type of communications adapter card installed in your computer. For Interact to communicate on an RS-485 network running from a computer, an RS-232 to RS-485 converter is needed.

The following table shows the standard pin-out for a 25 and 9 pin DTE connector.

Signal Name	25 Pin Connector	9 Pin Connector
chassis ground	1	-
transmitted data (TXD)	2	3
received data (RXD)	3	2
request to send (RTS)	4	7
clear to send (CTS)	5	8
data set ready (DSR)	6	6
signal ground (GND)	7	5
data carrier detect (DCD)	8	1
data terminal ready (DTR)	20	4
Diagrams showing the connections required to interface between an RS-232-C connector and the Modicon controller follow.

25-Pin Computer Port to 25-Pin Controller Port

25-Pin Computer Port to 9-Pin Controller Port

9-Pin Computer Port to 25-Pin Controller Port

9-Pin Computer Port to 9-Pin Controller Port

A PowerStation RS-485 port connection is shown below.

PowerStation RS-485 COM Port Cable Diagram


Modicon Modbus Ethernet Connection Information

For the MBEN device driver to communicate with a controller, you must have the following software installed in your computer:

•	MachineShop Shell version 1.0 or higher

•	TCP/IP stack version 1.02 or higher

The diagrams below show the connections required for the MBEN driver to communicate with a controller through the Ethernet port on a PowerStation.

Ethernet Point-to-Point 10BaseT/100BaseT Connection

Ethernet Hub Connection


Modicon Modbus Plus Connection Information

This topic describes additional concerns you should be aware of while installing the SA85/SM85 Network Adapter.

First, install the SA85/SM85 Network Adapters following the Network Adapter documentation.

Each Network Adapter in the computer requires a separate DEVICE statement with arguments to be added to your CONFIG.SYS file. There are a total of four arguments that define each board’s parameters.

/M - defines the memory base address.

/N - defines each SA/SM85 adapter when multiple SA/SM85 adapters are present.

/S - defines the software interrupt vector.

/R2 - defines SA/SM85 driver revision 2.0. This argument is required for normal operation.

A typical DEVICE statement would be:

DEVICE=C:\[your path]\SA85.SYS /ME060 /R2

This statement indicates a base address of E060 with defaults used for the /N and /S arguments.

When entering the /N argument (adapter number) record the adapter number selected for your adapter. This number must match the Adapter Number parameter on the Adapter page of the MBPL Device Driver property sheet.

When entering the /S argument (software interrupt vector) record the interrupt vector selected for your adapter. This vector must match the Interrupt Number parameter on the Adapter page of the MBPL Device Driver property sheet.


Omron FINS Host Link Connection Information

Following are the cable connections used for the CS Series CPU, CV Series CPU and a Host Link Unit. Refer to the appropriate OMRON documentation for detailed descriptions and proper DIP switch settings required for each connection.

RS-232-C Cables

CS/CV Series CPU RS-232-C Connections, 25-Pin Port

CS/CV Series CPU RS-232-C Connections, 9-Pin Port

Host Link Unit RS-232-C Connections, 25-Pin Port

Host Link Unit RS-232-C Connections, 9-Pin Port

RS-422 Cables

CS/CV Series CPU or Host Link Unit

RS-422 25-Pin PowerStation Connections

RS-422 9-Pin PowerStation Connections


Omron Host Link Connection Information

RS-232-C cable connections are shown in the figure below.

RS-232 25-Pin PowerStation Cable Connections

RS-232 9-Pin PowerStation Cable Connections

PowerStation RS-422 connections are shown below.

RS-422 25-Pin PowerStation Connections

RS-422 9-Pin PowerStation Connections


Omron SLNK SYSLINK Connection Information

This topic illustrates the configuration of the SYSLINK support card, along with the proper connection from the card to the controller. Refer to the appropriate OMRON SYSMAC Link documentation for detailed descriptions and proper DIP switch settings required for each connection.

Omron SYSMAC Link Support Board

The DIP Switch located on the card is used to set the location of memory used by the board.  The card can be set to four different segment locations, C000h, C800h, D000h, and D800h.  The pins on the DIP switch are numbered 1 to 8, left to right.  The following table shows the pin settings for the various segment locations.

Segment	Pin1	Pin2	Pin3	Pin4	Pin5	Pin6	Pin7	Pin8
C000h	UP	UP	UP	UP	UP	DOWN	DOWN	DOWN
C800h	UP	UP	UP	UP	UP	DOWN	UP	DOWN
D000h	UP	UP	UP	UP	UP	DOWN	DOWN	UP
D800h	UP	UP	UP	UP	UP	DOWN	UP	UP
This segment of memory needs to be set on the Adapter Page of the windows configuration.

Coaxial Connection

Once the board is properly installed (consult your OMRON documentation for card installation procedures), connect the coaxial cable from the controller to the SYSMAC Link support card through the F-Adapter as shown above.  The F-Adapter is supplied with the SYSMAC Link support card.


Omron SMAC SYSMAC Connection Information

The SMAC device driver communicates with the controller through the S3200-NSB board.  Refer to the appropriate OMRON documentation for proper DIP switch settings required for the S3200-NSB network board.  Make note of the I/O port number assigned to the S3200-NSB board as this will be needed in the SMAC driver’s configuration.


Siemens HMI Adapter Connection Information

In order to communicate with the Siemens S7 MPI Network, you must connect a null cable between the serial port of your computer and a Siemens HMI Adapter. The serial port should use the RS-232-C communication protocol.

This connection is shown below.

Pinout information is shown below for the cable connecting the computer and Siemens HMI adapter 6ES7 972-0CA11-0XA0. This adapter permits simultaneous communication between the SHMI device driver and up to four PLCs.


Siemens RK-512 Connection Information

The standard cabling between the computer's RS-232 port and the controller is shown.

Use the cabling shown below if you use the optional current loop converter.

Passive Current Loop Cabling (Converter Provides Current)

Active Current Loop Cabling (CP525 Provides Current)

Refer to your Siemens S5 controller documentation for more information.


Siemens S5 Programming Port Connection Information

Cabling between the current loop converter and the Siemens programming port is shown in the following figures. There are three possible current loop configurations:

•	Active

•	Passive

•	The third configuration replaces the external current loop converter with a Siemens Programming Port Cable. The cable has a built-in current loop converter.

If your Siemens controller has a reliable 20 mA current source for the connection, it is considered Active and you can use the Active connection shown.

Use the Passive connection shown if you can't (or don't want to) depend on the controller for current.

Use the Siemens Programming Port Cable to eliminate the external current loop converter altogether. This cable receives its 5 volt power through the Programming Port, eliminating the need for a transformer and extra electrical connection. The Siemens part number is 6ES5-734-1BD20.

Active Connection

Passive Connection (valid for all cases)

Siemens Programming Port Cable

Refer to your Siemens S5 Controller documentation for more information.


Siemens S7-PPI Connection Information

The SPPI device driver communicates with the controller through the computer's RS-232 port.  Since Siemens S7-200 controllers have an RS-485 interface, a converter box is required to connect the controller to the computer's RS-232 port.  The RS-232 port on the computer will vary depending on the type of communications adapter card installed in your computer.

RS-232-C Communications Cable

The RS-232-C port on the computer will vary depending on the type of communications adapter card installed in your computer. Diagrams showing the connections required to interface with an RS-232-C connector follow.

RS-232 25-Pin Connection

*  RS-485 converter dependent.  The driver asserts both RTS and DTR.  Refer to the converter manual for correct cabling.  For the PowerStation, connect DTR to the appropriate signal on the RS-485 converter.

RS-232 9-Pin Connection

 *  RS-485 converter dependent.  The driver asserts both RTS and DTR.  Refer to the converter manual for correct cabling.  For the PowerStation, connect DTR to the appropriate signal on the RS-485 converter.

9-Pin PowerStation to Siemens S7-200 PPI Port, RS-485 Connections

RS-485 Converter to Siemens S7-200 PPI Port

Siemens PPI communications use the RS-485 protocol. Connect a cable between the Siemens S7-200 PPI Port and the PowerStation’s COM port using the pin out diagram shown below as a reference. Refer to the Siemens documentation for information on connection to the controller.

PowerStation RS-485 COM1/COM2 Port

Note: The Siemens PC/PPI cable can also be used when communicating with a single controller.


Siemens TI Ethernet Connection Information

For the TIEN device driver to communicate with the CTI 2572 module, you must have the following software installed in your computer:

•	MachineShop Shell version 1.09 or higher

•	TCP/IP stack version 1.10 or higher

The diagrams below show the connections required for the TIEN driver to communicate with the CTI module through the Ethernet port on a PowerStation.

Ethernet Point-to-Point 10BaseT/100BaseT Connection

Ethernet Hub Connection


Siemens TIWAY Connection Information

Local Line Cable Installation

Connect the TIWAY cable to the 9-pin connector located on the access cover.

When connecting to a TIWAY network, the TIWAY adapter should be wired in the same fashion as any other device on the network. Refer to your SIMATIC TI controller documentation for details on wiring.

The TIWAY Local Line is a physical signaling technique (baseband, differential current drive) which operates over shielded, twisted-pair cabling. The Local Line cable may be up to 25,000 feet long, depending on loading and baud rate selection. It uses tap housing to simplify the addition of network connections. The Local Line is designed to operate with shielded, twisted-pair cable that has a characteristic impedance of 124 ohms.

The interface cable should have a male, 9-pin D-type receptacle with pin assignments as shown below:

Description	Pin
No Connection	1
No Connection	2
Cable shield and signal common (Shield)	3
No Connection	4
No Connection	5
Positive biased signal line (LLM+)	6
No Connection	7
No Connection	8
Negative biased signal line (LLM-)	9
SIEMENS recommends Belden 9860 twisted pair cabling, or its equivalent, for use as the Local Line network spine and Belden 9271 for the dropline.

RS-232-C Cable Installation

The physical layer in the TIWAY provides a modem interface for synchronous or asynchronous modems at data transmission rates up to 115.2K bits per second.

The modem interface provides standard signals for control of two-way alternate data transmission using both half and full duplex modems. The modem interface is a standard "Type E" DTE configuration. This interface uses a male plug 25-pin D-type connector on the communication cable. The circuits and pin assignments for the RS-232-C connector are shown below.

Name - Function	ISO#	Pin
AA Protective Ground (chassis)	101	1
BA Transmitted Data	103	2
BB Received Data	104	3
CA Request to Send (RTS)	105	4
CB Clear to Send (CTS)	106	5
CC Data Set Ready	107	6
AB Signal Ground	102	7
CF Received Line Signal Detector/Data Carrier Detect (RLSD/DCD)	109	8
DB Transmitter Signal Element Timing	114	15
DD Receiver Signal Element Timing	115	17
CD Data Terminal Ready (DTR)	108/2	20


Siemens Koyo Series 205/305/405 Connection Information

This section describes the various cable diagrams needed to interface with a Siemens/Koyo controller. Two communication methods are described; RS-232-C and RS-422 communications. A topic on networking is also included.

RS-232-C Communication Cables

These diagrams show the pin assignments and cabling for connecting the series 205, 305, and 405 controllers. Each diagram for an RS-232-C connection is shown in the following diagrams.

The diagram below shows connection to the model 230 port 1 or the 240 ports 1 and 2. The connection is an RJ-12 connection. Both 9 and 25 pin serial port connections are shown.

RS-232-C Series 205 Cable Diagram

The diagram below is an RJ-11 connection to a model 335 and 340.

RS-232-C Series 305 Cable Diagram (RJ-11)

The diagram below shows connections to a model 305 DCU.

RS-232-C Series 305 Cable Diagram (DCU)

The diagram below shows connection to models 430, 435, 440 bottom 25 pin port and a model 405 DCM. Both 9 and 25 pin serial port connections are shown.

RS-232-C Series 405 Cable Diagram

The RS-232-C port on the computer will vary depending on the type of communications adapter card installed in your computer. The following table shows the standard pin-out for a 25 and 9 pin DTE connector.

Signal Name	25 Pin Connector	9 Pin Connector
chassis ground	1	-
transmitted data (TXD)	2	3
received data (RXD)	3	2
request to send (RTS)	4	7
clear to send (CTS)	5	8
data set ready (DSR)	6	6
signal ground (GND)	7	5
data carrier detect (DCD)	8	1
data terminal ready (DTR)	20	4
RS-422 Communication Cables

The diagrams in this section show the pin assignments and cabling for connecting the series 305 and 405 controllers.

The diagram below shows connection to the model 305 DCU. The connection is specifically a 305 RS-422 DCU connection. Connections to the PowerStation COM port are shown. Refer to documentation on your specific RS-422 port for proper pin-out.

25-Pin PowerStation RS-422 to Series 305 DCU Cable Diagram

9-Pin PowerStation RS-422 to Series 305 DCU Cable Diagram

The diagram below shows connection to the model 405 DCM, 430, 435, and 440. Connection is to the 435 bottom port. This diagram is also valid for connecting model 435-CPU's in a multi-drop configuration. These communicate with the personal computer via an RS-232-C to RS-422 converter.

RS-422 Series 405 Cable Diagram with Converter

Additional model 405-CPU's can be daisy-chained in this fashion.

DCM's can also be connected into the chain, however the DCM serial port pin assignments are different from those shown above.

If you have an RS-422 interface board in your personal computer, then the converter is not required. Below, this type of connection is shown.

RS-422 Series 405 Cable Diagram Direct

Note   The Siemens DCM User Manual thoroughly documents the pin assignments and the various configurations that are possible.

Note that each CPU connected must be configured with a unique station address. Also, a 150 ohm terminating resistor may be required on the last drop, across the IN+ and IN- pins. Refer to the Siemens Series 405 User Manual for more information.

Networking

Networking is accomplished using the RS-422 interface multidropped by daisy-chaining the RXD+/-, TXD+/-, and SG lines.

Since Interact is the master, any CPU with a port that can act as a slave on the network can communicate. Note that those CPU’s with RS-232-C slave ports must connect through a 232/422 converter.

The 305 DCU also has the option of using pins 25 (RXD+), 24 (RXD-), 23 (TXD-), and 22 (TXD+). For connecting to the daisy chain for easy wiring.

Occasionally, if data errors occur, terminating resistors can be placed at the extreme ends of the multi-drop line. Connect a 120 ohm resistor between the TXD+ and TXD- lines or a 62 ohm resistor to ground for each of the TXD+ and TXD- lines.


Yaskawa Memobus Connection Information

The Memobus Device Driver communicates with the controller through the serial port of the computer. Thus, the driver is called a serial driver. No special hardware needs to be installed in the computer to communicate with the controller.

All Memobus controllers require similar connections at the controller end. The serial port on the computer will vary depending on the type of communications adapter card installed in your computer. The PowerStation incorporates the RS-232-C, RS-422, and RS-485 protocols for a 9-Pin and 25-pin computer connector. Refer to the following diagrams when connecting to a PowerStation.

RS-232-C Connections from a 9-Pin PowerStation

RS-232-C Connections from a 25-Pin PowerStation

RS-422 Connections from a 9-Pin PowerStation

RS-422 Connections from a 25-Pin PowerStation

RS-485 Connections from a 25-Pin PowerStation


Delta Tau Drivers

Below is a list of all Delta Tau drivers supported by Interact.

PMAC


Delta Tau PMAC Connection Information

The Delta Tau device driver communicates with the PMAC controller through the computer's RS-232-C or RS-422 port. This topic shows the connections required for a standard RS-232-C connection.

The serial connection on the PMAC controller is an RS-422 interface. This interface is very similar to the RS-232-C interface found on most computers. The PMAC controller can communicate with the computer using the wiring diagrams below without communication problems. Although, in the presence of high noise, communications can become intermittent. To minimize communication errors between the PMAC controller and the PC, use an RS-422 converter or connect the PMAC controller to an RS-422 port installed in the computer. For RS-422 connections, refer to the PMAC User’s Manual.

RS-232 25-Pin Computer to PMAC J4 Connector

RS-232 9-Pin Computer to PMAC J4 Connector

RS-422 PowerStation COM2 to PMAC J4 Connector

RS-422 PowerStation COM1/COM2 to PMAC J4 Connector


Profibus L2-DP Slave Connection Information

The SS-5136-PFB card should be wired with the same cabling and termination as any other Profibus device. Connect the Profibus cable to the Profibus standard DB9 connector located on the card. The SS-5136-PFB also contains a 5 pin Phoenix connector. Refer to your SS-Technologies documentation for SS-5136-PFB when wiring this connector.

Note: The SS-5136-PFB card incorporates a terminator on the circuit card. If this card is at the end of the Profibus cable, you should enable the built-in terminators. The terminator is enabled by placing jumpers between pins 1 and 2 and between 4 and 5 of the 5 pin Phoenix connector.


Profibus Drivers

Below is a list of all Profibus drivers supported by Interact.

L2-DP Slave


Koyo ECOM Ethernet Connection Information

For the ECOM device driver to communicate with the CTI 2572 module, you must have the following software installed in your computer:

•	MachineShop Shell version 1.09 or higher

•	TCP/IP stack version 1.10 or higher

The diagrams below show the connections required for the ECOM driver to communicate with the CTI module through the Ethernet port on a PowerStation.

Ethernet Point-to-Point 10BaseT/100BaseT Connection

Ethernet Hub Connection


Mitsubishi Q Connection Information

RS-232 Cable Connection

The following is a pinout for connecting a Male 6-pin mini DIN to a Female 9-pin Sub D (Model # SC-Q QC30R2):