Error 0x04: Help to Resolve Print Stoppages

Aitor

Good morning Duet Team,

A customer has reported an issue with their equipment; it stops during prints. I asked them to send me the G-code and the M122 response right after the failure, and I see that the error is 0x04. How can I solve this? What could be causing it?

Equipment specifications:

Duet 2 WiFi
Version 3.4.5
Panel Due 5i
G-code generated with Simplify3D (I have reviewed it and nothing seems out of the ordinary)

M122 response:

29/5/2024, 12:40:53: M122: === Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.5 (2022-11-30 19:36:12) running on Duet WiFi 1.02 or later
Board ID: 0JD2M-958DA-F64T0-6J1DD-3S46R-K6YB0
Used output buffers: 1 of 26 (26 max)
=== RTOS ===
Static ram: 23836
Dynamic ram: 75792 of which 0 recycled
Never used RAM 9596, free system stack 170 words
Tasks: NETWORK(notifyWait,14.2%,211) HEAT(notifyWait,0.0%,333) Move(notifyWait,0.0%,363) MAIN(running,85.7%,458) IDLE(ready,0.1%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:18:05 ago, cause: software
Last software reset at 2024-05-29 12:22, reason: StuckInSpinLoop, GCodes spinning, available RAM 8972, slot 2
Software reset code 0x4083 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x200025b4 Task MAIN Freestk 929 ok
Stack: 0042c637 004573d6 610f0000 3f800000 3dc6b000 424cf4fe 3edbc06f 3331bb4c 40000000 b5ddd98d 388ab355 bb360b61 3e2aaaab 3f800000 3c4192f5 43af028f 4354c416 3f800000 3f800000 20000010 00000000 00000000 0042c637 00000001 00035bf6 00000000 20000c98
Error status: 0x04
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 47.8, current 48.0, max 51.2
Supply voltage: min 24.0, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/8, heap memory allocated/used/recyclable 2048/66/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min n/a
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5: 
Driver 6: 
Driver 7: 
Driver 8: 
Driver 9: 
Driver 10: 
Driver 11: 
Date/time: 2024-05-29 12:40:52
Cache data hit count 4294967295
Slowest loop: 96.38ms; fastest: 0.18ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 30.0MBytes/sec
SD card longest read time 1.4ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.0
=== 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== Network ===
Slowest loop: 207.23ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 2 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.27
WiFi MAC address b4:8a:0a:f7:06:5b
WiFi Vcc 3.27, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 23120
WiFi IP address 10.100.102.228
WiFi signal strength -75dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

Best regards,

Phaedrux

Does it complete any prints, or does it halt on every print? Does it stop in the same place?

@Aitor said in Error 0x04: Help to Resolve Print Stoppages:

3.4.5

3.5.1 is out now with many fixes. It would be worth updating.

Aitor

Good morning @Phaedrux,

According to my client, it stops during some prints, but it doesn't seem to always stop at the same point. I have reviewed the G-code and it doesn't appear to be corrupt, which has me puzzled. I asked him to try disconnecting the LCD, as I had a similar issue some time ago due to a poor connection in another device. I also suggested improving his Wi-Fi signal, as it is very weak and he mentioned experiencing many disconnections. I have come to think that if many requests are being made to Duet Web Control, it could overload the system. Is this possible?

Regarding version 3.5.1, we are testing it on our internal equipment and preparing the necessary files to update our clients' devices, but it will still take some time to implement it in the devices already on the market. I am aware of the improvements that this version brings, although I am also encountering certain problems. When I am sure that they are due to the version and not my new configurations, I will indicate them in another post, since we are using Duet3 instead of Duet2 in the new models, and it is very possible that I have overlooked something.

Best regards,

dc42

@Aitor we have just released 3.5.2-rc.1. You might like to check whether the bug fixes we list in the release notes at https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x-RC#reprapfirmware-352-rc1-changes-since-351 relate to any of the issues you had with 3.5.1.

Aitor

Good morning @dc42,

I will try it as soon as I can. Next week we will be at a trade show with the new models, so I won't have time to run the tests until after that. However, the issues I am having with version 3.5.1 are likely due to a misconfiguration on my part and are not related to the incident in this post. But since you mentioned it, I'll explain what is happening: with the Duet3 6hc and 3hc electronics installed on three different machines, when I press the emergency stop button from Web Control or from PanelDue, sometimes the reboot doesn't complete correctly, and the 6hc and 3hc don't synchronize. As a result, I see communication errors, such as not being able to move the axes connected to the 3hc or incorrect temperature readings connected to the 3hc. If I power off and on the machine, they synchronize as expected. I have other issues, but I will explain them after I run more tests. In this case, I think it's possible that I don't have stop.g configured correctly, as I have it the same as when I use Duet2.

Best regards,