Would a mod please move this to the "Gcode meta commands" category? I forgot that had been added when I posted this.. Thanks

@helpimlost I will add this in RRF 3.4.

@phaedrux

thank you all! this article will be very useful!

@dc42 Thanks!

My solution for now if anyone is interested

if state.status == "off" M81 elif state.status == "busy" ; state can't be idle because controller is busy running this macro M400 ; wait for all movement to stop if heat.heaters[1].current < fans[1].thermostatic.lowTemperature ; check for all tool based thermostatic fans to be off M80 else M291 R"Prohibited" P"PSU toggle is only allowed in standby or idle state! Wait for cooldown of hotend." else M291 R"Prohibited" P"PSU toggle is only allowed in standby or idle state!"

@droftarts & DIY-O-Sphere

Thanks a lot, Exactly what I was looking for!

Jim

Please post your full config.g and homeall.g as well.

Need to see your probe offset.

@hbrownell said in G32 tries to go negative on X axis:

M208 X20

This means that when your X endstop is triggered your nozzle is actually at 20mm inside of the bed surface? Is that correct? Or do you mean it's 20mm outside of the bed surface?

@diy-o-sphere
thanks I had that, what I found and was looing for was the m569 needed to assign each to its own drive

Gonna move this to the gcode meta command forum because it's a good example of using variables.

@dc42 Brilliant - now working.
Thanks
Dave

@tristanryerparke there is a problem passing macro parameters from DSF to RRF in 3.3RC1. Try the RRF 3.3RC1+1 files at https://www.dropbox.com/sh/dlb58vkmu1u4fkx/AAAelkXSfRKVwI6_yqRnhGHPa?dl=0, or the RRF 3.3RC1+2 files at https://www.dropbox.com/sh/urr3rbnawf9ehcq/AAA_frdT0tcOXVlPUz3bHKU8a?dl=0.

I have tested an example similar to yours using the 3.3RC1+2 files in standalone mode. If you still can't get it working in SBC mode using these files then I will ask @chrishamm to take a look.

@fatalis22 said in Set z endstop as a trigger.:

The truth is that this is the best, the ease and speed of making a home with the endstop along with the compensation and the mapping of the sensor. 😁

Great! My first convert!

😉

Frederick

@engikeneer Thank you a lot !

I guess it's solved by now since I didn't know that it will get solved basically by making "PID autotune" since as I was used to Marlin there it is a bit different.

Thank you a lot once more and take care! 🙂

@paulhew Thanks, but i have seen that.
But i could not found the triggers in the OM!

Wow I was approaching this totally the wrong way...

All I have to do, as per your recommandations, is to set in relative mode, and add 100 to Z...

I was WAYYYYYYY overthinking this...

Thanks guys

In SBC mode too from 3.3beta3.

@t3p3tony
can I also send variables with M118 or 'strings-only'?

Just a sidenote: I read about SD-card stuff yesterday and I thought 'all' relevant M-codes are M20-M32.
Now I see M929 is also related to SD-card, but there was no_word about it in the other M-codes. (playing hide and seek?)
OTOH, there are M33-M35 currently not used by RRF. Why not put the M929 function there?

@sinned6915 yes, you do. 3.2.2 for it. The object model also changes somewhat between 3.1.1 and 3.2.2 so I suggest upgrading anyway

That's correct, the M98 P parameter is not included, on the grounds that it's not normally of interest because you know what file you are running.

In the meantime I tested the macros a bit more and had to adjust the math. Now every tool has it's own ooze-countdown.
ooze_compensation.txt

It also looks like, there's no math allowed in 'echo {expression}'?
Also I have to add a local variable and calculate things before using the result in 'G1 E{expression}'