@dc42 I haven't set up a start.g file. But that's a good idea.

@msamblanet it will be an index.

@fcwilt Ok i think i'll maybe do the Z home like this too.

Thanks you all for your patience and for your help 🙂 🙂

For the sake of completeness, I just want to post an update that this is all working now. The net result is that when changing from a filament which prints at 290 deg C to one which needs 210, the cool down time is reduced from 122 seconds to 38 by blowing air over the lower part of the hot end with a 40mm blower fan that I had laying around. So a worthwhile upgrade especially as it cost me nothing. 🙂

I used the same while loop principal to wait for the nozzle to heat when the opposite happens (i.e. when changing from a low temperature filament to a high temperature one), instead of using M116. There are two reasons for this. Firstly, M116 will wait for all heaters associated with a tool to stabilise and in my application, I don't much care what the secondary heater is doing because it doesn't change between tools and has a wide allowable tolerance. The second reason for not using M116 is that it waits for all heaters to be within 1 deg C which with this hot end, can take a while and is unnecessary - I'm happy if the heaters are with 3 or 4 deg of the set point.

Here is an annotated example of the tpost.g file I've ended up with in case it's of any use to anyone who might stumble upon this thread.

; tpost0.g ; called after tool 0 has been selected G4 S1 ; wait a sec ;the following will force cool the nozzle only to within 4 deg of the active temp if it's too hot while (heat.heaters[1].current > heat.heaters[1].active+4) M291 P"Force cooling nozzle" R"Tool Change Macro" S1 T1; display message M106 P2 S255; turn on force cooling fan G4 S1 ; wait a sec M106 P2 S0 ;turn fan off ; the following will wait for the nozzle only to heat to within 3 degrees of it's active temp if it's too cold ; it won't wait for the combining block temperaure to change while (heat.heaters[1].current < heat.heaters[1].active-3) M291 P"Waiting for Tool 0 to reach temperature" R"Tool Change Macro" S1 T1 G4 S1 M291 P"Purging Tool 0" R"Tool Change Macro" S1 T4 M98 P"0:/macros/SinglePurge.g" ; purge nozzle M291 P"Wiping nozzle" R"Tool Change Macro" S1 T4 M98 P"0:/macros/Nozzle wipe" ; wipe nozzle M400 ; wait for moves to complete G1 R2 X0 Y0 U0 V0 A0 B0 Z0 F18000 ; return gantries to wence they came prior to tool change G11; unretract

@dc42 - By any chance have you had a chance to look at my sample above showing the issue?

@o_lampe Many thanks, as always the evidence is just in front of your eye!

@oliof said in dynamic zProbe trigger value:

Maybe add a safeguard against the average being 900 or higher...

That's a good idea!
Thank you!👍

@chrishamm Again, my appologies. I need my printer at the moment and am not using beta firmware. I will consider a release candidate once a find the time to read up on all the changes.

@dc42

i updated to 3.4beta7 and as you said, the issue is no longer there. I did not realize there was a trail of space characters at the end of the quotation mark. that was a good catch and many thanks. I will try to test my macro later. I plan to put this into daemon.g

if job.file.fileName!=null if {job.filePosition}/{job.file.size}>=.09 & {job.filePosition}/{job.file.size}<=.11 M117 "AKM print completed 10%" elif {job.filePosition}/{job.file.size}>=.19 & {job.filePosition}/{job.file.size}<=.21 M117 "AKM print completed 20%" elif {job.filePosition}/{job.file.size}>=.29 & {job.filePosition}/{job.file.size}<=.31 M117 "AKM print completed 30%" elif {job.filePosition}/{job.file.size}>=.39 & {job.filePosition}/{job.file.size}<=.41 M117 "AKM print completed 40%" elif {job.filePosition}/{job.file.size}>=.49 & {job.filePosition}/{job.file.size}<=.51 M117 "AKM print completed 50%" elif {job.filePosition}/{job.file.size}>=.59 & {job.filePosition}/{job.file.size}<=.61 M117 "AKM print completed 60%" elif {job.filePosition}/{job.file.size}>=.69 & {job.filePosition}/{job.file.size}<=.71 M117 "AKM print completed 70%" elif {job.filePosition}/{job.file.size}>=.79 & {job.filePosition}/{job.file.size}<=.81 M117 "AKM print completed 80%" elif {job.filePosition}/{job.file.size}>=.89 & {job.filePosition}/{job.file.size}<=.91 M117 "AKM print completed 90%" elif {job.filePosition}/{job.file.size}>=.99 & {job.filePosition}/{job.file.size}<=1.01 M117 "AKM print completed 100%"

@icy_snake said in Problem with my bed calibration on my modix:

M558 P9 H5 F120 T18000 A1 R0.7

You don't need the full M558 line in your macros. If you just want to alter a parameter for speed or whatever you can just include that parameter. Since you've got a M558 P9 there it is expecting you to define the entire line now, but you're missing the pin name.

Have a look here as well

https://duet3d.dozuki.com/Wiki/GCode_Meta_Commands

Using the object model to get the state of the printer and conditional gcode to check it on a regular interval in the daemon.g file would probably get you what you want.

@owend Thank you for your support. also learned something new!

@avdoverflow the homes status is no longer returned when the "f" flag is used, because it does not change frequently. You can send M409 K"move.axes[].homed" to get just the axes homed status.

@owend

Thanks for looking at that! Great idea for a test.

@phaedrux Thank you very much.

@owend I think you can update to your github, I am your super fans now.