Posts made by tas

@dc42
Duet2Wifi print completed after 1 hour 46 minutes without issues.
Thanks for the fix.

@dc42 Testing 3.6.0-alpha.5 on my Duet2Wifi Ender 5 Plus using the same gcode that failed before. Also using DWC 3.6.0-alpha.2+1.

Just passed 40 minutes with no issues.

@dc42 Duet 2 Wifi on an Ender 5 plus stopped with the code 3 error. Your 38 minute mark sounds about right but I don't have an exact time when it stopped.

I installed 3.5.3 rc1 and ran the same gcode without issues.

@vbtalent2
The outer rings are looking much better. Measure them with a micrometer so there is no guesswork going on. Be careful to avoid any bumps so you don't get a false reading.

If you set 0.2mm as your first layer in the slicer then your printer should be putting down a 0.2mm first layer. That is the ideal situation you are aiming for.

@vbtalent2
Something still not quite right with the layer height. It looks too thick to me but if it is still too far away from the bed then you are extruding too much.

If Cura is not set right as far as filament diameter goes I recommend moving to PrusaSlicer. I think that would be a better beginner slicer.

I use multiple nozzle sizes on my printers but I always set the first layer to 0.2mm no matter what layer height I use for the print.

If your layer height is 0.2mm then 0.02mm would be a reasonable baby step height.

Don't worry about artifacts until you get the first layer right.

@vbtalent2 Please check that the thickness of the paper is what you expect. Due to post apocalyptic skimpflation all papers I have measured are significantly thinner than they used to be. HP premium was 0.2mm but not anymore.

Having written that it looks like your nozzle is too far from the bed not too close. Recheck the nozzle height for the first layer.

Make sure the part cooling fan is completely off for the first layer too.

@carlinicompetizione

I am wondering if commas and decimals are interchangeable in config.g.

Your M566 uses commas and the rest use decimals.

@carlinicompetizione said in Problems from the second layer to the 7th layer:

M566 X500,00 Y500,00 Z300,00 E1200,00 ; definir alterações instantâneas máximas de velocidade (mm/min)
M203 X3000.00 Y3000.00 Z1000.00 E1200.00 ; definir velocidades máximas (mm/min)
M201 X500.00 Y500.00 Z250.00 E1200.00 ; definir acelerações (mm/s^2)

@Arminas These look like Very Fine Artifacts (VFA's). That is the magic name to search for in the forum.

Lots of work has been done on this. Personally I think it is the steppers. I have Creality printers with Duet2Wifi controllers powered by Meanwell power supplies.

I changed every single component but the frames trying to solve this. I changed pulleys, belts, bearings, wheels and wheel bearings. Changed all multiple times with no effect. All are Gates or OpenBuilds now. I changed hotends several times and extruders as well with no real change noticed. Now using Bondtech LGX Pro Lite with Revo6. Prior to that it was Hemera with Volcano.

After you spend enough money on a problem you start to see very minor improvements in print quality but that may be from looking through tears in my eyes.

I finally changed all steppers for E3D units and the VFAs are completely gone.

I have kept up the Duet firmware and DWC versions to the latest. It is possible that that has had an effect. If so, don't tell me, I don't want to know!

@handyandy said in Fan1 Stuck on!:

M106 P1 S1 H1 T45 ; Set fan 1 value. Thermostatic control is turned on at 45°C

Set S1 to S0.0?

@patrickwjoyce The amplitude of XY is being shrunken by Z being so far away. Not sure why that is. I haven't seen that before.

Without Z the XY data might be in the normal range.

Sorry but I have no idea how to get rid of Z. Someone else probably will.

@bartekp

PrusaSlicer is telling your printer to move farther than the bed limits in your config file. That is why the back end of your print is cut off.

It looks like the bed dimensions shown in PrusaSlicer do not match your actual bed so that has to be fixed.

Your part is centered on the bed in the slicer but not on the actual bed.

I have found these issues are related to the origin in the 'bed shape' for PrusaSlicer but the way to fix it is rather complex.

First set the origin in PrusaSlicer Printer Settings - Size and coordinates - Bed Shape - Set to X:0 Y:0. I know that is not how you are supposed to do it but it is the only way I could get it to work. My X = 0 is actually X = +7mm on the bed but I ignore that.

Measure the total movement of your nozzle from your 0, 0 point to the maximum in X and Y. Set those values as the X and Y Size in Bed Shape - Settings.

On my printer my total X travel is 364mm and Y travel is 387mm.

In config.g M208 (Axis Limits) set these same X and Y values. So for my printer:
M208 X0:364 Y0:387

The final part of the solution is to create a custom bed image to show the actual bed limits.

To do this create an image where one pixel = 1mm. This makes it much easier to draw an image to scale. Draw the image to reflect the actual origin. It should also show any keep out zones. In my case I have a glass sheet with bed clips all around. The clips extend 5mm into the bed.

Here is my bed image as an example (Creality Ender 5+ with LGX Lite Pro and REVOsix):

Load the image in PrusaSlicer Printer Settings - Size and coordinates - Bed Shape - Set - Texture - Load and select your custom bed image.

I used a solid red border to indicate where the clips are. Orange is where I do not like to print as it is too close to the edge of the bed. Notice on the left side there is no red area because the nozzle can not reach far enough to touch the clips so there is no danger of hitting them.

The black/striped area at the front of the bed is where the nozzle can reach but there is no bed under it.

This allows me to place objects on the bed in Prusa Slicer and have them print in those exact locations on the actual bed.

I hope that helps.

@Richard-
40 is the default setting for Shaper Center Frequency I believe. Change that to 83 and try 0.0 as the damping factor.

Your config command would then be
M593 P"mzv" F83.0 S0.0 L0.25

If you are using Pressure Advance recheck that after any change to M593.

@nick9one1 150mm/s is more than fast enough. So that is not solving the problem.

@jens55 has a very good point. I have had to dry filament that was fully sealed with dessicant to get it to behave. I'm not sure how sensitive this LW-PLA is to moisture. When all else fails dry the filament.

If even drying doesn't work you could try wiping after retraction.

@nick9one1 Yes, the extra restart is not a good solution.

Another option might be faster travel.

@nick9one1 If retracting more slowly doesn't work then you could try compensating for the filament that gets pulled out of the nozzle by adding an extra restart amount after each retraction.

@nick9one1 Try retracting slower. That might help.

@dc42 said in Software bundle 3.5.0rc.4 now available:

Duet in standalone mode I have included a release zip for this version. This means that you can simply upload file Duet2and3Firmware-3.5.0-rc.4.zip

Just reporting I have done a fair bit of testing with the latest version on a cartesian printer with Duet2 wifi in standalone mode. I uploaded Duet2and3Firmware-3.5.0-rc.4.zip which installed without issues.

Printing well using both Input Shaping and Pressure Advance. No Wifi issues.

Thank you!

@TrippZ

Make sure you recheck your pressure advance after setting your input shaper. I needed to apply both input shaping and pressure advance to get the best results.

I have a note in my config to retune pressure advance if I change the input shaper from MZV.

@edsped
It may be an SBC issue then. I heard no clunks at all.

@dc42
I did a test 'print' without filament using the Klipper ringing part in vase mode at 100mm/s. I tried none, zvd, zvdd, zvddd and with IS off.

The noise sounded 'silkier' with IS enabled and to my ear is the same no matter which type was used.

I did not hear any clunks, clicks or other unusual noises. The highest value for max steps late was 1. I hope that is the new value you are referring to.

Using a speed of 100mm/s I tried all Input Shapers starting with IS disabled. I did M122 at random times during each 'print' to get the following info.

No IS:
M122 Move:
DMs created 83, segments created 9, maxWait 1020ms, bed compensation in use: none, height map offset 0.000, max steps late 1, ebfmin -0.89, ebfmax 0.98
next step interrupt due in 28 ticks, disabled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0

IS "zvd":
M122 Move:
DMs created 83, segments created 22, maxWait 881ms, bed compensation in use: none, height map offset 0.000, max steps late 1, ebfmin -0.79, ebfmax 0.98
next step interrupt due in 6 ticks, disabled
Moves shaped first try 34, on retry 18, too short 63, wrong shape 4, maybepossible 1

IS "zvdd":
M122 Move:
DMs created 83, segments created 33, maxWait 17471ms, bed compensation in use: none, height map offset 0.000, max steps late 1, ebfmin -0.97, ebfmax 0.99
next step interrupt due in 49 ticks, disabled
Moves shaped first try 73, on retry 25, too short 112, wrong shape 9, maybepossible 0

IS "zvddd":
M122 Move:
DMs created 83, segments created 38, maxWait 2364ms, bed compensation in use: none, height map offset 0.000, max steps late 1, ebfmin -0.95, ebfmax 1.00
next step interrupt due in 12 ticks, disabled
Moves shaped first try 114, on retry 65, too short 189, wrong shape 20, maybepossible 0

Let me know if you need any other info or other tests done and I can do them later today.