@rkaronde Update after using this for over a month.

• Had 0 false triggers

• Twice caught actual issues, one was filament grinding leading to no movement. The other was actual jam. Was able to resume the print with grinding issue. For jam had to cancel the print, but saved a lot of time

• Have printed PLA, PETG, TPU, Wood fill. Different color (but really that does not matter). It is good to see different material being tracked well.

• Reprinted the Axel in Prusament ASA Galaxy Black. This improved the range reported to be more consistent 215-230% over really long prints as well.

@cncmodeller You can also try the iOS app.

The app does not allow any actions so should help with the view only aspect.

https://apps.apple.com/gb/app/duet-app-control/id1548032260

@fart_plume Can you provide more details on which filament monitor is being used, and how it is mounted?

Also did you follow the instructions here to make sure you have the right parameters set for M591?
https://duet3d.dozuki.com/Wiki/Connecting_and_configuring_filament-out_sensors

@hekav What gcode is run at the end of the print? Anything from slicer or stop.g file?

Are there any more updates on when this will be available?

@fcwilt Adhesion is not a problem, and the first layer speed is slow 20mm/s.
Monotonic is just rectilinear if there are no other patterns in the first layer.

I used Hilbert Curve for the first time because I wanted to make the infill start from left side and go to right to make sure this is not an issue with bed leveling.

Check out this remix of the excellent design by Fractalenigneer to use a Duet3D Laser Filament Monitor.

https://www.thingiverse.com/thing:4796741

The filament tracking works well, and the readings during a long print were consistent between 190%-210%

@petriheino You can send M114 to get the current motor positions. This includes the step counts for each stepper motor and the bed correction applied.

I remixed the design by Fractalengineer to use the Duet3D Laser Filament Monitor, and it seems to be working well.
https://www.thingiverse.com/thing:4796741

@dc42 Thanks for the suggestions.

• Probing is being done after both then bed and hot end are upto temp. I have also tried probing with a 5min wait after both hot end and bed are heated.

• Once I get G30 S-1 at various points and find the difference in trigger heights, is there a way to use that information?

I think the X gantry has a sag, and that is why I put the Z Probe on a X=0 offset, but that did not seem to help.

@o_lampe Thanks. I will see if the Z belt path can be changed as you suggested.

I did a M122 after first layer was done, and before print ends, and the drag did not show any skipped steps.

@phaedrux Checked the grub screws again, and they were tight.

@tmicke Yes, the bed is clean.

The bed has PEI steel sheet on it.

With all the tweaking to solve this I do sometimes get finger prints/oil on the bed.
I normally just wash with soap and water.

@fcwilt First layer speed is 20mm/sec
First Layer height is 0.2mm

In a post above I have attached screenshots of most of the slicer settings.

@phaedrux Yes the cooling fan is OFF for the first layer

The first layer extrusion width is 0.42mm (nozzle is 0.4mm), should I try a different extrusion width?

I will try upping the temps.

Thanks

@engikeneer Fair question.
Except for the cooling duct and PINDA holder this printer does not use any plastic parts, it is all metal.
https://seckit3dp.design/kit/sk-go2-essential

@o_lampe I have not heard any skipping, not sure if there is any way to measure the skipping.

Also in the middle of the bed the Z motors don't actually have to move since the bed is pretty flat. I also marked the Z motor pulley with a Sharpie and it does not move from the initial position printing infill in the center of the bed.

This is a CoreXY with bed moving up/down, so if Z is stable then I would think the X gantry is somehow moving up (not sure how that can happen). I also did the bedlevel_nozzel print suggested by Phaedrux and that stuck well all through.

The reason I am trying large flat full infill print as test is because I ran into this issue when printing large footprint models/STLs and got into debugging.

I am going to recheck for any mechanical issues.

@phaedrux

Printed without an issue.
The lines are pretty well stuck to the bed, and I could see the Z motors move when printing near the bump in the front part of the bed.

@hekav What gcode is run at the end of the print? Anything from slicer or stop.g file?