Schneider Electric LUFP9 user manual Diagnostic Object Class 16#AA, Attributes of class 16#AA

Page 110

10. Appendix D: DeviceNet Objects

10.12. Diagnostic Object (Class 16#AA)

The “Diagnostic Object” has only one instance (Instance ID = 16#01) and is specific to the LUFP9 gateway. It contains a large amount of diagnostic data of all levels. As a result, some of these diagnoses should not be used, as these are reserved for maintenance operations carried out on the gateway or when developing its software. However, the attributes to which they correspond are all described below for the sake of completeness.

Attributes of class 16#AA

ID

Access

Name

Need

Type

Value

Description

16#01

Get

Revision

Optional

UINT

1

Revision index of the “Diagnostic Object” class.

Services in class 16#AA

Service code

Name of the service

Need

Description

16#0E

Get_Attribute_Single

Required

This service allows to read the value of one of the class attributes.

Attributes of instance 16#01 of class 16#AA

ID

Access

Name

Need

Type

Value

16#01

Get

DeviceNet module serial number

Optional

UDINT

(variable)

The value of the “DeviceNet module serial number” corresponds to the serial number of the gateway’s AnyBus-S DeviceNet card, that is to say the card on which the block of selector switches and the DeviceNet connector are located. e.g. 16# 20 DD 00 23.

16#02

Get

Vendor ID

Optional

UINT

16#0001

The value of this attribute is set to 16#0001 for the LUFP9 gateway.

The value 16#0000 cannot be used and values between 16#0002 and 16#FFFF are reserved for the gateway suppliers.

16#03

Get

Fieldbus type

Optional

UINT

16#0025

 

With the LUFP9 gateway, this attribute always takes the same value (16#0025), as it characterizes the

 

DeviceNet network. Any other value would be incorrect (e.g. 16#0001 for a Profibus-DP network).

16#04

Get

DeviceNet module software version

Optional

UINT

16#0105

This attribute shows the software version on the gateway’s AnyBus-S DeviceNet card. The major index of this version is given by the most significant byte and its minor index is given by the least significant byte, both in BCD format. e.g. 16#0105 corresponds to version 01.05.

16#05

Get

Interrupt count

Optional

UINT

(counter)

 

The value of the “interrupt count” is incremented by one every time an interrupt related to the management of the

 

downstream Modbus network do occur.

 

 

 

16#06

Get

Watchdog counter in

Optional

UINT

16#0000

This counter is not implemented, and using this attribute is pointless.

The primary function of this counter is to provide feedback from the lifetime counter represented by attribute 16#07, which would allow the AnyBus-S DeviceNet card to ensure that the card to which it is connected is working properly by comparing the values of these two attributes.

16#07

Get

Watchdog counter out

Optional

UINT

(counter)

The value of this counter is incremented by one every millisecond (at least one writing operation every 50 ms) and operates as an internal presence counter, intended to the gateway’s applicative card, that is to say the card on which the AnyBus-S DeviceNet card is inserted.

16#08

Get

Access method status

Optional

USINT [4]

16# 40 00 00 80

This array of 4 USINT elements determines the status of the method used to access the gateway’s memory’s general areas. This attribute is not relevant when using the gateway.

110

Image 110
Contents LUFP9 Page LUFP9 Page Table of contents Introduction Introduction to the user guideAltistart Introduction to the LUFP9 GatewayTerminology 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 NetworkOn Receipt Configuration Modbus RTUHardware Implementation of the LUFP9 Gateway Mounting the gateway Dismounting the gateway Powering the gatewayMounting the Gateway on a DIN Rail Connecting the Gateway to the Modbus Network Examples of Modbus connection topologiesLUFP9 gateway TSXCSA00 Pin outsHubs, drops, taps, and line terminations Wiring recommendations for the Modbus network120 Ω Cables Connecting the LUFP9 gateway to the DeviceNet networkWire colour PinConfiguring DeviceNet Communication Features Selector Switches DeviceNet speed 3 4 5 6 7Encoding the Gateway Address Selector DeviceNet Switches Address 3 4 5 6 7Speed Address Mac ID Signalling System Architecture Software Implementation of the GatewayIntroduction DeviceNet Master PLC SLC500 DeviceNet upstream networkManaging degraded modes Configuring the Motor StartersModbus cycle time Selecting and adding the master PLC’s DeviceNet scanner Configuring the Gateway in RsNetWorxInstalling the Gateway Description File 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.2Input Value Meaning MSB + LSB Description of Services Assigned to Gateway Inputs/OutputsOutput Value Meaning MSB + LSB Transferring the DeviceNet Scanner Configuration Developing a DeviceNet ApplicationSummary Gateway Initialization and DiagnosticsFull Management Control/Status Byte field Sub-chapterBits Description Fbhssend New DeviceNet master command wordFbdu Modbus exchange startup 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 FrameFrame FieldSize 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 Environment Appendix a Technical CharacteristicsCommunication Characteristics 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 State16# 20 04 24 64 30 Type ValueGet / Set Produced connection path 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#2B Data with ack path list Services of instance 16#01 of class 16#2B Type Value 16#06 Get Data with ack path list size 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 Frame Field Value or properties Read Holding Registers Command 16#03Preset Single Register command 16#06 Preset Multiple Registers Command 16#10 Modbus Protocol Exception ResponsesCode Name Description of the exception Exception Page User’s manual V1.0 2003-03