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

SparseTheory opened this Issue Dec 26, 2016 · 8 comments


None yet

5 participants

SparseTheory commented Dec 26, 2016 edited

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.

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


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 ( 16.13ms
2016-12-26 04:21:18,202 - tornado.access - WARNING - 401 POST /api/login ( 26.29ms
2016-12-26 04:21:41,191 - octoprint.server.util.sockjs - INFO - New connection from client:
2016-12-26 04:24:19,528 - tornado.access - WARNING - 404 GET /cgi/common.cgi ( 12.86ms
2016-12-26 04:24:19,984 - tornado.access - WARNING - 404 GET /stssys.htm ( 12.49ms
2016-12-26 04:24:22,448 - tornado.access - WARNING - 404 POST /command.php ( 22.54ms

Link to contents of terminal tab or serial.log


Link to contents of Javascript console in the browser

See screenshot

Screenshot(s) showing the problem:

See screenshot

I have read the FAQ.


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.


Please see updated ticket.


@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.

foosel 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.


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 foosel added a commit that referenced this issue Jan 10, 2017
@foosel Fix model size calculation during GCODE analysis
  * Properly handle G0/G1 with no X, Y, Z coordinates in relative mode
    instead of duplicating coordinates - should fix #1675
  * Only take move commands with X, Y, Z coordinates into account for
    model size calculation - this makes our internal GCODE analysis behave
    like the GCODE viewer's analysis and produce the same model size. The
    downside is that extrusions on the origin are no longer taken into account
    for checking if a model is within bounds of the print bed, but that should
    hopefully not produce any issues in the real world.
foosel 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment