@nikscha yes, do a check before hand e.g.

if !exists(global.feed_torque) global feed_torque = 0

@T3P3Tony
okay, thank you.
I'll search there.

@dc42 After looking at my code, I was querying the wrong probe. The sensors.probe[1].value works, the problem was between the keyboard and the chair.

However, using the Object model plugin, no probe value gets updated at sensors.probes[#].value[0]. Even when meta-commands and the status board shows the right value.

Add: The JSON file gets updated but requires refreshing the website for the values to be updated into the Object model plugin.

This may be covered by the events system.

https://docs.duet3d.com/en/User_manual/RepRapFirmware/Events

@Nazar
You can check the success of any Gcode command using "result"
0= success, 1= warning, 2 = error

G30 ; home Z by probing the bed if result !=0 abort "Print cancelled due to probe error"

@Phaedrux said in Macro to calculate remaining filament on a spool:

@deckingman Just sharing Ian. No need to take it personally.

No offence taken - I'm much too long in the tooth for that. Just pointing out the ridiculousness of the situation. It's like giving someone directions of how to get from A to B and then someone else saying one could get to B by starting at C instead of A. Then more people suggesting ways to get to C. While it may all be factually correct, it's rather pointless is one is already at A. 🙂

@chrishamm , Thanks for the quick follow up, appreciate it! Linking the github issue for those who may want to track.

This should work too:

echo "Time, ", state.time, move.extruders[0].factor

Looks like it only happens when I reload the page.

Thank You !

@dc42 Thanks for that.

Good to know that the choice selection for the M291 T0 S4 does not need to be indented, that makes a large difference and with that I should be able to get everything in a single file

@Siva thanks for the report about the documentation we will check that out.

@OwenD

@OwenD said in M291 cancel in nested macro does not abort parent macros:

Are you testing the result of M401 immediately after calling it?

Yes, currently the relevant snippet of homeall.g looks like:

M401 ; deploy probe if result != 0 abort "Probe deploy error"

I can't use the abort command in this context, since I have no control over what happens when cancel is pressed.

I'm not a big fan of the global variable fix, it feels like a hack. If there is no other solution, I will use that method though.

@rymnd That's expected in v3.4 and earlier. You need to check if the parameter is an expression (I think there is a parameter property for that) and evaluate it using the EvaluateExpression command if it is. @Falcounet may help with the Python specifics.

@elmw you can't use M569 for that.

The documentation is here:

https://docs.duet3d.com/Duet3D_hardware/Duet_3_family/Duet_3_Mainboard_6XD_Hardware_Overview#description-of-connections
4d153c34-0820-457b-bd26-8114941804e9-image.png

@T3P3Tony Thanks Tony, sorted now.

@deckingman My apologies, that was exactly what I needed, but took a bit more searching and test print to figure out how to implement it
In the S3D post processing box
{REPLACE "; layer 29" "M226/n; layer 29"}
Caveat is that the layer number must specify the layer to stop before it prints.. i.e. to stop after Layer 28 you have to enter 29..
Print head move to park as if you hit pause on the gui and once you are ready, hit resume. .. for those who come later looking for the same thing 🙂
Thanks!
Doug

@KennethR

NOTE: I found an easy fix for the issue and have created another post on my remaining problem. Please ignore the above post(I cannot edit it anymore)

BR Kenneth

Having spent some more time at this, I'm pretty sure I can implement a queue-like mechanism using a global variable array. I've knocked together a quick POT and its encouraging.

The downside is that it will require the user to install a macro instead of using a "native" command. The upside is (1) that its independent of the Duet3d dev cycle which has more than enough to be going on with 🙂 , (2) I'm not trying to shoehorn a mechanism into doing something that was not intended. (3) it can be kept independent of other programs / plugins.

I'll report back / share the macro when I have a reasonable V0.

@rymnd Yes, that's right. I've got the corresponding changes ready for 3.5.0-rc.1 and potentially 3.4.7.