It has been a while, but I wanted to share that the 1k resistor was the trick that kept it working. We will also add a new power supply to the whishlist for the near future.

Thanks for the support!

@dc42 The laser is a CO2 tube powered by a MYJG100W high voltage power supply.
The power supply powering the tube is near to the only reaming part of the original machine, it has been functioning well for the past 5 or so years.

@o_lampe we will try to add a 1k resistor (or is another value recommended?) in serie with the control wire coming from the Duet. And hopefully it will do the trick. Is there a reason that this could be needed all of a sudden?

He All,

We have been using the Duet3D platform for years on multiple machines, and it has been great.
Now we have hit a bump with a seemingly malfunctioning Duet3D. We purchased it from ReprapWorld, and they have advised us to seek help here, and figure out if it is a garantee issue.

Machine: A big laser cutter 900x600mm, most parts have been upgraded over the past years.

RepRapFirmware for Duet 3 Mini 5+ version 3.4.4 (2022-10-20 16:18:28) running on Duet 3 Mini5plus WiFi (standalone mode).

What works: When the machine starts, it can home, and start a job all fine. Controls work over the WiFi and we have built our own controls that use the API, both function fine untill it freezes. It has also been fully functioning for the past year, with the same config etc.

What fails: As soon as the laser needs to fire in a gcode file (G1 with an S value), the machine freeze, seems like it complete restarts.

Looking in the log saved to SD card data (M929), there is nothing to go on. The status after reboot shows:

Last reset 00:09:08 ago, cause: reset button

What we have already tried:

• Different SD cards
• Update to the latest firmware version
• Different gcode files, with different shapes etc. (all with the same result)
• Checked the wiring
• Checked the power supply
• Tried to connect with YAT (but it keeps saying: "warning: 5 bytes already buffered but not sent anymore")

Here is the config used: config_share.g.txt

Really hope that anybody can come up with something we can test or do, or explain how this could indeed be a fault in the hardware.

Thanks again! Cheers,
Kosmo - de CreatieHallen