Topics created by sunToxx

I felt like I had the same issue. I have a mesh of 23x19 points, always taken after at least an hour of heat soak in. I do this for each one is my removable print plates.

I have an extremely flat build surface underneath and I even go so far as to manually probe the bed at randomly chosen probe points to validate the mesh.

The tested points always nearly exactly match the saved mesh.

But when I print, there is always one area, on each of my 6 different plates that acts like a low spot.

All I could think of was that my kinematics were out of whack somewhere so the reasonably large offset between the probe and my tool must be revealing that.

Maybe you have the same issue? I have a tool changer, that's why my probe is so far away.

BTW, I fixed it by squaring my frame, checking all along the lengths of the body and added braces where they were the wrong distance apart.

Can I use the Echo command (https://docs.duet3d.com/en/User_manual/Reference/Gcode_meta_commands) in one of the files of the filaments section, in order to have it automatically create/overwrite a macro, according to the currently used filament? (the macro should have same name for all filaments, but then only contains the temperature for the currently selected filament).

So that i can call this macro with M98 custom gcode in the slicer and it would always set the other layer temperature to the one i define in the filaments section of dwc? Would config.g or load.g make the most sense to have it create that macro?

Also, is calling for M703 in start.g enough, or does it have to be included into the slicer start code too, in order so noting overrides it?

Edit: echo >"test.g" "M104 S210" does not seem to work

@dc42 said in Makro with variables:

Use the R0 parameter in the M290 command to set absolute instead of relative babystepping.

I already printed with half the value, but this is much better and makes it perfect, thanks! 😎

Thanks for the help @everyone, this is exactly what I have been looking for!

Could someone maybe post the code of a well filled filament config.g so i can look at it? I am specifically wondering how to set first layer and other layers temperature in a way that all slicers understand, as they seem to utilize differently named variables. That's already more than I aimed for, but I like the idea of having all my filament configuration in one place on the printer, a lot.

@fcwilt said in Strange Z error:

I honestly don't know. The biggest factor I found for first layer adhesion has been speed.

In which way? I experienced, that a keychain i did in various sizes and with different layer thickness and nozzles, started to warp very easily, when using the .25 nozzle and a certain size and thickness. The smallest version printed fine, the 20% bigger version, started to warp, despite strong layer adhesion. Not sure if it is the longer print time that caused it, or maybe the number of layers and the way they cool down being that thin. Maybe they are just super prone to moving air, when the layers are that thin (was .12mm layers).

What speed to you use? By now I always left it at the default 20mms. I only once had layer adhesion problems that were not z offset related, and solved them by increasing bed and nozzle temp beyond the temperatures recommended by the manufacturer. (was Fillamentum Vertigo Space and used 235° 70°C, then even fine outlines would stick).

If I was going to implement a temperature change feature it would involve using the slicer feature that allows invoking custom code on each layer change. It would be easy to have the filament specific config.g file set some global variables holding different temperatures and layer counts. Then the layer change custom code would use those values to determine what temperature to be using for the current layer.

I am going to try that just to see what sort of effect changing bed temp might have.

Setting variables would be probably much cleaner. I was thinking of using the echo command to create for example an "Additional-Filamentsettings.g" makro and add a sort of "if layer>1 then execute Additional-Filamentsettings.g" in the layer change custom code.

So I would just have to copy and paste that echo section into each filament config.g and simply set the desired values there and every time I use DWC or M701 to change the type of filament, the echo command would overwrite the Additional-Filamentsettings.g with the current values.

@fcwilt thanks for the response! It seems the print that failed before the problem appeared, left a small blob of filament on the tip of the nozzle and that interfered with the BLToch, because the BLTouch had moved up a tiny bit.

@jay_s_uk yes, those 2 are in the config.g. Something like
G31 X-xx.x Y-xx.x

you can't directly edit config.g with a command. Config-override exists to save those sorts of values and it does that by writing out all the values that it can save to a new file each time.

So it's taking the babystep amount and using that number in the G31 Z probe offset to make it permanent because G31 gets saved to config-override.

We're always here to help when you have specific questions.