Homeall file



  • ; homeall.g
    ; called to home all axes
    ;
    ; generated by RepRapFirmware Configuration Tool on Thu Apr 27 2017 06:26:16 GMT-0700 (PDT)

    ; Relative positioning
    G91

    ; Lift Z
    G1 Z5 F6000

    ; Course home X or Y
    G1 X-305 Y-305 F1800 S1
    ; Course home X
    G1 X-305 S1
    ; Course home Y
    G1 Y-305 S1

    : Move away from the endstops
    G1 X5 Y5 F6000

    ; Fine home X
    G1 X-305 F360 S1
    ; Fine home Y
    G1 Y-305 S1
    G1 Y150 X150 F6000
    M280 P3 S10 I3
    ; Move Z down until the switch triggers
    G1 Z-285 F1800 S1

    ; Absolute positioning
    G90

    ; Tell the firmware where we are
    G92 Z2.5
    M280 P3 S90 I1
    ; Uncomment the following line to lift the nozzle after probing
    G1 Z5 F100

    That is my Homeall.g file. I am having an issue with starting a print. I upload a file, 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. It does not run an autolevel either. That is with G28 in my slicers start up g-code script. If I change it to G28 X, G28 Y, G28 Z, then my printer will heat up, will home X Y and Z individually, run the autolevel and start printing. That makes me think the problem is in the homeall.g file. I don't know what in it would cause it.


  • administrators

    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?



  • 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


  • administrators

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



  • 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.



  • 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.



  • 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,



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


  • administrators

    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.



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


  • administrators

    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.



  • 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.


Locked
 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.