Schneider Electric 174 CEV Overview Software Configuration, Setting the Ethernet Configuration

Page 32

Configuring the Bridge

3.2Overview: Software Configuration

Here is an overview of the tasks for configuring the bridge. The references are to the sections of this guidebook that show the detailed installation steps.

3.2.1Setting the Ethernet Configuration

Configure the bridge’s IP address and other Ethernet parameters to allow your host application to recognize the bridge.

Configuration With a BOOTP Server (Section 3.3)

If a BOOTP server exists, configure the server to recognize the bridge. When the bridge is initially powered up, it will attempt for 30 seconds to connect to a BOOTP server. If the server is found, the bridge will automatically configure for the Ethernet connection. Note that you will still have to set up the mappings between Ethernet and Modbus Plus devices, or you can create a host file for centralized mapping which you can download.

Configuration With the CFGUTIL Utility (Section 3.4)

If a BOOTP server is not available, you can use the internal CFGUTIL program to configure the bridge. Connect a keyboard and VGA monitor to the bridge, start the utility, and use it to setup the bridge’s IP and gateway addresses, and subnetwork mask.

3.2.2Setting the Modbus Plus and TCP/IP Address Mapping

Setup your bridge’s mapping tables to control the flow of traffic through the bridge. Your mappings define the routing destinations for messages received by the bridge on one network and passed through it to destinations on the other network.

Setting the Mapping: TCP/IP to Modbus Plus (Sections 3.5 and 3.6) Messages received by the bridge over TCP/IP contain a Destination Index address byte in the range 1 ... 249 decimal. This byte corresponds to the dest_idx field in Modbus Application Protocol commands issued in Modicon panel software such as Concept and Modsoft. The bridge maps this byte to one of 249 possible Modbus Plus node destinations. You define the Modbus Plus node address to be associated with each Destination Index byte value.

Setting the Mapping: Modbus Plus to TCP/IP (Sections 3.7 and 3.8) Messages received by the bridge over Modbus Plus contain a routing byte in the range 1 ... 255 decimal (the dest_idx field). The bridge maps this byte to one of 255 IP destinations. You define the IP address to be associated with each Modbus Plus routing byte value.

28

Page 31 Page 33
Image 32
Page 31 Page 33
Contents Breite 185 mm Höhe 230 mm Breite 178 mm Höhe 216 mm Training Contents Using the Bridge Software Uploading and Downloading FilesDiagnostic Tools GlossaryModbus Plus to Ethernet Bridge CEV 200 Introducing the Ethernet to Modbus Plus Bridge Illustrates a typical bridge connectionTCP/IP Bridge Message Transactions and Paths Read Discrete Output Status Specifications Power Input Tolerance CurrentAgency Status Installing the Bridge Hardware Overview Hardware Installation Setting the Modbus Plus Node Address SectionSetting the Ethernet Connector Jumper Section Connecting the Network and Power Cables SectionCE Installation Requirements Section Verifying the Network Communication SectionSetting the Modbus Plus Node Address Bridge Enclosure Screws Remove ScrewsDefault Setting Setting the Ethernet Connector Jumper JP2 AUI Mounting the Bridge Hardware Mounting RequirementsInstalling the Bridge Hardware Connecting the Network and Power Cables BNC Ferrite Bead on RF-45 Cable CE Installation RequirementsGrounding Verifying the Network Communication Ethernet Card IndicatorsModbus Plus Card Indicators Factory Default Settings Ethernet Card DefaultsModbus Plus Card Defaults EdgePeriodic Maintenance Cleaning the FiltersUpper Filter Lower FilterConfiguring the Bridge Host Software Disk Files Supplied With the BridgeFiles Resident in the Bridge Files Generated or Modified by the Bridge Software Startup SequenceOverview Software Configuration Setting the Ethernet ConfigurationSetting the Modbus Plus and TCP/IP Address Mapping Configuration With a Bootp Server SectionConfiguration With a Bootp Server Navigating the Cfgutil Menu Configuration With the Cfgutil UtilityStarting Cfgutil Required Configuration Fields Additional Configuration FieldsSaving the Configuration Address Mapping Table FieldsHow Mapping Works TCP/IP to Modbus Plus Destination Indexes 1 .. Mapped RoutingReserved Destination Indexes Destination Index 255 Bridge Internal CommandDestination Indexes 0 and 254 Dynamic Message Routing Setting the Mapping TCP/IP to Modbus Plus 1 MB+ Mapping Table Layout and Default EntriesEntry Example MB+ Mapping Table Saving the MappingHow Mapping Works Modbus Plus to TCP/IP Bytes 1 and 2. Bridge Node Address and PathByte 3. First Bridge’s IP Routing Byte 4. Second Bridge’s Modbus Plus RoutingMessage is Originated Bridge 1 Maps the Message to TCP/IPBridge 2 Maps the Message to Modbus Plus Message is DeliveredSetting the Mapping Modbus Plus to TCP/IP TCP Mapping Table Layout and Default EntriesEntry Example TCP Mapping Table Example Modbus Plus to TCP/IP MappingSetting Up the Bridge for Dynamic Routing Contents Hex Contents DecimalDynamic Routing of Messages ExampleUsing Dynamic Routing Clearing the Configuration Clearing the Bridge’s ConfigurationSetup Using the Bridge Software Bridge Software Contents SW-MBPE-000 Setting Up a Custom Bridge Configuration Using the Software in Custom ConfigurationsMinimum Requirements for Custom Bridge Configurations DEVICE=MBPHOST.SYS /md000 /s5d /n0 /r2 Uploading and Downloading Files Configuring an Http Server Configuration ExampleCgi-bin Initiating an Upload Uploading Files to a HostUpload Overview Upload Example RTE.CFGInitiating a Download Downloading Files to the BridgeDownload Overview Download Example Diagnostic Tools Logging the Bridge’s Activity Diagnostics OverviewEthernet Diagnostics Modbus Plus Diagnostics MbpstatLogging the Bridge’s Activity How Logging WorksStarting Logging Stopping LoggingMode a Channel Logging Menu Saving the Logging Status and Log FileTcpinfo StartingStarting Ping at the Host PingStarting Ping at the Bridge Network Selection Examples Starting MbpstatSelecting the Network to be Analyzed Typical Mbpstat Routing Your Mbpstat Menu Entering Node AddressesOption 1 Set Routing Parameters Set Routing ParametersOption 2 Monitor Network Activity Monitor Network ActivityOption 3 Read Global Data Read Global DataOption 4 Global Data Present Table Global Data Present TableOption 5 Node Active Station Table Node Active Station TableOption 6 Node Error Statistics 05.00.00.00.00 Failure 244Option 7 Token Station Table Token Station TableOption 8 Token Owner Work Table Token Owner Work TableOption 9 Current Internal Path Transactions PathOption 10 Node Personality Node PersonalityMessage Examples Mstr Example TCP/IP Node Mstr in TCP/IP NodeMstr Example Modbus Plus Node Mstr in Modbus Plus NodeNCB Return Codes Network Control Block NCB Return Codes ERRsuccessGlossary Default gateway FieldFrame Framing typesInternet IP AddressLayer MAC AddressSwitch RepeaterRouter ServerUTP Winsock

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