Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

from gcode calucalted size and time wrong #1863

Closed
ManuelW77 opened this issue Apr 12, 2017 · 6 comments

Comments

Projects
None yet
4 participants
@ManuelW77
Copy link

commented Apr 12, 2017

What were you doing?

Upload a File to Octo

What did you expect to happen?

corret calculating

What happened instead?

i was wondering about the much off Printtime calculated by Octo. Now i found, that Octo is not correct calculate the modelsize.

Branch & Commit or Version of OctoPrint

Master Branch 1.3.2

Printer model & used firmware incl. version

CTC Bizer

Browser and Version of Browser, Operating System running Browser

it dosn't matter

Link to octoprint.log

it dosn't matter

Link to contents of terminal tab or serial.log

it dosn't matter

Link to contents of Javascript console in the browser

it dosn't matter

Screenshot(s) showing the problem:

i was wondering about the much off Printtime calculated by Octo. Now i found, that Octo is not correct calculate the modelsize.

This i found in all my uploaded files:

Modelgröße: 104.11mm × 52.53mm × 14719.80mm
Modelgröße: 26.08mm × 26.07mm × 3834.90mm
Modelgröße: 106.04mm × 101.93mm × 26679.82mm

I thing that is the height of the object, i haven't a printer that can print such dimensions :D
That causes completele off Printtimes. A object that takes about 2h will shown as 13h needet!

Here is a gcode file, created with S3D as example.
Rader-hinten-Manu.zip

I have read the FAQ.

@GitIssueBot

This comment has been minimized.

Copy link
Collaborator

commented Apr 12, 2017

Hi @ManuelW77,

It looks like there is some information missing from your bug report that will be needed in order to solve the problem. Read the Contribution Guidelines which will provide you with a template to fill out here so that your bug report is ready to be investigated (I promise I'll go away then too!).

If you did not intend to report a bug but wanted to request a feature or brain storm about some kind of development, please take special note of the title format to use as described in the Contribution Guidelines.

Please do not abuse the bug tracker as a support forum - if you have a question or otherwise need some kind of help or support refer to the Mailinglist or the G+ Community instead of here.

Also make sure you are at the right place - this is the bug tracker of the official version of OctoPrint, not the Raspberry Pi image OctoPi nor any unbundled third party OctoPrint plugins or unofficial versions. Make sure too that you have read through the Frequently Asked Questions and searched the existing tickets for your problem - try multiple search terms please.

I'm marking this one now as needing some more information. Please understand that if you do not provide that information within the next two weeks (until 2017-04-26 00:30 UTC) I'll close this ticket so it doesn't clutter the bug tracker. This is nothing personal, so please just be considerate and help the maintainers solve this problem quickly by following the guidelines linked above. Remember, the less time the devs have to spend running after information on tickets, the more time they have to actually solve problems and add awesome new features. Thank you!

Best regards,
~ Your friendly GitIssueBot

PS: I'm just an automated script, not a human being, so don't expect any replies from me :) Your ticket is read by humans too, I'm just not one of them.

@foosel

This comment has been minimized.

Copy link
Owner

commented Apr 12, 2017

it dosn't matter

Oh for.... I wouldn't ask for it if it didn't matter. Please do not make assumptions about what matters and what doesn't for me to analyze potential bugs - having to run after this kind of information takes away time that could better be spent on fixing issues.

foosel added a commit that referenced this issue Apr 12, 2017

Do not repeatedly apply any set offsets in the gcode interpreter
They would accumulate and cause wrong calculations

Solves #1863
@foosel

This comment has been minimized.

Copy link
Owner

commented Apr 12, 2017

Assuming you were running 1.3.2 (you didn't say) and assuming you were referring to the metadata displayed in the file list (you didn't say), the issue was that your GCODE specified a Z offset of -5mm which due to a bug was applied to all absolute positions, thus accumulating over the whole file.

I've pushed a fix to the maintenance branch (see above) that solves this and will soon also merge that to the devel branch. This will be part of the 1.3.3 release.

Marking this as solved since based on the information you provided I can only assume this was the issue you were facing.

@foosel

This comment has been minimized.

Copy link
Owner

commented May 31, 2017

1.3.3 was just released.

@foosel foosel closed this May 31, 2017

@adrianmihalko

This comment has been minimized.

Copy link

commented Apr 28, 2018

I have same problem:

Model size: 152.48mm × 170.00mm × 26.40mm
Estimated total print time: 25 minutes

I resized my model in cura to 50%, so the size should be:

screen shot 2018-04-28 at 22 43 18

Estimated time in cura is 28 minutes. Octoprint shows me Print Time: 00:12:22
Print Time Left: 27 minutes (was 40, 2 minutes ago).

@adrianmihalko

This comment has been minimized.

Copy link

commented Apr 28, 2018

The gcode zipped: cat.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.