πŸ‡ΊπŸ‡¦ We stand with Ukraine! πŸ‡ΊπŸ‡¦

Startup sequence

I'm new
Starting a CR-10 Max
At the beginning of every print it goes through the entire bed leveling process. How do I stop that?

Sounds like your slicer has the G29 command in the start scripts.

Unless you put effort into "saving" and "restoring" the bed leveling data, you are better off just letting the start gcode go through the entire process.

Every time you remove a finished print from the bed, you could possibly shift its position. If you don't level the bed before the next print, then a failure of that print will be the indication that you need to redo the bed leveling process.

As an experiment, use a stopwatch and time how long it takes to do the bed leveling process. Compare that to the total time it takes to do the print itself and unless you are printing a very small object, I'm guessing the leveling process is a very small percentage of the overall print time. If it is a large percentage, then you might consider printing more that one of those objects at a time.

I get that. Maybe my problem is that it is actually doing 1 thing at a time.

Heat the bed
Heat the nozzle
Check limits
Level the bed, 16 points
Then back to the center
Then back to X0 Y0
Then it goes to where the print starts

Since I am using a CR-10 Max, that is a lot of moving!

And since I’m just trying to get this thing set up, every attempts takes me 5 extra minutes. I’d think it can do more than 1 thing at a time

There are two gcode commands for heating the nozzle and two for heating the bed, M104 and M109 for the nozzle and M140 and M190 for the bed. M104 and M140 set the temperature and continue, M109 and M190 set the temperature and wait.

Check limits is probably G28 and level the bed is probably G29. Leveling the bed is most accurate when things are up to temperature so the following sequence should run as much as possible in parallel (using 200 for the nozzle and 60 for the bed temperatures).

M104 S200
M140 S60
G28
M109 S200
M190 S60
G29

If you want to try it, move the G29 to right after the G28. These commands are usually part of the start gcode that your slicer puts at the beginning of every job. Your slicer should allow you to edit the start gcode and that is where you would make the changes.

To be any more specific, we need to know what slicer you are using, and perhaps the existing start (and end) gcode. Use the </> button to surround any gcode you post.

So I found the starting G-Code, it is set in Cura

M201 X500.00 Y500.00 Z100.00 E5000.00 ;Setup machine max acceleration
M203 X500.00 Y500.00 Z10.00 E50.00 ;Setup machine max feedrate
M204 P500.00 R1000.00 T500.00 ;Setup Print/Retract/Travel acceleration
M205 X8.00 Y8.00 Z0.40 E5.00 ;Setup Jerk
M220 S100 ;Reset Feedrate
M221 S100 ;Reset Flowrate

G28 ;Home
G29 ;Auto bed Level
G92 E0 ;Reset Extruder
G1 Z2.0 F3000 ;Move Z Axis up
G1 X10.1 Y20 Z0.28 F5000.0 ;Move to start position
G1 X10.1 Y200.0 Z0.28 F1500.0 E15 ;Draw the first line
G1 X10.4 Y200.0 Z0.28 F5000.0 ;Move to side a little
G1 X10.4 Y20 Z0.28 F1500.0 E30 ;Draw the second line
G92 E0 ;Reset Extruder
G1 Z2.0 F3000 ;Move Z Axis up

Interesting. There's no temperature commands in the start gcode but there are commands that extrude filament. I'm not sure how this works.

What version of Cura? Can you please slice a small object like a 1x1x1mm cube, save the gcode, and upload it.

CCR10MAX_test cube.gcode (42.7 KB)
I made a 0.5 Cube, and sliced it
Using Cura 4.8

Ultimaker Cura 4.8.0 has a "feature" that inserts bed and nozzle temperature commands if the start gcode doesn't contain them.

If you change the following 2 lines in your start gcode to the 6 lines below that, you will overlap the bed and nozzle heating with the home and auto bed level.

G28 ;Home
G29 ;Auto bed Level
M140 S{material_bed_temperature} ; start bed heating up
M104 S{material_print_temperature} ; start nozzle heating up
G28 ;Home
G29 ;Auto bed Level
M190 S{material_bed_temperature} ; wait for bed heating
M109 S{material_print_temperature} ; wait for nozzle heating

Hey all,

Been a bit since I got back to this. And made a couple upgrades on the printer itself. I have narrowed down my problem a bit. So, all the goofy movements are still there. Now it is even printing in mid air. I banged my head for a while trying to figure it out. Finally last night I pulled up a test cube on my laptop, sliced it and used pronterface with a connection from my laptop to the printer. It worked flawless! No goofy moves, nothing printing in mid air, etc.

So my problem must be from octoprint itself. I wont be back home for a couple days, So, I am looking for input on what to start looking for in Octoprint that is causing all the BS. Any info will be appreciated.

I highly recommend that you start a new thread (and filling out a new template) for what appears to be a new issue.

1 Like