Allen Bradley Protocols

Allen Bradley Protocols

Table of Contents Allen Bradley Protocols.....................................................................................................................................1

Supported Allen Bradley Hardware.........................................................................................................1Allen Bradley Connection Methods.........................................................................................................1Data Types...............................................................................................................................................2

Allen Bradley Setup...........................................................................................................................................3Connection Methods.............................................................................................................................................6

Allen Bradley....................................................................................................................................................21

Allen Bradley Group........................................................................................................................................22


i


Allen Bradley devices are fully supported in the Hexatec software. The options available ensures that thecommunications work with the widest possible range of Allen Bradley hardware, including PLCs,Programmable Automation Controllers and Drives.

In−built drivers mean no extra OPC server is required. The connection method will usually be determined byexisting installation, the drivers support a wide range of connection methods.

Supported Allen Bradley Hardware

The Allen Bradley range includes:

PLC−5 Family. Use when communicating to PLC−5 style processors via Ethernet, DataHighwayPlus or Serial DF1

•

SLC/MicroLogix Family. Use when communicating to SLC 5/05 via Ethernet or Serial DF1, SLC5/0x via DH485 or Serial DF1, MicroLogix 1000/1200/1500 via DH485 or DF1 Serial.

•

SLC 5/04 via DH+. Use when communicating to a SLC 5/04 via DH+• ControlLogix L5555/L5550. Use when communicating to a ControlLogix Processor via1756−ENET, or 1756−ENTB Ethernet Module

•

1761NET (PLC−5). Use when communicating to Ethernet/IP to a PLC−5 style processor via1761−NET ENI Module.

•

1761NET (SLC/MicroLogix). Use when communicating to Ethernet/IP to a SLC or MicroLogixstyle processor via 1761−NET ENI Module

•

CLX Gateway (PLC5) – ControlLogix Gateway to PLC Family via DH+. Use when communicatingto a PLC−5 style processor via Ethernet to DH+ ControlLogix Gateway.

•

CLX Gateway (SLC) – ControlLogix Gateway to SLC 5/04 via DH+. Use when communicating to aSLC 5/04 processor via Ethernet to DH+ ControlLogix Gateway.

•

Allen Bradley Connection Methods

Supported connection methods include:

Serial DF1 (Full−Duplex)• AB 1784−KT (ISA Bus Card)• AB 1784−KTX and 1784−PKTX/D (ISA Card)• AB 1784−PKTX (PCI Card Single Channel Only)• AB 1784−PCMK (PCMCIA Card WIN 9x/NT Only)• SST 5136 SD (ISA and PCI Card)• Ethernet•

Up to 8 adapters can be accessed in a single computer and adapters can access multiple devices as required.

Setup options depend on which method is being used.

Data table addressing covers a wide range of File Types to offer the maximum flexibility without the need tomove / copy data in the hardware.

Allen Bradley Protocols 1

The flexible nature of the connection method configuration means that it is possible to address remote devicesby routing through intermediate hardware and networks.

For minimal installations − say one SLC processor, it is possible make a single device connection simply byconnecting to a serial port and using the DF1 protocol. This can makes very cost effective small installationspossible, without the need to purchase additional hardware or software.

Note: ensure that the connection method selected is supported by the hardware!

Data Types

A range of data types are supported including:

Bit• Byte• Short• BCD Short• Long• BCD Long• Float• String•

For data reads, either a regular poll is initiated on a tag group basis, or, for infrequently accessed points, taggroups can be refreshed on some other event. Data writes are performed per tag and are actioned as soon aspossible after a tag value is changed.

For more details, refer to your PLC documentation or the extensive range of information available at theAllen Bradley website


Data Types 2

http://www.ab.com/

Allen Bradley SetupBefore You Begin

Be familiar with your PLC network:•

Ethernet to PLC−5 / SLC / MicroLogix Know the IPAddress of thePLC’s

Have a list of datatable filesavailable

Ethernet to MicroLogix/SLC/PLC−5 via 1761 NET ENI or Digi 1AI Know the IPAddress of the1761 NET ENI


Ethernet to ControlLogix/CompactLogix CPU (Local Chassis) Know the IPAddress of theEthernet Module

Know the SLOTnumber of theCPU

Have a list ofnative Tag namesavailable

Ethernet to ControlLogix/CompactLogix CPU (Remote Chassis) Know the IPAddress of theEthernet Module

Know the CIPRouting Path ofyour RemoteCPU

Have a list ofnative Tag namesavailable

Ethernet to ControlLogix/CompactLogix via 1761 NET−ENI Know the IPAddress of the1761 NET ENI(Series B)Module

Know the nodenumber assignedto the DF1 port(Channel 0)

Have a list ofnative Tag names

Allen Bradley Setup 3

available

Ethernet to ControlLogix Gateway to DH+ Know the IPAddress of theEthernet Module

Know the CIPRoute Path of thePLC’s

Data Highway Plus to PLC / SLC Know the DH+Address of thePLC (in decimal)


Data Highway 485 to SLC / MicroLogix Know theDH−485 NodeAddress of thePLC’s


Serial DF1 to PLC / SLC / MicroLogix Know theChannel 0settings

Baud Rate

Checksum

If you have RSLinx installed, make sure you disable any drivers:•

Communications −> Configure Drivers −> Startup −> Disable1. Reboot the computer2.

Plan your application

Decide how much data your application will need. Organize PLC data tables so that read / writeoperations can be optimized to reduce network traffic and increase your application performance.

•

Decide on update rates for the data you need. You may need some data point more frequently thatothers. Organize these data points using multiple servers / groups. This will allow to have bettercontrol over data acquisition rates.

•

Quick Configuration

Configuration follows the normal Server – Group – Tags object creation and configuration.

Decide on a suitable connection method from the details below and take note of the settings detailed1. Server. Create a server object under the tree Tags object and do not connect to an OPC server.2. Access the objects server property pane and select Allen Bradley. The panes will change to reflect theselection.

3.



Select the Allen Bradley pane.4. Click Adapter Setup to access the CimQuest IN−GEAR32 – AB Studio Configuration. SetupAdapter(s) as required. Click Help to get full help on setting up adapters.

5.

When finished adapter setup, click Done to close the box.6. Select the appropriate adapter from the drop−down list (0..7). Note the selected adapter should havebeen setup in step 4.

7.

Leave Slave Reg empty (this is for unsolicited data support only).8. Close the server property pages.9. Add a group object to the server.10. Access the group object property pages.11. Access the Group property pane.12. Enter a Refresh Time. This is the time between read requests for the group.13. Select the Allen Bradley property pane.14. Enter properties as required (see below).15. Close the group object property pages.16. Create as many tag objects below the group object as required for the group.17.

Supported PLC's

Your PC Has You’re communicating To This PLC TypeEthernet Card TCP/IP PLC−5 ProcessorEthernet Card TCP/IP SLC 5/05Ethernet Card TCP/IP MicroLogix via 1761 NET ENI

(Series A or B )Ethernet Card TCP/IP PLC−5 / SLC / MicroLogix via

Digi 1AIEthernet Card TCP/IP ControlLogix/CompactLogix

(Local or Remote CPU)Ethernet Card TCP/IP ControlLogix/CompactLogix via

1761 NET ENI Series BEthernet Card TCP/IP ControlLogix Gateway to

PLC−5 or SLC 5/04 via DH+1784 PKTX−SingleChannel (PCI Bus)

Data Highway Plus 57.6K /115K / 230K

PLC−5, SLC 5/04

1784 KTX or KTXD (ISABus)

Data Highway Plus 57.6K /115K / 230K

PLC−5, SLC 5/04

1784 PCMK (PCMCIA) Data Highway Plus 57.6K /115K / 230K

PLC−5, SLC 5/04

1784 KT (ISA Bus) Data Highway Plus 57.6K /115K / 230K

PLC−5, SLC 5/04

SST 5136SD (ISA Bus) Data Highway Plus 57.6K /115K / 230K

PLC−5, SLC 5/04

SST 5136SD (PCI Bus) Data Highway Plus 57.6K /115K / 230K

PLC−5, SLC 5/04

1784 PKTX – SingleChannel (PCI Bus)

Data Highway 485 9600 /19.2K

SLC , MicroLogix

1784 KTX or KTXD (ISABus)

Data Highway 485 9600 /19.2K

SLC, MicroLogix

1784 PCMK (PCMCIA) Data Highway 485 9600 /19.2K

SLC, MicroLogix

Comm Port DF1 – Serial 9600 / 192.K PLC−5 (Channel 0)



Connection Methods

The following notes details how to setup for different PLC types and connection methods.

Accessing Ethernet PLC's

An adapter must be configured for Ethernet Communications and target PLC type.1. Set the Host property to the IP address of the PLC or Ethernet Module.2. The Node property has no meaning3. Set the File Address property to the starting Data Table Element4.

Accessing DH+ / DH−485 PLC's

An adapter must be configured for Data Highway Plus Communications and target PLC type.1. The Host property has no meaning.2. Set the Node property to the PLC’s Data Highway Plus address in decimal3. Set the File Address property to the starting Data Table Element4.

Accessing DH+ / DH−485 PLC's

An adapter must be configured for Data Highway Plus Communications and target PLC type.1. The Host property has no meaning.2. Set the Node property to the PLC’s Data Highway 485 address in decimal3. Set the File Address property to the starting Data Table Element4.

Accessing Serial DF−1 PLC's

An adapter must be configured for Data Highway Plus Communications and target PLC type.1. The Host property has no meaning.2. The Node property has no meaning if communicating point−to−point via Channel 0. Otherwise, setthe .Node property to PLC’s node address in decimal

3.

Set the File Address property to the starting Data Table Element4.

Data Table Addressing

PLC−5, SLC and MicroLogix Data Table Syntax

FileType FileNumber:FileElement [.FileSub−element]

Refer to your Allen−Bradley PLC Users Manual for additional information regarding data elementaddressing.

Examples of PLC−5 and SLC data table addressingI:0, I:0/15 (PLC,SLC, Micro Discrete Input)I:1.3, O:3.7 (SLC Analog Input)B3:100, B3:100/7, B3/255N7:15, N7:15/6F8:325


Connection Methods 6

T4:0.PRE, T4:8.DNPD32:11.SP, PD32:11.MO

PLC−5/250 Data Table Syntax

Module FileType FileNumber:FileElement [.FileSub−element]

Examples of PLC 5/250 data table addressing1N7:100, 2N1:1000, 3B3:1400

FileType FileNumber FileElement FileSub−ElementI – INPUT N/A 0−277 (oct) PLC−5

0−30 (dec) SLC

0 (MicroLogix)

/0 to /15 (DiscreteInput)/0 to /15 (DiscreteInput).0 to .31 (AnalogInput)/0 to 15 (DiscreteInput)

O – OUTPUT N/A 0−277 (oct) PLC0−30 (dec) SLC

0 (MicroLogix)

/0 to /15 (DiscreteOutput)/0 to /15 (DiscreteOutput).0 to .31 (AnalogOutput)/0 to /15 (DiscreteOutput)

S – STATUS N/A 0−127 (PLC−5)0−82 (SLC)0−32 (MicroLogix)

/0 to /15

B – BINARY 3 (default) or userdefined

0−999 (PLC−5)0−255 (SLC)0−31 (MicroLogix)

/0 to /15

T – TIMER 4 (default) or userdefined


.EN

.TT

.DN

.PRE

.ACCC – COUNTER 5 (default) or user

defined0−999 (PLC−5)0−255 (SLC)0−31 (MicroLogix)

.CU

.CD

.DN

.OV

.UN

.UA (SLC only)

.PRE

.ACCR – CONTROL



6 (default) or userdefined


.EN

.EU

.DN

.EM

.ER

.UL

.FD

.UL

.IN

.LEN

.POSN – INTEGER 7 (default) or user

defined0−999 (PLC−5)0−255 (SLC)0−104 (MicroLogix)

/0 to /15

F – FLOATINGPT.

8 (default) or userdefined

0−999 (PLC−5)0−255 (SLC)N/A (MicroLogix)

N/A

L − LONG User defined N/A (PLC−5)N/A (SLC)0 – 255 (Micrologix)

D – BCD User defined 0−999 (PLC−5)0−255 (SLC)N/A (MicroLogix)

/0 to /15

A – ASCII User defined 0−999 (PLC−5)0−255 (SLC)N/A (MicroLogix)

/0 to /15

ST – STRINGTBL

User defined 0−999 (PLC−5)0−255 (SLC)MicroLogix

N/A

PD – PID BLK User defined 0−999 (PLC−5)N/A(SLC/MicroLogix)

.INI

.SPOR

.OLL

.OLH

.EWD

.DVNA

.DVPA

.PVLA

.PVHA

.EN

.CT

.CL

.PVT

.DO

.SWM

.CA

.MO

.PE

.SP

.KP



.KI

.KD

.BIAS

.MAXS

.MINS

.MAXO

.MINO

.UDP

.PV

.ERR

.OUT

.PVH

.PVL

.DVP

.DVN

.PVDB

.DVDB

.MAXI

.MINI

.TIE

.ADDR[0−3]

.DATA[0−13]SC – SFC StatusUser Defined 0−999 (PLC−5)

N/A(SLC/MicroLogix)

.SA

.FS

.LS

.OV

.ER

.DN

.PRE

.TIMMG – MSG BLK User defined 0−999 (PLC−5)

N/A(SLC/MicroLogix)

.NR

.TO

.EN

.ST

.ER

.CO

.EW

.ERR

.RLEN

.DLEN

.DATA[0−51]BT – BLK XFR User Defined 0−999 (PLC−5)

N/A(SLC/MicroLogix)

.EN

.ST

.DN

.ER

.NR

.TO

.RW

.RLEN

.DLEN

.FILE



.ELEM

.RGS

ControlLogix Options

Note: This not all of the options described below are available in this release of Saturn−X425.

ControlLogix Local CPU

Controller Platforms: ControlLogix/CompactLogix

A Local CPU is when the ControlLogix CPU resides in the same I/O chassis as the 1756 Ethernet Module.

Configure the adapter with following settings:

DeviceType = Ethernet• PLCType = ControlLogix L55x•

Accessing a Local CPU

Enter the IP Address of the 1756 Ethernet Module in the Host Property1. Enter the I/O Chassis Slot of the ControlLogix in the Node Property2.

Example: ControlLogix CPU is located in Slot 0 of the I/O chassisHost = “192.168.23.10”Node = 0

ControlLogix Remote CPU

Controller Platforms: ControlLogix/CompactLogix

A Remote CPU is when the ControlLogix L555x CPU resides in a different I/O chassis than the 1756Ethernet Module.

Configure the adapter with following settings:


Accessing a Remote CPU

Enter the IP Address of the 1756 Ethernet Module in the Host Property1. Enter the CIP Routing Path in the Node Property(See CIP Routing Path Information)

2.

Remote ControlLogix over ControlNet

The Node Property needs a CIP routing to access remote ControlLogix processors over ControlNet.



Saturn−X425 uses a dotted−decimal CIP routing path. You can have up to 32 hops in a CIP routing path.

Local Chassis Remote Chassis1756ENET

BackPlane Local1756−CNBR

Remote1756−CNBR

BackPlane Remote1756−Lx CPU

A B C D E F

Routing Path Elements

A Backplane Number (Always 1)B Slot Number of Local 1756−CNBR (decimal value)C Channel Number of Local 1756−CNBR (2 = Channel A)D ControlNet Node ID of Remote 1756−CNBR (decimal value)E Backplane (Always 1)F Remote 1756−Lx CPU Slot Number (decimal)

Example CIP Routing Path:

Adapter = 0Host = “192.168.25.10”Node = “1.2.2.8.1.4”

1 = Backplane

2 = Local 1756−CNBR (Located in slot 2)

2 = (Use Channel A of Local 1756−CNBR)

8 = ControlNet Node ID of Remote 1756−CNBR (Node 8)

1 = Backplane

4 = 1756−Lx CPU Slot Number

Remote ControlLogix over DataHighway Plus

You enter a CIP routing path to bridge to a ControlLogix processor over Data Highway Plus. Saturn−X425uses a dotted−decimal CIP routing path. The server supports up to 32 hops in a CIP routing path.



Local Chassis Remote Chassis1756ENET

Backplane Local1756−DHRIO

Remote1756−DHRIO

Backplane Remote1756−Lx CPU

A B C D E F

Routing Path Elements

A Backplane Number (Always 1)B Slot Number of Local 1756−DHRIO (decimal value)C Channel Number of Local 1756−DHRIO (2 = ChA, 3 = ChB)D DH+ Address of Remote 1756−DHRIO (decimal value)E Backplane (Always 1)F Remote 1756−Lx CPU Slot Number (decimal)

Example CIP Routing Path

Adapter = 0Host = “192.168.20.23”Node = “1.0.3.23.1.4”

1 = Backplane

0 = Local 1756−DHRIO (Located in slot 0)

3 = (Use Channel B of Local 1756−DHRIO)

23 = DH+ Address of Remote 1756−DHRIO (23 decimal = 27 octal)

1 = Backplane

4 = 1756−Lx CPU Slot Number

ControlLogix Gateway

Controller Platforms: ControlLogix/CompactLogix/PLC−5 DH+ / SLC DH+

Accessing PLC−5’s or SLC 5/04 CPU’s over Data Highway PLUS via ControlLogix Gateway

Set the IP Address of the 1756 Ethernet Module in the Host Property1. Set the CIP Routing Path of the PLC in the Node Property(See CIP Routing Path Information)

2.



Understanding Control Logix Gateway Routing Path

When addressing a PLC node through a ControlLogix Gateway, Saturn−X425 uses a CIP Routing.

Always start with “1”• I/O Slot of the 1756−DH+/RIO Module• The 1756−DH+/RIO Channel to Use (A or B)• The Data Highway Plus Node Address of the target PLC. (Decimal Address)•

Example:

Host = “192.168.32.11”Node = “1.0.A.17”

Route Path 1.0.A.17 will access the PLC Node 17 (decimal) using Channel A of the 1756−DH+/RIO modulelocated in Slot 0 of the Control Logix Chassis.

Example:Host = “192.168.12.33”Node = “1.0.B.23”

Route Path 1.0.B.23 will access the PLC Node 23 (decimal) using Channel B of the 1756−DH+/RIO modulelocated in Slot 0 of the ControlLogix Chassis.

ControlLogix/CompactLogix via 1761 NET ENI

Controller Platforms: ControlLogix / CompactLogix

The 1761 NET ENI must be a Series B or later. The 1761−NET ENI Series A does not support connectionsto Channel 0 on the ControlLogix/CompactLogix processors.

Configure the adapterDriver with following settings:


Accessing ControlLogix / CompactLogix via 1761 NET ENI

Set the IP Address of the 1761 NET ENI Ethernet Module in the Host Property1. Set the CIP Routing Path of the PLC in the Node Property(See CIP Routing Path Information)

2.

Understanding Routing Path



When addressing a ControlLogix / CompactLogix node through a 1761 NET ENI Saturn−X425 uses a CIPRouting.

Always start with “B”• DF1 Channel Node Number•

Example:

Host = “192.168.1.35”Node = “B.1”

Route Path B.1 will access the Node 1 using Channel B of the 1761 NET ENI at IP address 192.168.1.35

CIP Routing Path Expression

CIP Route Path Expression is an optional method of entering a CIP routing paths that is easy to understand.The CIP routing path expression option uses symbol replacement for creating routing paths.

SYMBOL Meaning

BK Backplane – replaces “1”

BP Backplane – replaces “1”

@ “at” signed replaces . (period)

/ Slash sign replaces . (period)

−> . (period)

, Comma replaces . (period)

[ ] Square brackets (optional) can be used to identifymodule, node or segment

( ) Parenthesis (optional) can be used to identify module,node or segment

{ } Curly Braces (optional) can be used to identify module,node or segment

Examples

Node = “BP @ [2/B] −> (3)”

This is an example of a simple segment to a DH+ node via ControlLogix Gateway:

Backplane at Module 2 / Channel B goto Node 3

Node = “BP @ [3/A] −> (1) , BK @ [0]”



This is an example of addressing a ControlLogix processor on 1 remote hop

Backplane at Module 3 / Channel A goto Node 1, Backplane at Module 0

Node = “{ BP @ [3/A] −>(1) } , { BK @ [10/A] −> (6) } , { BP @ [4] }”

This example addresses a ControlLogix processor across 2 hops, and uses { } to define individual segments

{ Backplane at Module 3 / Channel A goto Node 1 } , { Backplane Module 10 / Channel A goto Node 6 } , {Backplane at Module 4 }

ControlLogix String Tags

String Tags are structures that consist of 2 members:

.DATA – This is ASCII data which is an array of chars (SINTS)

.LEN – This is a DINT value for the length of the ASCII data

ControlLogix TagData Type Type Specifier .FileAddr Property SettingMyString.DATA ASCII Member$ File Address = “MyString.DATA[0]$”MyString.LEN Length

Member& File Address = “MyString.LEN&”

ControlLogix Native Tage Type Declaration

When addressing a ControlLogix Native Tag for writing, Saturn−X425 needs to know the data type of thetag. A type−declaration character must be appended to the end of the native tag name in the property

Type DeclarationData Type ControlLogix Native Tag NameFileAddrProperty TagName

? BOOL MyBOOL MyBOOL?% INT MyINT MyINT%& DINT MyDINT MyDINT%! REAL MyREAL MyREAL!$ SINT / STRING MySINT MySINT$

ControlLogix Controller Scope Tags

To address a Controller Scope tag, simply enter the tag name with the type−declaration specified in the FileAddress property.



ControlLogix TagData Type Type Specifier .FileAddr PropertySetting

MyBOOL BOOL ? File Address =“MyBOOL?”

Bool1D BOOL Array 1 Dimension ? File Address =“Bool1D[0]?”

Bool2D BOOL Array 2 Dimension ? File Address =“Bool2D[0,0]?”

Bool3D BOOL Array 3 Dimension ? File Address =“Bool3D[0,0,0]?”

MyINT INT % File Address =“MyINT%”

INT1D INT Array 1 Dimension % File Address =“Int1D[0]%”

INT2D INT Array 2 Dimension % File Address =“Int3D[0,0,0]%”

MyDINT DINT & File Address =“MyDINT&”

DINT1D DINT Array 1 Dimension & File Address =“DINT1D[0]&”

DINT2D DINT Array 2 Dimension & File Address =“DINT2D[0,0]&”

DINT3D DINT Array 3 Dimension & File Address =“DINT3D[0,0,0]

MyREAL REAL ! File Address =“MyREAL!”

REAL1D REAL Array 1 Dimension ! File Address =“REAL1D[0]!”

REAL2D REAL Array 2 Dimension ! File Address =“REAL2D[0,0]!”

REAL3D REAL Array 3 Dimension ! File Address =“REAL3D[0,0,0]!”

MySINT SINT $ File Address =“MySINT$”

SINT1D SINT Array 1 Dimension $ File Address =“SINT1D[0]$”

SINT2D SINT Array 2 Dimension $ File Address =“SINT2D[0,0]$”

SINT3D SINT Array 3 Dimension $ File Address =“SINT3D[0,0,0]$”

ControlLogix Program Scope Tags



To address a Program Scope Tag is similar to a Controller Scope Tag, however, you must prefix the tag namewith:

PROGRAM: − This tells the ControlLogix the scope of the tag• PROGRAM NAME. – This specifies the location of the tag• TAGNAME – The Native Tag name• Type−Declaration specifier.•

Examples

File Address = “PROGRAM:MainProgram.MyIntTag%”

File Address = “PROGRAM:PowerConsumption.Watts!”

ControlLogix User Defined Types

You can access individual members of a User Defined Type as you would any other native tag. Theindividual member must be one of the following data types:

BOOL or BOOL ARRAY• INT or INT ARRAY• DINT or DINT ARRAY• REAL or REAL ARRAY• SINT or SINT ARRAY•

Examples:

File Address = “MyUDT.IntValue%”

File Address = “MyUDT.FloatArray[0]!”

The entire User Defined Type cannot be read or written as a single item. You must read/write to theindividual members of the UDT.

ControlLogix Pre−defined Data Types

Pre−defined data types such as TIMERS and COUNTERS are structures. You need to address the individualmembers of the data type for read / write access.

The individual member must be one of the following data types:

BOOL• INT• DINT•



REAL• SINT or SINT ARRAY•

Examples:

File Address = “MyTimer.PRE&”

File Address = “MyCounter.DN?”

TIMER .PRE.ACC.EN.TT.DN

COUNTER .PRE.ACC.CU.CD.DN.OV.UN.UA

MESSAGE .Flags.ERR.EXERR.DN_LEN.EW.DN.ST.TO.EN_CC

MOTION_GROUP .GroupStatus,.MotionFault.ServoFault.GroupFault.InhibStatus..GroupSynced.ACAsyncConnFault.ACSyncConnFault.POtrvlFault.NotrvlFault.PosErrorFault.EncCHALLossFault.EncCHBLossFault.EncCHZLossFault.EncNsFault.DriverFault.SyncConnFault.HardFault



.GroupOverlapFaultMOTION_STATUS .Flags

.ERR

.STATUS

.STATE

.EN

.EW

.DN

.ER

.PC

.IPPID .CTL

.SP

.KP

.KI

.KD

.BIAS

.MAXS

.MINS

.DB

.SO

.MAXO

.MINO

.UPD

.PV

.ERR

.OUT

.PVH

.PVL

.DVP

.DVN

.PVDB

.DVBD

.MAXI

.MINI

.TIE

.MAXCV

.MINCV

.MINTIE

.MAXTIE

.DATA[0−16]

.INI

.SPOR

.OLL

.OLH

.EWD

.DV

.DVNA

.DVPA

.PVLA

.PVHA



.EN

.CT

.CL

.PVT

.DO

.SWM

.CA

.MO

.PE

.NDF

.NOZC

.NOBC

Unsolicited Message

Unsolicited messages are not supported from ControlLogix processors, or PLC’s connected via 1761−NETENI Ethernet modules.

In a Peer−To−Peer network such as Data Highway Plus, PLC’s have the capability to be the message initiator,and send data to other nodes on the network. Instead of Saturn continually polling and evaluating dataregisters, you could program the PLC to send the data on an exception basis. From Saturn's point−of−view, itreceived data it did not explicitly ask for, or an unsolicited message. Saturn could then sit idle waiting to benotified when data arrives, along with who sent it, and how much it received.

Types of Unsolicited Messages Supported

Saturn supports unsolicited messages from PLC−5 Ethernet, SLC5/05 Ethernet, Data Highway Plus, DataHighway 485 and DF1.

DH+, PLC−5 EthernetPLC−2

UNPROTECTEDWRITE

DH−485, SLC5/05Ethernet

PEER−TO−PEERWRITE 485−CIF

Setting up Saturn to received Unsolicited Messages

Set the server SlaveReg Property to the PLC−2 Style octal address you want the control to beregistered as.

1.

Set the Adapter Property to Adapter you want to receive the message on.2. Create a script to decode incoming data connected to the WriteNotify event of the Saturn server object3.



Allen Bradley

Read the Allen Bradley Setup Page for details on configuring server and group objects for use with AllenBradley PLCs.

Allen Bradley configuration consists of this page, the Group Allen Bradley property page, the Group propertypage settings and the Adapter Configuration application.

Adapter

Allen Bradley devices are accessed by adapter, numbered 0..7. An adapter must be configured before it can beused. One adapter can be assigned to each server object. More than one server object can be configured to usethe same adapter if desired.

To setup individual adapters click the Adapter Setup button to access the separate configuration program. Thisprogram has its own help system which can also be accessed directly from its main window.

Slave Reg

For normal use, this entry should be left empty. To receive unsolicited data from PLCs, this property shouldbe set, a script written to decode incoming data and PLC(s) programmed to send data.

The Allen Bradley server can accept unsolicited data. This property sets the data address used to receiveunsolicited data. Setting this value in the range 10−777 octal enables the server to emulate a starting block ofPLC−2 type registers.

Allen Bradley 21

Allen Bradley Group

Read the Allen Bradley Setup Page for details on configuring server and group objects for use with AllenBradley PLCs.

Node

Enter the Node address for the target controller CPU.

Offset

Optional setting, needed if data writes are to be made to tags in the group. See File Address below for details.

File Address

The starting data point to read / write in the PLC.

If only reads are performed on the PLC, then set this in the style: S:4 or N7:0

If writes are to be made to any Saturn tag other than the first in the group, then a modified format is required.%i should be inserted into the File Address string for the portion of the address which will be different fordifferent tag writes.

Example: For 8 addresses starting N7:4, enter N7:%i and set the Offset property above to 4. when Saturnreads the whole group, it will create the string: N7:4 and set the number of points to read to the number of tagsin the group. For writes, which are single tag, Saturn will generate a different string for each tag. Thus for thethird tag, the address string used will be: N7:7

It will be necessary to place the %i substring in a different part of the File Address string for different datatypes.

Allen Bradley Group 22

Data Type

Select the way Saturn treats data passed to / from the PLC.

Ethernet Host

Only used for Ethernet connections. Normally, the IP address of the PLC Ethernet module in the form of adotted−quad address such as: 192.11.17.4

Ethernet Timeout

Only used for Ethernet connections. Determines how long Saturn waits for a response from an Ethernetprocessor before timing out.


Allen Bradley Group 23

Date post:	24-Oct-2014
Category:	Documents
Upload:	gondai
View:	240 times
Download:	13 times

Allen Bradley Protocols

Documents