Ender 3 S1 Pro
klippy.log (855.4 KB)
Hello, I have spent several hours searching the web and forum for a solution and I might be missing something so I decided to query this group.
I have been getting a move out range error when attempting to start prints and I do not see anything obvious in my config or g-code that would prompt the error. I have a stock enders 3 s1 pro and have had no trouble until the past few days.
I have started using the alpha build of Cura, but I get the error on any print. Even those sliced weeks ago that had no issues.
I had the same problem recently.
Add “G90” to your Start Code after the G28 as discussed here:
Sorry, where do I put it?
The current initial code is:
; myke's Custom CoreXY Start G-code
G92 E0 ; Reset Extruder
G28 ; Home all axes
; #### Put G90 here?
G1 Z2.0 F3000 ; Move Z Axis up little to prevent scratching of Heat Bed
G1 X0.1 Y20 Z0.3 F5000.0 ; Move to start position
G1 X0.1 Y200.0 Z0.3 F1500.0 E15 ; Draw the first line
G1 X0.4 Y200.0 Z0.3 F5000.0 ; Move to side a little
G1 X0.4 Y20 Z0.3 F1500.0 E30 ; Draw the second line
G92 E0 ; Reset Extruder
G1 Z2.0 F3000 ; Move Z Axis up little …
In your Cura Printer Profile, go into “Machine Settings” and add the gcode statement:
opened 01:57AM - 13 Aug 18 UTC
closed 11:56AM - 13 Aug 18 UTC
Status: Won't Fix/Do
Type: Question
<!--
The following template is useful for filing new issues. Processing an issu… e will go much faster when this is filled out, and issues which do not use this template WILL BE REMOVED.
Before filing, PLEASE check if the issue already exists (either open or closed) by using the search bar on the issues page. If it does, comment there. Even if it's closed, we can reopen it based on your comment.
Also, please note the application version in the title of the issue. For example: "[3.2.1] Cannot connect to 3rd-party printer". Please do not write things like "Request:" or "[BUG]" in the title; this is what labels are for.
It is also helpful to attach a project (.3mf or .curaproject) file and Cura log file so we can debug issues quicker.
Information about how to find the log file can be found at https://github.com/Ultimaker/Cura/wiki/Cura-Preferences-and-Settings-Locations. To upload a project, try changing the extension to e.g. .curaproject.3mf.zip so that github accepts uploading the file. Otherwise we recommend http://wetransfer.com, but other file hosts like Google Drive or Dropbox work well too.
Thank you for using Cura!
-->
**Application Version**
3.4.1
**Platform**
Windows 10
**Printer**
Custom FDM printer (Anet A6)
**Steps to Reproduce**
Create a printer profile and go into Machine Settings and add some code to the "Start G-code" section which includes a `G91` command to switch to relative positioning. Generate the G-code and open in something like OctoPrint. Odds are the print will be off the bed. OctoPrint will usually fuss about it "too large" for the machine.
**Actual Results**
Generate the G-code and open in something like OctoPrint. Odds are the print will be off the bed. OctoPrint will usually fuss about it "too large" for the machine.
Add a `G91` command to the end of the "Start G-code" section, and it renders and prints just fine.
**Expected results**
The part should render and print just fine in 3D controller software, like OctoPrint regardless of the user added G-code leaving the workspace in relative mode.
**Additional Information**
Please add any needed commands to make sure the workspace is set correctly for the style of G-code you will be generating after the user editable "Start G-code" section is inserted.
I am using a probe that needs Z movement to make sure its probe pin is retracted properly (HallON model probe) and I felt more comfortable using relative commands and did not put it back to absolute commands (`G90`) not knowing that you required absolute positioning and did not enforce it yourself. Took me several days to figure this one out while trying to learn Slic3r which does not exhibit this behavior.
1 Like
Thanks Myke, to clarify this is a gcode issue? Nothing to change in printer.cfg?
Correct. I just made the change in Cura and didn’t touch printer.cfg.
Good luck!