Error count | M122 ?

User3D

M122 output:

-Ethernet-
state : active
Error counts : 0 0 1 0 0
socket states : 5 2 2 2 2 0 0 0

what does this error count inform?
Using board - Duet3 MB6HC (3.3beta)
X-Y on EXP1XD
Observing using DWC 3.2

dc42

The error counts are:

rxErrorCount, rxBuffersNotFullyPopulatedCount, txErrorCount, txBufferNotFreeCount, txBufferTooShortCount

The nonzero txErrorCount means either there was a "Transmit Frame Corruption Due to AHB Error" or "HRESP Not OK" error. From the datasheet:

Bit 4 – TFC Transmit Frame Corruption Due to AHB Error
This bit is set when an error occurs during reading transmit frame from the AHB. Error causes include HRESP errors and buffers exhausted mid frame. (If the buffers run out during transmission of a frame then transmission stops, FCS shall be bad and GTXER asserted).
In DMA packet buffer mode, this bit is also set if a single frame is too large for the configured packet buffer memory size.

Bit 8 – HRESP HRESP Not OK
Set when the DMA block sees HRESP not OK.

The datasheet doesn't explain HRESP but it seems to be related to Ethernet in general rather than to Microchip's MAC implementation.

Do you get these errors frequently?

User3D

@dc42 said in Error count | M122 ?:

Do you get these errors frequently?

@dc42 YES !

dc42

Does the Ethernet connection run reliably, or not?

Do you just get one txerror when you first connect? I'm wondering whether the client is trying to see whether the Duet will accept a jumbo frame, or something like that.

User3D

@dc42 said in Error count | M122 ?:

Does the Ethernet connection run reliably, or not?

yes I suppose. DWC works fine!

Do you just get one txerror when you first connect?

I get it all the time... after connecting , during print , after print finishes .
If it is so because of unreliable Ethernet connection then how do i verify that?