Rockwell Automation 56AMXNB User Manual

Rockwell Automation

ControlLogix AutoMax DCSNet and

AutoMax Remote I/O Communication Interface

Module

(Cat. No. 56AMXN/B)

User Manual

Page 2 AutoMax DCSNet /RE RIO Module

Important User Information

Solid state equipment has operational characteristics differing from those of electromechanical equipment. “Safety Guidelines for the Application, Installation and Maintenance of Solid State Controls” (Publication SGI-

1.1) describes some important differences between solid state equipment and hard–wired electromechanical devices. Because of this difference, and also because of the wide variety of uses for solid state equipment, all persons responsible for applying this equipment must satisfy themselves that each intended application of this equipment is acceptable.

In no event will Rockwell Automation be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment.

The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and requirements associated with any particular installation, Rockwell Automation cannot assume responsibility or liability for actual use based on the examples and diagrams.

Rockwell Automation assumes no patent liability with respect to use of information, circuits, equipment, or software described in this manual.

Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation is prohibited.

Throughout this manual we use notes to make you aware of safety considerations.

Identifies information about practices or circumstances that can lead to personal injury or death, property damage, or economic loss.

Attentions help you:

• identify a hazard

• avoid the hazard

• recognize the consequences

Important: Identifies information that is especially important for successful application and understanding of the product.

Microsoft is a registered trademark of Microsoft Corporation.

Windows, Windows 95 and Windows NT are trademarks of Microsoft Corporation.

ControlLogix and Data Highway Plus are trademarks of the Allen-Bradley Company, Inc.

Publication number 56AMXN-UM002A-EN-P November 2002

56AMXN/B AUTOMAX DCSNET/RE RIO MODULE 6

Overview 6

Differences from the 56AMXN/A 7

Hardware Features 9

Other Requirements 9

INSTALLATION 10

Prevent Electrostatic Discharge 10

Set the Switches 10

Prepare the Chassis for Module Installation 11

Determine Module Slot Location 11 Insert the Module in the Chassis 11

Cabling and Termination 12

Software Installation 13

QUICK START 14

DCS Master and Slave 14

Remote I/O Master 14

CONNECTIONS AND TAGS 16

Connections 16

Listen Only Comm Formats 16

Tags 17

Configuration Tag 17 I and O Tags 20 Data Tags 20

CONFIGURING THE MODULE IN RSLOGIX 5000 23

DCS Master or Slave 23

Adding the Module 23 Configuring Listen-Only Connections 25

Page 4 AutoMax DCSNet /RE RIO Module

Remote I/O Master 26

Using the Configuration Signature 28 Importing Tags 29 Configuring Input-Only Connections 29

USING THE DCS CONFIGURATION PROGRAM 32

DCS Bridging 32

USING THE 56AMXN AS A REMOTE I/O MASTER 35

The Configuration Program 35

Procedure 35

AutoConfiguring from the Network 36

Uploading a Configuration from the 56AMXN 36

The Network Tree 36

Remote I/O Tags 38

The Configuration Signature 38

USING THE MSG INSTRUCTION TO ACCESS 56AMXN DATA 39

DCS Data Object 39

Instance Level Services 41

USING DDE/OPC TO ACCESS DCS DATA ON THE MODULE 53

USING THE MONITOR PROGRAM 54

Monitoring DCS Registers 55

Monitoring CLX Registers 56

Monitor Diagnostics 57

The Debug Log 59

The Copy Table 59

Fatal Errors 60

TROUBLESHOOTING 61

Publication number 56AMXN-UM002A-EN-P November 2002

LEDs 61

NET LED – DCS/RIO Network Status 61 CLX LED – ControlBus Status 61 OK LED – Module Health 62 All LEDs Red 62

4-Character Display 62

Using 56AmxnMon for Troubleshooting 63

Reading Diagnostic Counters into the ControlLogix Program 64

Using RSLogix 5000 to Diagnose Problems 64

General Tab 64 Connection Tab 64 Module Info Tab 65 Backplane Tab 66

UPDATING THE FIRMWARE 67

DCS NETWORK UPDATE TIME 68

SPECIFICATIONS 69

SUPPORT 70

Overview

56AMXN/B AutoMax DCSNet/RE RIO Module

This document is a user guide for the 56AMXN/B module, which allows a Rockwell Automation ControlLogix backplane to communicate with an AutoMax DCS network or an AutoMax Remote I/O network. The module can act as a DCS master, a DCS slave or a remote I/O master.

For DCS master or slave operation, the 56AMXN/B uses a specific RSLogix 5000 56AMXN module profile; for Remote I/O Master operation, it uses the 1756-MODULE generic module profile.

As a DCS master, the module:

• Scans up to 55 slave drops

• Transmits 8 words of broadcast data

• Maintains standard DCS diagnostic counters

• Supports up to 8 scheduled connections with the ControlLogix

processor for drop data. Each scheduled connection supports up to 7 drops of input data from slaves to the master and 7 drops of output data from the master to slaves. The connections can update at RPIs from 3 to 750 ms.

• Supports a separate connection for broadcast data, at a fixed update rate of 3 ms.

• Allows access to unmapped input, output and diagnostic data using the Logix MSG instruction or using PCCC messages from RSLinx and other HMIs

As a DCS slave, the module:

• Acts as any drop from 1 to 55, with drop depth from 1 to 55, with 32 words of input data and 32 words of output data per drop

• Receives 8 words of broadcast data from the master

• Monitors the input and output data on others drops on the network

• Maintains standard DCS diagnostic counters

• Supports up to 8 scheduled connections with the ControlLogix

processor. Each connection supports up to 7 drops of slave input data from the module to the master and 7 drops of output data from the slave to the master. The connections can update at RPIs from 3 to 750 ms.

As a Remote I/O master, the module:

• Scans up to 7 drops

AutoMax DCSNet/RE RIO Module Page 7

• Supports up to 248 words of scheduled output data and 250 words of scheduled input data

• Maintains diagnostic counters

As either a DCS master or slave, the module supports bridging, which means that it can obtain its transmit data for any drop from another 56AMXN module in the same chassis.

You can use a DDE or OPC server, such as RSLinx, capable of accessing the ControlLogix backplane, to access the DCS data directly on the 56AMXN. The module "emulates" PLC-5 integer files 100-155. Each file corresponds to a DCS drop.

A watchdog timer is implemented in the module’s hardware. If the firmware does not kick the watchdog within the timeout period the watchdog times out and places the module into a safe fatal failure state.

A jabber inhibit timer is implemented in the module’s hardware. If the network transmitter is on longer than 150% of the longest network frame time, the jabber inhibit forces the transmitter off and places the module into a safe fatal failure state.

The module firmware can be updated using ControlFlash.

Differences from the 56AMXN/A

For DCS Master and Slave operation, there is now an RSLogix 5000 56AMXN Module Profile. You configure the module as a 56AMXN in RSLogix 5000, not using the 1756-MODULE generic module profile. This results in better diagnostics for the 56AMXN in RSLogix 5000.

The 56AMXN/B can exchange much more scheduled data with the ControlLogix processor than the 56AMXN/A could.

The DCS Master or Slave configuration data is stored with the RSLogix 5000 program. No separate DCS configuration file or configuration program is required. It also makes the use of the configuration signature unnecessary.

Remote I/O configuration is unchanged. You configure the 56AMXN using the Generic Module profile in RSLogix 5000 and use the 56AmxnRioCfg program to configure the module.

The way the 56AMXN/B handles outputs in program mode and on loss of connection is different from the way they were handled by the 56AMXN/A.

In DCS master or slave operation, if the ControlLogix was in program mode, outputs from the 56AMXN/A continued to be updated with the current values from the ControlLogix. If there was a loss of connection between the ControlLogix processor and the 56AMXN, outputs held their last state.

Publication number 56AMXN-UM002A-EN-P November 2002

Page 8 AutoMax DCSNet /RE RIO Module

In remote I/O operation, if the ControlLogix was in program mode, the 56AMXN/A set outputs to 0. If there was a loss of connection, outputs held their last state

The 56AMXN/B firmware sets the outputs to 0 in program mode or on loss of connection in DCS Master and Slave and Remote I/O operation.

The 56AMXN/B is backward compatible with the 56AMXN/A. Applications written for the 56AMXN/A do not require modification to run on the 56AMXN/B. However if you want existing applications to use the multiple connection feature of the 56AMXN/B, those applications must be modified.

The firmware in a 56AMXN/A can be FLASH upgraded to 56AMXN/B operation. Refer to page 67 for details.

Publication number 56AMXN-UM002A-EN-P November 2002

Hardware Features

AutoMax DCSNet/RE RIO Module Page 9

The following diagram shows the features of the module.

DCSNet / RE RIO

XXXX

NETOKCLX

Network

The module has:

• A label to indicate that it is a scanner for AutoMax DCS and remote I/O

• A 4-character scrolling display (XXXX)

• 3 LEDs, labelled NET, CLX, and OK, to indicate the status of the

network, the connection to the ControlLogix processor, and its own internal state

• a 9-pin D-shell connector to connect to the DCS or remote I/O network

• switches at the top of the module to set the mode of operation and the drop number and drop depth

The module hardware consists of:

• Processor – 100MHz IDT MIPS

• FLASH memory - 1Mbyte (512Kx16)

• Local RAM - 1Mbyte (256Kx32) 50Mhz synchronous SRAM

• Shared RAM - 512Kbyte (128Kx32) 20ns asynchronous SRAM

Other Requirements

To use the configuration or monitor programs, you require RSLinx OEM or above. You cannot use RSLinx Lite.

To use multiple connections, you need RSLogix 5000 version 12.00 or above.

Publication number 56AMXN-UM002A-EN-P November 2002

Page 10 AutoMax DCSNet /RE RIO Module

Prevent Electrostatic Discharge

The module is sensitive to electrostatic discharge.

ATTENTION: Electrostatic discharge can damage integrated circuits or semiconductors if you touch backplane connector pins. Follow these guidelines when you handle the module:

• Touch a grounded object to discharge static potential

• Wear an approved wrist-strap grounding device

• Do not touch the backplane connector or connector pins

• Do not touch circuit components inside the module

• If available, use a static-safe work station

• When not in use, keep the module in its static-shield packaging

Installation

Set the Switches

The module’s mode of operation depends on the settings of the rotary switches at the top of the module. Before you install the module in the rack, set the switches as shown in the table.

Drop

MSD

0 0 0 0 DCS Master

X X Y Y DCS Slave Drop XX (1-55), Depth

0 0 0 1 RIO Master

Drop

LSD

Depth

MSD

Depth

LSD

AutoMax Network Operation

YY (1-55)

Table 1 56AMXN Switch Settings

Any other settings are invalid and result in the module going into “Thumbwheel test” mode. In thumbwheel test mode, the display shows the current switch settings. It doesn’t go out of thumbwheel test mode until you turn off the power and set the switches to valid numbers.

In thumbwheel test mode, the 56AMXN initially displays “Thumb Test Mode” on the 4-character display, displays the switch settings for 5 seconds, then resumes displaying “Thumb Test Mode”

For DCS slave operation, if the drop number and drop depth are individually valid but the combination results in invalid drop numbers (for example, drop number 55, drop depth 2), the module displays an

Publication number 56AMXN-UM002A-EN-P November 2002

AutoMax DCSNet/RE RIO Module Page 11

error message on the 4-character display but does not enter Thumbwheel test mode.

Prepare the Chassis for Module Installation

Before you install the module, you must install and connect a ControlLogix chassis and power supply. To install these products, refer to the installation instructions you received with them.

Determine Module Slot Location

This example shows chassis slot numbering in a 4-slot chassis. Slot 0 is the first slot and is always located to the right of the power supply. You can use any size ControlLogix chassis and install the module in any slot.

You can use multiple modules in the same chassis.

Insert the Module in the Chassis

This module is designed to be installed or removed while chassis power is applied.

ATTENTION: When you insert or remove the module while backplane power is on, an electrical arc can occur. This could cause an explosion in hazardous location installations. Be sure that power is removed or the area is nonhazardous before proceeding.

Repeated electrical arcing causes excessive wear to contacts on both the module and its mating connector. Worn contacts may create electrical resistance that can affect module operation.

Figure 1 Chassis Slots

Publication number 56AMXN-UM002A-EN-P November 2002

Page 12 AutoMax DCSNet /RE RIO Module

Cabling and Termination

Use drop cable (612574-36R) and passive tap (M/N 57C380) to connect the module to the coaxial network cable. This cable turns down and has a ferrite to reduce EMI. This cable must be used in CE applications. You can also use drop cable 612403-036R which points up.

The drop cable is a 3-foot long multiconductor cable with 9-pin D-shell connectors at each end. Connect one end to the connector on the module and the other end to the passive tap.

The passive tap has two BNC connectors for connection to the coaxial cables and terminating loads.

Figure 2 Inserting the 56AMXN

Publication number 56AMXN-UM002A-EN-P November 2002

Software Installation

AutoMax DCSNet/RE RIO Module Page 13

The network coaxial cable must be terminated with 75 ohm terminating loads attached to the taps at the physical ends of the network. There should be two and only two terminators on the network.

For DCS, the network cable can be RG-59/U or RG-11/U. For remote I/O, the cable must be RG-59/U.

The 56AMXN is supplied with a CD that includes the configuration and monitoring programs for the 56AMXN.

RSLinx should be installed before you install the 56AMXN software. The 56AMXN software requires RSLinx OEM or Professional; it does not work with RSLinx Lite.

You must delete any previous version of the 56AMXN software before you can install a new version. Use the Windows Control Panel Add and Remove Programs to remove the old version.

Insert the 56AMXN CD with the module software and run the program setup.exe on the CD.

Messages about DTL32.DLL when you install or run the programs indicate problems with the RSLinx installation. Confirm that you are have RSLinx OEM or RSLinx Professional (not RSLinx Lite) installed.

Publication number 56AMXN-UM002A-EN-P November 2002

Page 14 AutoMax DCSNet /RE RIO Module

The following sections provide a brief summary of the steps necessary to get the module running in each mode.

DCS Master and Slave

1. Set the switches on the 56AMXN module and install the module in the ControlLogix rack.

2. Run RSLogix 5000. If there a choice of RSLogix versions, select version 12 or above.

3. Create a new file or open an existing file. If necessary, select the appropriate processor properties.

4. Right click on I/O Configuration Folder, or on the bridge module in the desired remote chassis in the I/O Configuration Folder, and select New Module from the menu.

5. Select 56AMXN from the list and click OK.

6. Give the module a name and description and select the slot.

Quick Start

Remote I/O Master

7. Select an appropriate Comm Format. either Master - 56 Drops or Slave – 56 Drops.

8. Click Next.

9. Select the Requested Packet Interval (RPI) for data update.

10. Click Finish>>

11. Save the program and download it to the ControlLogix Processor.

1. Set the module switches and install the module in the ControlLogix rack.

2. Connect the module to the remote I/O network. (The 56AMXN must be connected to the network to read the configuration.)

3. Run the 56AmxnRioCfg program and connect to the module using RSLinx.

4. Perform an Actions/Auto Config command to read the network configuration and store it on the 56AMXN.

5. Select File/Export Tags to export the tags to a CSV file.

6. Run RSLogix 5000 and configure the module. Remember to enter the Configuration Signature (see page 38 for details).

7. Import the tags you exported from 56AmxnRioCfg into RSLogix

5000.

Publication number 56AMXN-UM002A-EN-P November 2002

AutoMax DCSNet/RE RIO Module Page 15

8. You can now write your ladder logic using the tags you imported, download the program, etc.

Publication number 56AMXN-UM002A-EN-P November 2002

Page 16 AutoMax DCSNet /RE RIO Module

Connections

When you add a 56AMXN to the I/O Configuration of a ControlLogix, a broadcast data connection and from one to eight data connections are created. The number of connections is determined by the Comm Format you select when you add the 56AMXN module.

The broadcast connection always updates every 3 ms.

The data connections update at a rate from 3 ms to 750 ms, based on the RPI selected on the Connection tab for the module entry. All data connections update at the same rate.

The broadcast connection contains the broadcast data the DCS master transmits. If the 56AMXN is the DCS master, the ControlLogix writes to output data in the broadcast connection to send the data to remote drops. If the 56AMXN is a DCS slave, the ControlLogix reads input data from the broadcast connection to receive the broadcast data transmitted by the master.

Connections and Tags

The data connections contain the drop data. Each data connection consists of 7 blocks of data. Each block contains the input data and the output data for one drop. You select which drops are mapped into a block by writing to the Config (C) tag for the 56AMXN. Input and output data for different drops can be mapped into the same block. The same drop cannot be mapped to more than one block. By default the blocks are mapped to consecutive drops.

The number of drop data tags created depends on the type of connection you select when you add the 56AMXN to the I/O configuration, for example, Master – Drops, Master, 14 Drops, Slave – 7 Drops, etc. You cannot change the Comm Format after you create the module; to change the Comm Format you must delete the current module and create a new one.

Listen Only Comm Formats

You can also create a 56AMXN in the I/O Configuration with a listen only Comm Format. A listen only Comm Format lets the ControlLogix receive only input data. An owning connection must exist for a listen only connection to work. The listen only Comm Format must be the same size as the owning Comm Format or smaller.

A listen only connection has no configuration data. All configuration is done in the owning connection.

For example, if one ControlLogix uses a Master – 28 Drops Comm Format to a 56AMXN, another ControlLogix can use a Master – Listen Only 28 Drops Comm Format to obtain input data from to the same 56AMXN. (It can also use a 7, 14 or 21 Drops Listen Only Comm Format as well.) The ControlLogix with the listen only Comm Format

Publication number 56AMXN-UM002A-EN-P November 2002

Tags

AutoMax DCSNet/RE RIO Module Page 17

will see the same input data as the ControlLogix with the owning Comm Format, but it will have no configuration or output data tags.

More than one processor can use a Listen Only Comm Format to obtain input data from the same 56AMXN, as long as an owner exists.

Remote Connections

If you are using a 56AMXN in a remote rack, for example a rack connected to the rack that holds the processor using ControlNet or Ethernet, it may be necessary to increase the RPI used to connect to the 56AMXN, as the intermediate network may not have sufficient bandwidth to support the fastest RPIs, especially for the larger Comm Formats (Master – 56 Drops, etc). In particular, 10 megabit Ethernet has insufficient bandwidth to support the 56AMXN/B over a remote connection.

Associated with each 56AMXN are several tags.

Configuration Tag

File Description

C Configuration tag

I Input data for broadcast connection

O Output tag for broadcast connection

I0 – I7 Input drop data tags

O0 – O7 Output drop data tags

Table 2 56AMXN Tags

The terms input and output are used from the point of view of the 56AMXN. If the 56AMXN is a DCS master, output data is data the module sends to remote drops; input data is data received from remote drops. If the 56AMXN is a DCS slave, output data is data it is sending to the DCS master; input data is data it is receiving from the DCS master or data other drops are sending to the master.

The contents of the configuration tag determine how the drop data maps into the ControlLogix drop data tags.

Publication number 56AMXN-UM002A-EN-P November 2002

Page 18 AutoMax DCSNet /RE RIO Module

Figure 3 Configuration Tag

The Configuration tag consists of an InputDropMap and an OutputDropMap section. The number of entries in each section depends on the Comm Format (Master 7 Drops, Master – 14 Drops, etc.) Each entry contains 7 blocks.

You write values to each block to tell the 56AMXN which drop’s data will appear in the corresponding section of the input and output drop data tags. There is a direct correspondence between the Config tag elements and the data tag elements. For example, Local:0:C.InputDropMap[4] corresponds to Local:0:I4, etc.

The configuration tag defaults to having data from consecutive drops. For example, in the screen capture, InputDropMap[0] determines the contents of input drop data tag I0, which will contain input data from drops 1, 2, 3, 4, 5, 6 and 7.

Listen only Comm Formats have no configuration tag since they require no configuration.

The following tables show the possible values that can be written to the configuration tag.

DCS Master

InputDropMap Value Description

0 56AMXN Status/diagnostic registers

Publication number 56AMXN-UM002A-EN-P November 2002

AutoMax DCSNet/RE RIO Module Page 19

InputDropMap Value Description

1 to 55 Drop data from drops, registers 0 to 31

56 Unused

Any other Invalid

OutputDropMap Value Description

1 to 55 Drop data to remote drops, registers 32 to 63

56 Unused

Any other Invalid

DCS Slave

InputDropMap Value Description

0 56AMXN Status/diagnostic registers

1 to 55 Drop data, registers 32 to 63, from master

-1 to –55 Drop data, slave to master, registers 0 to 31,

from monitored drops

56 Unused

Any other Invalid

OutputDropMap Value Description

1 to 55 Drop data, registers 0 to 31, from 56AMXN to

master

56 Unused

Any other Invalid

Duplicate entries in the InputDropMap or OutputDropMap areas are invalid. The only exception is that there can be multiple blocks marked as unused (56).

If the configuration tag contains invalid data, the connections to the 56AMXN do not open. The ControlLogix periodically retries the connections so if you correct the invalid configuration data, the connections will eventually open.

However, if you change the contents of a valid configuration tag in the ControlLogix, you must break and remake the connections to the 56AMXN to cause the 56AMXN to use the modified configuration data.

Publication number 56AMXN-UM002A-EN-P November 2002

Page 20 AutoMax DCSNet /RE RIO Module

For example, you can inhibit the connection, then remove the inhibit to break and remake all connections.

I and O Tags

The I and O tags are associated with the broadcast connection. The contents vary depending on whether the 56AMXN is a DCS master or slave.

DCS Master

The I tag contains a single DINT, Fault, which is 1 if no slaves are connected and is 0 otherwise.

In addition, the fault is -1 (16#FFFF FFFF) if the connection is not active. This could be because the module is not present, is inhibited, or was configured incorrectly (wrong slot, missing or incorrect parameters, etc.)

The O tag consists of the 8 INTs of Data, the 8 words of broadcast data that the 56AMXN sends on DCSnet.

DCS Slave

Data Tags

The I tag consists of a single DINT, Fault, which is 1 if the master is not active on the network and is 0 otherwise, and 8 INTs of Data, the 8 words of broadcast data the master is sending on DCSnet.

There is no O tag for a DCS slave.

Drop data appears in the I0-I7 and O0-O7 data tags. The number of tags depends on the Comm Format. Each tag consists of 7 blocks. The contents of each block are determined by the config tag.

The Input tags consist of a DINT Fault and 7 blocks of data. Each block consists of 32 INTs of drop data.

The Output tags consist of a set of blocks, each of which consists of 32 INTs of data.

For example, if the module is a DCS master in slot 7 and the Comm Format is Master – 56 drops and you write 30 to Local:7:C.InputDropMap[4].Block[1] and Local:7:C.OutputDropMap[4].Block[1], the drop data for drop 30 will appear in data tags Local:7:I4.Block[1].Data and Local:7:O4.Block[1].Data.

Input Fault Bits

The following table shows how the bits in the Fault DINT are used.

Publication number 56AMXN-UM002A-EN-P November 2002

Global Status Registers

AutoMax DCSNet/RE RIO Module Page 21

Bits Description

0-6 Input mapped drop offline

8-14 Output mapped drop offline

16-22 Monitored mapped drop offline (slave only)

Table 3 Input Fault Bits

The 56AMXN diagnostic/status registers can be mapped into one of the input tags by writing a 0 to the entry in the Configuration tag. They may provide useful information on the operation of the network.

Registers 4-7 contain the drop status table. The module sets bits to indicate which drops are exchanging data on the network. Register 4 bit 0 corresponds to drop 0, register 4, bit 1, corresponds to drop 1, and so on.

The table shows how bits in the drop status table are handled by the 56AMXN in each mode.

Master Slave

Bits for slave drops are set when the drops are online, and cleared if they are offline.

Bit 0, corresponding to the master, is always set.

If you disconnect the network, bit 0 remains set, all others go to 0.

If the 56AMXN is being scanned by a master, bits for its own active drops are set. Bits for monitored drops are set if the drops are online, and cleared if they are offline.

Bit 0 is set if the 56AMXN is being scanned by a master. and is cleared otherwise.

If you disconnect the network, all bits go to 0.

Table 4 Drop Status Table

Register 15 contains receive timeouts. This counter increments when the module is waiting to receive but no message arrives within a timeout period.

Publication number 56AMXN-UM002A-EN-P November 2002

Page 22 AutoMax DCSNet /RE RIO Module

Register 17 contains overrun errors. This counter increments when the module receives a packet that is longer than 272 bytes.

Register 18 contains abort errors. This counter increments when the module starts to receive a packet but the packet is never completed.

Offset Description

4 Drop status, drops 0 – 15

5 Drop status, drops 16 - 31

6 Drop status, drops 32 – 47

7 Drop status, drops 48 – 55

12 56AMXN drop number

14 Messages received

15 Receive timeouts

16 CRC errors

17 Overrun errors

18 Abort errors

19 Messages transmitted

20 56AMXN drop depth

Table 5 Diagnostic Registers

For example, if you set Local:0:C.InputDropMap[4].Block[3] to 0, then Local:0:I4.Block[3].Data contains the diagnostic counters, in Local:0:I4.Block[3].Data[0] to Local:0:I4.Block[3].Data[31]

Note: You cannot map the diagnostic counters more than once.

Publication number 56AMXN-UM002A-EN-P November 2002

+ 50 hidden pages