insufficient axis homed when start printing

fcwilt

@jens55 said in insufficient axis homed when start printing:

I had a similar problem when I set up my Jubilee printer. It turns out that Cura inserts some commands before the Cura start code. This included selecting a tool and homing the printer.

Hmm...

I have Cura 4.10.0 and this is what it inserts in the print start code:

; Cura (Repeteir flavor - no temps)

;M109 S0                        ; set extruder temp and wait (no wait with S0)
;M82                            ; absolute E moves
;M98 P"print_begin.g"           ; invokes my print start code
;G92 E0                         ; set E position
;G92 E0                         ; set E position again (have no idea why)
;G1 F1800 E-1                   ; do initial retract

I wonder why you are seeing something different.

Frederick

fcwilt

@agileproductontwikkeling said in insufficient axis homed when start printing:

First: The printer only homes after the heaters have reached their setpoint. Not a real big issue but I hate unnecessary waiting I will have a 1000mm z-axis so homing takes a while. I guess this can be circumvented but it seems the default situation and I'm not yet comfortable enough with the whole system to alter sequences.

That is easily dealt with, usually. There are commands that start the heating process and continue and commands that start the heating process and waits for temp to be reached.

For example M104 sets the extruder heating and continues on, M109 sets the extruder heating and waits.

The is M116 which waits for all temps to reach the set point.

So the basic steps are

M104 Snnn ; set extruder temp and start heating 
M140 Snnn ; set bed temp and start heating
G28       ; home printer
M116      ; wait for extruder and bed to reach temp

Second: When the printer is already homed, for instance when starting up a second print, it will halt the print and causes the " insufficient axis homed". Of course I could restart the print and it will work but not elegant.

Something is wrong with your code if that is happening. We need to look at your various configuration files and the start of a typical print file.

Frederick

agileproductontwikkeling

So I need to figure out what homing/tool/temp settings/commands are executed where: config, start, homing, cura. For me its not completely clear yet what makes the most sense.

Anyway the main problem I had is gone: I now have a more or less working pile of parts on my desk. I'm going to build the actual printer first and work from there.

thanks so far!

fcwilt

@agileproductontwikkeling said in insufficient axis homed when start printing:

Anyway the main problem I had is gone:

So what made the problem go away?

Frederick

agileproductontwikkeling

@fcwilt Dont give the homing command when already homed. Not sure why that is a problem, but apparently it is in my case.

fcwilt

@agileproductontwikkeling said in insufficient axis homed when start printing:

@fcwilt Dont give the homing command when already homed. Not sure why that is a problem, but apparently it is in my case.

Homing when already homed should never be an issue as (one of) the first thing a G28 command does is mark the axis as un-homed.

You have something wrong in your code.

We just need to find the problem and correct it.

Frederick

jens55

@fcwilt said in insufficient axis homed when start printing:

Homing when already homed should never be an issue as (one of) the first thing a G28 command does is mark the axis as un-homed.

You have something wrong in your code.

It most certainly CAN be a problem .... see my various postings on the Jubilee printer.
A Jubilee printer can only be homed when it has no tools loaded in the tool changer. The first thing Cura does, and this is BEFORE any Cura start code is executed, is to select a tool. Generally the homing is done after that in the Cura start code.
There is no known way of bypassing the fact that Cura selects a tool even before executing it's start codes.

fcwilt

@jens55 said in insufficient axis homed when start printing:

It most certainly CAN be a problem .... see my various postings on the Jubilee printer.

You write the code that does the homing - you can code it as needed.

There is no known way of bypassing the fact that Cura selects a tool even before executing it's start codes.

How is that possible - since the code in the sliced file is doing all the work.

The first command I see Cura 4.10.0 generate is M109 S0.

When RRF processes that command it selects the tool.

The next command I see is M82 which has no effect on tools.

The third command I see is the call to my own start code where I can, if needed, de-select the tool selected by the M109.

So perhaps I am missing the problem but I just don't see it.

Frederick

fcwilt

I made one change to Cura 4.10.0 to use RepRap as the "gcode flavor" instead of Repetier.

I still am setting all temps in Cura to 0 as I don't let slicers control temps.

The only difference I see in the generated code, compared to Repetier, is a T0 as the very first command.

But the result is the same in that when my code gets executed I still can de-select the tool.

Frederick

jens55

@fcwilt said in insufficient axis homed when start printing:

So perhaps I am missing the problem but I just don't see it.

It is a bit of an esoteric issue and yes, you are missing something.
I should first mention that I use the latest Master Branch of Cura rather than plain old Cura.
What happens, even before the start code from Cura is run, is that Cura calls for a tool and then sets up temperatures for said tool and the bed. The temperature calls can be bypassed but no matter what you do, Cura calls for a tool.
Generally the Cura start code calls for homing.
The Jubilee printer can not home if a tool is mounted period. If you try to do that you get all kinds of errors. Yes, you can most certainly remove all the code that generates the errors but you can't bypass the crash that happens as a result of trying to home while a tool is physically mounted in the tool changer.

I think we are getting way too fixated on a specific setup that the OP might not even have. There are apparently a few other printers that throw errors when you try to do a home with a tool mounted but this might still not be the issue with the OP. I only mentioned this issue because I had a bit of a struggle finding why things were happening and I wanted to make some mention in this thread about the issues I encountered in case somebody searches for the same problem.

I am more than happy to discuss more details via email to clarify things for you.

fcwilt

@jens55 said in insufficient axis homed when start printing:

What happens, even before the start code from Cura is run, is that Cura calls for a tool and then sets up temperatures for said tool and the bed. The temperature calls can be bypassed but no matter what you do, Cura calls for a tool.

One quick question:

Cura has no connection to the printer so how can it do anything like calling for a tool.

Frederick

jens55

@fcwilt, when I say "Cura is calling for a tool", please read that as "the gcode that Cura generated, when executed' calls for a tool"

fcwilt

@jens55 said in insufficient axis homed when start printing:

@fcwilt, when I say "Cura is calling for a tool", please read that as "the gcode that Cura generated, when executed' calls for a tool"

Thanks.