homea.g not found

fcwilt

Hi,

It would seem you have defined an A axis in your config.g file (most likely location).

Whenever you define an axis you need to create the corresponding home file.

Frederick

3DPMicro

I do have an A (4th) axis (CNC) but dont use an endstop or home file with it. Just use G92 to set 'home". Maybe I never noticed the error message before. Anyway thanks for the guidance gentlemen

Phaedrux

I guess you could create a homea.g file and use it to create a manual homing file for the A axis. Allow movement of unhomed axis, then use M291 prompt command to jog the A axis to the wanted position and then G92 to set it.

Danal

Create homea.g and leave it empty.

fcwilt

@3DPMicro said in homea.g not found:

I do have an A (4th) axis (CNC) but dont use an endstop or home file with it. Just use G92 to set 'home". Maybe I never noticed the error message before. Anyway thanks for the guidance gentlemen

Just create the homea.g file and put the G92 command in it.

Frederick

3DPMicro

Damn guys. 3 great suggestions. Just have to figure out which one.

A Former User

An empty homea.g file doesn't solve the underlying problem if you do have an A axis; but putting G92 A0 in homea.g will zero the A axis as part of the homing (or as @Phaedrux mentioned with the addition of allowing you to jog the axis).

Furthermore if you do the same in homeall.g it won't ask for homea.g (unless you actually press the Home A button or execute G28 A)

For convenience I'd probably use G92 in homeall.g and M291 in homea.g

(homea.g is only called when explicitly homing A axis or after home all if homeall.g doesn't have a G0 H1 for A, or G92 (or overriden with M564) or thereabouts)

3DPMicro

Point taken. I very rarely use the 4th axis and when I do I indicate in the stock or part. There is no homing switch on it. So basically just need to have the error message go away but being able to jog after home all without having to send G92 A0 would help relieve the already arduous workload

A Former User

@3DPMicro said in homea.g not found:

basically just need to have the error message go away but being able to jog after home all without having to send G92 A0 would help relieve the already arduous workload

then put G92 A0 in both homeall.g and homea.g (the latter to allow zeroing A by using the home A button)

3DPMicro

cool. Thanks

fcwilt

@3DPMicro Hi,

While some folks optimize homeall to save time (I guess), I don't do that.

I simply have homeall call all of the single axis home files.

While this might not be as quick it also means I only have the homing code for a given axis in one file.

Frederick