Trouble with the Duet 2 on a Monoprice Maker Ultimate

Phaedrux

How are you switching between rrf2 and rrf3?

thejmather

@Phaedrux said in Trouble with the Duet 2 on a Monoprice Maker Ultimate:

How are you switching between rrf2 and rrf3?

This is the million dollar question... for some reason, I had thought that just uploading the config zip file was enough.

Your last comment lead me to check my assumptions, and yeah, it's still running 2.x...

I'm trying to upload the bin via the web control panel now... I've managed to get web control panel to report that it's 3.x but diagnostics is still saying reprap is 2.05.1...

Do I have to do a hard power cycle maybe?

Phaedrux

Ah, ok, then. That answers that.

Here's how you should proceed with the updates.

First make sure you're running 2.05.1, and it sounds like you are, but just to make sure you have all the files needed here's how you do a complete firmware update. It just involves uploading a single zip file for each version to the sys folder via the web interface.

Start with the 2.05.1 zip file. Then upload the 3.0 zip file. Then 3.1.1. It'll reboot between each. Then you can upload your config zip file if you haven't already.

Upload the whole zip file. don't extract it.

https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip

https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/Duet2and3Firmware-3.0.zip

https://github.com/Duet3D/RepRapFirmware/releases/download/3.1.1/Duet2and3Firmware-3.1.1.zip

thejmather

@Phaedrux said in Trouble with the Duet 2 on a Monoprice Maker Ultimate:

Ah, ok, then. That answers that.

Here's how you should proceed with the updates.

First make sure you're running 2.05.1, and it sounds like you are, but just to make sure you have all the files needed here's how you do a complete firmware update. It just involves uploading a single zip file for each version to the sys folder via the web interface.

Start with the 2.05.1 zip file. Then upload the 3.0 zip file. Then 3.1.1. It'll reboot between each. Then you can upload your config zip file if you haven't already.

Upload the whole zip file. don't extract it.

https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip

https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/Duet2and3Firmware-3.0.zip

https://github.com/Duet3D/RepRapFirmware/releases/download/3.1.1/Duet2and3Firmware-3.1.1.zip

Alright! This seems to be working a lot better. It got to 3.0.0 successfully, though it's been spinning for quite a while on 3.1.1.

The temp sensors were working though.

Still just waiting on it to come back up after the 3.1.1 upgrade though. Might have to go a more manual route for this one since it seems to not be coming back up...

A Former User

@thejmather said in Trouble with the Duet 2 on a Monoprice Maker Ultimate:

though it's been spinning for quite a while on 3.1.1.

should take less than a minute; reset and try again if it takes longer.

thejmather

@bearer Yep, it just needed the ol' "turn it off and then on again" treatment. Let's see where I'm at functionality wise with 3.1.1 now that I'm not trying to run a v3 config on v2 firmware LOL...

thejmather

Neat! It mostly seems to be working. Endstops are good. BLTouch is good.

I was warming things up to do a bed probe though, and got:

Error: Heater 0 fault: temperature rising much more slowly than the expected 1.7°C/sec

I don't see much for options in the config editor to counter this, though...

Config:

; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Fri Oct 09 2020 21:30:59 GMT-0400 (Eastern Daylight Time)

; General preferences
G90                                                    ; send absolute coordinates...
M83                                                    ; ...but relative extruder moves
M550 P"MPUltimate"                                     ; set printer name

; Network
M552 S1                                                ; enable network
M586 P0 S1                                             ; enable HTTP
M586 P1 S0                                             ; disable FTP
M586 P2 S1                                             ; enable Telnet

; Drives
M569 P0 S0                                             ; physical drive 0 goes backwards
M569 P1 S1                                             ; physical drive 1 goes forwards
M569 P2 S0                                             ; physical drive 2 goes backwards
M569 P3 S1                                             ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3                                       ; set drive mapping
M350 X16 Y16 Z16 E16 I1                                ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z800.00 E94.30                       ; set steps per mm
M566 X600.00 Y600.00 Z24.00 E60.00                     ; set maximum instantaneous speed changes (mm/min)
M203 X7200.00 Y7200.00 Z300.00 E300.00                 ; set maximum speeds (mm/min)
M201 X800.00 Y800.00 Z100.00 E500.00                   ; set accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 E1000 I50                       ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                                ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1                                       ; set axis minima
M208 X200 Y200 Z175 S0                                 ; set axis maxima

; Endstops
M574 X1 S1 P"!^xstop"                                  ; configure active-high endstop for low end on X via pin !^xstop
M574 Y1 S1 P"!^ystop"                                  ; configure active-high endstop for low end on Y via pin !^ystop
M574 Z1 S2                                             ; configure Z-probe endstop for low end on Z

; Z-Probe
M950 S0 C"exp.heater3"                                 ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F120 T6000                    ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X31 Y-20 Z1                                   ; set Z probe trigger value, offset and trigger height
M557 X31:200 Y0:180 S10                                ; define mesh grid

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138         ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0                                  ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B1 S1.00                                       ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0                                                ; map heated bed to heater 0
M143 H0 S120                                           ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1                                   ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00                                       ; disable bang-bang mode for heater  and set PWM limit

; 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

; Tools
M563 P0 D0 H1 F0                                       ; define tool 0
G10 P0 X0 Y0 Z0                                        ; set tool 0 axis offsets
G10 P0 R0 S0                                           ; set initial tool 0 active and standby temperatures to 0C

; Custom settings are not defined

; Miscellaneous
M501                                                   ; load saved parameters from non-volatile memory
T0                                                     ; select first tool

Phaedrux

@thejmather said in Trouble with the Duet 2 on a Monoprice Maker Ultimate:

Error: Heater 0 fault: temperature rising much more slowly than the expected 1.7°C/sec

You'll need to PID tune your heaters.

Info: https://duet3d.dozuki.com/Wiki/Tuning_the_heater_temperature_control
Guide: https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+4:+Calibration/40#s161

Phaedrux

@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.

thejmather

@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.

Phaedrux

@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.

thejmather

@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.

thejmather

@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...

Phaedrux

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 45c

For 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.

thejmather

@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 45c

Awesome, after I'm pid-tuned I'll put the patient back on the operating table and flip things around a bit.

thejmather

@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.

Phaedrux

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

thejmather

@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".

thejmather

My lovely build bed, btw... lol...
My lovely build bed...
another shot...

Phaedrux

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.