Topics created by appjaws

@gloomyandy
Thanks

@droftarts
Thank you, all working properly now that I realized that the emergency stop pin should have been duex.e2stop

@appjaws Glad it's working for you now!

@appjaws
Hi - I'm curious as to your use-case. Is your need to have the backups on your windows computer for occasional use? e.g. restore / write to an SD card. Or do you have some other use-case.

Part of the reason I ask is that I am the author of the duetBackup plugin and curious if I need / should add additional functionality.

@tinchus Thank you for the info but I don't think this is my problem, I can't even get the printer setup to do a print. Hopefully another board will arrive today, which I hope will solve the problem.

Glad it was something simple. 😉

Problem solved, I checked all files and there were a few that had space and tabs. They now have all tabs and the error has been fixed.
Thank you for all who helped👍

I feel like M500 P31 and G30 S-3 could probably come into play here, but I'm not if that's needed now that conditional is available.

https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M500_Store_parameters

If the P31 parameter is used, the G31 trigger height, trigger value and X and Y offsets for each possible Z probe type (in older firmware versions the G31 parameters are stored even if the P31 parameter is not present)

https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_G30_Single_Z_Probe

G30 S-3 ; Probe the bed and set the Z probe trigger height to the height it stopped at (supported in RRF 2.03 and later)

The downside of G30 S-3 is that it takes the singular result and not any average of several results.

@appjaws said in variable (height) to calculate average trigger height:

I would like to have a variable (height) that would be incremented by the Z probe value, move.axes[2].userPosition, 10 times and then I would need to calculate the average, (height/10) but limit this result to 3 decimal places and then update G31 in the config file.
How is a variable defined?
Is this possible? If so could you show an example please.

Thanks for any help

Hi,

Currently variables are not implemented.

You can use existing properties of "dummy" objects that you create.

You cannot set a property value directly, you have to use a command that will achieve the desired result.

So if you created, as an example, a dummy axis, A you could use the following to set its userPosition property.

Reset to zero: G90 G1 A0

Increment by current Z position: G91 G1 A{ move.axes[2].userPosition}

But I don't know how you would update the trigger height in the G31 command in the config file.

Frederick

@sinned6915 3.2 I believe

Thank you for all the help, everything is now working correctly and my printer has a lot less vibration.

@appjaws I'm watching my 2-color print with those 2 additional temperature stabilization lines in the startup and tool change scripts. OMG, does that matter! Stringing is down, consistent appearance and sheen, even extrusion! Wow!

@dc42 thankyou, I tried the changes for R and D but it made little difference.

Eventually the temperature does stabilise so I need to have a check prior to the print start

With my limited skills I have tried to have a condition to check the heat.heaters[1].current
but I end up in a loop or it is ignored.

Could you suggest a suitable test please

Thank you

slightly offside; language and locale aren't necessarily the same setting.

I.e I run English language and switch between English and Norwegian locale (and keyboard layout)

@bearer Wow , that a secret I've not heard about before.

Thanks @dc42 for all your help, it now works great.
Will be even better when we can use variables.
What would be a good source to learn the syntax of the commands used for conditional gcodes?

M99 should exit the current macro file (but will not keep subsequent commands from being run). You could use this in conditional macros to get out early.

If you want to do something like kill the print, you should be able to use either a M25 to pause the print (without waiting for buffered commands), or M112, but I think with M112 you have to reset to get back up, similar to a reboot.

@dc42 said in Increasing M106 S value in a macro incrementaly:

M106 P3 S{fans[3].actualValue + 2}

Thanks, great answer, I am learning a lot.

@appjaws said in M116 appears to be not working:

Its almost as if the output blips to full power from idle, perhaps to aid actual fans to start quicker.

It's exactly that. See the M106 B parameter.