Schneider Electric 174 CEV Logging the Bridge’s Activity, How Logging Works, Starting Logging

Page 61

Diagnostic Tools

6.2Logging the Bridge’s Activity

Before running diagnostics you can build a log of the communication activity performed by the bridge. This can help you to determine the kind of diagnostics you may want to run.

You can set the bridge to log all traffic initiated on either its Ethernet network or Modbus Plus network. You can also set it to log errors only.

How Logging Works

Logging is turned on and off through a keyboard and monitor connected to the bridge. The bridge provides five logging modes. It writes the log results with date/time stamping to a file BRIDGE.LOG, as well as to the monitor.

The BRIDGE.LOG file is self--wrapping and contains enough space for several hundred lines of logging.

Note that logging will slow the throughput of any application running in the bridge. Particularly the use of Mode C (TCP/IP Tick Logging) will generate constant logging messages.

Setup

If a keyboard and monitor are not connected to the bridge, remove power to the bridge and connect them to the bridge’s panel. Restore power to the bridge.

To invoke logging, the bridge application must be running. If the bridge displays its CFGUTIL menu on startup, press Escape to close the menu. This should display the bridge’s C:\ > prompt. Enter GATELOOP to start the bridge.

Starting Logging

With the bridge running, type a letter: A, B, C, D, or E (upper case letter) to select a logging mode.

The logging modes are:

AChannel Logging.

BTCP/IP Error Logging.

CTCP/IP Tick Logging.

DRoutine Logging.

ERoutine Error Logging.

Stopping Logging

To stop logging type a letter: a, b, c, d, or e (lower case letter) to turn off the selected logging mode. Type the letter f to turn off all logging.

58

Page 60 Page 62
Image 61
Page 60 Page 62
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 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 DefaultsCleaning the Filters Periodic MaintenanceUpper Filter Lower FilterConfiguring the Bridge Files Resident in the Bridge Files Supplied With 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 Starting Cfgutil Configuration With the Cfgutil UtilityNavigating 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 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 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 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 DiagnosticsHow Logging Works Logging the Bridge’s ActivityStarting Logging Stopping 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 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.
Top Page Image Contents