Schneider Electric LUFP9 user manual I1.17, I1.18, I1.19, I1.20, I1.21, I1.22, I1.23, I1.24

Page 53

6. Configuring the Gateway

In this guide, we will be using the “AutoMap” command to establish a “raw” correspondence with all of the data from the LUFP9 gateway. We then get the correspondence shown below, derived from the one used with the gateway’s default configuration. The changes in relation to the default configuration are shown by a greyed-out background, like the “free memory locations”.

Service

PLC input

Description

Bit 0......................Bit 7

Bit 8 ...................Bit 15

Managing the downstream Modbus

I:1.1

 

LUFP9 gateway status word

network

 

(MSB Æ 16#xx••)

(LSB Æ 16#••xx)

 

 

 

I:1.2

Value of the motor starter c status register

Periodic communications

I:1.3

 

Free memory location

I:1.4

 

Value of the motor starter e status register

I:1.5

Value of the motor starter f status register

Monitoring of

I:1.6

Value of the motor starter g status register

TeSys U motor starters

I:1.7

Value of the motor starter h status register

 

I:1.8

Value of the motor starter i status register

 

I:1.9

Value of the motor starter j status register

Aperiodic communications

I:1.10

 

Free memory location

Slave no. (16#01-16#08)

I:1.11

 

Function number (16#03)

Number of bytes read (16#02)

Reading the value of a motor

I:1.12

 

Value of the

parameter read

starter parameter (RESPONSE)

 

(MSB Æ 16#xx••)

(LSB Æ 16#••xx)

 

 

Aperiodic communications

I:1.13

Slave no. (16#01-16#08)

Function no. (16#06)

I:1.14

Address of the parameter written

(MSB Æ 16#xx••)

(LSB Æ 16#••xx)

Writing the value of a motor

 

 

 

 

Value of the parameter written

starter parameter (RESPONSE)

I:1.15

(MSB Æ 16#xx••)

(LSB Æ 16#••xx)

 

 

 

Aperiodic communications

I:1.16

 

Read parameter

Write parameter

(“Trigger bytes” for the responses)

 

response counter

response counter

 

 

 

I:1.17

 

Value of the “TeSys U Status Register”

Periodic communications

I:1.18

 

Value of the “Complementary Status Register”

I:1.19

 

Value of the “K7 Status Register”

I:1.20

 

Value of the “K7 Status Register 2 (free format)”

Monitoring of

I:1.21

 

Value of the “K7 Status Register 3 (free format)”

TeSys U motor starter d

I:1.22

 

Value of the “Warning Number” register

 

I:1.23

 

Value of the “Warning Register”

 

I:1.24

 

Value of “Reserved : 2nd Warning Register”

9)Transferring the DeviceNet scanner configuration: Following the changes made to the list of DeviceNet scanner exchanges, it needs to be transferred to the DeviceNet scanner. Please see chapter 4.2.9 Transferring the DeviceNet Scanner Configuration, page 32.

6.8.4. Increasing the amount of periodic output data

E.g. “TeSys U n°4” motor starter. We are attempting to complete the control for this motor starter whilst retaining the currently controlled “Command Register” (address 704 = 16#02C0), and adding the following next register, that is to say “2st Command Register” (address 705 = 16#02C1). The number of registers controlled is therefore increased from 1 to 2.

There are quite a lot of operations to be carried out. They are described in order below:

53

Image 53
Contents LUFP9 Page LUFP9 Page Table of contents Introduction to the user guide IntroductionAltistart Introduction to the LUFP9 GatewayTerminology 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 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 Examples of Modbus connection topologies Connecting the Gateway to the Modbus NetworkLUFP9 gateway Pin outs TSXCSA00Hubs, drops, taps, and line terminations Wiring recommendations for the Modbus network120 Ω Wire colour Connecting the LUFP9 gateway to the DeviceNet networkCables PinSelector Switches DeviceNet speed 3 4 5 6 7 Configuring DeviceNet Communication FeaturesEncoding the Gateway Address Selector DeviceNet Switches Address 3 4 5 6 7Speed Address Mac ID Signalling Introduction Software Implementation of the GatewaySystem Architecture 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 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.2Input Value Meaning MSB + LSB Description of Services Assigned to Gateway Inputs/OutputsOutput Value Meaning MSB + LSB Developing a DeviceNet Application Transferring the DeviceNet Scanner ConfigurationFull Management Gateway Initialization and DiagnosticsSummary Control/Status Byte field Sub-chapterBits Description Fbhssend New DeviceNet master command wordFbdu Modbus exchange startup 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 FrameFrame FieldSize 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 Environment Appendix a Technical CharacteristicsCommunication Characteristics 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 Name16# 20 04 24 64 30 Type ValueGet / Set Produced connection path 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#2BData with ack path list Services of instance 16#01 of class 16#2BType Value 16#06 Get Data with ack path list size 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 Frame Field Value or properties Read Holding Registers Command 16#03Preset Single Register command 16#06 Modbus Protocol Exception Responses Preset Multiple Registers Command 16#10Code Name Description of the exception Exception Page User’s manual V1.0 2003-03