0% found this document useful (0 votes)
64 views11 pages

RACLib E3 AppUserManual Ext-V1

The document provides instructions for integrating Rockwell Automation's E3plus overload relays into an RSLogix5000 application using DeviceNet. It recommends: 1. Configuring the DeviceNet network and E3 relays using RSNetworx. 2. Generating tags for all DeviceNet devices using the DeviceNet Tag Generator tool to automate tag and structure creation. 3. Changing the data types of tags related to E3 relays to match the data types expected by the E3plus module. 4. Coding the application to read and write data to the E3 relays via the E3plus module, linking it to a motor block as the parent.

Uploaded by

Jared Tapia
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
64 views11 pages

RACLib E3 AppUserManual Ext-V1

The document provides instructions for integrating Rockwell Automation's E3plus overload relays into an RSLogix5000 application using DeviceNet. It recommends: 1. Configuring the DeviceNet network and E3 relays using RSNetworx. 2. Generating tags for all DeviceNet devices using the DeviceNet Tag Generator tool to automate tag and structure creation. 3. Changing the data types of tags related to E3 relays to match the data types expected by the E3plus module. 4. Coding the application to read and write data to the E3 relays via the E3plus module, linking it to a motor block as the parent.

Uploaded by

Jared Tapia
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 11

Rockwell Logix 5000 Standard Software Library for Holcim

User Manual

Creating RSLogix5000 Applications

Extension by
E3plus Module

Edited by: Rockwell Automation


REVISION MANAGEMENT

Document Information

Created by: Rockwell Automation


Hanspeter Indermühle

Date of 1st edition: 2007-07-03

Revisions

Revision Date Description


1.0 2007-07-03 1st Edition

Change Index

Chapter Date Description


Table of contents

1. INTRODUCTION ................................................................................................................. 4
2. E3 INSTALLATION AND WIRING ....................................................................................... 5
2.1 System: ..................................................................................................................... 5
3. RECOMMENDED WORKFLOW: ........................................................................................... 5
3.1 RSNetworx for DeviceNet ......................................................................................... 6
3.2 DeviceNet Tag Generator .......................................................................................... 9
3.3 Exchange Data Type................................................................................................ 10
3.4 Application RSLogix5000: ....................................................................................... 11
1. INTRODUCTION

Templates are operating the same as regular MotorN but with the add-on information of the
E3 module. Warning status, Trip status, Therm. Utilized and average current. The E3p_AOI
don’t have a specific HMI Template. Each Motor Device with E3plus Overload Relay will call a
specific HMI Template such as 06_MotorN_E3_small or 06_MotorN_E3_large.

The E3p_AOI module is an interface block between Network (scanner) and Motor block.
We don’t know any parameter at this module. There are noting to configure inside the
module structure.

Principal Diagram:

ScanList

"T
Node3 ag
G
en
er
at
or
fo
r D
ev
ic eN
et
"
CLX

DNB

DeviceNet

+24V
K
IN1
E3p IN2
E3p
OUT A
Node3
OUT B DX

DY

Motor
2. E3 INSTALLATION AND WIRING
Read User Manual 193-UM002C-EN-P/ Chapter 2 for details.

2.1 System:
The E3 Overload Relays provide for data exchange over the Network a configurable Input
and Output Assemblies.
Input’s (Data from E3) are 8 Bytes (4Words) and
Outputs (Data to E3) are 1Byte.
Note: If you will read more data out of the E3 then we have the possibility to go with
explicit messaging. However this asynchronous messaging will generate a high
communication load at the processor. IMPORTANT: Don’t use a MSG (explicit message)
operation to get data from the E3 Device.

3. RECOMMENDED WORKFLOW:

1. Configuration of the whole DeviceNet network related to a DNB-Scanner Module. This


is Possible in Online or Offline Mode. Don’t forget to set the E3plus Parameter
accordantly.
2. With Rockwell Automation Tool “DeviceNet Tag Generator” generate all Tags and
Structures of the DeviceNet Network. Following the 6 step Wizard easily.
3. Exchange all Data Types of E3 Data Tags which are create before by DeviceNet Tag
Genrator with common UDT “E3_Inp” respectively “E3_Out”.
4. Code programming in your application routine.
3.1 RSNetworx for DeviceNet
With this Software you have to configure all E3 Overload Relays which are connected at the
whole Network.
-This Document descried only additional configuration action.
Note: read carefully the User Manual, 193-UM002C-EN-P before you begin with programming
and use this manual as a reference for all question first.
E3 Operational parameters:

Below is a list of all parameters that must be set correctly in the E3. All others that are not
in this list should be left at their default value or doesn’t take affect at the E3p_AOI.

General list:

Par # Description

24 Trip enable
25 Warning enable
27 Single/three phase
28 FLA setting
30 OL/PTC reset mode
31 OL reset level
32 OL warning level
59 Output assembly
60 Input assembly
61 Assy word 0
62 Assy word 1
63 Assy word 2
64 Assy word 3

Parameter 24 Trip enable: (default).


Parameter 25 Warning enable.

Parameter 27 Single/three phase: Set to three phases.

Parameter 28 FLA setting: Set to full load amps from the motor nameplate.

Parameter 30 OL/PTC reset mode: Set to manual. E3 will not reset automatically.

Parameter 31 OL reset level: 75% (default). User will not be able to reset E3 until therm util.
is below this value.

Parameter 32 OL Warning level: 85% (default). E3 will show an overload warning when
therm util. is equal or above this value.

Parameter 59 Output assembly: 105

Parameter 60 Input assembly: 100

Parameter 61 Assy word 0: 21 (device status)

Parameter 62 Assy word 1: 14 (trip status)

Parameter 63 Assy word 2: 4 (Therm. Util.).

Parameter 64 Assy word 3: 9 (Average current).


3.2 DeviceNet Tag Generator

We recommend using the RSLogix5000 Tool “DeviceNet Tag Generator” to create all Tags
and Structures automatically in to your RSLogix5000 Project Application. This is a free Tool
and available at the RSNetWorx CD or can be Downloaded at the www.ab.com web side.

This useful Tool will also create some additional Routines and code in your project acd file.
The created code is handling all Data exchange between DeviceNet -Scanner Data list and
your Application. Also creates structures and all Tags related to each E3 by unique tag
names.
E.g. DNB_N03_POL_I DeviceNet Imput Data from Note 3
DNB_N03_POL_O DeviceNet Output Data to Note 3

Legend: ScannerName_Note#_Polled_Input
DNB N03 POL I

The Data Type which DeviceNet Tag Generator automatically creates is named by the
Catalog Number explanation and parameter configuration!

E.g. AB_193592_EC2P_I_70847BCC
Unique code#; depends the
parameter configuration.
3.3 Exchange Data Type

To match later on the Tags to the E3p_AOI DataInp resp DataOut we have to change the
Data type of each E3 related Tag!
You can do it by one by one at the Controller Tag Database or you can go with Tag export
/import function and change the Data Type in an Excel csv file.
Note: You have exactly to know which Note Number are related to an E3.
3.4 Application RSLogix5000:

The “Tool DeviceNet Tag Generator” creates also for you new program routines for all
DeviceNet Scanner data read and also for data write commands.

Application code example:

IMPORTANT:
Always program the E3p_AOI after a Motor block! The ParentBus is always linked to the
Motor local Bus! I.e. MotorName_C.Bus

You might also like