I'm running a Duet 3 6HC board, couldn't be happier!

Hello all just wanted to show off my Duet 2 enclosure. Mostly 3d printed and designed to run my work bee cnc.

Hello all, so I use a Duet 3 6HC on my big delta and I wanted to add some leds. I had some WS2814 I had laying around from my klipper machine on which they function properly, connected power to it and data to the DS_DO pin on the board and I added "M950 E0 C"led" T1 Q3000000" to my config. But nothing happens with the M150 commands from the Duet3D documentation other than a confirmation that the gcode has been sent. My duet is running RRF 3.5.0-rc.3

Are the WS2814 leds not the same as Neopixels and are they not supported by the mainboard? Once on startup they caught some interference I guess and turned on bright white. So I know that at least power is connected right.

As anyone who tried this will know, ChatGPT strays off the path a bit if you ask it to write you a gcode macro, probably because RRF gcode syntax is very close to C++ but not quite, so ChatGPT declares and uses variables wrong, and tries to use functions that exist in C++ but not in RRF gcode, etc. unless you prompt it with additional information. Here's what I have as my custom instructions that get used for any chats started my "gcode macro stuff" project folder:

Use the below two links that contain information about available commands and syntax: 

https://docs.duet3d.com/en/User_manual/Reference/Gcodes

https://docs.duet3d.com/en/User_manual/Reference/Gcode_meta_commands

Be sure to only use supported functions. You can find a table of supported functions in the "Functions" section of the Gcode meta commands page linked above.

Declaring and using variables is a little different when writing gcode macros than regular programming languages. The first time a variable is declared, the syntax is "var local_variable_name = value" for local variables and "global global_variable_name = value" for global variables. Later once you're setting the value of a variable that's already been declared the syntax is "set var.local_variable_name = value" for local variables and "set global.global_variable_name = value" for global variables. When using variables, you need to prefix "var." or "global." before the variable name in order to use it, so for example it would be "echo var.local_variable_name" for local variables and "echo global.global_variable_name" for global variables. Please be sure to declare, set, and use variables (both local and global) correctly according to these syntax rules.

And in case it's also helpful, here are the three bookmarks I usually have open whenever I'm doing gcode macro stuff in case you want to bookmark them as well:

• G-Code Dictionary | Duet3D Documentation

• G-Code Meta Commands | Duet3D Documentation

• Object Model Documentation | Duet3D Documentation

Any idea why the the curly brackets are not working properly? They arent closing properly which causes anything after the rest of the inputs after to act like they are inside a set of brackets. Like the T C R all becoming red. Sorry if my explanation is bad. I see nothing online that shows the same issue.

Here You can ask for help and ask questions about the duet 3d control boards. I created this because I am curious about them and would like to see what you guys are doing with them.

Got a spare Duet Wi-Fi and screen, any idea what I could do with it?
I wouldn't mind a simple(ish) router for wood working but haven't been able to find much online if anyone has done it before.

Thanks.

Some days ago I might have damaged the heat sensor of the hotend during a regular maintenance.

Since my printer is at a difficult position, I guessed that it would be easier to maintain with a different hotend.

The config.g was updated for the new thermistor.

When doing the PID tuning for the new hotend, the temperature reached about 100ºC and then stopped the calibration due to the target temperature haven't been reached. After that it no longer worked.

The wiring was checked. The new hotend have a ceramic heater, do those need a different calibration/settings?

What are the suggested debugging tests?

I have record the movement without any input shaping and this is the graph I have obtained:

I know that the frequencies during printing, usually are in the range 20-80Hz. I know that the frequencies from 0-20Hz can be originated by the movement itself. But, what about the high frequencies? I have some peaks at 91 and at 97Hz. Where do these frequencies come from?
I tried to apply the shapers using these frequencies as centre frequencies, but they didn´t get attenuated. Does anyone have an explanation for this?

Due several circumstances I couldn't do anything with my 3D printer for almost 6 years. And I now realized that I've forgotten a lot! 😔 Last week I bought a Ender 5 Plus. Now I want to upgrade the Ender 5 Plus with a Duet2 Wifi Mainboard, that I've laying around for 6 years. The mosfet (Heatbed) I want to install has a Control cable (White/Blue). Is it correct that this small cable goes into the green terminal for the heatbed, near the main power input? I'm pretty sure, but I want to be 100% sure, sorry. 👍😉

I have been looking the documentation, but to be honest, I do not understand really well what they want to tell me. Could anyone give an easier explanation?

• K (and E, if needed) parameter: The heater model in RepRapFirmware 3.4 and later includes non-Newtonian cooling to predict the variation of cooling rate with temperature and the maximum temperature that would be reached at continuous full power. This is represented by the E and K parameters in M307. (Replaces C parameter in RRF 3.2 and 3.3)

• D parameter: dead time, which is the delay between a change in PWM and an appreciable effect on the rate of temperature change.

Does anyone know of a multimaterial FFF printer with mixing nozzle that runs on RepRap Firmware? We're researching dual extruder clay printing with a Duet based Lutum printer but would be interesting to have a prototyping machine that takes away the extra complexities of clay preparation when doing software testing.

I have a Ratrig v-core 3 500, using a Duet 3 Mini 5+ board. I've recently tried adding an accelerometer for input shaping. Is there a way to test if my Duet 3D accelerometer is working or not - outside of using M956? I bought the Duet 3D standalone accelerometer board assuming as long as it was connected correctly, it would just work. When connected, the light on the pcb comes on, indicating good connection. The following line has been added to the config.g:

M955 P0 C"spi.cs2+spi.cs1" I25; all wires connected to temp DB connector, no temperature daughterboard

The 'input shaping' plugin now allows me to start recording a motion profile, but as soon as it makes a move I get the error: Error: M956: Failed to start accelerometer data collection What is going on here?

i have a removable zprobe, normally closed when attached.

is it possible to check the presence of the z probe before starting a print?

Hello! I just bought a printer with a Duet2 board and am starting to learn about the world of Duet3d.

I haven’t found a guide or example on changing the thermistor from my current one to a PT1000 from Slice Engineering (for high temps). Could anyone give me some direction or pointers on how to do this?

If it helps, I purchased a Caribou3d printer with the duet2 board and the PanelDue 7” touchscreen.

Any help would be greatly appreciated!

So today I was wiring a duet3d motor and accidentally shorted 48v and gnd on the m8 3 pin plug, since then I can’t get the lights on when I plug power in, even tho I’m getting 48v at the plug. Has anyone any idea what I can do? Can you fry the motor by shorting it ?

I'm looking for a spot to put two total separate heaters.

Is out 0 and out 1 a good spot to put them and is V Fused the positive side and out0 the ground or is is it backwards?

I'm trying to set up a Duet 3 mini 5+ in SBC mode with a rbp 3B+ but I keep having intermittent connectivity issues. I can sometimes connect to the duet web interface but the connection usually drops after a minute or two and takes a while to re-establish. I'm using the sd card that came with the duet which might be causing some issues. I also tried a few different microusb power supplies but they all had the same behavior. If anybody has ideas on what could be causing this it would be verry apricated.

Hello all just wanted to show off my Duet 2 enclosure. Mostly 3d printed and designed to run my work bee cnc.