@o_lampe

Thanks, the second motion system is working.

@OwenD WORKS GREAT now!! Thanks a lot!!!

@gloomyandy I mean turn on/off the output relay

@timschneider thank you!!! now work properly!!

@OwenD

Thanks for quick reply. Have got it working using echo.
I did see echo before but looked more verbose.

@OwenD said in Need some guidance on pausing a macro until I provide input:

M291 R"Wait" P"Check bed height. Press OK to continue" K{"OK","Abort"} S4if (input == 1) echo " cancelled" M99

Thanks so much! I'm using firmware version 3.46 (I'm not aware if 3.5 is stable enough), so I had to change it a little bit. I couldn't go higher than S3 and it wouldn't accept the "input" value. I ended up using the following:

G1 H2 X30 Y30 F6000

M291 R"Wait" P"This is a pause. Press OK to continue" K{"OK","Abort"} S3

G1 H2 X50 Y50 F6000

This works great so far! Thank you again!

@idcoilgroup you are correct, the axis number should be X0 Y1 Z2 A3 B4 C5, so M563 P1 X3 Y4 should be correct.

Did you change them to linear axes as @JoergS5 suggested, by adding R0 to the M584 command that creates the ABC axes. Also make sure ABC are homed, and are at an axis position that means they don’t break axis limits set by M208.

Ian

@Tinchus you would use something like this

P{"copy and paste the IP number: "^network.interfaces[0].actualIP}

Hi Guys
Thank you for your replies. I think I now have all the info I need to actually get going.
Cheers.

@fcwilt said in Possible bug with local variables use in config.g?:

@Mr-Yod

I've always used {var.variable_name} rather than just {variable_name}

Frederick

🤦

You are righ... 😅

@dc42 You are absolutely correct! I don't know why I thought otherwise. Thanks!

@sankafola
You have cross posted this question. Lets keep the discussion in the other post since its not clear at this point if you even have a clean install.

@OwenD
thanks so much.
It is exactly what I was looking for.

@droftarts yes it's still supported at present but will be removed in a future version of RRF, hence the warning.

@azs123 You need to call EvaluateExpression in your custom code handler to get the actual value of that parameter if it is an expression. Afair there is another code parameter property to flag this.

Thanks guys, this gives me all kinds of ideas.

Thanks. Crazy that there isn't a blessed way to do it.

I didnt know about this tool, it's cool. Makes this so much easier. Thanks

I think this is solved lets continue any discussion in the other topic: https://forum.duet3d.com/topic/34132/orbiter-filament-sensor-setup/9