Topics created by JRDM

@JRDM I think the maximum length is already increased in RRF 3.5.

@JRDM I guess you can use conditionals in the macro or start/stop the second stream from within the first stream. But I haven't tried it.
There is this article Duet3 Wiki that might help you.

@dc42 OK thank you. I didn't pick up on that from the docs. I made the changes, removed my attempt at a dummy heater output. It works great now.

Yes I suspect that the IAP files from earlier 3.x releases weren't present, so 3.3 couldn't install.

In future, always use the full release zip file to update and you should be good to go.

@dc42 Thank you the suggestion of deploying before and retracting after the group of G30 calls did the job

@o_lampe Totally different board, totally different ports/pinouts...

Yes it is, and support would be the same.

@jrdm this feature is currently experimental in firmware 3.4.0 beta 6. It is only partly functional in RRF 3.3.

@pcr Sorry for the wait but here it is:
There's a STEP file in there too in case anyone wanted to play with a solid model file.
https://cults3d.com/en/3d-model/gadget/duet3d-thermal-sensor-amp-standoff

@dc42

One request i would make is a future hardware change - add a jumper configurable “end of chain” resistor. I understand how the tool board was designed for use with the distribution board, but the tool board is extremely useful for single headed printers too. The termination resistor is kind of documented for this implementation of a tool board, but I can see it’s popularity by reducing wiring making it a popular approach. Allowing for wiring it up and then changing a jumper would make it much easier.

@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

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.

@JRDM If you haven't turned it off and on since, send M122 for the error report, which should give a hint about what happened.

Ian

So now you have an "axis & post-process", an "Arudino" and a "Mechanical" way to approach this.

Your call...

@Phaedrux

It looked like lemon candy melted in a cast iron pan. Its hard to describe really.

I got a 0.030 piece of PEI from CS Hyde and laid up the anodized sheet under it. The top surface was all slick and glossy, like glass. It was really quite pretty actually. Polished gloss actually. It reflected light too well so I wet sanded it with 400 grit and then ran a maroon then white scotchbrite pad over it to break the surface.

jrdm@, this may interest you, 1200x1200mm printer. Description has a link to thingiverse. He uses 4 silicon pads.

https://www.youtube.com/watch?v=4qjv9yPHOv8

I guess you are either pausing during initial heating, or you have modified the pause.g file to put the current tool in standby. I'll have the online configurator changed.

@dc42 Learnt something again today!

@jrdm, the current depends on the input voltage to the control terminals. The 5 to 12mA current rating is probably measured at some standard voltage such as 10V. The minimum input voltage is usually 3V, so the 3.3V provided by the Duet is only a little above this, and the input current will be low. If you are concerned, connect the SSR input to the output of the Duet as I suggested, and measure the voltage across the control terminals when you command it on. Check that you have at least 3V as required by the SSR datasheet.

In RRF 3 I have increased the maximum number of heaters supported by the Maestro to 4.