Turns out, I was fooled by the ObjectModel. Z offset is not set, but triggerHeight is ...

@dhusolo said in Staring macro doesn't behave as expected:

@deckingman Thank you very much sir. That was the answer I was looking for. I'll give it a shot later tonight.

No worries. Just remember that all moves are relative to something. With relative extrusion, the E value will be relative to the last move end position. With absolute extrusion, the E value is relative to when the extruder was last zeroed. If you think about it, when you want to extrude (say) 15 mm of filament, an absolute value would first have to be converted to a relative value which is why it's generally best to always use relative extrusion IMO).

@owend String arrays would make things even easier would they not? Then presumably one could do G1 E( stringarray(iterations)). I'm using my phone right now so can't easily use curly or square brackets but you get the idea.

@chrishamm thats nice! i forgot to mention that i got a raspberry with duet...

Hey @dc42

These are being run from within a print file. Trying to achieve the ability have an extended dwell (1 hour+), where the machine will be able to resume from its position if restarted etc. I was looking to achieve this by looping over much smaller dwell periods and tracking how many interactions its gone through.

Just reporting back that I've implemented this and it works a treat. 🙂

I added a few M291 commands so that I get to know what's happening. So at the start of homing I have this

; start by warming the hot end so that any oozed filamnt is molten T0; select a tool - any one will do ; check if tool is hot, if not start to heat it to 140 deg C if sensors.analog[1].lastReading < 140 G10 P0 S140 M291 P"Hot end set to 140 deg C" R"Homing Macro" S1 T10

Then I home XYUVA and B after which I check the hot end again and reset the temperature if it's still below 140. Then I wait until it attains that value (or higher) like so...

; check again if tool is still at or above 140 deg C, if not heat it if sensors.analog[1].lastReading < 140 G10 P0 S140 M291 P"Hot end below 140, so set to 140 deg C" R"Homing Macro" S1 T10 ; now wait for temp to get to 140 or above while sensors.analog[1].lastReading < 140 M291 P"Waiting for hot end to heat" R"Homing Macro" S1 T4 G4 S4

Then I go on to wipe the nozzle before moving the hot end to the centre of the bed and homing Z. The final part of the homing routine is to set the hot end back to 0 and restore the motor currents.

@dc42 thank you for your help David it worked.

@oc_geek Standalone or SBC? The macro handling for the two can be slightly different.

@chrishamm said in Type conversion (float -> int):

@oc_geek It sounds like you are looking for floor.

yes sorry...i'm blind LOL

floor(expression) made it happen

Thanks

@owend The limitation on M28 actually presents a problem on a project I'm currently working on, because the project has macros which do nested writes, which can only be achieved using both M560 and M28, and the nested write does include a conditional. I haven't thought of how to deal with that yet.

I'm wondering if there's a character meta commands consider to be indents but M28 doesn't consider space to be removed. A no-break space (C2 A0) didn't work. Neither did a character code 255.

@gloomyandy
Yes, I have just tested it and you are correct. Thanks for your input 👍
If I run it as a print job it sees the updated global and cancels.
Even if I have a print job that does nothing more than call my original macro it still works.
For good measure I called a macro from a print job where the macro changed the variable mid way through the loop and that also worked.

Marking this as solved, though perhaps some reference should be made in the documentation.

@gloomyandy C++ has something like Pascal has, in that you can create local constructs within a function, and the function becomes the enclosing scope and so is accessible. It's been too long and I don't remember the details.

@pixelpieper said in ^ operator:

@fcwilt

This works:

M117 {"foo" ^"bar"}

Got it - I need to use the {} pair for things like M117 - missed that fact somehow.

Thanks very much.

Frederick

@sindarius Oh yeah... that seems to be the right variable.
Thanks

@fcwilt Thanks for reporting this, I can confirm underscores aren't supported in SBC mode. I'll fix this in the next versions.

@nuramori

thanks. this works perfect. the only issue I ran into is when I manually pause, it wouldn't always stay paused but automatically resume. on the facebook thread, someone mentioned using daemon.g instead of m581. I'll have to dig a little more to see if this will work better.

Here's an example of using a macro to measure the exact z height and save it.

https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+5:+Upgrades/54#s221

The example assumes you have a probe already configured and calibrated to find Z0 reliably first, but you can substitute the G28 in that example for manually setting G92 Z0 when the nozzle is touching the bed.

That guide also goes through BLtouch setup.