Homeall file

dc42 · 18 Nov 2017, 09:53

I don't see anything wrong with that file, although you are using an unconventional method of Z homing with what I presume is a BLTouch.

Does G28 work if you send it for the console?

vhoward · 18 Nov 2017, 16:53

Yes, it does work. It's just that in my slicer start g-code script, If I specify G28 only, then when I start a print, the printer heats up, then it homes everything and then it thinks it's done and turns the heaters off. But if I specify G28 X, G28 Y, and G28 Z, then it will heat up, home everything, auto level and then start printing. The only difference is in one script I don't specify each individual axis and the other script I do. I just assumed it had to be the homeall file. I don't have this issue with the slicer and my 3 other printers

dc42 · 18 Nov 2017, 17:07

Please post the first 50 or so lines of the gcode file with the G28 that causes a problem.

deckingman · 18 Nov 2017, 17:13

That's very strange. I guess the obvious question is are there any differences between homez.g and the Z homing section of your homeall.g? Perhaps also post you slicer start g-code in case one of us can spot something that you may have missed?

Edit. Typing at the same time as David.

vhoward · 18 Nov 2017, 20:43

My start g-code script in my slicer that gives the problem is
G28
G32
That's all I have for a start script. That's the one where it heats up, homes everything and then shuts off.

The start g-code script that does not give me a problem is:
G28 X
G28 Y
G28 Z
G32

That one heats up, homes everything individually, runs an auto level and then starts printing.

I'll have to go down and slice an stl into gcode using the defective start script to post the first 50 lines because I deleted that one.

Crash69 · 18 Nov 2017, 22:41

the heaters heat up, then the printer homes every thing and then stops and the heaters shut down and the printer reports it is finished.

I had a very similar issue on mine after upgrading to 1.19. Mine would heat up then start to go through my startup script, then stop.

Just in case it helps you identify your issue, what I found was in my startup script I had a comment that had an open-bracket and close-bracket in it, and it went over two lines.. removing the unintentional carriage return so its only on one line OR removing the open & close brackets in the comments fixed the issue.

here is my original startup script.. its the 3rd line (M106) command that caused the issue.

G32 ; Calibrate prior to print…
M564 S0 ; allow movemount outside printable area for purge
M106 S40 P2 ; turn on led light (255 is full bright
40 is dim)
G0 Z5 X-60 Y-132 F5000 ; raise up and go off the edge of the bed for a purge
G1 E15 F400 ; purge
G0 Z0.3 ; drop to bed height ready for a wipe
G1 X-10 E20 F400 ; Extrude 20mm of filament in a 5cm line at speed of 400
M564 S1 ; limit to print area again now purge complete
G92 E0 ; zero the extruded length
G1 E-1 F800 ; Retract a bit
G1 X15 -0.3 F3000 ; Quickly wipe in another 2.5cm with some retraction then ready for print.

changing it to:

G32 ; Calibrate prior to print…
M564 S0 ; allow movemount outside printable area for purge
M106 S40 P2 ; turn on led light 255 is full bright
40 is dim
G0 Z5 X-60 Y-132 F5000 ; raise up and go off the edge of the bed for a purge
G1 E15 F400 ; purge
….

worked fine.. and also changing it to:

G32 ; Calibrate prior to print…
M564 S0 ; allow movemount outside printable area for purge
M106 S40 P2 ; turn on led light (255 is full bright 40 is dim)
G0 Z5 X-60 Y-132 F5000 ; raise up and go off the edge of the bed for a purge
G1 E15 F400 ; purge
…

works fine.. I didnt even realise I had a new line halfway through the comment which is just poor techinque anyway,

vhoward · 19 Nov 2017, 00:49

Except that my start up script is what you see above. No open brackets. Thanks.

dc42 · 19 Nov 2017, 08:13

I spotted the problem in your homeall.g file. It's this line:

: Move away from the endstops

The colon at the start should be replaced by a semicolon.

vhoward · 19 Nov 2017, 20:09

OK. I'll change it. I didn't even spot it.

dc42 · 19 Nov 2017, 21:25

AFAIR there was a bug in configtool that put the colon there instead if the semicolon, and that bug was fixed a few weeks ago. I guess you generated that file before configtool was fixed. I'm sorry about that.

vhoward · 20 Nov 2017, 02:22

Not a problem. The file for this machine was generated last year. I have been running it homing each axis separately for that long. Now I am trying to work out the bugs. Been learning a lot the last couple of weeks between reading and asking questions here.