OllisGit / OctoPrint-DisplayLayerProgress

OctoPrint-Plugin
GNU Affero General Public License v3.0
120 stars 24 forks source link

Height / Total Height issue #246

Closed nilshomeier closed 2 years ago

nilshomeier commented 3 years ago

Hi!

I've got an issue with the height reporting of the plugin. It seems as if its showing the current layer divided by 10 as current height and no total height at all. I'm using Octoprint 1.7.0 on octopi 0.18.0 and plugin version 1.27.1. Slicer is Superslicer 2.3.57.

Thanks!

DisplayLayerProgress_1 FlowTest_0.20mm NORMAL - PLA_extrudr NX2_10m (1).gcode.zip

nilshomeier commented 3 years ago

I've also enabled debug. Maybe it helps?

plugin_DisplayLayerProgress_events.log

OllisGit commented 3 years ago

Hi @nilshomeier, the max height of the print is analysed by OctoPrint and stored in a file called .metadata.json located in the upload folder. Should looks like this:

    "FlowTest_0.20mm_NORMAL_-_PLA_extrudr_NX2_10m_(1).gcode": {
        "hash": "8ecf4349ea8f4e5ad19e4574759ad45cd5b93463",
        "display": "FlowTest_0.20mm NORMAL - PLA_extrudr NX2_10m (1).gcode",
        "analysis": {
            "printingArea": {
                "maxX": 168.909,
                "maxY": 164.849,
                "maxZ": 2.2,
                "minX": 10.0,
                "minY": 4.0,
                "minZ": 0.2
            },
            "dimensions": {
                "depth": 160.849,
                "height": 2.0,
                "width": 158.909
            },
            "estimatedPrintTime": 432.73752605944816,
            "filament": {
                "tool0": {
                    "length": 510.80624000001194,
                    "volume": 1.2286329909156446
                }
            }
        },

If the analyse is missing, then please check the "Feature" settings image

Then it should looks like this image

nilshomeier commented 2 years ago

Thanks! Apparently it has to be set to "Always". Mine was set to "Only when idle". It now works as it should!

luizbgomide commented 2 years ago

@OllisGit I'm also having this issue of DisplayLayerProgress reporting "-mm" as total height, but I'm not sure what is causing it.

The model has the information required in the Gcode viewer: image

I've set Analyse Gcode to always. But still it says analysisPending: false??

 "TWOTB_Octopus_sup_v5.6.gcode": {
    "hash": "2f6a3476e655891adf329941858786534a137237",
    "analysis": {
      "analysisPending": false
    },
    "thumbnail": "plugin/UltimakerFormatPackage/thumbnail/TWOTB_Octopus_sup_v5.6.png?20220106211342",
    "DisplayLayerProgress": {
      "totalLayerCountWithoutOffset": "165"
    },
    "thumbnail_src": "UltimakerFormatPackage",
    "dashboard": {
      "layer_move_array": "[7, 5621, 5791, 5853, 6393, 6395, 4299, 4637, 4653, 4713, 5008, 5007, 5051, 5122, 5222, 5592, 5208, 5357, 5503, 5066, 5063, 4784, 4760, 4913, 4616, 4408, 4054, 4193, 3937, 3628, 3122, 3153, 3084, 2682, 2455, 2466, 2490, 2377, 1962, 1645, 1406, 1432, 1173, 1023, 883, 587, 423, 344, 353, 326, 359, 303, 287, 248, 231, 220, 225, 259, 269, 285, 294, 311, 303, 292, 277, 284, 262, 285, 280, 271, 254, 255, 232, 236, 307, 359, 362, 325, 298, 521, 473, 452, 476, 475, 461, 430, 308, 303, 288, 288, 324, 359, 398, 459, 358, 313, 290, 293, 338, 346, 367, 369, 288, 264, 242, 242, 287, 294, 283, 330, 268, 221, 260, 253, 277, 283, 256, 308, 215, 187, 185, 187, 238, 243, 241, 274, 196, 162, 159, 158, 200, 200, 195, 230, 157, 127, 122, 123, 161, 159, 160, 190, 143, 100, 99, 95, 124, 127, 399, 388, 363, 359, 339, 296, 314, 296, 260, 256, 211, 197, 147, 84, 71, 61, 54, 34, 36]",
      "filament_change_array": "[]"
    }

Any thoughts?

OllisGit commented 2 years ago

hmm..I searched the OP-Sourcecode for "analysisPending" value, but without success. Which version of OP do you use?

Btw. please raise a new issue (with attached gcode and octoprint.log), because this one is closed.

luizbgomide commented 2 years ago

@OllisGit nevermind. I managed to "fix" the issue. I removed PrintTimeGenius and it all worked.

So I cleaned all its data, reinstalled print time genius and now everything is working just fine... Somehow PrintTimeGenius was hijacking the analysis and never actually returning.

OllisGit commented 2 years ago

Good to know, thx. Have a nice day!