@simwiz start.g has to be in the sys folder and will run slicer indipendent at every start...
EDIT: sorry, you was answering to t3p3tony

@jbjhjm said in M703 - error if no filament is selected?:

if move.extruders[state.currentTool].filament == "" abort "Error: No filament selected" if move.extruders[state.currentTool].filament == null abort "Error: No filament selected"

I have not encountered a situation where the null check was needed - perhaps it can be null but I don't know when.

I have no test for a tool being selected as that is done just after the checks. I have no multi-tool printers.

T0 M703

Frederick

@owend it's the inner parentheses that are redundant.

Note to self. Don't muck with a running macro file.

@ctilley79 said in Filament Config.g and Conditional Gcode:

I was hoping to execute M703 once, and RRF automagically execute the condition at the appropriate layer height. Wishful thinking lol.

You could do that using a few global variables for the desired values.

They would be set once in the filament config.g file.

They would be used in a dedicated layer change file, something like print_layer_change.g.

Frederick

@fcwilt
Yea each stepper has its own driver all of the drivers are tied to the z axis in the config file.

I think the auto bed leveling is exactly what I am looking for, but I just need to do some reading to understand how to do this with my set-up.

@dc42 thank you!

@o_lampe the ringing frequencies do not depend on print speed.

@generisi I suspect not, because the function takes a variable name (no quotes) as an argument, not a string. I could imagine it being useful, though.

@phaedrux said in Custom Work Plane code for Homedelta.g:

This line also looks weird. The distances aren't the same, and there is a rogue H2 on that line as well.

Thanks. I made the suggested changes and it's working well now.

@aitor said in How to get the result of a M command:

heat.heaters[0].avgPwm

Thank you that it was 😄

@deckingman said in A couple of questions regarding global variables:

As an aside, would running M999 work after making changes to global variables? According to the wiki, https://duet3d.dozuki.com/Wiki/Gcode#Section_M999_Restart it restarts the firmware using a software reset. But I don't know if that restart also involves reading config.g and clearing anything that's in memory.

Yes, running M999 will clear global variables.

@t3p3tony
I appreciate this link!

@dc42 Thanks so much. It's already very useful.

@zapta said in How to write a gcode loop for exactly N iterations?:

BTW, since 'iterations' is loop specific, may be helpful to mention it also in the loop section.

Done!

@dc42 Ok, thank you

Good morning @dc42,

I'm on version 3.3.0, that's why it doesn't work, right?

Anyway I will update as this feature will solve my life.

Thank you very much

@dhusolo
My code was meant as an example.
You need to monitor the pin that your you're using.
i.e the The pin you created with M950 and the P parameter you use in M581.
You have M581 T2 P1 S1 R0
try

M80 ; Power on G4 S3 ; if sensors.gpIn[1].value = 1 ; check if button still pressed M81 ; turn off power

Not sure why you're using M582 in config.g
I believe it will cause the trigger to run as if you've pressed the button.