Schneider Electric LUFP9 Deleting a Modbus Slave, Procedure for deleting a Modbus slave

Page 45

6. Configuring the Gateway

6.6. Deleting a Modbus Slave

This step allows you, for instance, to free up a location on the downstream Modbus network, known as the “Sub- Network” in AbcConf, in order to replace one Modbus slave with another.

In fact the gateway’s default configuration already allows it to communicate with eight TeSys U motor starters, whereas the maximum number of Modbus slaves with which it can communicate is limited to eight.

If the gateway is used to manage exchanges on a Modbus network with fewer than eight TeSys U motor starters, it is preferable to delete the redundant TeSys U motor starters from the gateway configuration. In fact, the deterioration in performances linked to the absence of one or more TeSys U motor starters is such that it is preferable to carry out this operation using AbcConf.

If you wish to retain the read/write aperiodic services for the value of a motor starter parameter, never delete the first configured TeSys U motor starter, because the two transactions associated with these services are configured for this motor starter.

In fact, these two transactions are sent to any Modbus slave, because the value of the “slave number” field in the Modbus queries associated to them is fully managed wholly by the DeviceNet master PLC software (bits 0 to 7 of outputs O:1.10 and O:1.13).

Procedure for deleting a Modbus slave

1)Select the node corresponding to the Modbus slave you wish to delete from the configuration. If this is the only node remaining in the configuration, you will not be able to delete it, as the downstream Modbus network must include at least one slave.

2)Right click on the icon or the name of this Modbus slave. A menu pops up underneath the mouse cursor. or

In the AbcConf main menu, pull down the menu whose name corresponds to the name of the previously selected node.

3)On this menu, click on “Delete”. The confirmation window shown below then appears, asking you to either confirm that you want to delete the selected node (“TeSys U no. 2” in the example shown here) or cancel the operation.

4)If you confirm that you want to delete the node, the menu disappears, along with the previously selected node. Otherwise, the node will still be there once the window disappears.

Keyboard shortcut: Del” key.

Adjusting the gateway’s memory (optional step):

The data previously exchanged between the gateway and the Modbus slave which has just been deleted will free up locations in the gateway’s memory. If you want to optimize the exchanges between the gateway’s memory and the master PLC DeviceNet scanner inputs/outputs, you will need to change the configuration of all the other Modbus slaves in order to adjust the content of the gateway’s memory.

45

Image 45
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