Printer dosen't start the print job correct
-
Did you recently update your firmware? What version were you running previously?
Error: G0/G1: insufficient axes homed
That would indicate that you were using a version older than 1.21 before?
From the release notes of 1.21:
On Cartesian and CoreXY printers, normal G0 and G1 moves are no longer allowed before the corresponding axes have been homed. In particular, if your homex.g, homey.g and homeall.g files raise Z a little at the start and lower it at the end, you will need to add the S2 parameter to those G1 Z moves. Otherwise the G1 Z move will be refused unless Z has already been homed and the homing macro will be terminated. If you want to allow axis movement prior to homing, put M564 H0 in config.g.
I think this may resolve your problem. You haven't posted your homing files so I can't tell if you have S2 added to your G1 moves or not.
-
@phaedrux
I was before on 2.01 RCMy homing file looks like this:
https://pastebin.com/dAjNUw6Yafter this procedure it shows all Axis are homed.
I think it could be the stall detection that causes that Problem but i'am not shure. -
Ah I see. In that case homing failing is not your issue.
Perhaps try using the 2.01 full release, to eliminate a firmware issue with 2.02 Release candidate.
Also, looking at your start script:
G21 ;metric values G90 ;absolute positioning M82 ;set extruder to absolute mode M107 ;start with the fan off G28 G92 E0 ;zero the extruded length ; ---D-Bot no Probe start G29 S1 ;G32 S2 ; --Purgeline Script start at 20x and 20y and move 80mm while prime the nozzle G1 Y20 F5000 G1 X 20 Z0.150 F5000 G1 X60 E10 F500 G1 X100 E13 F500 G1 Z0.20 ; --- end G92 E0 ;zero the extruded length again G1 F9000 ;Put printing message on LCD screen M117 D-Bot Printing...
It looks like you are in Absolute positioning mode (G90) when trying to do your purge line, when I would think you would want to be in relative positioning mode (G91). The same question applies for your extruder. Do you intend to be using relative extrusion (M83) or absolute extrusion (M82) with the slicer?
Have you tried disabled stall detection yet?
-
@phaedrux
If i disable stall detection nothing works anymore cause there are no physical Endstops anymore.The positioning for the Nozzle is absolut yes (G90) and the Extrusion aswell.
BTW. i got the issue on 2.01 aswell so i thought maybe it is fixed in 2.02 but i remember that i printed with 2.01 so maybe my
Slicer(Simplify 3D) is differten than my last (before Windows broke).Strange cause i used the last gcode to configure my profile correct. (on every gcode it lists as a comment the configuration of the Profile).
//Edit:
Ok a old gcode File that i found on my printer works so it is my Profile that has a issue BUT there is a nother Problem:
23:15:28Error: motor phase A disconnected on drivers 2It posts this every few seconds:
23:18:11Error: motor phase B disconnected on drivers 2
23:18:06Error: motor phase B disconnected on drivers 2
23:18:01Error: motor phase A disconnected on drivers 2
23:17:57Error: motor phase B disconnected on drivers 2
23:17:17Error: motor phase A disconnected on drivers 2
23:17:07Error: motor phase A disconnected on drivers 2
23:16:21Error: motor phase B disconnected on drivers 2
23:15:44Error: motor phase A disconnected on drivers 2
23:15:38Error: motor phase A disconnected on drivers 2
23:15:33Error: motor phase A disconnected on drivers 2
23:15:28Error: motor phase A disconnected on drivers 2It is connected btw.
What can/should i do?Found that so it is a Firmware Thing that i can ignore in that Version (it looks like)
https://forum.duet3d.com/topic/6707/duet-error/14 -
Those look like spurious error messages that are a known issue in the 2.02 RC release. Go back to the previous 2.01 full release or the 2.02 beta release and try again.
-
If it dosen't damage my Printer or do something else it dosen't matter right?
-
@as-3d-druck said in Printer dosen't start the print job correct:
If it dosen't damage my Printer or do something else it dosen't matter right?
The spurious messages don't matter. If you were getting them on just one phase then I would suggest you have a genuine problem; but getting them on both phases when the motor is moving slowly (e.g. the Z axis moving just a little to do bed compensation) is not unusual in this release candidate.
In previous releases, the open load detection has been disabled because of spurious indications. I was hoping to get it working in this release to help diagnose bad motor connections.
-
@dc42 and what could you say about that my printer starts and stops after my purgeline and home it self?
-
@as-3d-druck, I would need to see an example GCode file that causes that behaviour when you try to print it.
-
@dc42 Ok, here is the Thing that i tryed to print: https://cloud.as-3ddruck.de/index.php/s/pcfzPngPzMj3c3e
-
I think I see your problem.
From your gcode file:
;Put printing message on LCD screen M117 D-Bot Printing... G92 E0 G1 E-5.0000 F3600 G1 Z1.000 F1002 ; process dbot ; layer 1, Z = 0.200 M104 S0 ; turn off extruder M140 S0 ; turn off bed G91 ; use relative coordinates G1 Z0.6 F5000 ; lift nozzle by 0.6mm G90 ; use absolute coordinates G28 X0 ; home X axis G1 Y100 ; move Y axis to end position M84 ; disable motors M107 ; turn off fan T1 ; tool H0.200 W0.408 ; skirt
Right before starting the skirt under the heading process dbot layer 1, it disabled your motors and turns off the heaters and fan. It looks like maybe your end gcode script is being inserted into the start of your file.
-
@phaedrux said in Printer dosen't start the print job correct:
I think I see your problem.
From your gcode file:
;Put printing message on LCD screen M117 D-Bot Printing... G92 E0 G1 E-5.0000 F3600 G1 Z1.000 F1002 ; process dbot ; layer 1, Z = 0.200 M104 S0 ; turn off extruder M140 S0 ; turn off bed G91 ; use relative coordinates G1 Z0.6 F5000 ; lift nozzle by 0.6mm G90 ; use absolute coordinates G28 X0 ; home X axis G1 Y100 ; move Y axis to end position M84 ; disable motors M107 ; turn off fan T1 ; tool H0.200 W0.408 ; skirt
Right before starting the skirt under the heading process dbot layer 1, it disabled your motors and turns off the heaters and fan. It looks like maybe your end gcode script is being inserted into the start of your file.
Why does my Slicer this?
-
Simplify3D? Check your various gcode insertion areas. Maybe something got copy and pasted into the wrong place?
-
@phaedrux said in Printer dosen't start the print job correct:
Simplify3D? Check your various gcode insertion areas. Maybe something got copy and pasted into the wrong place?
Did that anf for some Reason i got the Endscript in the Toolchanging Section in S3D but i don't know why it was there.
Anyway thx for you're help.
Printer is now back in the Game. -
Glad it got sorted out.