@claustro I think the image of the calibration pattern is rotated 90°. Assuming that is correct then the Y calibration is the line on the left and the X calibration is the line on the bottom.

It looks like there is pretty much no resonant frequency in the range 0Hz to 90Hz for Y and the X resonant frequency is about 4/5 of the way along the line at just over 70Hz.

Important question: was input shaping disabled when you ran the test?

@moth4017 So it seems that your woes were all due to the fact that you had an under powered heater. For sure, changing it should give a steeper rate if heating and alow PID tuning to work.

@claustro
Do you use retract ? Please posr the settings. Is it a direct drive or bowden?

@Firefly It applies it to both. See https://docs.duet3d.com/en/User_manual/Tuning/Input_shaping#why-we-dont-support-different-shaping-for-the-x-and-y-axes

Ian

The trigger time on a BLtouch is very short and then resets. The DWC display might not always refresh at the right time to catch it.

@droftarts, @fcwilt

guys really thanks. Can i offer u guys a coffee?

See you!

thanks again!!! 🙂

@Phaedrux instead of toothed idlers I have placed a bearing stack like in the RatRig (I assume those bearings will last longer).

Motors are not very smooth while turning by hand, motech motors nema23 on X axis and nema17 on Y.

@mrehorstdmd Thank you for your answer.

I made another test at the same speed with a triple-layer perimeter circular pattern.
My setup is a Revo Six hot end with a Titan extruder driven by a slightly underpowered Nema motor than the one suggested by E3D for Titan.

The pulleys and belts are okay, and the hot end attachment seems rock solid. My concern lies with the mini V wheels or the wheel bearings, which could deteriorate over time. I am searching for a reliable European seller to buy good-quality V wheels.

This is the result of the print at 130 mm/s. During the print, I could hear a rhythmic noise pattern coming from the Y-axis. This is the reason I am considering a wheel problem.

Immagine WhatsApp 2024-01-25 ore 08.40.18_8390771b.jpg

Is TAMV still working?

this is very odd

i flashed firmware 3.4.6 and dwc 3.4.6 and the www files that match

now it homes perfect

did not touch the config

@DocTrucker To elaborate a bit more, in Prusa Slicer, in the custom code section for filaments I have just one macro call - e.g M98 P"prePrintAbs". That macro sets things like retraction, pressure advance, speeds, etc and it resides in the .sys folder. So each machine has it's own .sys folder and therefore it's own "prePrintAbs" macro. So any gcode file becomes machine agnostic and by editing the single macro call at the beginning of the file it becomes filament agnostic too.

@rex_sl From the release notes, the M593 L factor is described as:

... the minimum fraction of the original acceleration or feed rate to which the acceleration or feed rate may be reduced in order to apply input shaping. The default is 0.25 and the acceptable range is 0.01 to 1.0.

ie if the commanded feedrate is F1000, L0.25 would allow the feedrate to reduce to F250, while L0.75 would only allow it to reduce to F750. So the least amount of reduction of acceleration or feed rate is from the highest L value.

I have updated the M593 Gcode dictionary entry to show this has changed in RRF 3.5.0-rc.2.

Ian

@dc42 when I when to use the printer again, I saw the message "Input Shaping is not configured. Record a new Motion Profile to set it up" seems I lost it, it happened before and I thought I deleted it by accident, but not this time. printer was off for awhile and don't see how to recall the last motion profile. I already removed the input shaping sensor, but if I do this again what is the proper way to save and make it stay?

@dc42 Hello ! I found the place in gcode.cpp where i could add a G11 or a G1 E10 at the end of ressurect.g . Not sure I want to go down the path of compiling a custom firmware though, but:
Would this work ? : adding

// Now unretract filament buf.catf("G11");

after

// Now move down to the correct Z height buf.catf("\nG0 F6000 Z%.3f\n", (double)pauseRestorePoint.moveCoords[Z_AXIS]);

in

if (ok) { // Build the commands to restore the head position. These assume that we are working in mm. // Start with a vertical move to 2mm above the final Z position buf.printf("G0 F6000 Z%.3f\n", (double)(pauseRestorePoint.moveCoords[Z_AXIS] + 2.0)); // Now set all the other axes buf.cat("G0 F6000"); for (size_t axis = 0; axis < numVisibleAxes; ++axis) { if (axis != Z_AXIS) { buf.catf(" %c%.3f", axisLetters[axis], (double)pauseRestorePoint.moveCoords[axis]); } } // Now move down to the correct Z height buf.catf("\nG0 F6000 Z%.3f\n", (double)pauseRestorePoint.moveCoords[Z_AXIS]); // Set the feed rate buf.catf("G1 F%.1f", (double)InverseConvertSpeedToMmPerMin(pauseRestorePoint.feedRate));

@Manuel207 said in Printing ovals instead of circles:

@deckingman I tested a 400mm move and it is nearly perfect (maybe 0,2-0,3mm if even measurable?).

I also printed the same part with the second tool and voila perfect circles. So you are on the right path. It has probably something to do with the external driver. I am going to test different microstep settings and currents on the external driver? Do you have other suggestions what it could cause?

Well at least that's narrowed it down to the external driver. Sorry I have zero experience of external drivers so can't offer any other advice. Maybe someone more knowledgable than me about these things will step in.

@deckingman I'm going to close this post and start a new one, I think I've mischaracterized some things and would like a fresh start on the convo

@Tobi_innit your max speeds in M203 are 100mm/s so you won't print any faster than that

Are you going to print airplane wings with this LW PLA? If yes, even and stable extrusion factor is important, I.e. you should look into vase mode. Recent Prusa Slicer has updated their vase mode to match the spiralize outer contour algorithm of Cura which should help with keeping extrusion more equal... and as always, printing slower will also help.