@bugpwr Yay! The other 2.85mm filament user! I trust that, like me, everyone you know who switched to 1.75mm gave you their old filament, and you just can't bring yourself to throw it away? I'm still trying to get through my stock, some of which is 6-7 years old, and needs a bit of drying before use!

Ian

When you print from DWC the print jobs are uploaded to the internal SD card. So you're fine. The only time prints occur without the SD card is when they are sent from a gcode streamer over USB, like Octoprint, or direct connection to a PC with Simplify3D, for example.

@timschneider said in Sensorless Filament Monitor:

Just to get you right, you are speaking about an extruder pushing 1.5 meter filament per 15 second?

DOH! I was not clear. It's not 1.5M of filament (inbound to the extruder) in 15 seconds, but 1.5M outbound from the nozzle. So the part will be missing something.

Regarding an interface in RRF - I'm not aware of any gcodes or object model properties that would give a current value. I don't know how the board enforces motor current limits, but if it's done in fw, then there might be a way to get it. I guess it would be possible to add a current sensor.

An interesting, but off topic discussion would be about making a list of the typical things that can go wrong during a print, the action that a user would take if they were present (and noticed), and whether it's possible to monitor in a way that would allow the action to be taken automatically. The present topic is one example about "end of filament", and/or "clogged nozzle" and/or "too-low extruder traction on fialment".

I am back with the actual results:

download.png

I ran the exact same GCode with M221 and M592 enabled and measured all prints again.

There seems to be an effect there, at least the 10-30 mm/s range does look flatter to me. But it is hard to say anything definitive compared to the measurement noise.

On the other hand, if 90 mm/s print speed (~10 mm³/s flow rate) is a hard maximum for the V6 hotends increasing the extrusion rate should not really do anything there. So maybe my calibration routine is somewhat flawed.

@dc42
at my first try, the sensors didn´t work(3.3beta1/3). One day later, without any changes they did work(3.3beta3and 3.3RC1). Since then they do work and only the M122 readout is wrong(3.3RC1).

@dc42 Thanks for pointing that bit out. I had missed that on the docs site. I filed it down some and it seems to be at a more acceptable range.

@dc42
Thanks. Using duet maestro. Using the E1 and E0 stops.