M122 results , failedOp 0x6f ?

[peter247]

Just looking at my m122 after printing a test cube , I can't see anything wrong with the print .
Drivers 2 and 3 are the Z axis so should be locked together , so why is the positions different ? AND is failedOp 0x6f / timeouts important ?

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.2.2 running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: MZSV6-S096U-D65J0-40KMD-3413Z-R7859
Used output buffers: 3 of 40 (14 max)
=== RTOS ===
Static ram: 98732
Dynamic ram: 108044 of which 60 recycled
Never used RAM 38380, free system stack 126 words
Tasks: NETWORK(ready,186) HEAT(blocked,192) CanReceiv(blocked,947) CanSender(blocked,358) CanClock(blocked,362) TMC(blocked,106) MAIN(running,440) IDLE(ready,20) AIN(blocked,264)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 02:05:31 ago, cause: power up
Last software reset at 2021-06-04 20:57, reason: User, GCodes spinning, available RAM 38380, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
Supply voltage: min 0.0, current 24.1, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 60000, standstill, SG min/max 0/100, read errors 0, write errors 0, ifcnt 15, reads 27229, writes 15, timeouts 0, DMA errors 0
Driver 1: position -60000, standstill, SG min/max 0/94, read errors 0, write errors 0, ifcnt 15, reads 27199, writes 15, timeouts 30, DMA errors 0, failedOp 0x6f
Driver 2: position 80560, standstill, SG min/max 0/8, read errors 0, write errors 0, ifcnt 16, reads 27191, writes 16, timeouts 36, DMA errors 0, failedOp 0x6f
Driver 3: position 0, standstill, SG min/max 0/8, read errors 0, write errors 0, ifcnt 16, reads 27205, writes 16, timeouts 22, DMA errors 0, failedOp 0x6f
Driver 4: position 0, standstill, SG min/max 0/48, read errors 0, write errors 0, ifcnt 15, reads 27229, writes 15, timeouts 0, DMA errors 0
Driver 5: position 0, assumed not present
Driver 6: position 0, assumed not present
Date/time: 2021-06-05 13:07:35
Cache data hit count 4294967295
Slowest loop: 29.23ms; fastest: 0.13ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 4.3ms, write time 142.3ms, max retries 0
=== Move ===
DMs created 83, maxWait 454826ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 30910, completed moves 30910, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 3], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1, chamberHeaters = -1 -1
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.7
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 149.56ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- WiFi -
Network state is active
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.25
WiFi MAC address f0:08:d1:02:eb:a5
WiFi Vcc 3.41, reset reason Power up
WiFi flash size 2097152, free heap 22512
WiFi IP address 192.168.0.186
WiFi signal strength -57dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
=== CAN ===
Messages queued 67788, send timeouts 67785, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 16

[dc42]

1. There is a bug in the firmware, whereby the reported position for internal drivers is actually the position of that axis number, not the driver position.

2. The timeouts and failed ops don't normally matter because they get retried. Firmware 3.3 includes a fix for them.