Z Axis does not move up when homing

LightBurn Hardware Compatibility
, ,
1

I have an Atomstack A70 with a movable z axis, the issue is that when I home the machine the z axis does not move up. I can move it with the move buttons and with a z home macro $HZ. The x and y axis home as they should. Thanks.

2

That’s defined in the firmware. There is no setting to change this from the outside. You would need a new firmware then (at least if Atomstack didn’t invent a new firmware setting to configure that).

3

I have seen others on their you tube channels with the same machine and theirs moves up when homing. I am also waiting a response from atomstack.

Thank you.

4

You could try this at your own risk. Works for dlc32 controller.
The command to turn on this feature: ($Homing/Cycle1=Z)or($Homing/Cycle0=Z;$Homing/Cycle1=XY)
The command to turn off this feature: $Homing/Cycle1=0

5

Thanks Dskall. I will try it.

6

I assume I type this in the console and it will then be a permanent part of the gcode for the machine? As I am sure you can tell this is new to me so I appreciate your help.

7

I don’t know what controller you have. For the dlc32 I had the Z was disabled and entering $homing/cycle0=z and then $homing/cycle1=xy enabled the Z axis during homing.

8

I tried putting these in the console and in the start gcode/end gcode under the gcode tab of device settings and it didn’t change anything.

9

In device settings is Z axis enabled

10

It was/is. I redid the z homing with adjusting the laser module height and it now homes after finishing a job. But it wont’ home to xy or go to a finished location. I have an atomstack a70 max with a small screen for running jobs via usb. On the screen after a job is complete it has a message "machine exceeds maximum range of motion. When I click close on the screen it will then home xy.

This is what is in the console after the job is finished.
ALARM:1

Hard limit triggered. Machine position is likely lost due to sudden and immediate halt. Re-homing is highly recommended.

On or near line 0:

Stream completed in 9:42

ok

Grbl 1.1h [‘$’ for help]

[MSG:‘$H’|‘$X’ to unlock]

$X

error:24

Two G-code commands that both require the use of the XYZ axis words were detected in the block.

Thank you for your assistance.