@gloomyandy no, the only special thing about system macros (apart form being invoked automatically) is that they ignore workplace coordinate offsets.

@dc42 Thank you!

@arnold_r_clark said in Conditional G-Code assistance:

@fcwilt

Yes

Thanks for the feedback.

One thing I forgot to mention, it may be of interest. You are invoking your homing files with M98 which usually works fine. Using G28 has one difference which can be important, it marks the specified axes as un-homed just before executing your homing files.

Frederick

Thanks all, I have 3.4 up and running. I'm now struggling with getting mjpeg-streamer working again. Final parts needed for docking the switch will be here Monday. I'm looking forward to having my printer back online.

@theindiandude
No, move.axes[2] refers to the axis, not the drivers.
I have two Z axis drives.
If you send

echo move.axes[2].letter

from the console it will confirm.

@dc42 Thanks

@dc42 I should clarify that when we use the move.axes[N].machinePosition in Gcode it works well. When using the rr_model with HTTP, it does not seem to have the same functionality.

@dc42 any chance of the current 3.5 wishlist being made available?

For future reference, this works.
The probe file can be adjusted to allow for different types of probing.

if !exists(param.X) || !exists(param.Y) ;if parameter X and Y are given echo "Make sure parameter X and Y are given (C and S optional). Aborting probe move." ;notify user G1 X{param.X} Y{param.Y} Z{sensors.probes[0].diveHeight} F6000 ;move to given X and Y coordinates and predefined diveheight M400 ;wait for moves to finish M98 P"waitForHeaters.g" H01 M568 P0 A0 ;turn the extruder heater off (interference changes sensor reading) G4 S1 ;wait 1 second M98 P"preprobe.g" ;call macro to determine triggervalue and see if it is okay to proceed probing ;M291 R"Probing." P" " S1 if global.proceedProbe = true ;if its okay to proceed probing if exists(param.C) ;if parameter C is given if exists(param.S) ;if parameter S is given G30 X{param.X} Y{param.Y} P{param.C} S{param.S} Z-9999 ;probe move else ;otherwise G30 X{param.X} Y{param.Y} P{param.C} Z-9999 ;probe move elif exists(param.S) ;if parameter S is given G30 X{param.X} Y{param.Y} S{param.S} Z-9999 ;probe move else ;otherwise G30 X{param.X} Y{param.Y} Z-9999 ;probe move elif (global.proceedProbe = false) ;if it isnt okay to proceed probing echo "Aborting probe move" ;notify user ;M292 M568 P0 A1 ;set the extruder heater to standby if global.bedLeveled == 0 G32 M98 P"probe.g" X525 Y250 echo >"heightmap.csv" "Height map file generated at", state.time echo >>"heightmap.csv" "xmin,xmax,ymin,ymax,radius,xspacing,yspacing,xnum,ynum" echo >>"heightmap.csv" global.xMin,",",global.xMax,",",global.yMin,",",global.yMax, ", -1 ,",global.xSpacing,",",global.ySpacing,",",global.xNum,",",global.yNum var y = global.yMin var i = 0 G90 while var.i < global.yNum var x = global.xMin var j = 0 while var.j < global.xNum M98 P"probe.g" X{var.x} Y{var.y} S-1 M400 if var.j == 0 set global.meshLine = sensors.probes[0].lastStopHeight - sensors.probes[0].triggerHeight else set global.meshLine = global.meshLine ^ "," ^ sensors.probes[0].lastStopHeight - sensors.probes[0].triggerHeight set var.x = var.x + global.xSpacing set var.j = var.j + 1 echo >>"heightmap.csv" global.meshLine set var.y = var.y + global.ySpacing set var.i = var.i + 1

@stephen6309

Thank you very much, i will test tomorrow and report back, thank you again.

@Piet
there is not currently a way to echo it directly to a file however the logging function can be used, e.g.:

M929 P{"M122_Log"^{state.upTime}^".txt"} S3 M122 M929 S0

If you put that in a macro then everytime you run it a new log file will be created with the output of M122.

Note this wont work if you are already logging to another file

This sounds doable. You could have a check in daemon.g that checks the value of the DHT22 in the object model and performs an action when the value is exceeded. https://docs.duet3d.com/en/User_manual/Reference/Gcode_meta_commands

Hopefully that's enough to set you on the right path.

@jay_s_uk I see - you are right. Echo to file was added in 3.4, an update should solve this. Thank you!

Sadly, we'll need our prototype for a presentation in the upcoming days and I don't want to risk that a firmware update changes or breaks any functionality that we already implemented.

Might have to go without this function for now.

@owend

THANKS you very, very much! That was exactly the snipit I was looing for! You helped me a lot with the understanding of working with the meta command!

I will start playing a bit with it that brings me to a view more ideas. 🙂

Thanks a lot...

Cheers, Chriss

@alankilian said in time measurements:

@mikeabuilder

Oh I see.

Maybe do everything in milliseconds then?

echo {state.upTime*1000 + state.msUpTime}

Yes, that will work better, until state.upTime * 1000 exceeds 2^31. This is about 2^21 seconds, which is about 2 million seconds, which is about 24 days.

If the machine might have been left turned on for more than 24 days when you do the timing, but the time you need to measure is a lot less than 24 days, then you still have some possibilities. For example:

var startTime = mod(state.upTime, 1000000) * 1000 + state.msUpTime G4 P4321 ; replace this by what you want to time var endTime = mod(state.upTime, 1000000) * 1000 + state.msUpTime; var elapsedTime = var.endTime - var.startTime if var.elapsedTime < 0 set var.elapsedTime = var.elapsedTime + 1000000 * 1000

Have you used these guides?

https://docs.duet3d.com/en/User_manual/Machine_configuration/Configuration_linear_delta
https://docs.duet3d.com/en/User_manual/Tuning/Delta_calibration

The calibration results can be saved by sending M500 and then can be loaded at startup by adding M501 to the end of config.g

I appreciate all the feedback, I have been thinking about this and going to scrap the idea and take a stab at a configuration plugin. The deeper I get the more problems I am seeing with using GCode and being a sr. frontend Vue developer I should be able to tackle this.

Stay tuned 🙂