Schneider Electric 174 CEV - Manual (Page 61)

Diagnostic Tools
58
6.2
Logging 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:
A Channel Logging.
B TCP/IP Error Logging.
C TCP/IP Tick Logging.
D Routine Logging.
E Routine 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.