@droftarts thanks, now i found it in the documentation with your info.
Is it possible to use an Duet 3 Mini 2+ if wired accordingly? Or are there any "plug and play" expansions out there?

Hi there,

i am currently using all 10 Stepper driver outputs on my Duet 2 Wifi + Duex5.
As the v0.11 Duex 5 has two/three additional outputs for external drivers i am wondering how to use them as the product description says all in all this combination can use 12 Stepper motors.
I need the two extra ports for pre feed extruders for my idex printer as 10kg spools each are probably causing to much wear on my extruders.
Currently i made a workaround running the extruder and pre feed extruder wired in parallel but this leads to the pre feed extruder in extruding 0,5-1% too much filament.
The steppers are identical.

Is there any daughterboard for the duex which has two additional stepper drivers?

Thanks,
Timo

@dc42 Perfekt, sounds promising. I will give it a try on monday

Thank you guys! I must been blind while reading the wiki earlier, have not found anything about it. Now i`ve found it
@benecito what exactly "does not really work yet" ?

Hi, are there any updates on how to enable filament monitoring while printing via usb? Is there a new enable mode which needs to be used?
Thanks, Timo

@oliof is this still needed if the host reads the outputs of the board?
The board just needs to output a certain message in the console and the host needs to react to this event as for example repetier-server can.

I would be totally happy with an S2 option for M591. This should resolve many problems.
If there is a quick and dirty workaround for this, please tell me

@dc42 That sounds very promising
If i understand correctly at this moment there is no point for me to manually enable this and a changes in the firmware need to be made from your site first?
Can you estimate without obligation how long this takes until its ready to use?

I think there shouldnt be any problems while filament loading and unloading etc. because (if i understand correctly) the filament monitoring is just checking printing moves (xy moves + extruding) and not move or extrude only commands.

@dc42 thanks for the super quick reply.
I am aware that the duet would still need to empty the buffer, that’s totally fine as ~40 moves are not that much.

I got a testing machine which is running Klipper while printing with repetier-Server, same thing but it works.
I just don’t want so swap all machines from RRF to Klipper as they are currently working fine besides the „issue“ that the clog and filament monitors are not working.

Is it possible to manually enable this in RRF or would this be bigger changes in the firmware itself?

@jay_s_uk The problem here is that i want my clog detector to work with duet and repetier-server. "Normal" Filament sensors which check if filament is loaded or not shouldnt be a problem to directly connect them to the pi running repetier-server. But with the clog dectector it gets more complicated as the printing moves are compared to the actual movement of the filament.
As RRF already handles this very well i think this should work with external hosts aswell. I just dont know how to get RRF to always monitor this.

Hello,

is there a possibility to enable filament monitoring while printing via an external host like Repetier-Server via USB?
Unfortunately the documentation states, that filament monitoring is only active when printing via SD-Card.

As the duet gets all information about xy moves without extruding, xy moves with extruding and extrude only commands isnt it possible to monitor all the time regardless of printing from SD?

I found this in an old thread:

"dc42 ADMINISTRATORS 25 May 2020, 12:14
How would the firmware notify Repetier that the filament has run out?

Even if Repetier paused, RRF would still empty the moves in its movement queue. Whereas when printing from SD card, RRF is usually able to stop without emptying the movement queue, and rewind the SD file position so that it can resume at the correct point.

Another issue is that RRF can't distinguish between commands received over USB that are from a file being printed, and commands being sent manually by the user.

I think the best we can do when RRF is not in control of the print would be to have a command that enables the filament monitor even when not printing from SD card, but when a filament error is detected it just sends a message to all channels saying so. It would then turn off filament monitoring until commanded to turn it on again."

Thanks in advance,
Timo