There is too much fuss around quietness of the printers. I dont mind the noise as i dont like being near them as there are particles released which you dont want to inhale anyway
Thank you for clarification. I am running test print on stock motor with D2 to see if that helps ripple effect.
@carlitototo said in Using External Drivers for X/Y/Z Axis:
It is my understanding that I need to remap the drivers pins, but I'm kinda stuck on the chart near the end of the page, not really shure what the X/Y/Z axis pin is on the duet... same for the E"number" axis pin, on the expansion slot there are 4 pins for each "E" !
Yes, use the E2, E3 and E4 pins (aka driver 5, driver 6 and driver 7 pins).
Thanks for the write up. The BLTouch is definitely one of the trickier probes to get working.
I think the main difference for mode 9 versus mode 5 is that it has faster response time to a trigger. It should also work more smoothly with the deploy and retract macros since you can use m401 and m402 which allows the firmware to keep track of whether the probe is deployed or not.
Wiring for the BLTouch is also commonly a problem since it has its own short leads with DuPont connectors and there are 5 wires. Lots of crimps and lots of ways to get wires crossed. Couple that with multiple valid ways to connect it and different configuration options needed for each way.
Oh and there are a bunch of clones and versions which help to confuse the situation even further.
Glad you got it working in the end. It is a good probe once it's working.
I'm making progress, had to reconfigure the firmware from scratch and re-upload. I still have a lot of settings to tweak and an additional axis to wire up and get working, but I do have one nozzle printing now
@taconite said in Fan Control, no Ground for Fans:
Why is the PWM done with ground and not V_FAN?
Because it's easier. All 3D printer control boards do it this way.
You can use a common positive wire for all the fans and also for the hot end heater, as long as they are all the same voltage.
Shorting fan pins blows the mosfet, and may also blow the 1A fuse (on Duet revision 1.03 or later) or the trace linking VIN to the VIN side of the fan voltage jumper selector block. If the fan still works when you plug it into one of the always-on outputs, then only the mosfet is blown.
There is a wiki page giving spare part numbers.
Jumpering the grounds will partially defeat the short-to-VIN protection on the thermistor inputs, and will also reduce the thermistor reading accuracy. I suggest you don't jumper the grounds, and accept that the reading of the PINDA thermistor will be a little less accurate than the other thermistor readings.
@steve-lynch said in Using E1 to run second Y Stepper?:
@dc42 said in Using E1 to run second Y Stepper?:
M584 X0 Y1:4 Z2 E3
Just to follow up.... I found my main issue... I didn't realize that Dual Y motors had to rotate in different directions.... Just never dawned on me.... The 2 motors were fighting each other! They were previously spliced together in parallell, so once I split them I needed to flip the wires around again.
Thanks for all the assistance!
No need to rewire, you can change the motor direction on individual drivers using the M569 command.
So I measured the voltage again. I plugged a connector with 2 cables at the fan1 pins and connected this to a multimeter.
If I measure between VFAN and FAN1- I see 7.6V when the fan is at 0% on the web control and 12V when the fan is at 100%.
@ov_darkness said in Problems with adapting Duet to 3D Kreator Motion 3D printer:
@dc42 no, it was edited by me.
I have M557 defined in Config.g
If you already have a M557 command in config.g and you are getting the "No valid grid defined" message, then that M557 command failed. Try sending exactly the same M557 command from the GCode Console to see what the error is.