@SIam said in Laser Filament Monitor - Return hardware?:

M591 D0 P5 C"e0stop" R40:120 E3.0 S0 ; Duet3D laser sensor for extruder drive 0, connected to endstop input 3 (E0), tolerance 40 to 120%, 3mm

Thanks, That did it. I guess I read the wiki wrong and was using the older syntax?

M591 D0 Duet3D laser filament monitor v2 on pin e0stop, disabled, allow 40% to 120%, check every 3.0mm, version 2, quality 218, brightness 12, shutter 135, no calibration data

Now I will start on calibration.

Question:
I would have expected the filament sensor to show up under sensors in the DWC. It would be nice to see what it is reporting just like the BLTouch.

sensors.png

@droftarts I've kind of got it figured, not entirely comfortable but seems close enough.

mfm.png

Ignore the tensioner errors in E3D's Hemera - it is good enough for what I need.

I've used numerous CAD packages, never could get to like the workflow in OpenScad although I know that some swear by it. I use Fusion360 enough to warrant paying for it, I got a really good deal during the black Friday sales. I'd have liked Solidworks but their prices are frankly way too high to justify for a non commercial user.

@droftarts perfect thank you

I've had to tweak my sensor configuration mid-print to ensure it doesn't pause incorrectly during printing, I haven't yet confirmed it's working as expected or at a good tolerance level as unfortunately by hot-end fan stopped again mid-print; I once again need to dismantle as heat has crept up and created a blockage.

On the plus side, the filament sensor did pause the print when the filament blockage occurred, which is great, unfortunately, this doesn't cut the power to the heater and I can't see any way to configure this.

I'm happy to start a new thread with the other issues unless @dc42 you are able to help me here:

[Q] I have a smart effector and while I've managed to print for several hours at one time (and get very good parts out of it) the hot end fan randomly stops and I need to manually spin the fins to get it going again. How can I work out what's happening here? I'm not sure it's ever been correct, the first print I made with the smart effector was perfect, the second was the first one where the hot end fan failed, and this has now happened 3 times and I've already replaced the hot-end fan with parts direct from E3D.

[Q] Is it possible to adjust the behaviour of the pause from the filament sensor without code modification? if I can get it to turn off the tools, this may be better for me while it currently has issues with the hot-end fan.

As always, thanks in advance for any assistance!

@brasse I'd suspect the wiring; it sounds like something is 'floating', or perhaps the filament is not pushing the switch down fully. Though could be a similar issue as in this thread (similar hardware) https://forum.duet3d.com/topic/14014/openbuilds-limit-switch-reads-hit-in-s1-and-s0

For connecting it up (and do check the wiring), see https://duet3d.dozuki.com/Wiki/Connecting_endstop_switches#Section_Makerbot_Mechanical_Endstop_v1_Num_2

Edit: from the above page:

These devices produce an active-low output. If using RepRapFirmware 1.x or 2.x, use the S0 parameter in your M574 command

I think you need to invert the switch logic. The above is for M574, which defines endstops. With M591 you invert by sending P2, so in RRF3 I think your command should be :
M591 D0 P2 C"e0_stop" S1 ; filament monitor connected to E0_stop
Ian

For some reason the forum wont let me edit that post to fix a typo in the M591. :
M591 D0 P3 C10 S1 R20:150 L25 E40
M591 D1 P3 C11 S1 R20:150 L25 E40

Thank you for the update. Could you please indicate if this version of the sensor has changed from the previous versions? I believe Filastruder has stock but would like to confirm that it is a current product and not an older design.

@Tony-Owens
is working quite well, I would like to reduce the dimension of the assembly in the future.

<BUMP>

Do you have an update of when this will be available ?
This item still showing out of stock

https://www.duet3d.com/DuetAddons/MagneticFilamentMonitor

Thanks,
J.

Since no one seems to have replied - yes if you enable the eventloging function in the firmware, it will state what caused the pause to occur. It will also show as a pop up notification on the web console. In the console itself it will just say it was paused though.

The full M122 is here:

=== Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05 running on Duet Ethernet 1.02 or later + DueX5 Board ID: 08DGM-917NK-F23T0-6J1F6-3SD6T-1GBWD Used output buffers: 3 of 24 (21 max) === RTOS === Static ram: 25712 Dynamic ram: 95048 of which 0 recycled Exception stack ram used: 480 Never used ram: 9832 Tasks: NETWORK(ready,628) HEAT(blocked,1232) DUEX(suspended,160) MAIN(running,3728) IDLE(ready,160) Owned mutexes: === Platform === Last reset 03:26:30 ago, cause: software Last software reset at 2020-01-05 12:19, reason: User, spinning module GCodes, available RAM 9864 bytes (slot 1) Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d Error status: 8 Free file entries: 8 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest block write time: 0.0ms, max retries 0 MCU temperature: min 41.7, current 42.6, max 43.4 Supply voltage: min 23.9, current 23.9, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes Driver 0: ok, SG min/max 40/1023 Driver 1: standstill, SG min/max 406/1023 Driver 2: standstill, SG min/max 401/1023 Driver 3: standstill, SG min/max 0/238 Driver 4: standstill, SG min/max not available Driver 5: standstill, SG min/max not available Driver 6: ok, SG min/max 15/1023 Driver 7: ok, SG min/max 29/1023 Driver 8: standstill, SG min/max not available Driver 9: standstill, SG min/max not available Date/time: 2020-01-05 15:46:07 Cache data hit count 4294967295 Slowest loop: 6.28ms; fastest: 0.09ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Move === Hiccups: 0, FreeDm: 155, MinFreeDm: 97, MaxWait: 0ms Bed compensation in use: mesh, comp offset 0.000 === DDARing === Scheduled moves: 86200, completed moves: 86160, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 Heater 0 is on, I-accum = 0.1 Heater 1 is on, I-accum = 0.5 === GCodes === Segments left: 1 Stack records: 3 allocated, 0 in use Movement lock held by null http is idle in state(s) 0 telnet is idle in state(s) 0 file is doing "G1 X85.111 Y104.983 E1.2412" in state(s) 0 serial is idle in state(s) 0 aux is idle in state(s) 0 daemon is idle in state(s) 0 queue is idle in state(s) 0 autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 15.26ms; fastest: 0.05ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0) HTTP sessions: 1 of 8 Interface state 5, link 100Mbps full duplex === Filament sensors === Extruder 0: pos 75.23, errs: frame 1 parity 0 ovrun 0 pol 0 ovdue 0 Extruder 1: pos 227.81, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0

I dont like it all, things are not organized in any way, I just converted back

I don't use any special cable, the typical servo cable. and does not pass near any 230V cable. It is located about 30cm from the Duet3D

OK thanks for pointing me in the right direction. It was connected to E1, moved the cable to E0 now. Going to try again but I'm fairly certain that was it. And yes, the led on the board blinks along with the led on the sensor. Thanks again.

EDIT: Just to confirm, everything works now. 👍

@ericrane Please start a new thread for your issue. It isn't related to the issue described by the original poster, which is over a year old. Please see the post here about how to ask for support, eg details required etc. https://forum.duet3d.com/topic/5909/guide-for-posting-requests-for-help

Make sure you say which filament sensor do you have. Most likely, it's your wiring. Either it's connected incorrectly, or the wiring is faulty (poorly crimped terminals). Check continuity on the wires. Post your config.g so we can see how it is set up.

But please start a new thread, do not reply to this one.

Ian

@dc42,

Thanks for the advice. I will try increasing the measurement length as you suggest. My sensor is mounted ~20mm above a direct drive extruder and was flexing around a lot. I added a brace which helped a lot but am still having issue. I will try increasing the measurement length as you suggest.

@dc42 disabling the sensor during the calibration worked. But I still get occasional "Extruder 0 reports sensor not working" errors during printing. Last print was 4h in which the error appeared 2 times. Could it be the wiring? Is there a way to debug this issue further, maybe some log files i can check?