Duet 0.8.5 freezing during print

[KeithW]

Recently my Duet has started freezing in the middle of prints, The max operating temperature is 85c but on the last print it never got above 65c and I sat and watched it until it failed. It just stopped, the board and head cooling fans kept running but the print cooling fan stopped and I had to power it off and back on for the web interface to respond. It's probably coincidental but the last 2 prints stopped on the same layer. Is it possible for the print gcode file itself to cause this?, I haven't tried printing anything else since this started.

Any Ideas? Power Supply? Board? Gremlins?

[dc42]

What firmware version are you running?

If it happens again, run M122 to see if the board has reset, and if so, why. Look at the last reset time and reason, and the software reset data if it was a software reset.

[KeithW]

Hey DC42,

Thanks for the quick reply. I am running Firmware version 1.16 and wouldn't you know it, it finished the print this time so I cannot run the command. This is the first time I am upset a print didn't fail. I will keep an eye on it so the next time it happens I can check to see if it reset though the fact that I had to switch the printer off and on to get access to the WI last time means I probably won't be able to run the command but we will see.

[KeithW]

Well it failed again, this is the output of M122, Last software reset code & available RAM: 0x7003, 1904

[[language]]
M122
=== Diagnostics ===
Used output buffers: 4 of 32 (8 max)
=== Platform ===
Memory usage:
Program static ram used: 45724
Dynamic ram used: 42396
Recycled dynamic ram: 1992
Current stack ram used: 2752
Maximum stack ram used: 4292
Never used ram: 3900
Last reset 00:10:46 ago, cause: software
Last software reset code & available RAM: 0x7003, 1904
Spinning module during software reset: GCodes
Error status: 0
Bed probe heights: 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000
Free file entries: 10
SD card 0 detected, interface speed: 21.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 50.1, current 52.2, max 63.2
Current date and time: 2017-04-12 12:57:28
Slowest main loop (seconds): 1.064331; fastest: 0.000061
=== Move ===
MaxReps: 0, StepErrors: 0, MaxWait: 0ms, Underruns: 0, 0
=== Heat ===
Bed heater = 0, chamber heater = -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Move available? no
Stack pointer: 0 of 5
macro is idle
http is ready with "M122"
telnet is idle
serial is idle
aux is idle
file is idle
=== Network ===
Free connections: 9 of 16
Free transactions: 23 of 24
=== Webserver ===
HTTP sessions: 1 of 8
FTP connections: 0, state 0
Telnet connections: 0, state 0

[dc42]

Please upgrade to latest 1.18.1 firmware. It may fix the problem, and if.it doesn't then it will provide more diagnostic information.

[KeithW]

OK Thanks, I have updated to 1.18.1, will see how it goes.

[KeithW]

Ok so since updating the firmware to 1.18.1 whenever I go into the GCode files I get an ajax error and have to reconnect to the duet with the connect button in the WI.

[[language]]
 Communication Error

An AJAX error has been reported, so the current session has been terminated.

Please check if your printer is still on and try to connect again.

Error reason: timeout

Edit: Ok weirdly this only happens on my laptop, on my desktop it works fine.

[dc42]

Did you upgrade DWC to version 1.15a at the same time, or are you running an old version of DWC?

[KeithW]

I upgraded DWC to 115a. it only happens using Chrome on my (Ubuntu) laptop, it doesn't happen on my Windows desktop using any browser and doesn't happen on my laptop using Firefox. I can live with it as I can just use Firefox.

I haven't been able to test the new firmware as I am having issues getting the first layer in Simplify3D right now, If I print with a raft it is fine but if I print without the first layer is really bad as if it isn't extruding enough or the lines are too far apart. Once I get that sorted I will try a full print again and see what happens.

[KeithW]

It's a bit late but I Just wanted to say that the upgraded firmware seems to have fixed the issue. Thanks David