Closed ModischFabrications closed 6 years ago
Please provide the log files otherwise your report cannot be processed.
MF_Icon_v2.gcode is the gcode that I prepared with a M600 half way through. If needed I can upload it too, but the described behaviour can be reproduced with any file containing a M600
I don't see any issue. For the first half 3674 mm filament was used and 1443 mm for the rest.
2018-04-02 15:05:46,199 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2018-04-02 16:04:02,274 - octoprint.plugins.filamentmanager - INFO - Filament used: 3674.49209 mm (tool0)
2018-04-02 16:29:29,616 - octoprint.util.comm - INFO - Finished in 5023.431 s.
2018-04-02 16:29:32,780 - octoprint.plugins.filamentmanager - INFO - Filament used: 1443.21396 mm (tool0)
Huh, it seems that I have misinterpreted something in my client. This issue can be closed.
What were you doing?
It seems like swapping filament leads to the first difference being dropped, this is how I reproduced it:
What did you expect to happen?
I expected both filaments to be reduced in weight according to the printed amount. Ideally M600 in gcode would be detected and a change dialog would be displayed.
What happened instead?
The second filament is decremented, the first one is unmodified.
Link to octoprint.log
My installation is at home and can't be accessed, but I'm certain that this is just a missing implementation and not a bug.
Link to gcode file
Insert M600 into any random gcode, no additional dependencies needed
Link to contents of Javascript console in the browser
...?
Further information
Related to #76.
I have read the FAQ and provided all required information.