Schneider Electric LUFP9 user manual Diagnostic only

Page 37

5. Gateway Initialization and Diagnostics

5.2. Diagnostic only

The gateway uses a 16-bit register, located at the addresses 16#0000 and 16#0001 in its memory (inputs), to send diagnostics to the DeviceNet master. A second 16-bit register, located at the addresses 16#0200 and 16#0201 (outputs), allows the DeviceNet to acknowledge each of these diagnostics.

So you must configure your DeviceNet master so that it has access to the first two bytes of the gateway’s output data area, as well as to the first two bytes of the gateway’s input data area (see chapter 4.2 Configuring the Gateway in RsNetWorx, page 25).

5.2.1. Gateway Status Word

The input word located at addresses 16#0000 (MSB) and 16#0001 (LSB) in the gateway’s input memory constitutes the gateway’s status word. Its structure is described below:

Bits

Description

15ABC_HS_SEND: New gateway diagnostic

(See description of bit 15 of the DeviceNet master command word, FB_HS_CONFIRM.)

14

Reserved.

13ABC_DU: Modbus exchanges activated

The gateway activates this bit to tell the DeviceNet master that the Modbus data located in its input memory area have all been updated at least once since the last activation of FB_DU (“ABC_DU” means “ABC – Data Updated”). These Modbus input data include every data in responses from all Modbus slaves, for both periodic commands and aperiodic commands.

This bit is deactivated by the gateway when the FB_DU bit is deactivated, that is to say when the DeviceNet master demands a shutdown of Modbus exchanges.

N.B. Once it is active, this bit is not deactivated if there are any communication errors with the Modbus slaves. To signal this type of error, the gateway uses bit 12 of its status word.

12Periodicity of Modbus exchanges

The gateway activates this bit provided that it is periodically communicating with all of the Modbus slaves. It deactivates it as soon as it loses communication with one of them.

The “Reconnect time (10ms)”, “Retries” and “Timeout time (10ms)” elements of each of the Modbus queries (see chapter 6.11.2.2 Configuring the Query, page 66) are used to determine whether communication is lost, then restored.

N.B. If a number of periodic exchanges are configured for the same Modbus slave, only one of them needs to remain active for the periodic communications with this slave to be declared active.

8-11EC: Error code associated with the Modbus network

Code of the error detected on the Modbus network by the gateway and transmitted to the DeviceNet master.

0- 7 ED: Error data item associated with the Modbus network

Data item associated with the EC error code.

37

Image 37
Contents LUFP9 Page LUFP9 Page Table of contents Introduction to the user guide IntroductionTerminology Introduction to the LUFP9 GatewayAltistart Additional Documentation Notational ConventionsModbus VW33-A48 ModbusDownstream network no.3 Modbus Downstream network no.1Principle Used to Configure and Operate the LUFP9 Gateway Modbus network ABC ConfiguratorRSNetWorx LUFP9 gatewayRSLogix 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 Examples of Modbus connection topologies Connecting the Gateway to the Modbus NetworkLUFP9 gateway Pin outs TSXCSA00120 Ω Wiring recommendations for the Modbus networkHubs, drops, taps, and line terminations Wire colour Connecting the LUFP9 gateway to the DeviceNet networkCables PinSelector Switches DeviceNet speed 3 4 5 6 7 Configuring DeviceNet Communication FeaturesSpeed Address Mac ID Selector DeviceNet Switches Address 3 4 5 6 7Encoding the Gateway Address Signalling Introduction Software Implementation of the GatewaySystem Architecture 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 Editing gateway parameters Selecting and Adding the Gateway to the DeviceNet NetworkSoftware Implementation of the Gateway Configuring the DeviceNet Scanner Service PLC input Description Configuring Inputs from the GatewayI1.1 I1.2Service PLC output Description Configuring Outputs Intended for the GatewayO1.1 O1.2Output Value Meaning MSB + LSB Description of Services Assigned to Gateway Inputs/OutputsInput Value Meaning MSB + LSB Developing a DeviceNet Application Transferring the DeviceNet Scanner ConfigurationFull Management Gateway Initialization and DiagnosticsSummary Control/Status Byte field Sub-chapterFbdu Modbus exchange startup Fbhssend New DeviceNet master command wordBits Description 11EC Error code associated with the Modbus network Bits Description Abchssend New gateway diagnosticED Error data item associated with the Modbus network Gateway Status WordDescription of the error Diagnostic only DeviceNet Master Command Word Simplified Operation Connecting the Gateway to the Configuration PC Configuring the GatewayRS-232 link protocol LUFP9 Configuration Female RJ45Male RJ45 PC COM Male 9 point SUB-DImporting the Gateway Configuration Installing AbcConfMonitoring the Content of the Gateway’s Memory Transferring a Configuration to the GatewayConfiguring the Gateway Deleting a Modbus Slave Procedure for deleting a Modbus slaveAdding a Modbus Slave Copying a previously configured Modbus slaveAdding a new type of Modbus slave Keyboard shortcut CtrlImporting/exporting a Modbus slave configuration Replacing a Periodic Input Data Element Changing the Periodic Data Exchanged With a Modbus SlaveReplacing an Output Periodic Data Element Increasing the Amount of Periodic Input Data Configuring the Gateway Configuring the Gateway I1.18 I1.17I1.19 I1.20Configuring the Gateway Configuring the Gateway Configuring the Gateway O1.18 O1.17Deleting Aperiodic Parameter Data Configuring the Gateway Changing the Name of a Modbus Slave Changing a Modbus slave ConfigurationChanging the Address of a Modbus Slave Name of the Modbus command Modbus query Adding and Setting Up a Modbus CommandWith TeSys U Motor Starters Modbus responseWith a Generic Modbus Slave Configuring the Gateway DeviceNet Configuration Description Element Configuring the QueryConfiguring the Gateway Default communication mode. The query is transmitted Configuring the Response Field Size Description Frame Configuring the Content of the Query FrameSize FieldFrame Configuring the Content of the Response Frame Mode. The default value, CRC, should not be changedModbus Commands Based on Standard Commands Adding a Special Modbus CommandModbus Commands which Can Be Completely Changed by the User Fieldbus element Configuring the General Characteristics of the GatewayABC Element Sub-Network Element Configuring the Gateway Adding a Broadcaster Node Communication Characteristics Appendix a Technical CharacteristicsEnvironment Input data area InputsGeneral data OutputsOutput data area General data areaConfiguring Modbus exchanges Appendix B Default Configuration16#10 16#06Input Data Memory Area Content of the Gateway’s Dpram Memory16#0200 Main Program LAD 2 MAINLUFP9 Appendix C Practical Example RSLogixScanvalidation Address Symbol DescriptionAddress Symbol Display Cmdreset ModuleAppendix C Practical Example RSLogix Numparam Appendix C Practical Example RSLogix Wrrunning Reserves relating to the RSLogix 500 example Address Symbol DisplayIntroduction to the Gateway’s DeviceNet Objects Appendix D DeviceNet ObjectsList of the Gateway’s DeviceNet Objects Class Required Instances InterfacesIdentity Object class 16#01 Graphical Representation of the Gateway’s DeviceNet ObjectsAttributes of instance 16#01 of class 16#01 Services of instance 16#01 of class 16#01DeviceNet Object class 16#03 Message Router Object class 16#02Services of instance 16#01 of class 16#03 Assembly Objects Class 16#04Services in class 16#04 Revision index of the Assembly Object classConnection Object Class 16#05 Services of instances 16#64 and 16#96 of class 16#04Attributes of instance 16#64 of class 16#04 Modbus Inputs Attributes of instance 16#96 of class 16#04 Modbus OutputsAttributes of class 16#05 Services in class 16#05Watchdog timeout action Initial comm. characteristics16#83 Produced connection IDType Value 16#01 Get State Access NameGet / Set Produced connection path Type Value16# 20 04 24 64 30 Type Value 16#07 Get / Set Produced connection size #0 xx Type Value 16#04 Get / Set Produced connection IDAcknowledge Handler Object class 16#2B Services in class 16#2BAttributes of instances 16#01 to 16#04 of class 16#05 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 Services of instance 16#01 of class 16#A0 Services in class 16#A010.10. I/O Data Input Mapping Object Class 16#A0 Attributes of class 16#A0Services of instance 16#01 of class 16#A1 Services in class 16#A110.11. I/O Data Output Mapping Object Class 16#A1 Attributes of class 16#A1Services in class 16#AA Diagnostic Object Class 16#AAAttributes of class 16#AA Attributes of instance 16#01 of class 16#AAModule type Access Name Need Type Value 16#09 Get LED statusDeviceNet module status 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 Modbus Protocol Exception Responses Preset Multiple Registers Command 16#10Code Name Description of the exception Exception Page User’s manual V1.0 2003-03