ENET-Analyzer Docs

Product positioning

ENET-Analyzer is used to observe real messages and live timing in industrial Ethernet links. It is suitable to be placed between the master station and the slave station, and between the slave station and the slave station to record the communication process and assist the host computer to complete protocol analysis, timing analysis and data visualization.

What problem is solved?

Product features

Typical applications| scene | value |

| --- | --- | | EtherCAT device joint debugging | Observe the master station initialization process, PDO mapping, state machine changes and abnormal messages | | Servo debugging | Visualize CiA402 position, speed, status word and other process data | | Production line return | Reuse packet capture files and filtering rules to verify whether device behavior is consistent | | On-site problem recurrence | Save the real link data as pcap and bring it back to the R&D side for review | | DC synchronization diagnosis | Analyze cycle jitter, loopback delay and master station transceiver interval, and generate timing analysis reports | | IO timing analysis | Put external IO capture and network events on the same timeline for observation | | Customer delivery report | Precipitate time series indicators, abnormal points and analysis conclusions into PDF reports |

Product composition

Quick specs

Quick overview of host computer capabilities

1. Software positioning

The ENET-Analyzer host computer is a desktop analysis software used with the analyzer. Its interface style is close to Wireshark, but it adds dedicated functions such as timing analysis reports, PDO data charts, IO capture, alarm location, and on-site review for EtherCAT debugging.

The software is suitable for the following tasks:

• Real-time packet capture from the analyzer uplink port.
• Open and save pcap files.
• Parse EtherCAT messages and common network fields.
• Filter data by time, protocol fields, EtherCAT addresses and commands.
• Automatically identify DC sync frames and analyze period jitter.
• Export timing analysis PDF reports and timing data.
• Convert PDO process data to curves.
• Capture IO status changes and link them with network events.

2. Preparation

Please confirm before use:

• Analyzer body.
• USB cable.
• Ethernet cable.
• For Windows computers, it is recommended to use PCIE Gigabit network card.
• The ENET-Analyzer host computer has been installed.
• Npcap is installed and WinPcap API-compatible Mode is checked.

If you need to use Wireshark to observe ESL messages, you can enable ESL and esl_eth protocols in Wireshark.

3. Complete the first packet capture in five minutes

3.1 Wiring

1. USB connection to the analyzer for power supply.
2. Connect the field link to the analyzer IN/OUT detection ports.
3. Connect the analyzer’s UP port to the computer’s Gigabit network card.
4. Wait for the device to start up and the red and yellow LEDs to turn off normally.

3.1.1 Interface and wiring description

The left-side IN / OUT ports are used to insert the analyzer into the field EtherCAT link. Connect the IN port to the master side, such as a PLC or industrial PC. Connect the OUT port to the slave side, such as a servo drive, remote IO module, or downstream EtherCAT slave. After wiring, the analyzer captures link packets without changing the field communication direction.

The right-side interfaces are used for PC connection, power supply, status indication, and external trigger / IO capture.

Port notes:

• IN and OUT detection ports only support 100Mbps, not 10Mbps.
• The UP uplink port only supports 1000Mbps and does not support 100Mbps / 10Mbps.
• If the yellow LED flashes, it usually means that the network port is not connected correctly or the negotiated rate does not match.
• If the red LED comes on and does not go out, it usually means the device is not starting up properly.

3.2 Software operation

1. Open the ENET-Analyzer host computer.
2. Click to automatically find the device network card, or manually select the network card corresponding to the UP port.
3. Click Lock after the background of the network card turns light green.
4. Click to start packet capture.
5. Reproduce live action.
6. Click Stop.
7. Click Save to export the pcap file.

4. Software main interface

The main interface consists of device selection, packet capture control, packet list, parsing details, hexadecimal view, status bar and multiple analysis windows.

Common tool buttons:

Icon	Function	Description
	Automatically find the device network card	Automatically match the network card corresponding to the upstream port after connecting to the device
	Lock the network card	Confirm the current packet capture network card to avoid accidental switching
	Start packet capture	Start real-time capture from the selected network card
	Stop packet capture	Stop current capture
	Re-capture packets	Clean the current session and start again
	Open file	Open existing pcap file
	Save file	Save current packet capture data
	Filter	Open the filter input field
	Timing Analysis	Open DC Cycle and Delay Analysis Window
	Export timing report	Export the current timing analysis results as a PDF report
	IO capture	Open IO capture waveform window
	Data Analysis	Open PDO data chart window
	Alarm	Open status alarm window
	Time jump	Locate the target data frame according to the timestamp
	Settings	Open system settings

5. Capture, open and save packets

Real-time packet capture process:

1. Select the network card corresponding to Select Ethernet port on the main interface.
2. Or click the Automatically find device network card button.
3. After the network card background turns light green, click the lock button.
4. Click to start packet capture.
5. Observe the packet list, parsing details and status bar during the packet capture process.
6. Click the Stop button when you need to stop.
7. Use the save button to save the captured packet as a pcap file.

Open the file:

• Click the Open button to select the pcap file.
• After opening, you can continue to use functions such as filters, timing analysis, and PDO data analysis.
• Non-analyzer packet capture files may lack critical timing information, and some functions may not be available.

Save file:

• Click the Save button to save the current packet capture data.
• After successful saving, you will not be prompted to save repeatedly when closing the file or exiting the software.
• If there are unsaved data when exiting, the software will pop up a save confirmation.

Suggestions:

• Before capturing packets, confirm that the UP port is connected to a Gigabit network card.
• For long-term packet capture, it is recommended to use chunked packet capture and a cache directory with sufficient space.
• When the problem recurs on site, packet capture should be started before the device is powered on and the master station is initialized.

6. Message viewing and filtering

The message list is used to view captured data in chronological order. After selecting a frame, you can view the protocol fields in the details area and view the raw data in the hexadecimal view area.

Common filtering examples:

protocol == EtherCAT
mac.type == EtherCAT && ec.cmd != 0x00
mac.type == EtherCAT && ec.addr == 0x00000910
mac.type == EtherCAT && ec.len == 8 && ec.index == 0
mac.type == EtherCAT && ec.addr > 0x1000
(ec.intr != 0x00) || (ec.cmd == 0x01)

Commonly used fields:

Supports ==, !=, >, <, contains, and &&, || combination conditions are available.

7. Timing analysis

The timing analysis window is used to observe the cycle stability of EtherCAT DC synchronization related messages.

The software supports two methods:

• Automatic recognition of DC sync frames for common masters.
• Manually set DC cycle command, address and command length.

Main indicators:

Common interactions:

• Right click the mouse to jump to the data frame corresponding to the waveform.
• Ctrl + Mouse wheel Scales the horizontal axis.
• Shift + Mouse wheel Zooms the vertical axis.
• Separate scroll wheels to zoom horizontal and vertical axes simultaneously.

If the automatic identification does not meet the on-site conditions, you can view the Datagram Header in the message details, and then manually configure the DC cycle command, address, and command length.

8. Generate timing analysis report

Timing analysis reports are used to precipitate on-site cycle data into deliverable and repeatable PDF files. The report is suitable for equipment joint debugging records, exception review, test documentation and customer communication.

Generate suggestions:

1. First complete a packet capture containing DC periodic frames.
2. Open the timing analysis window and confirm that the DC frame is recognized correctly.
3. Manually set the DC cycle command, address and command length if necessary.
4. Check the master station sending interval, master station receiving interval, slave station loopback delay and other curves.
5. Click Export Timing Report.
6. Select the save path and wait for the export to complete.

The report can reflect:

If you use IO capture at the same time, you can confirm the time relationship between IO events and network events before reporting, making the timing conclusion more complete.

9. IO capture analysis

The IO capture window is used to observe changes in external IO signals and assist in analyzing the relationship between network events and actual actions.

Operation points:

• Mouse wheel zoom horizontal axis.
• The upper scale bar can measure the time difference.
• Channel symbols can be dragged up and down.
• Right click the mouse to jump to the corresponding data frame.

Typical uses:

• Analyze the time relationship between external trigger signals and EtherCAT messages.
• Observe the sequence of device actions, IO flips and network status changes.
• There was a short-term abnormality at the review site.

10. PDO data analysis

PDO data analysis is suitable for converting EtherCAT process data into curves, such as position, speed, status words, control words, sensor values, etc.

Tool buttons:

Icon	Function
	PDO automatic selection
	Current entry summary information
	Clear cache data
	Manual entry
	Delete selected entry
	Save entry configuration
	Select or import an XML file

10.1 PDO automatic selection

Recommended process:

1. Capture or open the pcap containing the EtherCAT initialization process.
2. Configure the ESI XML directory in settings.
3. Open the data analysis window.
4. Click PDO Auto Select.
5. The software recognizes the slave and PDO configuration.
6. Select all slaves or a single slave as required.
7. Add target items to the chart.

If the slave is not detected or the XML cannot be matched, please confirm:

• Whether the packet capture includes the complete initialization process.
• Whether the XML directory is configured correctly.
• Whether the target device XML exists.

10.2 PDO manual selection

When automatic matching does not meet your needs, you can choose manually:

1. Select the ESI XML file.
2. View TxPDO/RxPDO entries.
3. Filter by module or pattern.
4. Click the Add button to join the data analysis list.
5. Manually adjust the direction, command, address, offset and length if necessary.

11. Alarm and time jump

The alarm function is used to monitor status changes. Typical example:

• EtherCAT status changes from OP to SafeOP.
• The error bit in the status word has changed.
• The specified PDO data exceeds the expected range.

Time jumps are used to locate messages directly from charts, alarms or external records. After you enter a target time point, the software jumps to a frame close to that time.

12. Blocked packet capture and caching

Blocked packet capture will automatically divide the packet capture data into multiple small files to prevent a single temporary file from being too large.

Configurable in settings:

• Group size.
• Cache directory.
• Whether to keep the old cache before the next startup.

Note:

• In the default temporary directory, old caches are usually cleared on the next startup.
• Please use the save button to save important packet captures as pcap.
• Disk space should be confirmed before capturing packets for a long time.

13. Recommended workflow

Suggested process for reproducing on-site problems:

1. Connect the analyzer and host computer.
2. Start capturing packets before the device is powered on or the master station is started.
3. Reproduce the problem.
4. Stop capturing packets and save pcap.
5. Use filters to locate abnormal phases.
6. Open timing analysis to observe period changes.
7. Open PDO data analysis to observe key process data.
8. Configure alarms and time jumps if necessary.
9. File the pcap, screenshots, and conclusions together.

It is recommended to keep at least the following for each issue review:

• Original pcap file.
• ENET-Analyzer version.
• Photos or topology diagrams of field wiring.
• Screenshots of key time points.
• Timing analysis PDF report.
• If using PDO analysis, keep the XML file and entry configuration.

14. FAQ

14.1 The network card list is empty

Possible reasons:

• Npcap is not installed.
• Npcap unchecks WinPcap compatibility mode.
• The host computer has insufficient authority.
• The system network card status is abnormal.

Processing:

1. Reinstall Npcap.
2. Check WinPcap API-compatible Mode.
3. Restart the host computer.
4. Restart the computer if necessary.

14.2 Failed to automatically find the device network card

Check:

• Whether the UP port is connected to the computer's Gigabit network card.
• Whether the network cable is normal.
• Whether the computer network card negotiates at Gigabit rate.
• Whether the yellow LED is flashing.

Processing:

• Manually select possible network cards and start packet capture verification.
• Replace the network cable or computer network port.
• Avoid connecting to 100M only USB network cards or switch ports.

14.3 Unable to catch EtherCAT messages

Check:

• Whether the field link is connected to the IN / OUT detection port.
• Whether the master station has started communication.
• Whether the IN / OUT port speed is 100Mbps.
• Whether the UP port is connected to the computer's Gigabit network card.
• Whether the wrong packet capture network card was selected.

Suggestions:

• Start capturing packets before the master station starts.
• Without using the filter, confirm whether the original packet enters the list.
• Use Wireshark to open the saved pcap for cross-validation.

14.4 Timing analysis does not automatically identify DC frames

Possible reasons:

• The captured packet does not contain DC synchronization frame.
• The DC configuration method used by the master station is not within the scope of automatic identification.
• The starting point of packet capture is too late, lack of initialization or key cycle frame.

Processing:

• Manually configure DC cycle command, address and command length.
• Capture packets again before starting from the master station.
• Check the Datagram Header in the message details to confirm the matching conditions.

14.5 PDO automatic selection has no results

Possible reasons:

• pcap does not contain the full EtherCAT initialization process.
• ESI XML directory is not configured.
• The XML file does not match the field device.
• Multi-axis or modular equipment configuration is more complex and requires manual selection.

Processing:

1. Configure the XML directory in settings.
2. Verify that pcap contains the initialization process.
3. Try device sequence summary to see matching status.
4. Use PDO to select manually if necessary.

14.6 Open pcap displays very little data

If the pcap was not generated by the analyzer link, it may be missing critical timestamp or format information. The software will filter unrecognizable data and only display limited content or statistical tips.

Suggestions:

• Use ENET-Analyzer to re-capture packets.
• Use Wireshark when common protocol viewing is required.

14.7 Device red LED is not off

A red LED that comes on and then doesn't turn off usually means the device is not starting up properly.

Processing:

• Re-plug the USB.
• Replace the USB cable or USB port.
• If it still cannot be restored, contact technical support.

14.8 Yellow LED flashes

A flashing yellow LED usually indicates that the network port is not connected correctly or that the negotiated rate does not match.

Processing:

• Confirm that the UP port is connected to a Gigabit network card.
• Verify that the IN/OUT probe ports are connected to a 100Mbps link.
• Replace the network cable.

15. Minimum Checklist