Schneider Electric 174 CEV manual Introducing the Ethernet to Modbus Plus Bridge

Page 7

Modbus Plus to Ethernet Bridge

1.1Introducing the Ethernet to Modbus Plus Bridge

The Modicon Ethernet to Modbus Plus Bridge provides a transparent multipath connection between Ethernet host applications and the Modbus Plus industrial network. The bridge functions as an addressable node on each network, managing the Ethernet and Modbus Plus protocols and translating messages between the network applications in both directions.

Ethernet hosts can establish connections to the bridge and send messages intended for Modbus Plus nodes. The bridge accepts the messages, creates internal paths for the Modbus Plus transactions, waits for the Modbus Plus token frame, and forwards the messages to the destination nodes. It receives the data responses from the Modbus Plus nodes, returns them to the Ethernet hosts, and closes the paths.

Messages sent to the bridge on either Ethernet or Modbus Plus contain an embedded Modbus message, consisting of a function code and additional information such as register addresses and data. The bridge uses the Modbus function code to determine the type of internal path required for the transaction, and opens a path if one is available. If a path is not available, a Modbus error code (exception code) is returned by the bridge to the requesting node.

The bridge provides Modbus Data Master, Data Slave, Program Master, and Program Slave paths as defined by the Modbus function codes in the messages. It supports up to eight concurrent Data paths and eight concurrent Program paths.

The bridge supports full five--byte Modbus Plus routing, enabling transactions through Modicon BP85 Modbus Plus bridges to Modbus Plus nodes on up to three networks beyond the Ethernet bridge.

Note that Modbus Plus Global Data or Peer Cop messages are not supported because those types of messages are passed as part of the Modbus Plus token frame. The token frame is passed among nodes on the local Modbus Plus network, but is not passed through any bridge devices to other networks.

Figure 1 illustrates a typical bridge connection.

2

Page 6 Page 8
Image 7
Page 6 Page 8
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 Connecting the Network and Power Cables Section Overview Hardware InstallationSetting the Modbus Plus Node Address Section Setting the Ethernet Connector Jumper 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 Grounding CE Installation RequirementsFerrite Bead on RF-45 Cable Modbus Plus Card Indicators Ethernet Card IndicatorsVerifying the Network Communication Ethernet Card Defaults Factory Default SettingsEdge Modbus Plus Card DefaultsLower Filter Periodic MaintenanceCleaning the Filters Upper FilterConfiguring the Bridge Files Resident in the Bridge Files Supplied With the BridgeHost Software Disk Software Startup Sequence Files Generated or Modified by the BridgeConfiguration With a Bootp Server Section Overview Software ConfigurationSetting the Ethernet Configuration Setting the Modbus Plus and TCP/IP Address MappingConfiguration With a Bootp Server Starting Cfgutil Configuration With the Cfgutil UtilityNavigating the Cfgutil Menu Address Mapping Table Fields Required Configuration FieldsAdditional Configuration Fields Saving the ConfigurationDestination Indexes 1 .. Mapped Routing How Mapping Works TCP/IP to Modbus PlusDestination Indexes 0 and 254 Dynamic Message Routing Destination Index 255 Bridge Internal CommandReserved Destination Indexes 1 MB+ Mapping Table Layout and Default Entries Setting the Mapping TCP/IP to Modbus PlusSaving the Mapping Entry Example MB+ Mapping TableByte 4. Second Bridge’s Modbus Plus Routing How Mapping Works Modbus Plus to TCP/IPBytes 1 and 2. Bridge Node Address and Path Byte 3. First Bridge’s IP RoutingMessage is Delivered Message is OriginatedBridge 1 Maps the Message to TCP/IP Bridge 2 Maps the Message to Modbus PlusTCP Mapping Table Layout and Default Entries Setting the Mapping Modbus Plus to TCP/IPExample Modbus Plus to TCP/IP Mapping Entry Example TCP Mapping TableExample Setting Up the Bridge for Dynamic RoutingContents Hex Contents Decimal Dynamic Routing of MessagesUsing Dynamic Routing Setup Clearing the Bridge’s ConfigurationClearing the Configuration Using the Bridge Software Bridge Software Contents SW-MBPE-000 Minimum Requirements for Custom Bridge Configurations Using the Software in Custom ConfigurationsSetting Up a Custom Bridge Configuration DEVICE=MBPHOST.SYS /md000 /s5d /n0 /r2 Uploading and Downloading Files Configuration Example Configuring an Http ServerCgi-bin Upload Overview Uploading Files to a HostInitiating an Upload RTE.CFG Upload ExampleDownload Overview Downloading Files to the BridgeInitiating a Download Download Example Diagnostic Tools Ethernet Diagnostics Diagnostics OverviewLogging the Bridge’s Activity Mbpstat Modbus Plus DiagnosticsStopping Logging Logging the Bridge’s ActivityHow Logging Works Starting LoggingSaving the Logging Status and Log File Mode a Channel Logging MenuStarting TcpinfoStarting Ping at the Bridge PingStarting Ping at the Host Selecting the Network to be Analyzed Starting MbpstatNetwork 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 Framing types Default gatewayField FrameMAC Address InternetIP Address LayerServer SwitchRepeater RouterWinsock 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.
Top Page Image Contents