@veti I am running 2.0(RTOS) (2018-06-05b3).
I do have a paneldue, I have researched this before and I never got conclusive results, so I just live with it.

Ok, thanks for the tip, I enabled logging. I am curious if the faults are a result of the high filament flow rate going through the hotend. It is designed for ludicrous volumetric output and it delivers, however I tuned the PID's with it just sitting there, maybe the amount of cold filament running through affects the heating parameters?

Hello,
I am running the Duet WiFi 2 on a cr-10s5 with the E3d Supervolcano hotend. I have the silicone sock installed and I have run the autotune function for this hotend. I run 12+ hour print files at work all the time, and a large portion of my prints pause themselves 1-2 hours from the end and throw a heater fault. By the time I arrive at work the next morning, the Duet has already abandoned the print, and the gcode log is so full of checksum errors I can't get to the original error. I have never once had a heater fault while I'm in the room. I need some help getting to the bottom of the issue.

Hi,

I recently got the Duet WiFi for my CR-10S5 and i'm working on tuning skipped steps recognition. I thought I'd start with the X-Axis, and then move on to Y. The command I've put in config.g is as follows: M915 X Sxx F0 H50 R2. If I set the S-Value to anything below 30 it falsely detects lost steps every time the axis moves, however if I set it at 30 or above, it wont detect lost steps, even if I force the axis to skip. I am very frustrated and would greatly appreciate some help!

Thanks