@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.

@maytasjohn

How do you plan to control the heater if you turn off "PWM"?

Keep in mind that the alternate control method of "bang-bang" is really just PWM at a very slow rate.

For my 110 VAC bed heater I use a SSR (solid state relay) in PID mode at 10 Hz at it works just fine.

Frederick

@dc42 OK, thanks.

Temperatures aren't our concern now. Were still far from heat up or print despite having all the hardware finished

We saw some temp variations/inaccuracy with 3.3 and 3.4b2 during previous tests.

@fcwilt I've just been doing an M999 between jobs for now.

@fcwilt

going to the release version of 3.3 seems to have fixed it.
Thank you very much indeed!!

@achrn

Currently there is a problem with using the underscore character when running in "SBC" mode.

The developers are aware of the problem and it should be fixed when 3.4 is released.

Frederick

@owend, no problem and thanks for chiming in !

@achrn and @kb58, filamentPresent was removed from the object model in RRF 3.2 as documented in the change list. Use the "status" field instead.

@rodrigormaraujo yes, use daemon.g
some like

if heat.heaters[1].current > 45 M150...

It can definitely be improved a lot, but it is enough for the basic function. Thanks to everyone for the help.

daemon.g

G4 S1 if heat.heaters[1].current > 55 && heat.heaters[1].current < 1000 ; hotend temp more than 55c ? ; hotend temp more than 55c ?, termostacic fan set to 45c (fan have time to start spin) if fans[1].rpm < 500.0 ; hotend fan spining faster than 500rpm? M150 R128 ; Neopixel red! M104 S0 ; set hotend temp to 0c M291 P"Hotend fan error!!!" S1 M98 P"pause.g" ; run pause.g else ;M150 U128 ; Neopixel green else ;M150 U128 ; Neopixel green G4 S1