DWC (3.2) not showing object height (might be DSF related)
Every now and then, I come across .gcode files where the object height isn't shown in DWC. Sometimes this is because of a change in my slicer (cura 4.8 now), but I've changed so many things for my printer in the past few days that I don't know what to point at.
This is being uploaded to DSF 3.2 (RRF 3.2) with DWC 3.2. The layer height, filament usage and slicer estimated print time are all showing up, but the "object height" isn't (which also prevents "layer" based time estimations when printing.)
Other files sliced with the same slicer and similar settings work fine. I'll attach a .zip file (renamed to add a "gcode" extension to make the board code happy) containing two gcode files. Both are sliced with Cura 4.8 and they are using similar settings. (At the very least, the startup and ending scripts are identical.)
One shows a layer height in DWC, and one doesn't.
I'm unable to test this with RRF 3.2 (standalone.)
When opening this attachment, please remember that it's really a .zip file containing gcode files (and not a gcode file.) Just rename it to drop ".gcode" from the filename.
One thing I note is the file size. 7mb vs 16mb. I think there may be a file size limit beyond which it doesn't try to scan the whole file for certain details. But @chrishamm would have to clarify.
The irony is that cura (and likely other slicers) leave comments in the gcode file with the max Z height printed.
RRF (and DSF) scan the gcode files for comments like this for other variables already. For example, slicer estimated print time, layer height, etc.
Here's a smaller 7MB gcode file that also doesn't show a layer height in DWC (via DSF.) It's using the same slicer settings.
As with the previous upload, the file is actually a .zip file, but the extension changed to make the forum software happy. Download, change the extension to .zip, and the gcode is within.
I'll take a closer look a bit later.
Odd. After I started printing the smaller (7MB) file, the job height has shown up in DWC. The larger (16mb) file was printed, but the job height never showed up.
Maybe I'm just losing my mind.
Well that scan isn't instant, so maybe it hadn't done it yet on the smaller file yet. I'm not exactly sure of the inner workings there.
The last G0/G1 ... Z code is too far from the end of the G-code file (-418284 chars). DSF scans only the last 256KiB (~262144 chars) and RRF scans even less. But you can increase this limit in
FileInfoReadLimitFooter. If you double that value, it will scan the last 512KiB which would suffice for your particular file. Note that file info parsing may take longer though.