Communication Module Ethernet Diagnostics
Original instructions
About us
Introduction
Use the Ethernet Diagnostic page to view the dynamic and static data for the Ethernet ports on the Ethernet communications module.
NOTE: Before you can open the diagnostics page, make the connection between the DTM for the target communication module and the physical module.
Open the Page
Access the Ethernet Diagnostic information:
Step
Action
1
In the DTM Browser, find the name that is assigned to your Ethernet communications module.
2
Right-click on the module name.
3
Scroll to Device menu → Diagnosis.
4
In the left pane of the Diagnosis window, select the communication module node.
5
Select the Ethernet Diagnostic tab to open that page.
NOTE: The number of ports on the communication module determines the number of columns displayed in this page.
Data Display
Use the Refresh Every 500ms checkbox to display the static or dynamic data:
Checkbox
Description
Selected
  • Display data that is dynamically updated every 500 ms.
  • Increment the number at the top of the table each time data is refreshed.
De-selected
  • Display static data.
  • Do not increment the number at the top of the table. That number now represents a constant value.
Ethernet Diagnostic Parameters
The Ethernet Diagnostic page displays the following parameters for each communication module port:
Parameter
Description
General parameters:
Interface Speed
Valid values include: 0 (no link), 10, 100, 1000 (Mbits/s)
Interface Flags
Bit 0: Link Status (0 = Inactive link; 1 = Active link)
Bit 1: Duplex Mode (see below)
Bits 2...4: Negotiation Status (see below)
Bit 5: Manual Setting Requires Reset (see below)
Bit 6: Local Hardware Fault (see below)
Duplex Mode
0 = half duplex; 1 = full duplex
Negotiation Status
3 = successfully negotiated speed and duplex
4 = forced speed and link
Manual Setting Requires Reset
0 (automatic, Inactive link) : The interface can activate changes to link parameters automatically.
1 (Active link): Devices require a reset service to be issued to its Identity.
Local Hardware Fault
0 = no event; 1 = event detected
Physical Address
Module MAC Address
Input parameters:
Octets
Octets received on the interface
Unicast Packets
Unicast packets received on the interface
Non-Unicast Packets
Non-unicast packets received on the interface
Discards
Inbound packets received on the interface, but discarded
Errors
Inbound packets that contain detected errors (does not include In Discards)
Unknown Protocols
Inbound packets with unknown protocol
Output parameters:
Octets
Octets received on the interface
Unicast Packets
Unicast packets received on the interface
Non-Unicast Packets
Non-unicast packets received on the interface
Discards
Inbound packets received on the interface, but discarded
Errors
Outbound packets that contain detected errors (does not include In Discards)
Unknown Protocols
Outbound packets with unknown protocol
Error counter parameters:
Alignment Errors
Frames that are not an integral number of octets in length
FCS Errors
Frames received that do not pass the FCS check
Single Collisions
Successfully transmitted frames that experienced exactly one collision
Multiple Collisions
Successfully transmitted frames that experienced more than one collision
SQE Test Errors
Number of times the SQE test error is detected and generated
Deferred Transmissions
Frames for which first transmission attempt is delayed because the medium is busy
Late Collisions
Number of times a collision is detected later than 512 bit times into the transmission of a packet
Excessive Collisions
Frames for which transmission does not finish due to excessive collisions
MAC Transmit Errors
Frames for which transmission does not finish due to detected internal MAC sublayer transmit error
Carrier Sense Errors
Times that the carrier sense condition was lost or never asserted when attempting to transmit a frame
Frame Too Long
Frames received that exceed the maximum permitted frame size
MAC Receive Errors
Frames for which reception on an interface does not finish due to a detected internal MAC sublayer receive error