Trouble with the Duet 2 on a Monoprice Maker Ultimate
-
@thejmather said in Trouble with the Duet 2 on a Monoprice Maker Ultimate:
; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
It looks like you're missing a hotend heatsink fan, which would normally be on fan1.
-
@Phaedrux said in Trouble with the Duet 2 on a Monoprice Maker Ultimate:
https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+4:+Calibration/40#s161
Cool - I wasn't sure if that still applied when using the "bang-bang" control method.
-
@thejmather Bang-bang isn't recommended at all. Once the heaters are tuned with M303, you can send M500 to save the results to config-override.g. Your config.g already has M501 at the end to load them at boot.
-
@Phaedrux said in Trouble with the Duet 2 on a Monoprice Maker Ultimate:
@thejmather said in Trouble with the Duet 2 on a Monoprice Maker Ultimate:
; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
It looks like you're missing a hotend heatsink fan, which would normally be on fan1.
I'm lazy and have it plugged into one of the always-on fan spots.
I've read that I can hook up the built-in LED lights to one of the PWM fan connections too... might give that a try.
-
@Phaedrux said in Trouble with the Duet 2 on a Monoprice Maker Ultimate:
@thejmather Bang-bang isn't recommended at all. Once the heaters are tuned with M303, you can send M500 to save the results to config-override.g. Your config.g already has M501 at the end to load them at boot.
Ah, good to know bang-bang isn't recommended. I'll get the pid tuning done in a jiffy here...
-
Fan2 would be a good candidate for LEDs. Fan1 is intended for the hotend because it will power on automatically briefly at power up in case the hotend was hot during a reboot.
You'd need this in your config to add a thermostatically controlled fan for the hotend.
; Fans M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on when hotend is 45cFor fan 2 and the leds it would be the same as your fan0, except F2 and P2
; Fans M950 F2 C"fan2" Q500 ; create fan 2 on pin fan1 and set its frequency M106 P2 S1 H-1 ; set fan 2 for LED controlled by slider. on by default.The Q value is the PID frequency and you can adjust it needed for fans or LEDs. Different fans and leds will work differently sometimes.
-
@Phaedrux said in Trouble with the Duet 2 on a Monoprice Maker Ultimate:
Fan2 would be a good candidate for LEDs. Fan1 is intended for the hotend because it will power on automatically briefly at power up in case the hotend was hot during a reboot.
You'd need this in your config to add a thermostatically controlled fan for the hotend.
; Fans M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on when hotend is 45cAwesome, after I'm pid-tuned I'll put the patient back on the operating table and flip things around a bit.
-
@Phaedrux Thank you so much for the tips. The 500 seems to be working good for the fans I have in place at the moment, but I could totally see the LEDs being more fickle, and it's great to know what lever to start with.
-
https://duet3d.dozuki.com/Wiki/Connecting_and_configuring_fans
You're well on your way now that you have the right firmware and config paired.
When in doubt there's the gcode wiki. https://duet3d.dozuki.com/Wiki/Gcode
-
@Phaedrux said in Trouble with the Duet 2 on a Monoprice Maker Ultimate:
https://duet3d.dozuki.com/Wiki/Connecting_and_configuring_fans
You're well on your way now that you have the right firmware and config paired.
When in doubt there's the gcode wiki. https://duet3d.dozuki.com/Wiki/Gcode
I'll be curious to see what the calibration cube looks like once this is all set.
The one on the v2 firmware looked pretty good, aside from some weirdness around the edge corners of the X, even after doing an extruder calibration.
Any recommendation on the best balance for auto bed leveling? Is there a such thing as "too many points of data" if I'm willing to wait for it to take tons of measurements?
On the Wanhao controller, there was only enough memory (or something) for Marlin to handle 9 points of data, but it seemed to still work fairly well.
This printer was a super cheap open-box-special, and I'm fairly certain it was open box because whoever got it realized the bed was ... we'll say "special".
-
My lovely build bed, btw... lol...
-
That PID calibration guide I linked also goes into extruder calibration so check that part out too.
That bed map could indicate a sagging X gantry as well.
You can use up to 441 points and save the results. So as long as your bed is fairly stable you can do it once and then load it before the print in the slicer start gcode with G29 S1.
-
@Phaedrux said in Trouble with the Duet 2 on a Monoprice Maker Ultimate:
G29 S1
So without the G29 S1 in the print start code it doesn't use any bed leveling?
That could explain some of the other issues I've been having trying to use more of the build bed...
-
If you run G29 and create a map it will save it and apply it right then and there but it won't persist across power cycles or if given a command to disable it. G29 S1 loads a previously saved heightmap.
-
@Phaedrux Duly noted. Added to the slicer's pre-print gcode.
Latest print seems to be coming out fine.
Next up is the controller mount for the Duet 2...
Thanks to everyone for all the help!
