Script to make babysteps permanent

A Former User

@droftarts said in Script to make babysteps permanent:

@jens55 Probably best to actually tag him with @dc42 if you want him to look!

Ian

That doesnt seem to work I asked a question in another thread last week (regarding firmware)

I tagged him and got no reply, so either its not working or he didn't want to answer the question.....

jens55

Thanks .... how do you tag somebody and what does that do? Does he get a message when it's tagged ?

droftarts

@CaLviNx He gets a lot of requests. Last week he was on holiday, so try again.

Ian

droftarts

@jens55 Type an '@' sign in your post, and you'll get a list of people that have replied to the post. If the person who's attention you want is not on the list, just continue and type their name. Like replying to a particular post (the blue 'Reply' or 'Quote' words on each post), the person tagged will get a notification via the bell icon.

Ian

dc42

@jens55, are you running firmware 3.1.1, or an earlier version?

jens55

@dc42 , thanks for replying!
3.1.1

dc42

I confirm that's a bug, which I will fix in 3.2beta1. Meanwhile, you may be able to work around it by putting M400 just before the G31 command.

jens55

Thanks! No need to work around it ... I just wanted to make sure you were aware.

flobler

@jens55 thanks for your work on getting this macro right.

I just tried using what you shared here. For my use case I see an issue with the macro:

1. I have configured my "rough" trigger height, then start a print
2. During the first layer I realize I want to adjust the trigger height slightly
3. I apply the desired change through baby stepping
4. I execute the macro to write the change to config-override.g

As far as I understand this will then reset the baby stepping on my current print and will bring me back to the initial trigger height I had at 1.)

This means the updated trigger height will be only applied after I restart the printer and would not persist for the print I have ongoing at that moment, is that correct?

My ideal scenario for this macro would be:

1. Start the print with per-configured "rough" trigger height
2. Fine tune through babystepping during the print
3. Execute the macro to save the new trigger height to config-override.g
4. Continue printing at the adjusted trigger height (taking the baby stepping I applied into account)

Now I know this could probably be solved through simply removing the M290 R0 S0 command but I would like to have the option to to another round of adjustments through baby stepping if needed and save it again with the macro. Problem here would be that if the reset is removed, I would then adjust my trigger height by the value I have adjusted originally + the value I have adjusted with in my second round of baby stepping adjustments which results in a too small or too big trigger height value. (e.g. first save was baby steeping +0.02, second adjustment is +0.04 which will then save a total of +0.06 to the value I have saved after my first round of adjustments).

Does that make sense? Do you have an idea how I could solve this?

If not, I only see the following options to achieve what I want to do:

a) Use the macro as shared above and always run a specific calibration print to fine tune the trigger height, save it, restart the printer and then kick off the print I actually want to print

b) Remove the reset of baby stepping and only save it to config-override.g when I am 100% happy with my adjustment, so I would not have to do it a second time throughout the print

Tinchus

Usefull script. Question: how would you do it if you have a second tool? A second tool offset is always relative to the other Tool (T0 offfset is set using G31, T1 offset is set using G10).
Lets say you have T0 offset OK, and now you are printing a test with T1 and using babystep you get to the sweet spoot, the babystep value you get is recognized as belonging to T1 when you execute the M500 P10:31 command?

Hernicz

I already have this working. It saves babystep value on pause, cancel, print end and loads it at print start.

G32 and G29 resets it to 0.

It's also possible to continously monitor it with daemon.g in case of event of power loss.