Schneider Electric TSXCUSBMBP user manual Explicit, Direct, Implicit

Page 28

Configuring the TSXCUSBMBP Driver

1. Explicit

The Explicit Addressing process is described as follows:

Addressing

z Explicit Addressing is used whenever the Modbus ID in a message received

 

through the Virtual Serial Port is present in the Modbus Routing Table, regardless

 

of what range of values the Modbus ID falls into. In Explicit Addressing, the

 

routing path will be the one that was entered into the Modbus Routing Table for

 

the Modbus ID of the received message.

 

z Any value can be selected for the Modbus ID as long as it does not conflict with

 

any Modbus IDs currently used by the application for Direct Addressing or Implicit

 

Addressing. However, it is helpful for each Modbus ID to have some

 

correspondence in value to the Modbus Plus node that it will be used to access.

 

z If no Modbus Plus node addresses are duplicated in the network (same

 

Modbus Plus node address used on more than one local network if separated by

 

Bridge Plus devices), the Modbus IDs to use for Explicit Addressing can be the

 

actual Modbus Plus node addresses.

2. Direct

 

The Direct Addressing process is described as follows:

Addressing

z If the Modbus ID in a message received through the Virtual Serial Port is not

 

present in the Modbus Routing Table and it is in the range of 1-64, the

 

TSXCUSBMBP Driver will use Direct Addressing.

 

z In Direct Addressing, the Modbus ID of the received message is used directly as

 

the 1st byte of the routing path, and the remaining 4 bytes are set to 0.

 

z For example, a Modbus ID of 2 would be routed to [2.0.0.0.0], and a Modbus ID

 

of 45 would be routed to [45.0.0.0.0]

3. Implicit

 

The Implicit Adressing process is described as follows:

Addressing

z If the Modbus ID in a message received through the Virtual Serial Port is not

 

present in the Modbus Routing Table and it is in the range of 80-255, Implicit

 

Addressing will be used.

 

z When the TSXCUSBMBP driver uses Implicit Addressing, it divides the Modbus

 

ID of the received message by 10. The quotient is used as the 1st byte of the

 

routing path, the remainder is used as the 2nd byte of the routing path, and the

 

remaining 3 bytes are set to 0. For example, a Modbus ID of 87 would be routed

 

to [8.7.0.0.0], and a Modbus ID of 230 would be routed to [23.0.0.0.0].

 

 

28

35011984 02/2006

Image 28
Contents Tsxcusbmbp Page Table of Contents Connecting to a Modbus Plus Network Using the Tsxcusbmbp with an ApplicationModbus Plus Network Diagnostic Functions Appendix a Tsxcusbmbp Settings for UnitySafety Information Important InformationSchneider Electric. All Rights Reserved About the Book At a GlanceAbout the Book Introduction Glossary Abbreviations Acronyms Glossary of Abbreviations AcronymsAbbreviation/Acronym Expansion Abbreviations & Acronyms Subject of this chapter Whats in this Chapter? OverviewTopic Modbus Plus Communication for Applications IntroductionVirtual Serial Port VSPTsxcusbmbp Hardware Modbus Plus Network DiagnosticsDescription Overview Subject of this InstallationChapter? Installation Requirements Upgrading From Previous VersionInstalling the Tsxcusbmbp Hardware Installing the Tsxcusbmbp Driver SoftwareIntroduction How to install Tsxcusbmbp Driver? How to install Tsxcusbmbp Hardware Establishing a Connection to StatusDriver Icon Color Status of the driverHow to rescan? Rescan AdaptersShow Interface If the iconConfiguring the Tsxcusbmbp Driver Tsxcusbmbp Driver Interface Window InterfaceWindow Display Select Show InterfaceAddress Configuring the Modbus Plus Node AddressAddress Changing Process Timeout Configuring the Slave Response TimeoutSlave Response Configuration Configured as follows Assignment Configuring the Virtual Serial COM PortThen Configuring the Modbus Plus Routing ConfiguringAddressing MethodsDirect ExplicitImplicit Routing Example Routing example Modbus + Slave IDModbus Plus Routing Path Node Used by Routing Table Address Application EntryTsxcusbmbp Entering Routing Paths into the Routing Table Configuring the Tsxcusbmbp Driver Connecting to a Modbus Plus Network Modbus Plus Network Status IndicatorFlash Codes LED Flash Code DescriptionConnecting to a Modbus Plus Network Using the Tsxcusbmbp with an Application Tsxcusbmbp with an Application Whats in this Chapter?Start the Tsxcusbmbp Driver Introduction Typical Configuration Configure the Application SoftwareConnect Using the Tsxcusbmbp with an Application Modbus Plus Network Diagnostic Functions Section TopicModbus Plus Network Diagnostic Functions Starting the Diagnostic Functions Procedure for Starting the Diagnostic FunctionsScanning the Modbus Plus Network Procedure for Scanning the Modbus Plus NetworkScanning Local or Complete Network Displaying Diagnostic Information Introduction Whats in this Section?Procedure for Displaying Diagnostic Information Modbus Plus Network Diagnostics screenProcedure ResultsNode Error Statistics Node Personality ScreennodeInternal Path Transactions Transactions Selected node ScreenScreen Green when active and gray when inactive Token Owner Work TableMap screen. This section describes this screen Node TokenActive Station Table Token Station Table Global Data Present Table Present TableRead Global Data Global DataModbus Plus Network Diagnostic Functions Appendices Introduction Whats in this Appendix?Appendices Tsxcusbmbp Settings for Unity Tsxcusbmbp Settings for UnityThis situation from occurring Configuring Unity Make sure both drivers are running You should now be able to Connect Tsxcusbmbp Settings for Concept & ProWORX32 SettingConfiguring Concept ProWORX32 TsxcusbmbpStep Action