I got a message on heater channel X201 that I had a short. After some debugging I isolated the fault to the daughterboard itself:
I repeated the fault with a brand new PT100 and new wiring
The fault cleared when using the X200 channel.

How precisely is the fault identified as a short by the system. Are there other problems that can give a false short indication?

Using a multimeter over the pins of the daughterboard of the failing channel measures ~100Mohm without the heater (around 100 with) which is what I would expect.

Is there anything I can do to further isolate and possibly fix the problem or will I need a new daughterboard?

Maybe this is a bit unfair as I just tested cura right now for the first time (because of this thread) coming from s3d.

Parts layout is not very nice. I could not find any way to drop the part to the bed and had to resort to rotating and translating manually. This is way to clumsy. A basic drop face to bed needs to be implemented. Auto arrange placed parts outside the build volume

In the gcode preview I accidentally moved a model which wiped out the gcode I was reviewing.

No manual supports (yes I knew that, this is why I really didn't bother with it until today), and I do not se that i have any additional control over supports to make up for it. I use manual supports in 90% of my models (Most of the rest need no supports). I had to go hunting in the menus to actually get any semblance of controls to be visible. The usual problem I use manual support to solve is that I have parts with gaps that are too cramped to be able to extract supports from but can be bridged or can tolerate a little drooping, while I have other areas that needs the support. Hence the lack of control of the support is pretty much a dealbreaker.

I could not find any way to save the print settings changes I did as a profile. I guess there is a way, but it is not obvious. Clicking the create button in manage materials (which is where I thought it would be) does not appear to do anything.

You might want to list some of the settings you have tried.

From the config.g you posted my immediate reaction is that it seems to be a low amount of pressure advance for the length of bowden cable you use.

Did you try a little negative extra restart distance?

As a starting point I would likely begin with ~4mm retract, 80mm/s retract speed 0.2 pressure advance, no wipe (unless it is PETG), no coast, no extra restart.

@dc42:

To those who have experienced this issue:

1. Which Duet are you using?

2. Do you also have a DueX2 or DueX5 connected?

3. Which firmware version(s) were you using when the problem occurred?

1: Duet Wifi
2: Yes, duex5
3: 1.19

From the reply I gather you suspect some interrupt storm/high traffic density from the wifi module. I do have access to a MSO scope so if there any test point relevant to the issue I might try to monitor them (If it works out logistically)

I can confirm 1 and 2
I'll do 3-5 once I can reproduce

I have a reliability issue with my duet wifi/duex setup. Occationally and in the middle of a print the printer slows down dramatically executing a couple of cm of moves then pauses for several seconds. Even when I pause the print movement to homne is really slow. Other functions are also slow, web interface is barely responsive. Jog controls on the panel due are unresponsive or extremely slow.

Obviously this slowdown causes a failed print.

The only remedy is to reboot, cold or warm reset does not matter.
This is on 1.19

VIdeos and picture: https://photos.app.goo.gl/6nvOED4R3x1qW2hi2

In my printer profile for PETG I am adding some z offset by using baby stepping:

[[gcode]]
G28 ; 
G29 S1 ; Load and activate detailed bed map
G1 Y1.0 Z0.2 F1000.0 ; prepare to prime
G92 E0 ; reset extrusion distance
G1 X60.0 E9.0  F1000.0 ; priming
G1 X100.0 E12.5  F1000.0 ; priming
M290 S0.20 ; set baby stepping

This works perfectly the first time, however if I make a second print (which uses the same starting script) I see the printer using 0.4mm baby stepping offset.
The documentation states that homing should reset baby stepping but in my case it does not appear to do so.

I see a very uneven motion on high speed XY moves (travel moves) At first I thought I was getting lost steps but a test print with three objects at far ends of the platform prove otherwise.

What I observe is that long travel moves appear to be split into 2-4 segments where the carriage significantly slow down then speed up again between the segments.

It is also observable when using the panel due movement controls so it would not be segments declared in gcode

These are my speeds settings:

[[language]]
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping
M92 X80 Y80 Z1600 E2755 ; Set steps per mm
M566 X1200 Y1200 Z12 E40 ; Set maximum instantaneous speed changes (mm/min)
M203 X18000 Y18000 Z400 E2400 ; Set maximum speeds (mm/min)
M201 X1500 Y1500 Z250 E120 ; Set accelerations (mm/s^2)
M906 X1500 Y1500 Z800 E650 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

@DjDemonD:

Both the flex3drive and nimble require to use low motor current, the motor can't make a fast direction change at high current as quickly. I use 500mA with nimble and a 34mm motor. A 20mm pancake motor or nema 14 would also work. Acceleration needs to be low 120 to facilitate the direction changes. Jerk at around 40. More motor current is a red herring.

In my experiments with a nimble and a pancake stepper I had to go to 600mA. 500mA and less the stepper stalled on high extrusion speeds. (~12-16mm^3 on a 0.6mm volcano nozzle).