Issues with my Duet Maestro or bad config?
-
This is the correct info for a E3D V6
M308 S1 P"temp1" Y"thermistor" A"E0 E3D v6" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin temp1Follow my adventures in 3D Printing, laser cutting and electronics. https://linktr.ee/Rushmere3D
-
@Rushmere3D Yes thanks i looked it up
just running a PID tune on the heater again now then going to try the benchy again. Fingers crossed thats all it was -
Unfortunately those changes have done very little to resolve the issue.
As you can see its pretty much the same as before. The new one is on top.
-
Hi, can you post the text from you're current config.g into the code function ( </> ).
And also what slicer are you using, what temps, speeds are you using? and maybe also upload the .gcode file of the benchy for us to look at.
Thanks.
-
Sure I have pasted the current config.g below and tidied it up a bit. I am 100% certain it is not slicing, filament, temps or speeds though. As stated at the start this has produced the exact same error on two completely different printers with no common parts other than the Duet, both a cartesian and coreXY, multiple filaments and across multiple slicers and did not happen with those same slicer settings and filaments before the Duet was added to either machine. I have had both of the machine producing good quality prints before the duet was added and have been 3d printing for years now so i have a good grasp of slicers, filaments and temps. Which is why this can only be either an error with the Duet its self or an error with my config on the Duet everything else has been proven working.
; Configuration file for Duet Maestro (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.2.2 on Sat Feb 06 2021 16:48:07 GMT+0000 (Greenwich Mean Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Sapphire Plus" ; set printer name M669 K1 ; select CoreXY mode ; Network M551 P"*(removed for forum)*" ; set password M552 P192.168.2.12 S1 ; enable network and set IP address M553 P255.255.255.0 ; set netmask M554 P192.168.2.1 ; set gateway M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S0 H100 v100 ; physical drive 0 goes forwards M569 P1 S1 H100 v100 ; physical drive 1 goes forwards M569 P2 S1 H100 v100 ; physical drive 2 goes forwards M569 P3 S0 H100 V100 ; physical drive 3 goes forwards M584 X0 Y1 Z2:4 E3 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z400.00 E408.00 ; set steps per mm M566 X600 Y600 Z60.00 E420.00 ; set maximum instantaneous speed changes (mm/min) M203 X18000.00 Y18000.00 Z360.00 E1500.00 ; set maximum speeds (mm/min) M201 X2000.00 Y2000.00 Z300.00 E10000.00 ; set accelerations (mm/s^2) M906 X1200 Y1200 Z1200 E1200 I30 ; 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 X300 Y300 Z350 S0 ; set axis maxima ; Endstops M574 X1 S1 P"!xstop" ; configure active-low endstop for low end on X via pin xstop M574 Y2 S1 P"!ystop" ; configure active-low endstop for low end on Y via pin ystop M574 Z1 S1 P"!zstop+!e1stop" ; configure active-low endstop for low end on Z via pin zstop and e1stop ; Z-Probe M950 S0 C"zprobe.mod" ; 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 X0 Y-42.8 Z1.24 ; set Z probe trigger value, offset and trigger height M557 X50:250 Y50:250 S50 ; 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 R0.175 C745.8 D3.56 S1.00 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 C0.0000000706 ; 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 R1.941 C309.177:309.177 D6.72 S1.00 B0 ;Set PID values for heater 1 M143 H1 S280 ; set temperature limit for heater 1 to 280C ; Fans M950 F0 C"fan0" ; create fan 0 on pin fan0 and set its frequency M106 P0 S1.0 H1 T45 ; set fan 0 value. Thermostatic control is turned on M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency M106 P1 S0 H-1 ; set fan 1 value. Thermostatic control is turned off M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency M106 P2 S0 H-1 ; set fan 2 value. Thermostatic control is turned off ; Tools M563 P0 S"Hot End" D0 H1 F1:2 ; 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 -
@jbirley said in Issues with my Duet Maestro or bad config?:
M569 P0 S0 H100 v100 ; physical drive 0 goes forwards
M569 P1 S1 H100 v100 ; physical drive 1 goes forwards
M569 P2 S1 H100 v100 ; physical drive 2 goes forwards
M569 P3 S0 H100 V100 ; physical drive 3 goes forwards
M584 X0 Y1 Z2:4 E3 ; set drive mapping
you forgot drive 4.
also do not enable stealthchop on the extruder.also the hybrid switching gets more problematic at higher speeds
and i dont think the H parameter is supported on the tmc2224
try this
M569 P0 V10 ; Stealthchop2 till about 150 mm/sec
M569 P1 V10 ; Stealthchop2 till about 150 mm/sec
M569 P2 V10 ; Stealthchop2 till about 150 mm/sec
M569 P3 D2 ; Extruder in Spreadcyle
M569 P4 V10 ; Stealthchop2 till about 150 mm/sec -
@Veti Cheers, I will try that, I did not notice I forgot to add drive 4 when I setup the independent Z motors and I will disable stealthchop on the extruder and give it a go. I don't see how changing the V param to increase the speed and which is changes to speadcycle is going to help though? unless I'm missing something which is entirely possible.
-
the switching to spreadcycle at higher speed can cause problem. even layer shifts.
so its best to either leave the default very low switchover or use a high one that does not cause a switchover -
Thanks all for the help so far, the last changes got me some progress, not perfect but enough to give me hope that all is not lost
top picture is the most recent print in both images, exact same gcode file.
banding has definitely gone down and the surfaces are much improved, its is still by no means what I would consider good though.
-
@jbirley I have to ask... is this a genuine Duet3D Maestro, or a clone board? I’ve seen people have issues with clone boards. Also, can you post the (presumably) Marlin config the printer had before. What version of RRF? Send M115 and post response. Have you tried the default stealthchop/spreadcycle settings, ie remove M569 H and V parameters? Having the change at high speed will produce an audible clunk, and as @Veti points out, a loss of position. I don’t think I’ve ever needed to mess with the default setting on a Maestro.
Ian
Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth
-
@droftarts Hi, yes genuine Duet Maestro board bought through ooznest UK, genuine v6 hotend (copper block, titanium heatbreak, 0.4mm nozzle X). Printer ships with a makerbase robin nano which was running what i believe to be a modified version of Marlin but I don't have a copy of it. Running latest version of firmware (m115 output: FIRMWARE_NAME: RepRapFirmware for Duet 2 Maestro FIRMWARE_VERSION: 3.2 ELECTRONICS: Duet Maestro 1.0 FIRMWARE_DATE: 2021-01-05) but also had the same issues when running RRF2.
I have tried the defaults straight out of the config tool with regards to stealthchop. However its a corexy with linear rails and a V6 on a bowden, its moving very little weight around so there is no reason that it should not be able to cope in stealthchop at the 60mm/s i'm printing at and since the printer is about 1m from my desk it needs be as quiet as possible which is why i bought the duet.
I have had this board on two machines now with no common components across them other than the duet, they both printed fine without it but produce the same artefacts with it, so that rules out any mechanical issues. So that leaves me with electronics, config, or slicing i guess. Starting to pull my hair out now.
-
I have just forced all the motors to spreadcycle and trying a test print now.
-
@jbirley have you checked what the accel/speed/jerk settings were on either of the Marlin boards to compare? Just plug the boards in via USB and use YAT to see what they report to M205 etc. Would at least let you compare apples to apples!
-
@droftarts That is a good shout i will do that
-
Unfortunately forcing the motors to spreadcycle did very little.
The cube on the right was printed with stealthchop, the cube on the left with the motors set to spreadcycle with M569 D2. Both printed at 40mm/s including travels.
-
@droftarts previous settings were:
Accel : 1000mm/s XY 100mm/s Z
Speeds: 200mm/s XY 4mm/s Z
Jerk: 15mm/s XY 0.4mm/s Z and 5mm/s Econverting them into mm/min the values are close enough to what was set already.
-
@jbirley Although I still think the motor current is on the high side, have you tried different filament? All the prints from Duet hardware you've shown are white and the other prints are not. I've had filament cause issues like this, just a thought.
-
@jbirley thanks for the answers, and sorry this is proving difficult to track down. Another option, if you feel there is a flakey driver, is to move the drives onto different drivers eg M584 Z0:1 E2 X3 Y4
If a test print is still the same, it’s not a driver issue.Can you also send M569 P# (where # is the driver number) with no additional parameters to see the current driver settings.
I also assume you are resetting after each change to config.g to ensure the new settings are being used?
Finally, try setting/changing the jerk policy; set P1 in your M566 command for Marlin-like jerk.
Ian
-
@Rushmere3D I left the motor current high on purpose, they are 1.7A motors so 1200ma is roughly 70% of max current. I was under the impression the only downside to running high current was extra heat and wear on the motor provided you are within the limits of the board and motors. since there was a possibility it was missing steps i left them high to remove it as a factor, i have tried them at 800 / 900 and 1000ma also though with no improvement. once i have it sorted it will start dropping them to see at what point it misses steps for long term printing though. I will change the spool for the next test just in case but i have had this behaviour with other spools so did not see much point in changing filaments for each test, again trying to keep the amount of variables down.
@droftarts M569 P1 returns
Drive 1 runs forwards, active low enable, timing fast, mode spreadCycle, ccr 0x00053, toff 3, tblank 0, hstart/hend/hdec 5/0/0, pos 680i have left them in spreadcycle for now, again just to remove as many variables as possible.
I will move the motors around and give that a go
and yes i have been resetting after each change.
-
Adding P1 to the M566 command seems to have provided some improvement. The far right is the before, middle is M566 P1, the green one is exactly the same just a different brand and colour of PLA.
It is not as obvious on the picture but in person there is a definite improvement
