@mikeabuilder

Rather then create a new file to execute a constructed G10 command you can simply have a pre-existing file with G10 command(s) using variables for the values you wish to be able to change.

You set the variables to the desired values and execute the file. Or you could pass the values as parameters to the file.

That persists for the duration of the session. To persist the settings you simply execute M500 P10.

You are obtaining the same result but with the extra code for creating the file each time you wish to change the values.

In either case you have the macro and the file with the G10 command(s) which needs to be executed.

Frederick

@mikeabuilder Thanks!

@3dreamer

Perhaps you should first determine if the current approaches to the problem of uneven bed surface are inadequate for the majority of users.

You may be trying to solve a problem that is mostly theoretical.

If I were tasked with solving this problem I would focus on the possibility of creating a device which would allow measuring nozzle-to-bed distance in real-time and dispense with the whole array of points approach.

Frederick

@jay_s_uk Doh! I'm sorry I missed the last word of your post.

@oliof I've added this to the firmware wishlist.

@fcwilt - I am speaking of code I want to execute via a macro button (thanks for teaching me the proper term). And I was being a bit daft when I wrote my post. The macro in the sub-folder did show up as a macro button and I when I selected it "nothing" happened - I thought. But I just verified that the macro did execute. On PanelDue, there is no request for confirmation (like in DWC), so my macro executed without me realizing it.

My takeaway is that for my macros I'll always write a message so I know it's executing.

So to summarize - Pilot error (the best kind of SW "bug"), followed by too-quick-to-post-itis.

Optical endstops can provide very high precision homing: https://drmrehorst.blogspot.com/2020/03/testing-ummds-xy-optical-endstops.html

@oliof said in Use accelerometer to measure backlash:

whether it would be possible to measure backlash with an accelerometer

I wonder if any of these approaches would be practical for the tiny backlash we expect to find:

Move in one direction and stop. Then move a small distance in the other direction and see if it registered an acceleration bump.

Compare the accelerations (second integral?) in these two scenarios:
a. Move and stop. Then move distance x in the same direction.
b. Move and stop. Them move distance x in reversed direction.

Move back and force in small direction x. Increase x until some acceleration is registered.

I'll add this to the firmware wish list. What is the preferred communication method between the filament width measuring system and the Duet: async serial, or something else?

I don't think there's anything to worry about. If and when MCU temp probe calibration becomes available for expansions it would be an easy fix.

@dc42 some manuals how to calibrate S value? I have best results with M309 S0.03 (lowest temperature fluctuation by extruding the same amount of filament (PETG 235 degrees) on same speed G1 E60 F200).

@fcwilt I don't know. There is underlying housekeeping that the firmware must be doing. The drive mapping could be changed but I don't know whether that would be sufficient.

@owend, it may be helpful in the use case below, splinting the terms and converting them to numbers

https://forum.duet3d.com/topic/27201/macro-parameter-letters

@diamondback

I was not happy with the limitations of homing with a probe or leveling the bed.

I solved it all with multiple Z endstops. Homing is as fast as your printer allows and the result is good enough the final leveling with a probe always works without any change in settings.

Here is a video showing how it works in practice:

Multiple Z Endstops

Frederick

@ccs86

Sounds like a good idea.

In the meantime you can edit those points in the CSV file as needed. I've done that in the past when it was just one point that was way off.

Frederick

@konk you can use triggers on a GPIO pin to run a macro. Think its M581 to define the pin as a trigger. This page details how to do it:
https://duet3d.dozuki.com/Wiki/Using_M581_-_External_Triggers_and_Building_a_Control_Panel