Not clear on properly configuring M591 on Duet3/Toolboard...

Nuramori

I have a toolboard, with the extruder motor connected to it on drive 0. The toolboard ID is 20.

I have configured the line as follows:

; Filament Sensor
M591 D20.0 P7 C"0.io3.in" S0 L1.84 ; Detect filament issues

I get an error that the "D" value is too high. It's not quite clear in the documentation what exactly D is supposed to be. From the docs it says, "Dnn Extruder drive number (0, 1, 2...)," But I can interpret this to mean the drive number as in driver. For me that's 20.0 (toolboard driver). Is it meant to be 0 if I only have one extruder?

dc42

The current firmware does not support filament monitors connected to tool boards. I plan to add this support in firmware 3.02. See https://duet3d.dozuki.com/Wiki/Duet_3_firmware_configuration_limitations.

However, you have connected the filament monitor to the main board, so this does not apply. The D parameter is the extruder number, the same as the D parameter in the M563 and M572 commands. If you have just one extruder, it should indeed be zero.

Nuramori

Thank you, Sir!

dc42

I've just realised a further problem. The filament monitor needs to be on the same board as the extruder motor driver, so that is can correlate the live motor movement commands with the filament motion. So I'm sorry, you will need to wait for the release 3.02 beta firmware before you can use a filament monitor with a tool board; and then you will need to connect it to the tool board.

Nuramori

@dc42 bummer! Ok thanks for the heads up and pre-empting further posts about my hair loss. :).

Looks like I will have to forgo it then - I am using an optical endstop and I believe I’m out of io options, given I also use a BLTouch on the toolboard.

dc42

@Nuramori said in Not clear on properly configuring M591 on Duet3/Toolboard...:

Looks like I will have to forgo it then - I am using an optical endstop and I believe I’m out of io options, given I also use a BLTouch on the toolboard.

Not necessarily, because it should be possible to use the TEMP1 input to connect the optical endstop.

What type of filament monitor do you have?

BTW on later tool boards we've added an extra input for an endstop switch (but that doesn't help you).

Nuramori

I may upgrade to a newer toolboard then, if I can change the wiring. I monitor the filament near the spool, not the printhead, so there’s a complication I suppose.

I made my own filament sensor using a lerdge optical endstop and slotted impulse wheel I drew up, together with a bond tech gear. Works really well.

jdumoulin

@dc42
Hi, I just ran into the same issue but I do monitor filament right at the hermera. I am working on a rather large printer (900x900x800) and a filament out sensor is crucial. I hope you would be so kind to answer the following three questions so that I can figure out how to move forward:
When do you think 3.02 beta will be released?
Where can I find information on how to connect an end stop to Temp1?
Will the attached end stop work with the new firmware? I do have some optical switches laying around if there is no other way.

Thanks in advance.

dc42

@jdumoulin said in Not clear on properly configuring M591 on Duet3/Toolboard...:

Where can I find information on how to connect an end stop to Temp1?
Will the attached end stop work with the new firmware?

I think it should work in 3.0-RC12 if you connect a switch-type endstop across the temp1 pins and specify port "xx.temp1" in the M574 command, where xx is the CAN address. Let me know if it doesn't work.

jdumoulin

@dc42 said in Not clear on properly configuring M591 on Duet3/Toolboard...:

I think it should work in 3.0-RC12 if you connect a switch-type endstop across the temp1 pins and specify port "xx.temp1" in the M574 command, where xx is the CAN address. Let me know if it doesn't work.

OK, I will work on that today. I think I need to upgrade to RC12 first. Thanks

jdumoulin

@jdumoulin said in Not clear on properly configuring M591 on Duet3/Toolboard...:

I think it should work in 3.0-RC12 if you connect a switch-type endstop across the temp1 pins and specify port "xx.temp1" in the M574 command, where xx is the CAN address. Let me know if it doesn't work.

So far I have not been able to get it going. I am running Rc12 on the main board, RC11 on the tool board. I borrowed the Y end stop M574 command to see if I could see the trigger on webcontrol but no luck.

Config was M574 Y1 S1 P"20.temp1"