I have tried about everything I can think of to add the Plugins. I am on the current release of RepRap FW 3.4.0. Every time I try to add the zip file like the instructions say, it uploads, then I get an error that says "Only a single file can be uploaded & started". So then I tried to upload through the files system. No luck... So I tried to upload through the Plugin manager. No luck. Anyone have any ideas?
I am on the Duet 3 6HC Board with a V1.1 Toolboard attached.
Please let help.
@dc42 I bought one of the displays shown above with the two ribbons. I tried to get this work with my Duet Mini 3 5+ Wifi... but after plugging in it's just dead? I did add the gcode to the config. But it's still non responsive. Everything I see online is for the PanelDue... Any help David?
@chrishamm I did finally figure it out. I unfortunately had to find a windows machine because doing anything on my MacBook was impossible. I had to erase the board, and use BOSSA to get it to upload back to stock FW. Once i did that it booted up fine.
I think it's important to say... If I wanted to update to the latest Beta, what file can I upload through the DWC via the SBC?
@jumpedwithbothfeet for what it’s worth I am using a Toolboard V1.1 also.
@jumpedwithbothfeet thank you for the reply. However I am on MacOS. And I’m actually not using a USB? I’m simply ssh into the pie.
I guess one of my questions is since I erased the Duet Board do I need to reload the FW onto it before I do anything? If so I’ve tried to connect all twenty USB’s I have in my house and for some reason the Duet never shows up?
So... I have a RatRig V-Core 500 Corexy. I have the Duet 6hc + Raspberry Pi 4. Initially when I got it all wired up it was working great... Then because I wanted to try to the Accelerometer I decided to try to update to the latest Beta. It hung on "installing"... After an hour I decided to abort and shut off and reboot and thats when my hell started.
I first tried to fix the Pi. I reimaged the SD card, and that did nothing. Still the same DWC image. 
So I reimaged again and again... thinking... the Duet board is running off the Pi with DUETPI right? Well I have researched and googled and I am finally out of options. I ran scripts to start and stop DCS and it is giving me an error. But every suggestion I have seen to fi it fails.
So then I thought "I'll just erase the board and reload the FW"... of course nothing is that easy on Duet. But I installed the jumper, powered it on, installed a USB (thats what it said to do?), held the reset down for 30 seconds... at this point I have no idea if the FW is on there or not. I tried to reload the FW via BOSSA on the Pi... but it doesn't seem to work.
At this point I would settle for just going back to stock... brand new board, brand new Pi... and reset everything up. Can anyone help me here... I am so frustrated I almost bought a BTT board tonight. Please help.
Hello everyone. So I am building a RatRig 500 V-Core. Unlike 99% of builders I am electing to go with Duet RepRap FW.
Here's my question. So I am running a RPi, on a Duet 3 Mainboard, and while preparing I came across the benefits of using the Toolboard 1LC V1.1. Especially for the Accelerometer and only running 4 wires back to the board. But I am trying to see anyone who has actually mounted the tool board besides the Toolchanger.
Is the bolt patter on the Toolboard the same as a Stepper bolt pattern? Can it be mounted to the back of a Stepper? or is there some other suggested way? All the documentation says how to mount it to a Hemera, but I don't have one, nor do I want one.
Can anyone show me some examples of where they mounted theirs? again no Hemera...
I would appreciate any ideas or help. Thanks.
@dc42 David, so after many months of trying to get first a Laser and now a Magnetic sensor working.. I FINALLY HAVE IT WORKING! YAY. The sensor I got had a cracked piece of plastic not letting it tension the filament. The Installation guide should ensure there is tension on the filament before proceeding.
But to the reason i am posting here. Did the "post Script" ability every get implemented ? Like a Prusa I would like to allow it to do a specific action upon detection.
Thanks
I have to set a G30 single probe in the middle before the G29 or the heightmap is a foot over the bed. It’s the solution I was given.
After the print starts I set baby step. The next time the printer homes or restarts the baby steps are gone. That’s why.
So I am a Prusa guy. Lately in my recent Cartesian build I went with a Duet. In Prusa Marlin flavor you dial in the Z Offset and leave it. You can have different offsets for different temperatures. In my build using a EZABL, I got it all figured out, but no matter what I do, when it starts printing it’s way too high.
I naturally baby step down but I don’t want to have to set the babystep everytime. I tried to cheat but adding the offset to my Start Gcode but that did not work. About four layers in it was like it started plowing the nozzle into the layer before ruining the layer until it self corrected and would start stacking normal again.
So here’s my workflow:
M561 turn off mesh compensation
M208 S1 Z-3
Baby step to the bed until it touches.
G92 Z0
M500 to save.
G1 Z5
G30 S-1
Repeat four times and average the result; then add to G31 in config.g
When I probe before a print at temp, I do one G30 in the middle of the bed.
G29.
So when it starts printing it’s always 1+mm too high. I can add the babystep gcode until the first layer is perfect.
Shouldn’t I be able to change the G31 offset and adjust the printing height? Can I take the amount I have to babystep and subtract that from the G31 offset?
Please help’
David did you ever implement this? This is my biggest issue with Duet. Prusa allows you to fine tune the Z Offset OT Babystep, then it stays until you change it again. In later firmware Prusa has managed to make profiles so depending on the filament you’re using you can have different offsets. Pretty clever that a Marlin function works so good when Duet requires you to adjust baby stepping every single print.
I finally figure it out! Basically I think I needed a center bed Probe for the Datsum=0? This macro worked a treat! https://forum.duet3d.com/topic/4552/mesh-bed-levelling-oddities
I’ve been working on this for 24 hours trying to fix this. I’ve double checked everything. I’ve probed all four corners, made sure they are dead flat. I’ve leveled the bed best I can, and I can get a heightmap that’s near perfect, but it’s WAY in the air... in some cases over a .6 mm higher than the Z plane?
I’ve gone through the configuration of setting the nozzle height, probe height, etc. I’m using a EZABLE pro from TH3D. The probe seems to work flawlessly into the Z Probe port on the board. I have the I1 in the M558. I have the probing pattern set right.
I’ve commented out the M92 Z0 in the homez.g I set the Z0 and set the trigger height and add to the config file. But alas I keep getting the heightmap miles in the air and I don’t know why. For a long this is my most recent attempt. I get the front probes right, but the rest refuse. The bed is smooth and completely level to the X Axis. The X axis is flat.
Please help me!
There is no fan that ash on makes of that size in 24v that I know of. It does though. Sounds stupid loud!
So got my duet working. Yay. But my Hotend fan for the Mosquito is crazy loud, and at full blast. Can I maintain the thermostatic functions and reduce the amount of the fan speed? For example have it at 50% after 49°c ?
Hey! So I have 5v Endstops. I would like to keep 5v inductive Endstops. I know I can use Pin1 of the expansion header for a 5v source while keeping the ground and signal hooked to the regular pins. My question is obviously I have a X, Y and Z endstop and only 1 5v pin. Can I connect all three 5v pins to that one pin on the expansion header without damaging it? I’m assuming 3.3v won’t be enough to power them.
Thanks.
