Schneider Electric LUFP9 user manual DeviceNet Master Command Word

Page 38

5. Gateway Initialization and Diagnostics

Due to the inversion of the LSB and the MSB for this register between the gateway and the DeviceNet master, the structure of the corresponding input word (“I:1.1” in the case of the default configuration) is as follows:

Bits

Description

8-15

ED: Error data item associated with the Modbus network

7

ABC_HS_SEND: New gateway diagnostic

6

Reserved.

5

ABC_DU: Modbus exchanges activated

4

Periodicity of Modbus exchanges

0-3

EC: Error code associated with the Modbus network

E.g. If the gateway’s status word is set to 16#B031, the input word I:1.1 will be set to 16#31B0.

The correct use of this status word by the DeviceNet master, to read a diagnostic generated by the gateway, goes through the following steps:

Checking of (ABC_HS_SEND ≠ FB_HS_CONFIRM).

 Reading of the value of ABC_DU to determine whether all of the Modbus inputdata are up-to-date.

 Reading of the value of the “Periodicity of Modbus exchanges” bit to determine whether the periodicity of the Modbus communications has been maintained.

 Reading of the values of EC and ED to check for any error detected by the gateway on the Modbus network (see table on page 36).

 Copying of the value of the ABC_HS_SEND bit to the FB_HS_CONFIRM bit.

This last step is essential because it allows the gateway to transmit a future diagnostic! Even if you do not wish to read the content of the gateway’s status word, it is preferable to automate this step in your DeviceNet master software.

5.2.2. DeviceNet Master Command Word

The output word located at addresses 16#0200 (MSB) and 16#0201 (LSB) in the gateway’s output memory constitutes the DeviceNet master command word. Its structure is described below:

Bits

Description

15

FB_HS_CONFIRM: Acknowledgement bit of a gateway diagnostic

 

The DeviceNet master must compare the value of the FB_HS_CONFIRM bit to the value of the

 

ABC_HS_SEND bit (bit 15 in the gateway’s status word). If these two values are different, this means

 

that the gateway has transmitted a new diagnostic to the DeviceNet master.

 

To tell the gateway that it has read a diagnostic, the DeviceNet master must copy the value of the

 

ABC_HS_SEND bit to the FB_HS_CONFIRM bit. This allows the gateway to issue a new diagnostic.

 

Summary:

If ( FB_HS_CONFIRM = ABC_HS_SEND ) Æ The gateway’s status word contains a diagnostic which has already been acknowledged by the DeviceNet master. So the gateway is free to use this status word to place another diagnostic there.

Else Æ A new diagnostic is available in the gateway’s status word. The DeviceNet master can read this diagnostic, but must also copy the value of ABC_HS_SEND to FB_HS_CONFIRM in order to allow the gateway to generate new diagnostics.

0-14 Reserved.

38

Image 38
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#2BData with ack path list Services of instance 16#01 of class 16#2BType 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