Using the external switch on laser filament monitor
-
Since i never got to make the duet laser filament monitor working with reliable results, is there a way to use only the switch as trigger and ignore the laser feedback?
I will rework the idea of the indirect enclosure (the extruder gear I have on there does not grab the filament properly and thus the shaft doesn't rotate, which defeats the purpose.. I tried 4 different extruder gears from different brands to no avail..)
-
You mean this switch?
I'm not sure if it can be used as a simple endstop separate from the laser monitor function itself. I'm thinking probably not. Will check.
-
Can you try seeing the sensor up as the type with switch (P6) and then use S0 to disable comparison.
-
I'll try that as soon as it is done printing (15h left.. )
-
I've received a note saying that my recommendation likely won't work because...
That would disable the switch too. They would need to enable comparison but use a very wide tolerance in the R parameter.
So there you have it. S1 to enable comparison but a wide R range to make it inconsequential.
-
Ah shoot.. Was about to try it. Oh well, i'll have to find a darn extruder gear that grips the filament properly so that shaft turns...
-
No no, you mistake me. It won't need to turn. It won't matter if the R value is wide enough. It will just ignore the fact it's not turning.
Try R0:1000 or something
-
Oh, I get it. Use it with something like:
M591 D0 P6 C"io3.in" R-1000:100000 E8.0 S1
Would this work?
-
@Thalios said in Using the external switch on laser filament monitor:
Would this work?
No idea. If you send the command in the gcode console it might give an error message if it's wrong. You'll just have to test a bit.
-
@Thalios said in Using the external switch on laser filament monitor:
M591 D0 P6 C"io3.in" R-1000:100000 E8.0 S1
Just activated it. We'll see!
-
Well it worked for about 2h, then it stopped saying it had too little movement..
-
Try jacking up the E value as well.
-
I tried it, and deliberately cut the filament to see what would happen and it just kept going, ignoring the switch. (I heard the switch click out when the filament ran out).
Back to the drawing board i guess..
Duet3D laser filament monitor v2 with switch on pin io3.in, enabled, allow 0% to 160%, check every 100000000.0mm, version 2, quality 223, brightness 172, shutter 125, no calibration data
-
I found a way to make it work. I grinded down the location of the bearings in the indirect filament casing to bring lower the shaft and now it has enough pressure to make the filament turn the shaft. Getting 196 to 226 readings. Very happy!
Would still be nice if it was possible to use the switch only in case of temporary failure..
-
Dammit, still stopped with a -48 reading. how is that even possible?
Duet3D laser filament monitor v2 on pin io3.in, disabled, allow 1% to 500%, check every 5.0mm, version 2, quality 223, brightness 75, shutter 132, measured min -48% avg 225% max 296% over 68774.4mm
-
What settings are you currently running with? Were you able to get a successful calibration?
-
I cried victory too soon in my earlier post.
current settings:
M591 D0 P5 C"io3.in" R1:500 E5 S1
Stops randomly with negative values.
-
I also disabled the switch. Completely useless.
-
What type of filament are you using? It can be sensitive to the transparency of the filament.
Have you tested with different types yet?
There have been a few mods posted to transform it into an indirect sensor.
There are a few options discussed here: https://forum.duet3d.com/topic/10042/indirect-bearing-laser-filament-monitor-concept
-
that's the thing, it is an indirect sensor. I followed the steps and slightly modified it. When I check the readings, I get regular 150-250 values. But sometimes, I get a negative value.
Here's the current:
Duet3D laser filament monitor v2 on pin io3.in, disabled, allow 1% to 500%, check every 5.0mm, version 2, quality 223, brightness 72, shutter 136, measured min -47% avg 226% max 400% over 65950.4mm``` How can it be in the negatives? I used a stainless steel rod as indirect which I sanded down to "de-polish" it. could that cause a problem?