# BASEstartm Classic DAS
for Modicon®
Programmable Controllers
Installation and User's Guide

Previous | Contents | Index

# 2.4 Tracing Device Communications

The DAS for Modicon programmable controllers has built into it the capability to trace programmable controller communications and to send this output to either a file or a user terminal. The purpose of this tracing is to allow the troubleshooting of programmable controller communications.

To enable tracing do the following:

- Set one of the following logicals to 1:

  DCM_MOD$MODBUS_TRACE | Trace the MODBUS NI (Network Interface)
  DCM_MOD$MPLUS_TRACE | Trace the MPLUS NI (Network Interface)
  DCM_MOD$MODTCP_TRACE | Trace the MODTCP NI (Network Interface)

  The logical name must be defined in a scope that will be seen by the device server process (ILAN$DEVSRV).
- Set the trace output logical to a file or other output device:

  DCM_MOD$MODBUS_TRACE_OUTPUT | Trace the MODBUS NI (Network Interface)
  DCM_MOD$MPLUS_TRACE_OUTPUT | Trace the MPLUS NI (Network Interface)
  DCM_MOD$MODTCP_TRACE_OUTPUT | Trace MODTCP NI (Network Interface)

  The logical name must be defined in a scope that will be seen by the device server process (ILAN$DEVSRV).
- Start the tracing.
  To start tracing for the NI, disable all devices on the line for which tracing is desired and reenable them. The trace logical is read when the first device on the line is enabled.

The trace output is flushed to the file after every 100 lines that are traced, so trace output may lag actual device I/O.

To turn tracing off, reverse the steps used to turn tracing on.

# 2.5 Failures During Product Use

If an error occurs while this product is in use and you believe the error is caused by a problem with the product, take one of the following actions:

- If you have a Software Product Services Support Agreement, contact your Customer Support Center (CSC) by telephone or by using the electronic means provided with your support agreement (such as DSNlink). The CSC provides telephone support for high-level advisory and remedial assistance. When you initially contact the CSC, indicate the following:
  - The name and version number of the operating system you are using
  - The version number of the product you are using
  - The version number of BASEstar Classic you are using
  - The hardware system you are using (such as a model number)
  - The Modicon programmable controllers you are communicating with
  - A brief description of the problem (one sentence if possible)
  - How critical the problem is
- If you have a Self-Maintenance Software Agreement, you can submit a Software Performance Report (SPR).
- If you do not have any type of software services support agreement and you purchased this product within the past year, you can submit an SPR if you think the problem is caused by a software error.

When you submit an SPR, take the following steps:

1. Describe as accurately as possible the circumstances and state of the system when the problem occurred. Include the description and version number of the product being used. Demonstrate the problem with specific examples.
2. Reduce the problem to as small a size as possible.
3. Remember to include listings of any command files, INCLUDE files, or relevant data files, and so forth.
4. Report only one problem per SPR. This will facilitate a faster response.
5. Mail the SPR package to Compaq.

Previous | Next | Contents | Index