Schneider Electric TSXCUSBMBP Configuring the Modbus Plus Routing, Addressing, Methods, Before

Page 27

Configuring the TSXCUSBMBP Driver

Configuring the Modbus Plus Routing

Introduction

When interfacing to an application through the Virtual Serial Port, the TSXCUSBMBP

 

operates as a serial Modbus to Modbus Plus converter, similar to the BM85 Bridge

 

Multiplexer. The Virtual Serial Port captures serial Modbus RTU messages sent by a

 

Modbus application and redirects them to the TSXCUSBMBP driver. The driver then

 

converts each message from the Modbus RTU format into the Modbus Plus format

 

before sending it out onto the network and waiting for a response.

Addressing

 

When converting a Modbus RTU request to Modbus Plus, the driver must convert a

Methods

single Modbus ID into a 5-byte Modbus Plus routing path. The TSXCUSBMBP driver

 

supports three different methods of doing this:

 

1. Explicit Addressing,

 

2. Direct Addressing,

 

3. Implicit Addressing.

 

The first method, known as Explicit Addressing, uses the TSXCUSBMBP driver's

 

Modbus Routing Table. A unique Modbus ID (also known as Modbus Slave Address

 

or Modbus Slave ID) is assigned by the user to each Modbus Plus device that will

 

be accessed from a Modbus application. An entry is then made into the Modbus

 

Routing Table that specifies the Modbus Plus Routing path to use whenever a

 

Modbus application sends a Modbus RTU message to that Modbus ID.

 

The second and third methods use the value of the Modbus ID to generate the

 

Modbus Plus routing path according to a predefined set of rules. These methods

 

include Direct Addressing and Implicit Addressing, where the actual addressing type

 

used is determined by the range of values that the Modbus ID falls into. Direct

 

Addressing and Implicit Addressing are only used when an entry does not exist in

 

the Modbus Routing Table for a Modbus ID.

 

The Explicit, Direct, and Implicit addressing methods are the same methods used by

 

the BM85 Bridge Multiplexer.

Before

 

Before configuring the Modbus Plus routing

configuring

1. make a complete list of all Modbus Plus nodes that will be accessed from Modbus

 

applications. Do not include any Modbus Plus nodes that will be accessed only

 

with the Diagnostic functions of the TSXCUSBMBP,

 

2. determine which nodes can be accessed using Direct Addressing or Implicit

 

Addressing (see below). The Modbus Routing Table has a maximum size of 64

 

entries and using Direct or Implicit Addressing where possible will limit the

 

number of table entries that must be used,

 

3. assign Modbus IDs to all remaining Modbus Plus nodes before entering them into

 

the Modbus Routing Table where Explicit Addressing will be used.

 

 

35011984 02/2006

27

Image 27 Contents
Tsxcusbmbp Page Table of Contents Appendix a Tsxcusbmbp Settings for Unity Connecting to a Modbus Plus NetworkUsing the Tsxcusbmbp with an Application Modbus Plus Network Diagnostic FunctionsImportant Information Safety InformationSchneider Electric. All Rights Reserved At a Glance About the BookAbout the Book Glossary of Abbreviations Acronyms Introduction Glossary Abbreviations AcronymsAbbreviation/Acronym Expansion Abbreviations & Acronyms Overview Subject of this chapter Whats in this Chapter?Topic Port VSP Modbus Plus Communication for ApplicationsIntroduction Virtual SerialModbus Plus Network Diagnostics Tsxcusbmbp HardwareDescription Overview Installation Subject of thisChapter? Upgrading From Previous Version Installation RequirementsInstalling the Tsxcusbmbp Driver Software Installing the Tsxcusbmbp HardwareIntroduction How to install Tsxcusbmbp Driver? How to install Tsxcusbmbp Hardware Icon Color Status of the driver Establishing a Connection toStatus DriverIf the icon How to rescan?Rescan Adapters Show InterfaceConfiguring the Tsxcusbmbp Driver Select Show Interface Tsxcusbmbp Driver Interface WindowInterface Window DisplayConfiguring the Modbus Plus Node Address AddressAddress Changing Process Configuring the Slave Response Timeout Timeout Slave Response Configuration Configured as follows Configuring the Virtual Serial COM Port AssignmentThen Methods Configuring the Modbus Plus RoutingConfiguring AddressingExplicit DirectImplicit Node Used by Routing Table Address Application Entry Routing Example Routing exampleModbus + Slave ID Modbus Plus Routing PathTsxcusbmbp Entering Routing Paths into the Routing Table Configuring the Tsxcusbmbp Driver LED Flash Code Description Connecting to a Modbus Plus NetworkModbus Plus Network Status Indicator Flash CodesConnecting to a Modbus Plus Network Tsxcusbmbp with an Application Whats in this Chapter? Using the Tsxcusbmbp with an ApplicationStart the Tsxcusbmbp Driver Configure the Application Software Introduction Typical ConfigurationConnect Using the Tsxcusbmbp with an Application Section Topic Modbus Plus Network Diagnostic FunctionsModbus Plus Network Diagnostic Functions Procedure for Starting the Diagnostic Functions Starting the Diagnostic FunctionsProcedure for Scanning the Modbus Plus Network Scanning the Modbus Plus NetworkScanning Local or Complete Network Introduction Whats in this Section? Displaying Diagnostic InformationModbus Plus Network Diagnostics screen Procedure for Displaying Diagnostic InformationResults ProcedureNode Error Statistics Screennode Node PersonalityTransactions Selected node Screen Internal Path TransactionsNode Token Screen Green when active and gray when inactiveToken Owner Work Table Map screen. This section describes this screenActive Station Table Token Station Table Present Table Global Data Present TableGlobal Data Read Global DataModbus Plus Network Diagnostic Functions Introduction Whats in this Appendix? AppendicesAppendices 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 Setting Tsxcusbmbp Settings for Concept & ProWORX32Tsxcusbmbp Configuring Concept ProWORX32Step Action