Schneider Electric LUFP9 user manual Configuring the Response

Page 69

6. Configuring the Gateway

6.11.2.3. Configuring the Response

Next select the “Response” element from the Modbus command. The various elements of the configuration of the response for this command are shown opposite. The values displayed correspond to the default values for any new command.

These elements allow you to configure a single aspect of managing the command, described at the top of the page on the right. Each of these elements is described, in order, in the table below.

Configuration

Description

 

element

 

 

 

Trigger byte

This element is used by the gateway to activate the unitary incrementation of an 8-bit

 

counter in order to notify the DeviceNet master of the receipt of a new response to the

 

associated Modbus command. It takes one of the following two values:

 

- Disabled

Default configuration. The gateway does not increment any

 

counter on receipt of the Modbus response.

 

- Enabled

Each time that the gateway receives a new response to the

 

associated Modbus command, it increments the value of an 8-bit counter designated

 

by the “Trigger byte address” element (see below). If used, this counter allows the

 

DeviceNet master, for example, to only consider the response’s corresponding data

 

when this counter’s value is incremented.

Trigger byte

This element is only used by the gateway if the element “Trigger byte” is set to “Enabled”. In

address

this case, it specifies the address, in the gateway’s input memory (16#0002 to 16#0002), of

 

an 8-bit counter managed by the gateway.

 

When the gateway receives a response to the associated Modbus command, it increments

 

the value of this counter in a unitary manner (value = value+1). So the DeviceNet master

 

must have access to this counter in the same way as for the periodic input registers from

 

the TeSys U motor starters.

 

 

This mode allows the DeviceNet master to be informed that a new response is available.

 

This can be useful, for example, if it is possible that the data from two consecutive

 

responses may be identical.

 

 

N.B.: In the specific case of the gateway’s default configuration, the “Trigger byte” element

 

for responses to the “Transactions 1” and “Transactions 2” personalized commands of the

 

“TeSys U n°1” node is set to “Enabled”. Hence, the management of responses to read and

 

write commands for parameters is event driven.

 

The “Trigger byte address” elements of the “Response” elements for these two commands

 

are configured at addresses 16#001E and 16#001F. These are the “parameter read/write

 

response counters”. Considered under DeviceNet and RSNetWorx, these two data are

 

configured the same way as the other inputs (see chapter 4.2.6Configuring Inputs from the

 

Gateway, page 29) and both correspond to the I:1.16 input.

 

The DeviceNet master PLC will be able to detect the receipt of a response from a Modbus

 

slave by comparing the previous value and the current value of the associated counter

 

(address 16#001E or 16#001F). If there is a unitary incrementation of this counter, the PLC

 

may, for example, read all of the data from the response (addresses 16#0013 to 16#0017

 

or addresses 16#0018 to 16#001D) and allow the transmission of a new query for reading

 

or writing the value of a parameter (using a “Trigger byte” for the queries). Contrarily to the

 

counter one can associate to the queries of any command, a response’s “Trigger byte” is a

 

true modulo 256 counter, i.e. zero must be managed (… 254, 255, 0, 1, 2 …).

E.g. With the ATS48, we do not want the response to be event driven. So we will be retaining the default configuration.

69

Image 69
Contents LUFP9 Page LUFP9 Page Table of contents Introduction to the user guide IntroductionIntroduction to the LUFP9 Gateway TerminologyAltistart 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 NetworkConfiguration Modbus RTU Hardware Implementation of the LUFP9 GatewayOn Receipt Powering the gateway Mounting the Gateway on a DIN RailMounting the gateway Dismounting the gateway Examples of Modbus connection topologies Connecting the Gateway to the Modbus NetworkLUFP9 gateway Pin outs TSXCSA00Wiring recommendations for the Modbus network 120 ΩHubs, 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 FeaturesSelector DeviceNet Switches Address 3 4 5 6 7 Speed Address Mac IDEncoding the Gateway Address Signalling Introduction Software Implementation of the GatewaySystem Architecture DeviceNet Master PLC SLC500 DeviceNet upstream networkConfiguring the Motor Starters Modbus cycle timeManaging degraded modes Configuring the Gateway in RsNetWorx Installing the Gateway Description FileSelecting 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.2Description of Services Assigned to Gateway Inputs/Outputs Output Value Meaning MSB + LSBInput Value Meaning MSB + LSB Developing a DeviceNet Application Transferring the DeviceNet Scanner ConfigurationFull Management Gateway Initialization and DiagnosticsSummary Control/Status Byte field Sub-chapterFbhssend New DeviceNet master command word Fbdu Modbus exchange startupBits 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 FrameField SizeFrame 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 Appendix a Technical Characteristics Communication 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 NameType Value Get / Set Produced connection path16# 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#2BServices of instance 16#01 of class 16#2B Type Value 16#06 Get Data with ack path list sizeData 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 Read Holding Registers Command 16#03 Preset Single Register command 16#06Frame 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