@SamKudarauskas you will need to detect it's held down in the trigger then have a while loop that looks for the release, if it's released within a certain time then carry out action A, if after that time, Action B

@fabflo yes you can connect to those pins without affecting the functionality of the expansion breakout. They are connected directly to MCU pins without any protection, so be careful not to apply excessive voltage or static discharge to them.

@nsgarde I've upvoted you, so you should be able to post now. It's to stop spammers posting links.

I'd guess you have the endstops plugged in incorrectly, as two of them (X and Y) are saying they are at the endstop, and one of them (Z) isn't. Assuming the axes are all touching, or not touching, the endstops, I would expect them to either all be on (at max/min), or all off (not stopped). Double check you have wired the correct endstop to the correct IO header on the Duet. Post a picture of the wiring if in doubt.

Ian

@dc42 Good Morning, Thank you for your reply.

The GND connection between X11 and the 1XD worked, a day later i had another issue with another 1XD but this time outputting step/dir signals.
I think the whole problem is/was that i had the machine turned on for 11 days straight and there must be too much static (pellets conveying to the extruder have alot of static (the hopper and conveyer tubes are grounded).

For the 1XD with the The step/dir signal problem, the signal was irregular and 'missed steps' all of a sudden, it became worse and worse. I unplugged power to the board and plugged it back in, it was working fine right away. So last night i turned off the machine and turned it on this morning. Now everything works fine for the past 2 hours.

Do you think this is a grounding issue? with static buildup in the whole machine being the issue?

@Addithy @dc42 I've added this note to the OUT2 description in the 'Description of connections' table https://docs.duet3d.com/en/Duet3D_hardware/Duet_3_family/Duet_3_Toolboard_1LC#description-of-connections

Note At power on/reset, before it comes under firmware control, OUT2 is on by default. This is so the hotend fan is on in the event of a firmware failure or reset.

Ian

@ProfChris Thanks, I've amended the text to:

If the reset button is stuck in (rare), or has been mounted so it is pushed in by an enclosure (also check connected PanelDue/12864 displays for this, by disconnecting them), the Duet will get stuck in a boot loop, which will cause the DIAG LED to be on permanently. Check there is clearance around the reset button, or use some tweezers to gently pull the button out.

Ian

@nachogil said in Control and power four 23CL motors:

Could I pass the signal from a 6HC through the CAN bus of a TDB to four Motors 23CL (with brake) and power them through the TDB's four power connections, powering the TBD with the correct power supply?

Yes you could do that.

@nachogil said in Control and power four 23CL motors:

Which kind of power supply could be adequate? 48v 480w 20a shout be enough?

48V 480W 20A doesn't make sense, it's either 48V 480W 10A (which would be sufficient) or 48V 960W 20A (which would be overkill). Even 48V 240W 5A should be sufficient.

@dc42 thanks, exactly what I needed to know! I'll be staying within safe operating limits. Given this information I probably won't push much past 48V.

@jfhunt said in Duet custom board on Fusion3 F410:

Does anyone know if the custom board that was built for the Fusion3 F410 has any extra control pins that might be able to control a 12v or 24v switch or relay activated by gcode? It would be similar to what is used in many smaller tabletop laser or cnc's where a solenoid is opened to start air flow for the laser or other device.

Any thoughts?

You might want to post a photo or two of the board you're talking about, if its one I'm thinking of its not made by Duet so no one here is going to know what you're asking about.

I have discovered this is an OrcaSlicer issue:

alt text

Its randomly injecting a G10 S0 ~95% of the way into the print.

@flopo76 your PID P term is clearly oscillating excessively. Try a lower P term (e.g. 20) and perhaps a small D term (0.01 to 0.05).

You may be better off using the Custom GCode field to command a 50mm Z move instead of letting the plugin generate the move command.

Also I suggest you change the data collection setting from "As fast as possible" to a lower value such as 500 or 1000 per second, that way you should be able to see the complete move.

@Razani another option is to connect the Duet USB port to the PC via a hub that provides an on/off power button for each port. That's what I do.

@Dizzwold yes it's safe t connect IO_IN pins to 5V. On Duet 3 they are rated at 30V or 50V depending on the board version. Make sure that the negative side of the 5V supply is connected to negative VIN.

@jltx The two pin CAN connector on the Mini 5+ is 2.54mm Molex compatible. Use the crimps and shells that came with the Mini 5+, not the crimps that came with the toolboard.
See https://docs.duet3d.com/en/User_manual/Troubleshooting/Parts#connectors-used-on-main-and-on-most-expansion-boards for details

Ian

@droftarts
There is a sticker right under that driver.
20250314_165333.jpg 20250314_165546.jpg

This was a brand new board, but puchased in August 2024. I believe this might have been my fault. When creating my initial power cable to the Tool Distribution board about a month ago and got the PINs reversed in the circuit layout. I immediately powered off and reversed things at one end and plugged it in and didn't notice any issues. At least not until now...

None of the other boards had this issue since I had updated the build guide for those circuits.

@Inlinebrother & @misterjtc I just finished converting my flashforge creator pro (replicator 2) to a duet 3 mini 5+ .. with the exception that I did gut the extruders and replace them with a biqu h2 v2.... so you're on your own with setting up the two extruders.. but the rest of it I got worked out.. respond and tag if you are looking for help ...

@adhanabal your very welcome hope you got what you needed to do done 🙂

@droftarts

Thank you for your help!

I was able to get my bed working 🙂

@jay_s_uk

thanks!

Yes you would need to modify the homing files to position the probe where you want it before the G30 happens.

Not sure why the initial file using variables wasn't working correctly to get to the center. It's possible your M557 grid isn't setup correctly for your bed size.

For the lead screw positions you can estimate by moving the print head as close to the lead screw position as you can get it and then using a ruler to measure the distance from there. It doesn't need to be sub millimetre accurate to work, just close enough.

Then in your bed.g file you would manually move the probe to the nearest position it can reach close to the lead screw and probe there. The guide describes everything needed in more detail.