@aceranic you can easily do this
I use a custom start macro thats called by the slicer
this is that i have in orcaslicer

M98 P"start_print.g" A[bed_temperature_initial_layer_single] B"[filament_type]" C[nozzle_temperature_initial_layer] D[nozzle_diameter]

You could then have, in start_print.g

if param.B = "ABS" G29 S1 P"heightmap50.csv"

and so on.
My example start_print.g is here https://github.com/TeamGloomy/Troodon-V2/blob/improved/Config/sys/start_print.g

@jay_s_uk thanks a lot

M906 X1600 Y1600 Z1200 E1200 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

@ianborg From the heater curve on the graph you posted, it does look like the heater is getting close to the maximum heat it can achieve. Controlling it at this point does get a bit squirrelly, because the heating rate isn't what is expected. Not much you can do about that, apart from what you've already done, unfortunately. Did you tune it at 90C with M303, or lower?

Ian

@micaheli said in Dual Z endstops and G30:

@fcwilt OG is "original gangster". Means old school.

I guess I just have hope that there would be a fancy new way that works better. Guess not. Boo.

I have tried many and they often sound great but end up disappointing.

The BLTouch may be old school but it just works.

Here is how the coil will be mounted (more or less)

NANO print head.jpg

@dc42 said in PID manual tunning help needed:

It's also possible that the PID tune is giving the correct results but the problem is the extra heat needed to melt the filament. If that's the case then configuring heater feedforward may help, if your current heater is capable of supplying enough heat.

I will try both things, Thanks. My bet is that a 1.75 mm filament and a 1.5x0.5 extrusion are hard to do with an old school volcano, but sure it can be tunned a bit....

@Fuzionline said in Scara manual control:

I updated to version 3.6.0 Release Candidate 1, but the M571 command doesn't work. I reverted to Release 3.5.4, and it's working. Thank you.
I have a Duet 2 wifi.

Confirmed, M571 doesn't work in 3.6.0-rc.1 and 3.6 beta versions. It will be fixed in rc2.

If you're going to print more tests, you could make an 8-sided box to enable looking at X-axis, Y-axis, and also each motor separately. You might also make that shape a "stepped pyramid" to be able to see if artifacts are starting at the corner (which might imply something to do with print head acceleration or extrusion speed). Your pictures posted on 16 Fed look like they have a very slight step at the bottom of the part, which gave me this idea.

Other thoughts after looking at the picture of the printer posted on 11 Feb...

Is there anything other than the shaft couplers preventing vertical motion of your Z lead screws? On my printer, I had some issues with z-banding and I switched from couplers like those you are using to the spring kind (which allows more Z movement). Then I put a screw collar (https://www.amazon.com/Shaft-Collar-Aluminum-Thickness-Screws/dp/B0BNZ937MV) on each z-shaft and put a thrust bearing (https://www.amazon.com/uxcell-F8-16M-Miniature-Bearings-8x16x5mm/dp/B07QLTXJDH) between that the the top of the lower bearing. Finally, I designed a spring loaded thing to put above the top of the shaft and keep a downward force on it. That cleaned up my z-banding.

On another printer, I had an issue where the threaded z shafts were not perfectly straight and they were moving the cars on the Z tracks slightly (again, z-banding). On this printer, I added oldham couplings (https://www.amazon.com/2-Pack-Coupling-Couplers-Compatible-Printer/dp/B0B17QWTG2) between the lead screw nut and the bed supports. It looks like you've maybe got something equivalent there. If so, these would isolate shaft wobble., but you might look for anything else that might be applying a force to the bed supports or the bed itself. It looks like there's a cable that may be tie-wrapped to the rear 2020 bed support. Better to tie wrap that the the lead-screw nut below the wobble decoupler. Any forces it applies will be isolated by the wobble-decoupler. The wiring from there to the bed would them have constant forces.

I think I might also be seeing a spring for a bed leveler on the right front corner (hard to tell for sure in the picture. If there isn't a hard connection for leveling (meaning the spring is holding it in place), that's another possible place for movement to happen if there are small irregular forces on the bed assembly.

Another thing to thing about is how rigid the print head is on the slider on the bridge. If there is any "play" in the slider, then the cables going to the print head might be wiggling the print head. If the extruder is "far" from the slider, it will amplify tiny movements.

@fcwilt I didn't understand now I understand perfectly thanks. you have the sailing canoe and pedals, beautiful

@fcwilt It worked. Thank you so much!!

@dc42

Yes, i run them at 48V!

This is X axis print speed:
X-Print.png
(X-Print)51_2025-03-18_13.50.50.csv

Y axis print speed:
Y-Print.png
(Y-Print)50_2025-03-18_13.51.00.csv

X axis travel speed:
X-Travel.png
(X-Travel)51_2025-03-18_13.51.10.csv

Y axis travel speed:
Y-Travel.png
(Y-Travel)50_2025-03-18_13.51.14.csv

This is in open loop:
X-Print(spreadcycle).png X-Travel(spreadcycle).png

@dc42 will try it later, thanks

After extensive testing, I concluded that something was distorting my sensor reading. Since I had two SameSky CUI AMT10E3 capacitive encoders.
WhatsApp Image 2025-03-14 at 20.22.22.jpeg

I set them to 2500PPR and mounted them. Now closed loop runs whisper quiet. Here are two examples:

stealthchop.mp4
closed loop.mp4

@kazolar said in Odd bed mesh:

Wondering if there are plans to true zero like beacon/cartographer do to auto calibrate my understanding all they're doing is measure variations in eddy currents until they stop changing meaning nozzle touched the bed.

From the 3.6.0-beta.3 release notes:

[Duet 3] Experimental support for using supported scanning inductive Z probes (i.e. Duet3D Scanning Z Probe and TOOL1RR tool board) in touch mode is available. This support is enabled using the new M558.3 command. See https://docs.duet3d.com/en/User_manual/Tuning/scanning_z_probe_calibration#using-the-szp-in-touch-mode-to-set-z-height. Use it with caution!