search

malnvenshorn / OctoPrint-CostEstimation

OctoPrint plugin to display the estimated print cost for the loaded model
GNU Affero General Public License v3.0
23 stars 19 forks source link

No cost displayed instead Cost: no filament from meta #34

Open wormiedk opened 3 years ago

wormiedk commented 3 years ago

I get a message which I am unsure how to fix: Cost: no filament from meta

I am using prusaslicer for slicing my gcode and uploading using the api.

JonasZaverka commented 3 years ago

I have the same issue.

EricKrohnfeldt commented 3 years ago

I have same issue

riccardo74 commented 3 years ago

same issue

Torrax commented 3 years ago

Same issue, is this getting fixed?

Edit: Have tried Simplify 3D, and Cura as well. Uploaded the File, loaded it and waited for the analysing to complete. The whole time it just said "Cost: no filament from meta".

Louisianapilot commented 3 years ago

Same issue, never works for the first time printed. Used three different browsers, reboot rpi, reboot octoprint. "Cost: no filament from meta" Cura has time, weight and length in the gcode.

Jayraydee commented 3 years ago

Same issue, might be related to file size? It works on some of my smaller print files

marcelsavegnago commented 2 years ago

Same issue.

MetroLab-Berlin commented 2 years ago

I have same issue

Required Filament unknown Ungefähre Dauer: - Kosten: no filament from meta Dauer: 02:18:09 Verbleibend: 06:40:48 ● Gedruckt: 5.3MB / 21.1MB Current Height: 5.9 / -mm Layer: 96 / 373

Oninaig commented 2 years ago

Same issue. Only seems to happen on large file size prints.

jet8300 commented 2 years ago

I have this same issue. Has anyone found a fix? Cura was working fine but I recently switched to superslicer and now I get this error.

sergey08 commented 2 years ago

I have installed plugin now, and sam error

stforhub commented 2 years ago

Please check.

"In my case this was indeed caused by the PrintTimeGenious plugin. To resolve this, open PrintTimeGenious settings and enable "Enable OctoPrint's built-in analyzer (slow and unnecessary)". This allows the metadata file to be created."

https://githubmemory.com/repo/OllisGit/OctoPrint-CostEstimation/issues/9

sym0nd0 commented 2 years ago

Please check.

"In my case this was indeed caused by the PrintTimeGenious plugin. To resolve this, open PrintTimeGenious settings and enable "Enable OctoPrint's built-in analyzer (slow and unnecessary)". This allows the metadata file to be created."

https://githubmemory.com/repo/OllisGit/OctoPrint-CostEstimation/issues/9

Thanks, this sorted it for me.

MetroLab-Berlin commented 2 years ago

I was able to fix my error. My Octopi system was based on 17.x with an update to 18.x. After a sudo apt-get update && sudo apt-get upgrade, the OctoPrint CostEstimation plugin works as it should again. I assume the developer of the plugin doesn't use the standard Octopie image, but a more recent Linux system on which he tests the plugin. Maybe that's where the error comes from.

mdziekon commented 1 year ago

Please check.

"In my case this was indeed caused by the PrintTimeGenious plugin. To resolve this, open PrintTimeGenious settings and enable "Enable OctoPrint's built-in analyzer (slow and unnecessary)". This allows the metadata file to be created."

https://githubmemory.com/repo/OllisGit/OctoPrint-CostEstimation/issues/9

This worked for me as well, however the original analyzer is rather slow. As an alternative, one can enable Analyzers > Marlin firmware simulation (much faster than the original analyzer), which seems to work just as well in terms of allowing cost estimation to work correctly.