Schneider Electric LUFP9 Appendix D DeviceNet Objects, List of the Gateway’s DeviceNet Objects

Page 94

10. Appendix D: DeviceNet Objects

10.1. Introduction to the Gateway’s DeviceNet Objects

The LUFP9 gateway’s software has been developed in accordance with the Object Modelling from the DeviceNet protocol. This model leads to a method used for addressing the gateway’s data, known as Attributes, made up of four separate values: c the node address (MAC ID), d the Object’s class identifier (Class ID), e the Instance Number (Instance ID) and f the Attribute Number (Attribute ID). An address made up in this way is known as a “Path”. The Connection by Explicit Messaging, for example, uses paths of this sort to exchange data from one point to another on a DeviceNet network.

Address

Min. – max.

Description

Node

0 –

63

This field allows you to address one subscriber out of the series of subscribers on a

DeviceNet network using its MAC ID.

 

 

 

Class

1 – 65 535

All objects sharing the same characteristics belong to the same class, characterized by its

Class ID.

 

 

 

 

 

 

The instances represent the various objects from one class. All instances from one class

 

 

 

share the same behaviours (1) and the same attributes, but each of them has its own set of

Instance

0 – 65 535

values for these attributes. When a subscriber creates an instance (instantiation), he assigns

 

 

 

a unique Instance ID, which allows the other DeviceNet subscribers to have individual

 

 

 

access to it.

 

 

 

Each attribute represents one of the characteristics of the Instances belonging to the same

 

 

 

class. It is assigned some sort of value (byte, unsigned integer, character string, etc.) in

 

 

 

order to supply information about the subscriber’s status or to make settings on the

Attribute

1 –

255

subscriber’s behaviours (1).

N.B. To access the attributes of an object’s base class, you need to use Instance 16#00

 

 

 

 

 

 

when entering the full path. e.g. To access the “Revision” attribute from the “Identity Object”

 

 

 

class for DeviceNet subscriber no. 4, you will need to use the following path:

 

 

 

“16#04 • 16#01 • 16#00 • 16#01”.

(1) The behaviours designate actions taken by a DeviceNet object in response to particular events.

10.2. List of the Gateway’s DeviceNet Objects

Class

ID

Required

Instances

Interfaces

Identity object

16#01

Yes

1

Message router

Message router

16#02

Yes

1

Explicit message connection

DeviceNet object

16#03

Yes

1

Message router

Assembly object

16#04

No

2 (1)

I/O connections or Message router

Connection object

16#05

Yes

4 (2)

I/O connections or Explicit messages

Acknowledge handler object

16#2B

No

1

I/O connections or Message router

I/O data input mapping object

16#A0

No

1

Message router

I/O data output mapping object

16#A1

No

1

Message router

Diagnostic object

16#AA

No

1

Message router

(1)One input area and one output area are created in the gateway’s memory.

(2)The four instantiated connections are as follows: c Explicit Connection, d Polled Command/Response, e Bit Strobed Command/Response and f Change-of-State / Cyclic. The last three connections are of the “I/O Connection” type.

94

Image 94
Contents LUFP9 Page LUFP9 Page Table of contents Introduction Introduction to the user guideTerminology Introduction to the LUFP9 GatewayAltistart Notational Conventions Additional DocumentationDownstream network no.3 Modbus ModbusModbus VW33-A48 Downstream network no.1Principle Used to Configure and Operate the LUFP9 Gateway ABC Configurator Modbus networkRSLogix LUFP9 gatewayRSNetWorx DeviceNet NetworkHardware Implementation of the LUFP9 Gateway Configuration Modbus RTUOn Receipt Mounting the Gateway on a DIN Rail Powering the gatewayMounting the gateway Dismounting the gateway Connecting the Gateway to the Modbus Network Examples of Modbus connection topologiesLUFP9 gateway TSXCSA00 Pin outs120 Ω Wiring recommendations for the Modbus networkHubs, drops, taps, and line terminations Cables Connecting the LUFP9 gateway to the DeviceNet networkWire colour PinConfiguring DeviceNet Communication Features Selector Switches DeviceNet speed 3 4 5 6 7Speed Address Mac ID Selector DeviceNet Switches Address 3 4 5 6 7Encoding the Gateway Address Signalling System Architecture Software Implementation of the GatewayIntroduction DeviceNet Master PLC SLC500 DeviceNet upstream networkModbus cycle time Configuring the Motor StartersManaging degraded modes Installing the Gateway Description File Configuring the Gateway in RsNetWorxSelecting and adding the master PLC’s DeviceNet scanner Selecting and Adding the Gateway to the DeviceNet Network Editing gateway parametersSoftware Implementation of the Gateway Configuring the DeviceNet Scanner I1.1 Configuring Inputs from the GatewayService PLC input Description I1.2O1.1 Configuring Outputs Intended for the GatewayService PLC output Description O1.2Output Value Meaning MSB + LSB Description of Services Assigned to Gateway Inputs/OutputsInput Value Meaning MSB + LSB Transferring the DeviceNet Scanner Configuration Developing a DeviceNet ApplicationSummary Gateway Initialization and DiagnosticsFull Management Control/Status Byte field Sub-chapterFbdu Modbus exchange startup Fbhssend New DeviceNet master command wordBits Description ED Error data item associated with the Modbus network Bits Description Abchssend New gateway diagnostic11EC Error code associated with the Modbus network Gateway Status WordDescription of the error Diagnostic only DeviceNet Master Command Word Simplified Operation Configuring the Gateway Connecting the Gateway to the Configuration PCMale RJ45 LUFP9 Configuration Female RJ45RS-232 link protocol PC COM Male 9 point SUB-DInstalling AbcConf Importing the Gateway ConfigurationTransferring a Configuration to the Gateway Monitoring the Content of the Gateway’s MemoryConfiguring the Gateway Procedure for deleting a Modbus slave Deleting a Modbus SlaveAdding a new type of Modbus slave Copying a previously configured Modbus slaveAdding a Modbus Slave Keyboard shortcut CtrlImporting/exporting a Modbus slave configuration Changing the Periodic Data Exchanged With a Modbus Slave Replacing a Periodic Input Data ElementReplacing an Output Periodic Data Element Increasing the Amount of Periodic Input Data Configuring the Gateway Configuring the Gateway I1.19 I1.17I1.18 I1.20Configuring the Gateway Configuring the Gateway Configuring the Gateway O1.17 O1.18Deleting Aperiodic Parameter Data Configuring the Gateway Changing a Modbus slave Configuration Changing the Name of a Modbus SlaveChanging the Address of a Modbus Slave With TeSys U Motor Starters Adding and Setting Up a Modbus CommandName of the Modbus command Modbus query Modbus responseWith a Generic Modbus Slave Configuring the Gateway DeviceNet Configuring the Query Configuration Description ElementConfiguring the Gateway Default communication mode. The query is transmitted Configuring the Response Configuring the Content of the Query Frame Field Size Description FrameSize FieldFrame Mode. The default value, CRC, should not be changed Configuring the Content of the Response FrameAdding a Special Modbus Command Modbus Commands Based on Standard CommandsModbus Commands which Can Be Completely Changed by the User Configuring the General Characteristics of the Gateway Fieldbus elementABC Element Sub-Network Element Configuring the Gateway Adding a Broadcaster Node Communication Characteristics Appendix a Technical CharacteristicsEnvironment Inputs Input data areaOutput data area OutputsGeneral data General data area16#10 Appendix B Default ConfigurationConfiguring Modbus exchanges 16#06Content of the Gateway’s Dpram Memory Input Data Memory Area16#0200 Appendix C Practical Example RSLogix Main Program LAD 2 MAINLUFP9Address Symbol Description ScanvalidationCmdreset Module Address Symbol DisplayAppendix C Practical Example RSLogix Numparam Appendix C Practical Example RSLogix Wrrunning Address Symbol Display Reserves relating to the RSLogix 500 exampleList of the Gateway’s DeviceNet Objects Appendix D DeviceNet ObjectsIntroduction to the Gateway’s DeviceNet Objects Class Required Instances InterfacesGraphical Representation of the Gateway’s DeviceNet Objects Identity Object class 16#01Services of instance 16#01 of class 16#01 Attributes of instance 16#01 of class 16#01Message Router Object class 16#02 DeviceNet Object class 16#03Services in class 16#04 Assembly Objects Class 16#04Services of instance 16#01 of class 16#03 Revision index of the Assembly Object classAttributes of instance 16#64 of class 16#04 Modbus Inputs Services of instances 16#64 and 16#96 of class 16#04Connection Object Class 16#05 Attributes of instance 16#96 of class 16#04 Modbus OutputsServices in class 16#05 Attributes of class 16#0516#83 Initial comm. characteristicsWatchdog timeout action Produced connection IDAccess Name Type Value 16#01 Get StateGet / Set Produced connection path Type Value16# 20 04 24 64 30 Type Value 16#07 Get / Set Produced connection size Type Value 16#04 Get / Set Produced connection ID #0 xxAttributes of instances 16#01 to 16#04 of class 16#05 Services in class 16#2BAcknowledge Handler Object class 16#2B Attributes of class 16#2BType Value 16#06 Get Data with ack path list size Services of instance 16#01 of class 16#2BData with ack path list 10.10. I/O Data Input Mapping Object Class 16#A0 Services in class 16#A0Services of instance 16#01 of class 16#A0 Attributes of class 16#A010.11. I/O Data Output Mapping Object Class 16#A1 Services in class 16#A1Services of instance 16#01 of class 16#A1 Attributes of class 16#A1Attributes of class 16#AA Diagnostic Object Class 16#AAServices in class 16#AA Attributes of instance 16#01 of class 16#AADeviceNet module status Access Name Need Type Value 16#09 Get LED statusModule type Changed data fieldServices of instance 16#01 of class 16#AA Appendix E Modbus Commands Preset Single Register command 16#06 Read Holding Registers Command 16#03Frame Field Value or properties Preset Multiple Registers Command 16#10 Modbus Protocol Exception ResponsesCode Name Description of the exception Exception Page User’s manual V1.0 2003-03