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

Erroneous Warning Message: Object doesn't fit print volume #1675

Closed
SparseTheory opened this issue Dec 26, 2016 · 18 comments

Comments

Projects
None yet
8 participants
@SparseTheory
Copy link

commented Dec 26, 2016

What were you doing?

Loading gcode print (gcode was generated by Simplify3D)

What did you expect to happen?

Print to load without warning message (bounding box of object is 70mm x 70mm x 70mm - while my printer has capacity of 200x200x200. (see attached file)

What happened instead?

Warning message:
Object doesn't fit print volume
Object in stool.gcode exceeds the print volume of the currently selected printer profile, be careful when printing this.

More
Object exceeds print volume in depth.
Object's bounding box: (0.00, 0.00, 0.00) × (195.45, 245.75, 120.81)
Print volume: (0.00, 0.00, 0.00) × (200.00, 200.00, 200.00)
You can disable this check via Settings > Features > "Enable model size detection [...]"

Note: you can ignore warning and file will print fine.

Branch & Commit or Version of OctoPrint

1.3.0

Printer model & used firmware incl. version

xyz DaVinci - which was flashed with Repetier firmware

Browser and Version of Browser, Operating System running Browser

Chrome - Version 55.0.2883.87

Link to octoprint.log

(error does not show here)
2016-12-26 03:34:59,534 - tornado.access - WARNING - 404 GET http://www.baidu.com/favicon.ico (127.0.0.1) 16.13ms
2016-12-26 04:21:18,202 - tornado.access - WARNING - 401 POST /api/login (127.0.0.1) 26.29ms
2016-12-26 04:21:41,191 - octoprint.server.util.sockjs - INFO - New connection from client: 192.168.1.178
2016-12-26 04:24:19,528 - tornado.access - WARNING - 404 GET /cgi/common.cgi (127.0.0.1) 12.86ms
2016-12-26 04:24:19,984 - tornado.access - WARNING - 404 GET /stssys.htm (127.0.0.1) 12.49ms
2016-12-26 04:24:22,448 - tornado.access - WARNING - 404 POST /command.php (127.0.0.1) 22.54ms

Link to contents of terminal tab or serial.log

n/a

Link to contents of Javascript console in the browser

See screenshot
image

Screenshot(s) showing the problem:

See screenshot

stool.zip

I have read the FAQ.

@GitIssueBot

This comment has been minimized.

Copy link
Collaborator

commented Dec 26, 2016

Hi @SparseTheory,

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-01-09 04:50 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.

@SparseTheory

This comment has been minimized.

Copy link
Author

commented Dec 26, 2016

Please see updated ticket.

@JohnOCFII

This comment has been minimized.

Copy link

commented Dec 26, 2016

@SparseTheory - Do you have any priming activity happening outside the default print area? The Prusa i3 MK2 primes outside the standard print area, and thus needs a separate custom bounding box defined in the printer profile area.

@SparseTheory

This comment has been minimized.

Copy link
Author

commented Dec 26, 2016

@foosel

This comment has been minimized.

Copy link
Owner

commented Jan 9, 2017

Something in your file makes OctoPrint's GCODE interpreter think that an extrusion happens at Y=245.75mm, which is outside your print volume. Which in turn triggers the message.

On first look I couldn't find what that is - the actual movements look well within the bounding box. I'll have to dig deeper.

@kevinkahn

This comment has been minimized.

Copy link

commented Jan 9, 2017

Just FYI I have seen this as well on a FFCP with model sliced by Simplify3D. Interestingly it only seemed to happen on 2 fairly thin models. A taller (Z axis) model didn't issue the warning whereas a model that was about 1mm high did and another about 3-4mm high did.

@foosel

This comment has been minimized.

Copy link
Owner

commented Jan 10, 2017

Found it. The culprit was a combination of a relative movement mode and a non-move G0 or G1 (e.g. to retract at the end of the print) causing relative position calculation to do utterly wrong stuff and duplicating coordinate values. This should now be fixed by the above commit. Is already pushed to the maintenance branch and will be part of the 1.3.1 release. Will also be merged into devel later.

@foosel foosel added this to the 1.3.1 milestone Jan 10, 2017

@SparseTheory

This comment has been minimized.

Copy link
Author

commented Jan 11, 2017

@foosel foosel closed this in 6e474d9 Jan 25, 2017

@fform

This comment has been minimized.

Copy link

commented Jan 31, 2017

@foosel I'm seeing this error with 1.3.1 (hadn't seen it prior with 1.2.16) using a Makerbot Replicator 2X using gcode from Simplify3d and the GPX plugin. Should I make a new issue or attach my gcode / logs here?

@kevinkahn

This comment has been minimized.

Copy link

commented Jan 31, 2017

I'm still seeing it also on the FFCP after upgrading to 1.3.1 FYI

@foosel

This comment has been minimized.

Copy link
Owner

commented Jan 31, 2017

@fform @kevinkahn example gcode files and profile settings for reproduction please, no way to determine if you are actually seeing the same issue or something else without more information than "me too"

PS: also might take a bit to check once information is there, currently down sick

@kevinkahn

This comment has been minimized.

Copy link

commented Jan 31, 2017

Sure - of course you need an example. Sorry I didn't initially send one. Here's a gcode file that caused the issue with my FFCP. It was sliced by Simplify3D if that matters and I can send the stl if you need it as well. No rush on this at all since it doesn't really impact in any way given you can print anyway. Just figured you'd want to know the behavior was still occurring. Thanks.

bezelv4top.zip

@SparseTheory

This comment has been minimized.

Copy link
Author

commented Feb 1, 2017

@fform

This comment has been minimized.

Copy link

commented Feb 16, 2017

@foosel Here's a gcode file that gives me this error but prints fine
https://gist.github.com/fform/908a7c448a307f5a81ec4952650f8531

It's a Makerbot Rep 2X so the platform is 246mm x 152 mm x 154mm (xyz) and says that in the printer profile settings. This error only started with 1.3.1 (I came from 1.2.16). Even the same gcode files that I used on the old version show it and didn't before.

@Cyphen-Cyn

This comment has been minimized.

Copy link

commented Jul 29, 2017

Bed_Level_Calibration.txt
i have the same issue here is the gcode provided below. The printer is the Replicator 1 dual.

@Kunsi

This comment has been minimized.

Copy link

commented Jul 30, 2017

Please only report bugs related to latest release of OctoPrint. 1.3.1 is outdated, and 6.3.1 isn't even a valid verion number.

@Cyphen-Cyn

This comment has been minimized.

Copy link

commented Jul 30, 2017

ill post a new one, not sure where you got 6.3.1 since i never posted a version number.

@foosel

This comment has been minimized.

Copy link
Owner

commented Aug 21, 2017

@Cyphen-Cyn

since i never posted a version number

Indeed you didn't. You should have though ;) So what version are you seeing this on? Also please provide your printer profile information (bed width, depth, height & if configured custom bounding box values).

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.