Hello, everyone, thank you for the replies.

As my final entry what I have done is place M1 at the end of my End G-Code.

And that does exactly what I need it to do.

Again, thank you for all off your suggestions and help.

One last question. How do I mark this as solved?

In PrusaSlicer, go to Printer Settings, and then custom gcode.
Then add M117 [layer_num] to the After layer change G-code section.

@obiwan2print

Have you tried Increasing the S parameter in your M671 command.

Frederick

@jay_s_uk said in power loss with UPS:

@deckingman I run M669 S1 T1 on my CNC no issue

Good to know - thanks.

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.

@örjane that's not implemented at present, only the existing ability to choose the number of decimal places.

@sinole If you are not getting missed steps on Z then just lower the current and/or set the motor standstill current using M917.

@dc42
M119 gave me this:

M119 Endstops - X: at max stop, Y: not stopped, Z: not stopped, Z probe: not stopped

So I'll check the connections. Just figured it worked since the light is on and responds.

Edit: that was the issue. Crimping these tiny cables and connectors are annoying 🙃
Thanks everyone for your help! I have other issues as well (hotend not heating, hotend fan always on even though it has temperature control), but will make a new thread for those I guess.

@oliof Ok,thanks. Now is clear.....

@rilot I have orbiters 1.5 and 2.0 which have the same ldo36sth201004ahg(xh) steppers; they have the same recommended steps/mm, so the gearbox is the same too. I used the 1.5 with a bowden for a while, then added a 2.0 as a direct drive - using them in tandem off e0 and e1 drivers at 850mA, 24V. I am using 300 jerk (with P1) , 7200 max speed, and 10000 acceleration. They run very smoothly and quietly at up to 250mm/sec with 0.4 nozzle.

@selva_tvi Can you re-upload the sample print (gcode) files? Looks like there is an issue with the original upload.

Questions:

; Axis Limits M208 X-35 Y0 Z0 U0 S1 ; set axis minima M208 X500 Y500 Z500 U516 S0 ; set axis maxima

You have X minimum X=-35, and U maximum of U=516. In your tfree files, you're moving to X=-33 and U=523 respectively. Why not move to the defined min/max in M208?

Can you record a video of the very first tool change (showing the first time T1 moves to the tfree1 position)? Can you upload the tpost files?

@phaedrux Thank you

@adamfilip probably just a typo and should be F

@phaedrux Right now I'm just using M956 to gather csv data. I can see the data as text and in the accelerometer plugin.

(edit) I found the plugin and while setting up the motion profile it stops during the "Please stand by while Motion Profiles are being recorded..." phase for the x axis, I need to cancel it (after waiting awhile) to get back to DWC.

(edit) switching to 8 bits creates data viewable in the gui, so I suppose I am ok now.

@rocaranrai TMC2209 stallguard4 is supported, see the docs for how to tune https://docs.duet3d.com/en/User_manual/Connecting_hardware/Sensors_stall_detection

Please note that not all motors in all configurations can trigger stallguard, and its inherently imprecise (=-2 full steps) so you may want to consider another way to measure whatever it is you want to measure.

Do the fans have a large impact on maintaining a steady temperature? If not, you can tune as a heater rather than tool. If it does have a large impact you can try and aim the fans better and add a silicone sock to help stop the drop. Or you can just set the fan speed manually and tune as a heater and get most of the effect as tuning as a tool.

@dken21 if the scaling you need doesn't change, put it in config.g. If it does vary, you may prefer to put it in start.g instead. I wouldn't put it in the slicer start GCode because then if you modify the printer so that the required scaling changes, you won't be able to use previously-sliced files.

@tratoon said in Z Offset + Babystep Offset:

@fcwilt No I am decreasing the distance

Then that number should display as -0.86 on the DWC.

If that is what it is doing then you still subtract it but subtracting a negative number is the same as adding the absolute value.

So just remember that if you take the actual baby-stepping value without changing the sign then you can always subtract it and get the correct value for the Z Trigger Height.

Frederick.

@virtualbrown said in Heightmap, fill in missing data and interpolation:

@fcwilt this is my M557 line in my config:

M557 X0:200 Y0:200 S10 ; define mesh grid

What will your macro do? Will it interpolate to missing data? Sorry, I’m only a couple weeks into all of this.

It will take the values you enter and set M557 to the best values it can given the limits of the area you can probe.

The code does make an assumption that your M208 command has specified the printable area of the bed. In some printers the M208 min/max values actually are outside the printable area to allow certain movements, such as changing a tool on a multi-tool printer.

Here is a version that allows for that:

Code_to_set_M557.g

As to interpolation I know of no reasonable and accurate way to do that.

There are some systems that have a probe that is in the exact same XY location as the nozzle. These, of course, don't have the issue of not being able to reach all points.

You can "probe" with the nozzle but the results are very unlikely to be accurate, and it would be tedious in the extreme.

Frederick

@phaedrux

Hey ya,

I know it's been a long time, but previous laptop which printer was set on died 😞 Will need to setup this huge printer again on my new PC. Will jump through the hoops and try my best to optimise and tune it to do those big prints again.

I noticed my heatbed died a while ago, not sure if something on the board went as I did smell something toasty.

But yeah, looking to put some time into getting this machine back to life and not pester you too much... Back to square one I guess...