Laser Filament Monitor - test results

dc42

I used cotton buds and isopropyl alcohol to clean the image sensor. AFAIR this is close to what the manufacturer recommends.

wilriker

@dc42 Thanks, will do it like that then.

dc42

PS - the manufacturer says you must not squirt alcohol on the image sensor because it could get inside. So moisten the cotton bud with alcohol and then use it to gently wipe the sensor.

wilriker

@dc42 said in Laser Filament Monitor - test results:

PS - the manufacturer says you must not squirt alcohol on the image sensor because it could get inside. So moisten the cotton bud with alcohol and then use it to gently wipe the sensor.

Did it like that. Sensor seems to be clean now. I have not printed anything yet but the status gives a lower brightness than before. No idea if that is somehow related.

Also did a first print with the internally cone shaped housing and the results are worse than with the default square window and open top. Not much worse but measurable. See my Google Spreadsheet for details.

wilriker

And a second print with the cone-housing. Again slightly worse than the straight square open-window version.

I printed @T3P3Tony's housing with divergence today but when I tried to mount it I noticed that it does not fit. Has there been a rearrangement on the PCB at some point in time? Because the window for the sensor is much to far down. I took a photo with mounting holes aligned because they fit:
housing comparison

Left is Tony's design, right is my cone-shaped based on @dc42's version on Thingiverse.

wilriker

@wilriker said in Laser Filament Monitor - test results:

the straight square open-window version.

Can I get a patent on this term - or better word-spaghetti?

T3P3Tony

@wilriker that is very odd - maybe i uploaded the wrong version i need to check this when i get a chance!

wilriker

So, while porting @T3P3Tony's changes to get a diverging light path into my "fork" of @dc42's OpenSCAD file I went back to the original housing and now with the cleaned sensor this gave the best results so far. min/avg/max where about 2% above the average for all of these values.

I modified my Spreadsheet to include some color coding now. Green means greater or equal to the average in that column, red means below average.

The print that had this very good measurements was the new housing with diverging light path so I am going to switch housings again tonight.

wilriker

@t3p3tony said in Laser Filament Monitor - test results:

@wilriker that is very odd - maybe i uploaded the wrong version i need to check this when i get a chance!

I just checked the documentation page and the screenshots you exported from OpenSCAD on this page also show the sensor window being offset from the mounting holes.

wilriker

Last test with black PLA is done and entered into my Spreadsheet. This was done with the diverging housing and it was a tiny bit below the quality of the default housing.

I now loaded grey PLA and also recalibrated my steps/mm (they were to low). I did not do this with the black PLA but I think this would only introduce a relative shift because all tests with black PLA were performed with the same steps/mm. I still have the diverging housing mounted and will use it to set a baseline for the grey PLA.

wilriker

Added some results for the grey PLA now to my Spreadsheet. AVG and MAX values are somewhat consistent (among all results for grey PLA) though still wider spread than with black PLA. The MIN values however have an enormous range.

I will switch back to the straight housing tonight and see how this influences the results.

keyz182

Hey, sorry, work has been busy for me, so I've only now had a chance to get back to printing. I'm still finishing off a run of parts I need that are in Spannerhands Yellow translucent PETG, which is a far cry from the Black PLA requested! Here are the sensor readings for that anyway:

M591 D1
Duet3D laser filament monitor on endstop input 4, disabled, allowed movement 30% to 100%, check every 3.0mm, current position 9.0, brightness 82, shutter 13, measured minimum -22%, average 30%, maximum 92% over 8353.5mm

Once these are printed, I'll get the black PLA running

wilriker

@keyz182 You should print with whatever you just print. Only the sensor housing is supposed to printed in black PLA.

keyz182

@wilriker As usual, I've misread something then! I really should pay more attention

tinkerz

Hey all, been a bit since I was here. Getting ready for our local MakerFaire but had the SD card on the Duet die today so I ended up with a pre-filament sensor backup config and had to come get the filament sensor running again.

Tony, wanted to share the results I do have, I haven't updated (completed all the columns) but it's a living document and will get updated from time to time. Hardest part is remembering to do a M591 before hitting print again. Doh. Feel bad I keep forgetting it. Hmm, maybe I need a sticky not on the PanelDue.

Anyways results doc is here:
https://docs.google.com/spreadsheets/d/1yy3DLxXhCFD81EiPyyuIEZaPnIgQgkvuVNcFQiZ7ceU/edit?usp=sharing

Tinkerz

wilriker

@tinkerz said in Laser Filament Monitor - test results:

Hardest part is remembering to do a M591 before hitting print again. Doh. Feel bad I keep forgetting it. Hmm, maybe I need a sticky not on the PanelDue.

I put it in my end codes, so I cannot forget it.

keyz182

I have a suggestion for the M591 command. I did look at adding it myself, but having issues getting the firmware to build.

The suggestion is two-part:

Add a parameter to set the filament name going through the sensor
Add a parameter to append data to a CSV file, using the set name as the first col.

That way, we can add start and end GCode in our slicer start+end code per filament. Start code would have the settings for that filament with the name, end gcode would then add data to the CSV file. That way, data gets built up over time without thinking about it.

T3P3Tony

@keyz182 thats a really good idea. @dc42 can we add this to the firmware wish list, maybe naming within M591 or integrate with the ecisitng filament system but then the output via the logging subsystem?

tinkerz

@wilriker In your end codes you say, then where does the response show up? Is it on the console page of the WebUI or console of the PanelDue (output is limited to 100 chars so the real data gets cut off doing it here).

Thanks,
Tinkerz

tinkerz

@wilriker disregard, wrote a quick gcode file and figured it out, comes out on the WebUI. Perfect. Adding to end scripts. Now we just need logging.

Tinkerz