[Possible bug] DWC Wrong Height Value
-
I noticed that there seems to be an issue with the reported height value when you are printing multiple objects in sequence, depending on the order you are printing them in.
To give an example I have 2 objects in the print. 1 is 16mm high and the other is 5mm high. If I print the 16mm one first and the 5mm second it will report a height of 5mm. Whereas if I print them the other way around it will show a height of 16mm which is the one I would suspect in both cases.
In other words, the max height value seems to always display the height of the object that is printed last.
I noticed this when I tried to write some code that would move the Z to a height that would not interfere with any of the printed objects at the end of a job. In order to do this I wanted to grab the height value of the file but because it always reports the height of the last object this isn't trustworthy enough. Ofcourse I could just make sure I always print the tallest object last but relying on me remembering that is a bad solution haha.
In the screenshot the "small" file is printing the smallest item as last where in the other file the tallest item is being printed last. Other then the order they are the exact same print job.
A possible solution could be to take a look at the
plattercomment which for instance super slicer generates, this correctly reports the tallest object no matter the order. If said comment isn't there it could fallback on the current solution
-
It grabs the height from the last command z move.
Can you share your gcode files?
-
@Phaedrux that makes sense of course when not printing each object individually but when printing each object individually it means the height displayed is different from what I would expect it to be.
I've included the 2 example files, I had to upload them to wetransfer. They where to big to upload here.
-
