Schneider Electric LUFP9 user manual Configuring the Gateway

Page 67

6. Configuring the Gateway

Configuration

Description

element

 

Retries

This element indicates the number of re-transmissions carried out by the gateway if there is

 

no response from the Modbus slave to a query, or if the response is incorrect. This re-

 

transmission process ceases as soon as the gateway gets a correct response within a given

 

time. If none of the re-transmissions has allowed the gateway to obtain a correct response,

 

the Modbus slave is deemed to be off-line, but only in relation to the command in question.

 

The gateway then uses the “Offline options for sub-network” and “Reconnect time (10ms)”

 

elements and the LED r MODBUS becomes red. This LED will only revert to a green state

 

if the Modbus command is answered with a correct response, once the reconnection has

 

started (see element “Reconnect time (10ms)”).

 

If the number of re-transmissions is set to 0, the process described above will not be run.

Timeout time

This element represents the time that the Modbus slave will wait for a response. If a

(10ms)

response has not reached the gateway within the given time, configured using the “timeout

 

time (10ms)” element, the gateway proceeds to a re-transmission. This process continues

 

until it reaches the last re-transmission allowed (see “Retries”), then the gateway declares

 

the Modbus slave off-line, but only for the command to which the “timeout time (10ms)”

 

belongs to.

Trigger byte

This element is only used by the gateway if “Update mode” is set to “Change of state on

address

trigger”. In this case, it specifies the address, in the gateway’s output memory (16#0202 to

 

16#03FF), of an 8-bit counter managed by the DeviceNet master.

 

When the value located at this address is changed by the DeviceNet master but different

 

from zero, the query configured with a “Change of state on trigger” related to this address is

 

transmitted to the Modbus slave. So the DeviceNet master must have access to this counter

 

in the same way as for the periodic output registers sent to TeSys U motor starters.

 

In comparison to the “On data change” mode, this mode allows you to send a command on

 

a specific order from the DeviceNet master if, for example, the latter is unable to update all

 

data of any given query at the same time.

 

N.B. In the specific case of the gateway’s default configuration, the “Transactions 1” and

 

“Transactions 2” personalized command mode for the “TeSys U n°1” node is set to “Change

 

of state on trigger”. These aperiodic commands are respectively used to read and write the

 

value of a parameter for one of the Modbus slaves.

 

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

 

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

 

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

 

configured the same way as the other outputs (see chapter 4.2.7 Configuring Outputs

 

Intended for the Gateway, page 30) and both correspond to the O:1.16 output.

 

To transmit one of these two commands, the DeviceNet master PLC must first of all update

 

all of the data to be transmitted on the Modbus network for this command (addresses

 

16#0212 to 16#0217 or addresses 16#0218 to 16#021D), then change the value of the

 

associate counter (address 16#021E or 16#021F). The gateway will then transmit the query

 

corresponding to the command.

 

N.B. The “trigger byte” does not have to be an item of output data updated by the

 

DeviceNet master. In fact it is quite possible that it may be an input between 16#0002 and

 

16#01FF. In this case, the Modbus slave which updates this byte will condition the

 

exchanges of the command you’re currently configuring.

67

Image 67
Contents LUFP9 Page LUFP9 Page Table of contents Introduction to the user guide IntroductionTerminology Introduction to the LUFP9 GatewayAltistart Additional Documentation Notational ConventionsDownstream network no.1 ModbusModbus VW33-A48 Downstream network no.3 ModbusPrinciple Used to Configure and Operate the LUFP9 Gateway Modbus network ABC ConfiguratorDeviceNet Network LUFP9 gatewayRSNetWorx RSLogixHardware 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 Pin Connecting the LUFP9 gateway to the DeviceNet networkWire colour CablesSelector 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 DeviceNet Master PLC SLC500 DeviceNet upstream network Software Implementation of the GatewayIntroduction System ArchitectureModbus 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 I1.2 Configuring Inputs from the GatewayService PLC input Description I1.1O1.2 Configuring Outputs Intended for the GatewayService PLC output Description O1.1Output Value Meaning MSB + LSB Description of Services Assigned to Gateway Inputs/OutputsInput Value Meaning MSB + LSB Developing a DeviceNet Application Transferring the DeviceNet Scanner ConfigurationControl/Status Byte field Sub-chapter Gateway Initialization and DiagnosticsFull Management SummaryFbdu Modbus exchange startup Fbhssend New DeviceNet master command wordBits Description Gateway Status Word Bits Description Abchssend New gateway diagnostic11EC Error code associated with the Modbus network ED Error data item associated with the Modbus networkDescription of the error Diagnostic only DeviceNet Master Command Word Simplified Operation Connecting the Gateway to the Configuration PC Configuring the GatewayPC COM Male 9 point SUB-D LUFP9 Configuration Female RJ45RS-232 link protocol Male RJ45Importing 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 slaveKeyboard shortcut Ctrl Copying a previously configured Modbus slaveAdding a Modbus Slave Adding a new type of Modbus slaveImporting/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.20 I1.17I1.18 I1.19Configuring 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 Modbus response Adding and Setting Up a Modbus CommandName of the Modbus command Modbus query With TeSys U Motor StartersWith 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 area OutputsGeneral data Output data area16#06 Appendix B Default ConfigurationConfiguring Modbus exchanges 16#10Input 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 DisplayClass Required Instances Interfaces Appendix D DeviceNet ObjectsIntroduction to the Gateway’s DeviceNet Objects List of the Gateway’s DeviceNet ObjectsIdentity 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#02Revision index of the Assembly Object class Assembly Objects Class 16#04Services of instance 16#01 of class 16#03 Services in class 16#04Attributes of instance 16#96 of class 16#04 Modbus Outputs Services of instances 16#64 and 16#96 of class 16#04Connection Object Class 16#05 Attributes of instance 16#64 of class 16#04 Modbus InputsAttributes of class 16#05 Services in class 16#05Produced connection ID Initial comm. characteristicsWatchdog timeout action 16#83Type 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 IDAttributes of class 16#2B Services in class 16#2BAcknowledge Handler Object class 16#2B Attributes of instances 16#01 to 16#04 of class 16#05Type Value 16#06 Get Data with ack path list size Services of instance 16#01 of class 16#2BData with ack path list Attributes of class 16#A0 Services in class 16#A0Services of instance 16#01 of class 16#A0 10.10. I/O Data Input Mapping Object Class 16#A0Attributes of class 16#A1 Services in class 16#A1Services of instance 16#01 of class 16#A1 10.11. I/O Data Output Mapping Object Class 16#A1Attributes of instance 16#01 of class 16#AA Diagnostic Object Class 16#AAServices in class 16#AA Attributes of class 16#AAChanged data field Access Name Need Type Value 16#09 Get LED statusModule type DeviceNet module statusServices 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