Schneider Electric 174 CEV manual Using Dynamic Routing

Page 45

Configuring the Bridge

3.9.2Using Dynamic Routing

First setup the bridge for Host--based or Socket--based routing.

The bridge will now associate messages from the host’s IP address with the Modbus Plus path you established, when you address those messages to the Destination Index defined for the Host--based or Socket--based routing.

H Destination Index 0: Host-based routing After you setup the bridge for Host--based routing from a TCP/IP host to a Modbus Plus path, any messages from that host addressed to index 0 will be routed to that path.

The bridge maintains a cache of 10 associations between TCP/IP hosts and Modbus Plus paths using Destination Index 0. Thus up to 10 hosts may set associations and use them concurrently for transactions with Modbus Plus nodes. If all 10 cache locations are in use and another host establishes an association to index 0, the new association will overwrite the oldest one in the cache.

This routing option allows the bridge to be configured for simple addressing from TCP/IP nodes which do not support routing through gateways, such as programming panels.

H Destination Index 254: Socket-based routing After you setup the bridge for Socket--based routing from a TCP/IP host to a Modbus Plus path, any messages from that host addressed to index 254 will be routed to that path.

The TCP/IP host can initiate messages to the Modbus Plus destination for the duration of the host’s connection to the bridge. When the connection terminates, the Modbus Plus path no longer exists for that TCP/IP host.

The bridge maintains up to 16 available socket connections, corresponding to its eight Program and eight Data paths. For example, Modsoft panel software uses both a Program and a Data path during its connection with the bridge. The bridge will establish a socket for both paths during dynamic routing, and will close the sockets when the connection is terminated.

This routing option allows the bridge to handle concurrent sessions from multiple TCP/IP hosts using independent routing assignments. It provides a means for your application to manage routing dynamically in addition to the fixed routings you configure in the bridge’s TCP/IP to Modbus Plus mapping table.

41

Image 45
Contents Breite 185 mm Höhe 230 mm Breite 178 mm Höhe 216 mm Training Contents Uploading and Downloading Files Using the Bridge SoftwareGlossary Diagnostic ToolsModbus Plus to Ethernet Bridge CEV 200 Illustrates a typical bridge connection Introducing the Ethernet to Modbus Plus BridgeTCP/IP Bridge Message Transactions and Paths Read Discrete Output Status Power Input Tolerance Current SpecificationsAgency Status Installing the Bridge Hardware Setting the Modbus Plus Node Address Section Overview Hardware InstallationSetting the Ethernet Connector Jumper Section Connecting the Network and Power Cables SectionVerifying the Network Communication Section CE Installation Requirements SectionBridge Enclosure Screws Remove Screws Setting the Modbus Plus Node AddressDefault Setting Setting the Ethernet Connector Jumper JP2 AUI Mounting Requirements Mounting the Bridge HardwareInstalling the Bridge Hardware Connecting the Network and Power Cables BNC CE Installation Requirements GroundingFerrite Bead on RF-45 Cable Ethernet Card Indicators Modbus Plus Card IndicatorsVerifying the Network Communication Ethernet Card Defaults Factory Default SettingsEdge Modbus Plus Card DefaultsCleaning the Filters Periodic MaintenanceUpper Filter Lower FilterConfiguring the Bridge Files Supplied With the Bridge Files Resident in the BridgeHost Software Disk Software Startup Sequence Files Generated or Modified by the BridgeSetting the Ethernet Configuration Overview Software ConfigurationSetting the Modbus Plus and TCP/IP Address Mapping Configuration With a Bootp Server SectionConfiguration With a Bootp Server Configuration With the Cfgutil Utility Starting CfgutilNavigating the Cfgutil Menu Additional Configuration Fields Required Configuration FieldsSaving the Configuration Address Mapping Table FieldsDestination Indexes 1 .. Mapped Routing How Mapping Works TCP/IP to Modbus PlusDestination Index 255 Bridge Internal Command Destination Indexes 0 and 254 Dynamic Message RoutingReserved Destination Indexes 1 MB+ Mapping Table Layout and Default Entries Setting the Mapping TCP/IP to Modbus PlusSaving the Mapping Entry Example MB+ Mapping TableBytes 1 and 2. Bridge Node Address and Path How Mapping Works Modbus Plus to TCP/IPByte 3. First Bridge’s IP Routing Byte 4. Second Bridge’s Modbus Plus RoutingBridge 1 Maps the Message to TCP/IP Message is OriginatedBridge 2 Maps the Message to Modbus Plus Message is DeliveredTCP Mapping Table Layout and Default Entries Setting the Mapping Modbus Plus to TCP/IPExample Modbus Plus to TCP/IP Mapping Entry Example TCP Mapping TableContents Hex Contents Decimal Setting Up the Bridge for Dynamic RoutingDynamic Routing of Messages ExampleUsing Dynamic Routing Clearing the Bridge’s Configuration SetupClearing the Configuration Using the Bridge Software Bridge Software Contents SW-MBPE-000 Using the Software in Custom Configurations Minimum Requirements for Custom Bridge ConfigurationsSetting Up a Custom Bridge Configuration DEVICE=MBPHOST.SYS /md000 /s5d /n0 /r2 Uploading and Downloading Files Configuration Example Configuring an Http ServerCgi-bin Uploading Files to a Host Upload OverviewInitiating an Upload RTE.CFG Upload ExampleDownloading Files to the Bridge Download OverviewInitiating a Download Download Example Diagnostic Tools Diagnostics Overview Ethernet DiagnosticsLogging the Bridge’s Activity Mbpstat Modbus Plus DiagnosticsHow Logging Works Logging the Bridge’s ActivityStarting Logging Stopping LoggingSaving the Logging Status and Log File Mode a Channel Logging MenuStarting TcpinfoPing Starting Ping at the BridgeStarting Ping at the Host Starting Mbpstat Selecting the Network to be AnalyzedNetwork Selection Examples Typical Mbpstat Routing Entering Node Addresses Your Mbpstat MenuSet Routing Parameters Option 1 Set Routing ParametersMonitor Network Activity Option 2 Monitor Network ActivityRead Global Data Option 3 Read Global DataGlobal Data Present Table Option 4 Global Data Present TableNode Active Station Table Option 5 Node Active Station Table05.00.00.00.00 Failure 244 Option 6 Node Error StatisticsToken Station Table Option 7 Token Station TableToken Owner Work Table Option 8 Token Owner Work TablePath Option 9 Current Internal Path TransactionsNode Personality Option 10 Node PersonalityMessage Examples Mstr in TCP/IP Node Mstr Example TCP/IP NodeMstr in Modbus Plus Node Mstr Example Modbus Plus NodeNCB Return Codes ERRsuccess Network Control Block NCB Return CodesGlossary Field Default gatewayFrame Framing typesIP Address InternetLayer MAC AddressRepeater SwitchRouter ServerWinsock UTP

174 CEV specifications

Schneider Electric, a global leader in energy management and automation, has designed the Schneider Electric 174 CEV to meet the evolving demands of industrial applications. This innovative controller is engineered to enhance efficiency, flexibility, and reliability across various sectors.

One of the main features of the Schneider Electric 174 CEV is its robust communication capabilities. It supports multiple protocols, including Ethernet/IP, Modbus, and both serial and parallel communication interfaces. This multiplicity allows seamless integration with existing systems, ensuring that users can connect and manage devices within their operational setup without extensive changes to their infrastructure.

The 174 CEV is equipped with a powerful processing unit that ensures rapid data processing and real-time analytics. This is particularly advantageous for industries where quick decision-making is crucial. The controller is designed to handle large data sets and perform complex functions, all while maintaining optimal performance levels.

Another significant aspect of the Schneider Electric 174 CEV is its modular design. This feature allows for tailored solutions suited to specific application needs. Users can customize their setup by adding or removing modules based on their operational requirements, which enhances the controller’s versatility and longevity.

In terms of technology, the 174 CEV utilizes advanced algorithms for energy management and optimization. Users can benefit from predictive maintenance capabilities, which leverage data analytics to anticipate equipment failures before they occur. This proactive approach reduces downtime and maintenance costs, ultimately contributing to higher operational efficiency.

The controller also emphasizes user-friendly interfaces. With intuitive programming tools and a graphical user interface, operators can easily navigate through its functionalities, customize settings, and monitor performance metrics. This accessibility fosters greater user engagement and reduces the learning curve for new operators.

Safety is a top priority in the design of the Schneider Electric 174 CEV. The controller is built with compliance to international safety standards, ensuring that it can be deployed in a wide range of industries while guaranteeing the protection of both personnel and equipment.

Overall, the Schneider Electric 174 CEV stands out due to its combination of robust communication options, powerful processing capabilities, modular design, and user-friendly features. With its focus on energy efficiency and safety, the 174 CEV is an excellent choice for fulfilling the increasing demands of modern industrial environments.