Unfortunately, M106 doesn't support frequency change in RRF3 :(. Gotta use M950.

@Phaedrux thanks!

Moved to the wishlist.

@Phaedrux

This is somewhat related to this topic.

I was trying out the bed leveling assistant feature of the firmware.

I entered the location of the adjustment screws, I created the bed.g with the appropriate probing.

It worked just fine.

The ODD thing was that I specified probe points that required the nozzle to go outside the Y axis min limit.

But with G32 I didn't have to use M208 to allow that to happen. It happily probed the points I specified moving past the Y min limit as needed.

I double checked after it was done to see if the axis limits were still in effect and they were.

Very curious. It would seem that if G32 "understands" that the axis limits can be temporarily extended to allow for the probe offsets than G29, when creating a height map, could do the same.

Frederick

@Phaedrux said in Would like to have fan state accessible in Object Model:

Very Soon

Sounds good but M409 solved my immediate problem once I found out it could provide information about the structure of the OM in addition to specific values.

Frederick

@Phaedrux said in Config tool: wrong paramater for thermostatically controlled fan:

The config tool is asking what speed do you want the fan to come on at, nothing more.

Perhaps I am misunderstanding, but when E0 reaches 45 degrees, it turns it on at 100%, not 25%.

I think the S parameter sets the instantaneous speed when sending an M106 command, but is ignored when the fan is thermostatically controlled (my experience at least, may be wrong)

Thanks for reporting this! We'll get it fixed.

@goury
@dc42

And why not add another fan-Advance for the cooling fan of the heatbreak of the extruder:

That Needs to be spun up before retract, but could be considerably lower when feeding out material.

Two extreme examples:

A complicated part with endless retracts that need to keep the heatbreak cool so with all the retracts the heat doesn´t slowly go/creep up the heatbreak-tube, with 100% pwm for that fan.

An endless spiral Vase, that has 0 retract (oh wait, when the part is finished there is 1 retract at the end) which could run considerably quieter and consumes less electricity, e.g. with the same fan on a pwm of ca. 25-50% because the heat is pushed out way more with the filament.

Since fans take time to change speed, there would need to be some sort of look ahead, that compensates for ca. 1-2seconds lag of the fan.

Lucas

You're not the first to ask for it. There is a memory limitation, but this may not be the case in RRF3 now.

See here: https://forum.duet3d.com/topic/11449/possible-increase-possible-441-points-for-bed-mesh-compensation?_=1595472778569

I'll move this to the wishlist forum.

I've just realised, I just need to wait for variables...

Use object model to get value and assign to variable. Make changes/run script, and then use variable to assign the previous values.

Nothing to see here! As you were! 🙂

then you could go with using a variable for now; altough you'd need to do something like create a dummy tool and store the acceleration value as f.ex. tool offsets, or dummy fans/heaters etc.

not sure if you can set tools[n].offsets[0] .. tools[n].offsets[2] or if you need to use G10 to set the offset, but you can test that easily enough. If you have more axes than xyz, you can probably set more than 3 offets pr tool as well.

@dc42 this would be good. I have to calculate the slicer to avoid collisions, so I need to know when the kinematics are where at which timestamp.

@zapta said in Motor speed limits:

Here is another view of same printer. It seems to move from island to island in zero time. As if the moves were edited out.

https://www.youtube.com/watch?v=1sPf8K_JV08

I wonder if this is the same person... @PAULDGROOT

@JRDM said in Using StallGuard to detect extruder jam & slow down?:

That's configurable

then you'd probably need to move to RRF3 to make use of conditional g-code and react to it

@dc42 Since you're in the process of developing 3.2.0, wanted to see if this "command buffer" for the console was in the works.

If the moves being executed are being read from the SD card then it should already be possible to adjust some things (e.tg. fan speeds and spindle speed) from DWC while the moves are being executed. It is only commands received from the same GCode input channel that are strictly sequenced. However, commands that affect movement (e.g. speed factor override and extrusion factor override) will only affect subsequent motion commands, not motion commands already in the pipeline.

Found it.

Seems I have to set also U and V to 0 reference after a Z probe.

Now it works.

macro calibrate Z max for each axis:

M208 S1 Z-3; Allow z to be negative G90; G1 X0 Y0 F10000; go to the center G1 Z30 F1000; G30 ; probe bed and set z=0 G32 ; start 3 point bed leveling G1 X0 Y0 F10000; G30 ; Probe for Z=0 G1 Z10 F800 ; raise nozzle M584 Z6 U8 V7 P5 ; split z axis G92 U10 V10; set U V axis to 10 as Z G91 ; relative mode G1 H3 Z370 U370 V370 F1000; move Z, U, V down until endstops trigger and get new z limits M500 P31 ; save new z height M584 Z6:8:7 P3 ; unsplit z axis G90

Have to say, object models and conditionnal gcode is a killer feature. 🙂

@deckingman yes, for dual Z (we have this on the machine with a problem) we see that you cannot set Z motors separately but only a whole axis.

@koaldesigns

I've been working on a scara arm for some time, I'm glad to try the 3rd axis but I don't know how to recompile the firmware to reload on a duet is there a guide? or if it is not so complicated can you explain how to do it? thanks!