Schneider Electric LUFP9 user manual Address Symbol Description, Scanvalidation

Page 87

9. Appendix C: Practical Example (RSLogix 500)

The various data used by the main program are shown in the following table:

Address

Symbol

Description

I:1.1/

7

→ I:1/23

ABC_HS_SEND

Flip flop indicating that there is a new gateway diagnostic

O:1.0/

0

→ O:1/ 0

SCAN_VALIDATION

Enable DeviceNet communications: this bit must be set to 1 to validate the exchanges

O:1.1/

5

→ O:1/21

FB_DU

Activation of Modbus communications by the gateway

O:1.1/

6

→ O:1/22

FB_HS_SEND

Flip flop telling the gateway that there is a new command

O:1.1/

7

→ O:1/23

FB_HS_CONFIRM

Bit used by the DeviceNet master to acknowledge diagnostics of the gateway

 

N7:0

MODULE

Parameter giving access (index) to the motor starter (called “module” to simplify things)

O:1.16

TRIGGER_OUT_RD_WR

"Trigger bytes" used to trigger the emission of the read parameter request

 

 

 

 

(LSB) or of the write parameter request (MSB)

 

N7:36

————

Local counter related to the “trigger byte” of the read parameter request

 

N7:37

————

Local counter related to the “trigger byte” of the write parameter request

9.2.Controlling/Monitoring Sub-Program for a TeSys U Motor Starter: “LAD 3 - CMD_MON”

The role of this sub-program consists of exercising very simple control over one of the TeSys U motor starters, depending on its current status and the user’s commands. The processes carried out in this sub-program are described below, in the order in which they are run:

Control of the motor to run forward / in reverse / to stop. Register N7:0 is used as a parameter. It contains the number of both the input word and the output word used to control and monitor the TeSys U motor starter. This same number is used to index one of the bits of each register for registers N7:32 to N7:35. The input word used is located between I:1.2 and I:1.9 (motor starters nos. 1 to 8), and the output word used is located between O:1.2 et O:1.9 (ditto). So the value of N7:0 must be between 2 and 9, according to the number of the motor starter currently controlled.

The user controls the motor starter’s running mode using bits 2 to 9 (motor starters nos. 1 to 8) of registers N7:32 ( Run (1) / Stop (0) ) and N7:33 (Run Forwards (0) / Reverse (1) ).

The forward, reverse and stop commands for the TeSys U motor starter are carried out under the following conditions:

ƒBit 14 of a TeSys U status word = 0 ........ The motor starter is not in local mode.

ƒ

Bit

2 of a TeSys U status word = 0

There is no fault on the motor starter.

ƒ

Bit

0 of a TeSys U status word = 1

The motor starter is in the “Ready” or “Switched on” state.

When all of these conditions are met, registers N7:32 and N7:33 (bit 2 to 9, depending on the value of N7:0) are used to control either the motor starter running forwards / in reverse, or to stop it by means of braking. The user updates these two registers bit by bit, according to the commands he wishes to undertake.

The faults on the TeSys U motor starter are reset. Register N7:0 is used in the same way as above and the input and output words are the same as for controlling the motor starter.

When there is a fault on the motor starter (bit 2 of the monitoring register equal to 1), this fault is copied to one of the bits 2 to 9 (one bit per motor starter) in register N7:34 (Faulty device (1) / Motor starter OK (0) ), simply to show this state together with the user command which allows you to reset motor starter faults. This user command corresponds to one of the bits 2 to 9 of register N7:35 (fault reset (1) ) and is used to activate bit 3 of the command register of the corresponding TeSys U motor starter (“Reset” bit), that is to say bit O:1.[N7:0]/3.

This fault reset user command is then cancelled by the program when the TeSys U motor starter no longer shows that there is a fault.

87

Image 87
Contents LUFP9 Page LUFP9 Page Table of contents Introduction to the user guide IntroductionIntroduction to the LUFP9 Gateway TerminologyAltistart 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 RSLogixConfiguration 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 Pin Connecting the LUFP9 gateway to the DeviceNet networkWire colour CablesSelector 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 DeviceNet Master PLC SLC500 DeviceNet upstream network Software Implementation of the GatewayIntroduction System ArchitectureConfiguring 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 I1.2 Configuring Inputs from the GatewayService PLC input Description I1.1O1.2 Configuring Outputs Intended for the GatewayService PLC output Description O1.1Description of Services Assigned to Gateway Inputs/Outputs Output Value Meaning MSB + LSBInput Value Meaning MSB + LSB Developing a DeviceNet Application Transferring the DeviceNet Scanner ConfigurationControl/Status Byte field Sub-chapter Gateway Initialization and DiagnosticsFull Management SummaryFbhssend New DeviceNet master command word Fbdu Modbus exchange startupBits 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 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 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 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 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#05Services of instance 16#01 of class 16#2B Type Value 16#06 Get Data with ack path list sizeData 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 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