Resolved, when the print finished, retightened my wires in the mosfets, looks like something must've come loose…

I did a little searching on this, but I only found the solution for when someone is using a thermocoupler, which I'm not. I just have my heated bed wired up like normal to the mosfet on the board. What would cause this heater fault on the bed like that? I have a print going right now so it's actually working fine, it's like halfway through, but afterwards I'd like to know what steps to take to try and resolve this. My first thought is to play around with the thermistor and double check the bed wires. But I'd like some feedback on this as well. Thanks.

@dc42:

Why not connect the hot end directly to the Duet? Hot end heaters draw only a few amps, so the external mosfet serves no useful purpose.

To bypass the drain directly from the board and go straight to the PSU, using the H1 as the signal for the mosfet to indicate draw. It's not completely necessary, but it's something I'm used to doing. I've always had a preference for running the heating aspect of a printer directly from the supplies for the sake of complete energy efficiency.

So, I'd like to preface this post with a little background. Historically I'm more familiar with cheaper melzi boards, the Duet is higher end and is one of the nicer boards out there, so I'm not as familiar with it. If the wiring diagram below seems funky, just be aware this is almost exactly how it works with a lower end board. Perhaps there's an issue with the signal wires I'm using, maybe not.

I have a couple of cheap little 360 watt 12v Power Supplies, I'd like to use one to power the hotend and the board, and another to power the bed. Typically how the mosfets work is, when the board sends current to heater 1, the 18 gauge wire triggers the signal on the mosfet, which in turn pulls the voltage from the PSU to power the heating element. This gives a stronger and more stable current, allows for an additional PSU which helps to reduce loads, basically allowing for potentially faster heating, even if it's by fractions. The same thing goes for the bed.

However, here's the problem. When I signal for the hotend to heat, my signal wires don't seem to be triggering for heater 1, but when I wire the hotend directly to the board, it works fine. I'm thinking at this point perhaps it's just a defective mosfet, but I'd like some input on whether or not what I'm doing here is even supported by the board, and possibly if there's just some issues with it signaling. Let me know what you think.

Prepare your eyes for my terrible MSPaint skills

Thanks all

Hey thanks for the quick responses guys :), I do believe it's the gcode file that Cura is generating, I'll have to look into the settings a bit more and find out where it's stopping the heating. This is my first attempt at a multi-filament setup so there's certainly a learning curve here. Thank you both for the great info. And yes, I do have the cyclops style setup.

Just curious, I've noticed when I slice a multi-extruder gcode file, that when my duet runs the print and goes to switch tools, it stops heating. If I set my standby temp to 235 (Both filament lines/extruders share a single nozzle) will that resolve the issue of losing the heat when it switches tools? I'm testing that out now, but I'm also curious to see how any of you may have your setups done, just to compare it to what I have.

Currently I just have my 2 tools, both are assigned to heater 1, and then tool 1 is assigned extruder 0, tool 2 extruder 1. I've just now set my standby temps to 235 and my extrusion temps to 235. Looking forward to your replies. Thank you

Just a friendly update. Replacement board got here, Runs great now absolutely in love.

@dc42:

If your E1 motor output is free, try putting this command in config.g:

M584 X4 Y1 Z2 E3

Make sure it is earlier in the file than the M906 command. Then connect your X motor to the E1 motor output.

If that gets your X axis working, then I'm sorry you do have a bad X driver, and you should ask for your Duet to be replaced or repaired under warranty.

Are you using 12V or 24V power?

12v. I've gotta get to bed so I'll give this a shot tomorrow. Thanks for the help.

I did another test. When swapping a motor that was just previously working (y axis) over to my x axis, the y stepper motor produced the same issue, while the x axis worked fine. Both stepper motors work, both cables work (didn't change the cables I used just swapped the connections on the board). Y axis now jiggling, x axis works fine. What could be causing this? I really hope it's not a bad driver. I have no clue what the issue is.

Edit: changing the ma values in the config didn't work either. Increased it slightly but at that point the motor didn't even move. Put it back down to 800ma, it's just back to jiggling again.

I uploaded a config where I changed the endstops to NC from NO, unplugged all the end stops and turned it on, tried jogging the motor, same results, just jiggling rapidly back and forth.

@dc42:

To do this test, unplug the motor from the Duet. Push a short piece of solid core wire into 2 of the connections in the socket to short them.

I think I must have a bad stepper driver on my x axis. I fixed my y, my z works as well, but my x refuses to function, it's doing the same thing as before. I checked my crimps, I even tried a new wire, and another new stepper I had lying around, it's just not functioning. My endstops seem to be wired correctly, as they all work. My wires work, my motors work, my crimps are fixed, my cables are good, so the only thing I feel it's rooted to at this point is maybe somehow my x endstop is triggering, or it's a bad stepper driver. Any other ideas for troubleshooting my x axis? I feel like I've tried it all at this point.

Thank you both for taking your time with this