False “Object does not fit into print volume” warning from OctoPrint
Clash Royale CLAN TAG#URR8PPP
$begingroup$
Octoprint warns me that the objects do not fit into the print volume. I noticed that this happens after a power-off cycle. Since I was overly anxious until today, I always uploaded the GCode file again and it didn't complain any more.
Of course, always uploading the files again is also error prone. So today I gave it a try and simply started to print the object. As far as I can tell, it prints nicely.
Image: Octoprint saying something like "Object does not fit into print volume" in German
Is this a known bug in OctoPrint? Are my files really damaged after a power off cycle?
The values (0.00, -3.00, 0.00) seem to be constant in this error message, no matter what object I want to print.
I'm using OctoPrint in the PrusaPrint flavor and I'm running version 1.3.10 (hopefully a recent version, since I usually update). I generate the G-Code with Slic3r.
octoprint
edited Feb 18 at 19:45
Kevin Reid
1055
asked Feb 13 at 10:27
Thomas WellerThomas Weller
274111
$endgroup$
add a comment |
$begingroup$
Octoprint warns me that the objects do not fit into the print volume. I noticed that this happens after a power-off cycle. Since I was overly anxious until today, I always uploaded the GCode file again and it didn't complain any more.
Of course, always uploading the files again is also error prone. So today I gave it a try and simply started to print the object. As far as I can tell, it prints nicely.
Image: Octoprint saying something like "Object does not fit into print volume" in German
Is this a known bug in OctoPrint? Are my files really damaged after a power off cycle?
The values (0.00, -3.00, 0.00) seem to be constant in this error message, no matter what object I want to print.
I'm using OctoPrint in the PrusaPrint flavor and I'm running version 1.3.10 (hopefully a recent version, since I usually update). I generate the G-Code with Slic3r.
octoprint
edited Feb 18 at 19:45
Kevin Reid
1055
asked Feb 13 at 10:27
Thomas WellerThomas Weller
274111
$endgroup$
$begingroup$
The chance of corrupting a gcode file during upload is extremely small. If you are in fact getting errors there, you may want to check your connectors and the quality of power supply for the printer circuit board. But as the answer points out, you don't actually have a problem with volume dimensions.
$endgroup$
– Carl Witthoft
Feb 13 at 15:24
add a comment |
$begingroup$
Octoprint warns me that the objects do not fit into the print volume. I noticed that this happens after a power-off cycle. Since I was overly anxious until today, I always uploaded the GCode file again and it didn't complain any more.
Of course, always uploading the files again is also error prone. So today I gave it a try and simply started to print the object. As far as I can tell, it prints nicely.
Image: Octoprint saying something like "Object does not fit into print volume" in German
Is this a known bug in OctoPrint? Are my files really damaged after a power off cycle?
The values (0.00, -3.00, 0.00) seem to be constant in this error message, no matter what object I want to print.
I'm using OctoPrint in the PrusaPrint flavor and I'm running version 1.3.10 (hopefully a recent version, since I usually update). I generate the G-Code with Slic3r.
octoprint
edited Feb 18 at 19:45
Kevin Reid
1055
asked Feb 13 at 10:27
Thomas WellerThomas Weller
274111
$endgroup$
Octoprint warns me that the objects do not fit into the print volume. I noticed that this happens after a power-off cycle. Since I was overly anxious until today, I always uploaded the GCode file again and it didn't complain any more.
Of course, always uploading the files again is also error prone. So today I gave it a try and simply started to print the object. As far as I can tell, it prints nicely.
Image: Octoprint saying something like "Object does not fit into print volume" in German
Is this a known bug in OctoPrint? Are my files really damaged after a power off cycle?
The values (0.00, -3.00, 0.00) seem to be constant in this error message, no matter what object I want to print.
I'm using OctoPrint in the PrusaPrint flavor and I'm running version 1.3.10 (hopefully a recent version, since I usually update). I generate the G-Code with Slic3r.
octoprint
octoprint
edited Feb 18 at 19:45
Kevin Reid
1055
asked Feb 13 at 10:27
Thomas WellerThomas Weller
274111
edited Feb 18 at 19:45
Kevin Reid
1055
asked Feb 13 at 10:27
Thomas WellerThomas Weller
274111
edited Feb 18 at 19:45
Kevin Reid
1055
edited Feb 18 at 19:45
Kevin Reid
1055
edited Feb 18 at 19:45
Kevin Reid
1055
1055
asked Feb 13 at 10:27
Thomas WellerThomas Weller
274111
asked Feb 13 at 10:27
Thomas WellerThomas Weller
274111
asked Feb 13 at 10:27
Thomas WellerThomas Weller
274111
274111
$begingroup$
The chance of corrupting a gcode file during upload is extremely small. If you are in fact getting errors there, you may want to check your connectors and the quality of power supply for the printer circuit board. But as the answer points out, you don't actually have a problem with volume dimensions.
$endgroup$
– Carl Witthoft
Feb 13 at 15:24
add a comment |
$begingroup$
The chance of corrupting a gcode file during upload is extremely small. If you are in fact getting errors there, you may want to check your connectors and the quality of power supply for the printer circuit board. But as the answer points out, you don't actually have a problem with volume dimensions.
$endgroup$
– Carl Witthoft
Feb 13 at 15:24
$begingroup$
The chance of corrupting a gcode file during upload is extremely small. If you are in fact getting errors there, you may want to check your connectors and the quality of power supply for the printer circuit board. But as the answer points out, you don't actually have a problem with volume dimensions.
$endgroup$
– Carl Witthoft
Feb 13 at 15:24
$begingroup$
The chance of corrupting a gcode file during upload is extremely small. If you are in fact getting errors there, you may want to check your connectors and the quality of power supply for the printer circuit board. But as the answer points out, you don't actually have a problem with volume dimensions.
$endgroup$
– Carl Witthoft
Feb 13 at 15:24
add a comment |
2 Answers
2
active
oldest
votes
$begingroup$
That's the purging that Slic3r PE adds, the broad line of filament at the edge of the sheet. That is outside the official print volume, which triggers this error.
The G-Code generated by Slic3r PE at the start of the file contains the following lines:
G1 Y-3.0 F1000.0 ; go outside print area
G92 E0.0
G1 X60.0 E9.0 F1000.0 ; intro line
M73 Q0 S174
M73 P0 R173
G1 X100.0 E12.5 F1000.0 ; intro line
G92 E0.0
You can see that it explicitly goes to -3 on the Y axis, and then extrudes two times on a line along the X axis.
The model size detection is labeled as beta in the settings dialog. It's not very reliable at detecting stuff like this purging line outside the boundaries.
edited Feb 13 at 13:45
0scar
12.3k31647
answered Feb 13 at 10:56
Mad ScientistMad Scientist
24115
$endgroup$
add a comment |
$begingroup$
This answer is correct, it's normal for Prusa printers to purge at -3 mm on the Y axis.
This answer is an addition that describes how to get rid of the error.
- Open Octoprint web UI
- Go to
Settings->Printer Profiles - Find active profile, click on the pen icon next to it (
Edit Profile) - Go to
Print bed and build volume - Tick
Custom bounding box - Enter -3 to
Y CoordinatesMininput box - Hit
Confirm
edited Feb 18 at 22:11
0scar
12.3k31647
answered Feb 15 at 0:14
anttixanttix
1414
$endgroup$
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
return StackExchange.using("mathjaxEditing", function ()
StackExchange.MarkdownEditor.creationCallbacks.add(function (editor, postfix)
StackExchange.mathjaxEditing.prepareWmdForMathJax(editor, postfix, [["$", "$"], ["\\(","\\)"]]);
);
);
, "mathjax-editing");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "640"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2f3dprinting.stackexchange.com%2fquestions%2f8266%2ffalse-object-does-not-fit-into-print-volume-warning-from-octoprint%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
$begingroup$
That's the purging that Slic3r PE adds, the broad line of filament at the edge of the sheet. That is outside the official print volume, which triggers this error.
The G-Code generated by Slic3r PE at the start of the file contains the following lines:
G1 Y-3.0 F1000.0 ; go outside print area
G92 E0.0
G1 X60.0 E9.0 F1000.0 ; intro line
M73 Q0 S174
M73 P0 R173
G1 X100.0 E12.5 F1000.0 ; intro line
G92 E0.0
You can see that it explicitly goes to -3 on the Y axis, and then extrudes two times on a line along the X axis.
The model size detection is labeled as beta in the settings dialog. It's not very reliable at detecting stuff like this purging line outside the boundaries.
edited Feb 13 at 13:45
0scar
12.3k31647
answered Feb 13 at 10:56
Mad ScientistMad Scientist
24115
$endgroup$
add a comment |
$begingroup$
That's the purging that Slic3r PE adds, the broad line of filament at the edge of the sheet. That is outside the official print volume, which triggers this error.
The G-Code generated by Slic3r PE at the start of the file contains the following lines:
G1 Y-3.0 F1000.0 ; go outside print area
G92 E0.0
G1 X60.0 E9.0 F1000.0 ; intro line
M73 Q0 S174
M73 P0 R173
G1 X100.0 E12.5 F1000.0 ; intro line
G92 E0.0
You can see that it explicitly goes to -3 on the Y axis, and then extrudes two times on a line along the X axis.
The model size detection is labeled as beta in the settings dialog. It's not very reliable at detecting stuff like this purging line outside the boundaries.
edited Feb 13 at 13:45
0scar
12.3k31647
answered Feb 13 at 10:56
Mad ScientistMad Scientist
24115
$endgroup$
add a comment |
$begingroup$
That's the purging that Slic3r PE adds, the broad line of filament at the edge of the sheet. That is outside the official print volume, which triggers this error.
The G-Code generated by Slic3r PE at the start of the file contains the following lines:
G1 Y-3.0 F1000.0 ; go outside print area
G92 E0.0
G1 X60.0 E9.0 F1000.0 ; intro line
M73 Q0 S174
M73 P0 R173
G1 X100.0 E12.5 F1000.0 ; intro line
G92 E0.0
You can see that it explicitly goes to -3 on the Y axis, and then extrudes two times on a line along the X axis.
The model size detection is labeled as beta in the settings dialog. It's not very reliable at detecting stuff like this purging line outside the boundaries.
edited Feb 13 at 13:45
0scar
12.3k31647
answered Feb 13 at 10:56
Mad ScientistMad Scientist
24115
$endgroup$
That's the purging that Slic3r PE adds, the broad line of filament at the edge of the sheet. That is outside the official print volume, which triggers this error.
The G-Code generated by Slic3r PE at the start of the file contains the following lines:
G1 Y-3.0 F1000.0 ; go outside print area
G92 E0.0
G1 X60.0 E9.0 F1000.0 ; intro line
M73 Q0 S174
M73 P0 R173
G1 X100.0 E12.5 F1000.0 ; intro line
G92 E0.0
You can see that it explicitly goes to -3 on the Y axis, and then extrudes two times on a line along the X axis.
The model size detection is labeled as beta in the settings dialog. It's not very reliable at detecting stuff like this purging line outside the boundaries.
edited Feb 13 at 13:45
0scar
12.3k31647
answered Feb 13 at 10:56
Mad ScientistMad Scientist
24115
edited Feb 13 at 13:45
0scar
12.3k31647
edited Feb 13 at 13:45
0scar
12.3k31647
edited Feb 13 at 13:45
0scar
12.3k31647
12.3k31647
answered Feb 13 at 10:56
Mad ScientistMad Scientist
24115
answered Feb 13 at 10:56
Mad ScientistMad Scientist
24115
answered Feb 13 at 10:56
Mad ScientistMad Scientist
24115
24115
add a comment |
add a comment |
$begingroup$
This answer is correct, it's normal for Prusa printers to purge at -3 mm on the Y axis.
This answer is an addition that describes how to get rid of the error.
- Open Octoprint web UI
- Go to
Settings->Printer Profiles - Find active profile, click on the pen icon next to it (
Edit Profile) - Go to
Print bed and build volume - Tick
Custom bounding box - Enter -3 to
Y CoordinatesMininput box - Hit
Confirm
edited Feb 18 at 22:11
0scar
12.3k31647
answered Feb 15 at 0:14
anttixanttix
1414
$endgroup$
add a comment |
$begingroup$
This answer is correct, it's normal for Prusa printers to purge at -3 mm on the Y axis.
This answer is an addition that describes how to get rid of the error.
- Open Octoprint web UI
- Go to
Settings->Printer Profiles - Find active profile, click on the pen icon next to it (
Edit Profile) - Go to
Print bed and build volume - Tick
Custom bounding box - Enter -3 to
Y CoordinatesMininput box - Hit
Confirm
edited Feb 18 at 22:11
0scar
12.3k31647
answered Feb 15 at 0:14
anttixanttix
1414
$endgroup$
add a comment |
$begingroup$
This answer is correct, it's normal for Prusa printers to purge at -3 mm on the Y axis.
This answer is an addition that describes how to get rid of the error.
- Open Octoprint web UI
- Go to
Settings->Printer Profiles - Find active profile, click on the pen icon next to it (
Edit Profile) - Go to
Print bed and build volume - Tick
Custom bounding box - Enter -3 to
Y CoordinatesMininput box - Hit
Confirm
edited Feb 18 at 22:11
0scar
12.3k31647
answered Feb 15 at 0:14
anttixanttix
1414
$endgroup$
This answer is correct, it's normal for Prusa printers to purge at -3 mm on the Y axis.
This answer is an addition that describes how to get rid of the error.
- Open Octoprint web UI
- Go to
Settings->Printer Profiles - Find active profile, click on the pen icon next to it (
Edit Profile) - Go to
Print bed and build volume - Tick
Custom bounding box - Enter -3 to
Y CoordinatesMininput box - Hit
Confirm
edited Feb 18 at 22:11
0scar
12.3k31647
answered Feb 15 at 0:14
anttixanttix
1414
edited Feb 18 at 22:11
0scar
12.3k31647
edited Feb 18 at 22:11
0scar
12.3k31647
edited Feb 18 at 22:11
0scar
12.3k31647
12.3k31647
answered Feb 15 at 0:14
anttixanttix
1414
answered Feb 15 at 0:14
anttixanttix
1414
answered Feb 15 at 0:14
anttixanttix
1414
1414
add a comment |
add a comment |
Thanks for contributing an answer to 3D Printing Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
Use MathJax to format equations. MathJax reference.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2f3dprinting.stackexchange.com%2fquestions%2f8266%2ffalse-object-does-not-fit-into-print-volume-warning-from-octoprint%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
$begingroup$
The chance of corrupting a gcode file during upload is extremely small. If you are in fact getting errors there, you may want to check your connectors and the quality of power supply for the printer circuit board. But as the answer points out, you don't actually have a problem with volume dimensions.
$endgroup$
– Carl Witthoft
Feb 13 at 15:24