Schneider Electric 174 CEV Mode a Channel Logging Menu, Saving the Logging Status and Log File

Page 62

Diagnostic Tools

6.2.1Notes for Logging

Mode A: Channel Logging Menu

When you invoke the Channel Logging mode A (On) or a (Off), you will be prompted with the message:

Enter M for MBP initiated sessions

Tfor TCP initiated sessions B for both

Session initiator? _

Enter: M to select sessions initiated from Modbus Plus, T for sessions initiated from TCP/IP, or B to select sessions initiated from either network.

Next you will be prompted:

Please enter the sessions you want to (un)log (a-p)

Enter X when done, T to log all sessions

Session? _

Channels are identified by 16 letters: a...p. The channels are made available to incoming transactions as they become open within the bridge, with p being the first available channel. Note that the letters a...p correspond to the sequence in which the channels are made available. They do not correspond to a specific Program path or Data path number.

For example, if the bridge is inactive when it receives a transaction, the transaction will be processed on channel p. If the transaction is initiated from Modsoft and requires both a Program path and a Data path, then it will be processed on two channels, p and o.

Channels are freed for new transactions in the order p ----> a as they become

available.

Saving the Logging Status and Log File

The current logging mode is saved to the WATTCP.CFG file in the field:

log_level=<level>

where <level> is the currently selected mode.

defaults are: log_errors (all TCP/IP and routine errors) log_channels (all channels) log_messages (all routine messages)

Both the WATTCP.CFG and the BRIDGE.LOG file can be uploaded to a host.

59

Page 61 Page 63
Image 62
Page 61 Page 63
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 Setting the Ethernet Connector Jumper Section Overview Hardware InstallationSetting the Modbus Plus Node Address 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 EdgeUpper Filter Periodic MaintenanceCleaning the Filters 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 SequenceSetting the Modbus Plus and TCP/IP Address Mapping Overview Software ConfigurationSetting the Ethernet Configuration Configuration With a Bootp Server SectionConfiguration With a Bootp Server Navigating the Cfgutil Menu Configuration With the Cfgutil UtilityStarting Cfgutil Saving the Configuration Required Configuration FieldsAdditional Configuration Fields 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 MappingByte 3. First Bridge’s IP Routing How Mapping Works Modbus Plus to TCP/IPBytes 1 and 2. Bridge Node Address and Path Byte 4. Second Bridge’s Modbus Plus RoutingBridge 2 Maps the Message to Modbus Plus Message is OriginatedBridge 1 Maps the Message to TCP/IP 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 MappingDynamic Routing of Messages Setting Up the Bridge for Dynamic RoutingContents Hex Contents Decimal 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 MbpstatStarting Logging Logging the Bridge’s ActivityHow Logging Works 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 Frame Default gatewayField Framing typesLayer InternetIP Address MAC AddressRouter SwitchRepeater 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