Attached is the Homing Log Stack for just the A-Axis.

Perhaps this might help or not, it will start the logging within the plc and dump it out to a file called Output.log in the mach4 directory. The internal logging is a lot faster updating than this but might just take you to just before the crash.

Using the Screen Editor use the codes below.

--screen load script
local inst = mc.mcGetInstance()
mc.mcCntlSetLogging(inst, 1)
local done = ''

function WriteLog()
    local var = mc.mcCntlGetLastLogMsg(inst)
    if var == done then
    return
    else
    file =io.open("Output.log", "a")
    file:write(var..'\n')
    file:close()
    done = var
    end
end
and in the PLC Script

if testcount > 5 then WriteLog() end
Theres 2 variables being used here 'var' and 'done' just check and make sure these are not in use elswhere...

DazTheGas

I tried daz`s homeimg code with changing the code to reflect A instead of Y it worked as it should under test condition`s I could not try on the machine it was being used

I have also tried His code. that is what i had started with. The issue is not with the coding that is done by me. I understand that the coding works as it should. My day to day job is software development. The issue is when my Motor 3 is mapped to the Y axis and Motor 1 is mapped to the A axis, Homing switches wired and activated accordingly, Mach4 will go into a non-responsive state when the A axis makes contact with its homing switch during the homing sequence.

Your missing the point, we are trying to get the log so we can see what is called before it hangs.....

DazTheGas

I posted the log.

Attached is the Homing Log Stack for just the A-Axis.

The posted log is showing the estop etc,

With the log being outputed start up the machine, and click home all axis. Then we can see only what has been run in the api and motion controller befor it hangs.

The thing we need to discover is if there is something else that is causing the hang.

DazTheGas

set all other axis to home in place, then run just the A mapped as Y with no code, then with your code keeping a copy of the log each time, doing that way will show if it can be done with out code and what does or does not go wrong. same with running your code.

then the code can be compared, everything has a order to it where that order goes wrong is what is need that`s why the logging is used to find where it`s going wrong.

on what was in the log you posted it showed something when`t wrong but it had the other axis in it and calling of your code you can see where the estop was hit but it carried on if you run the code what daz posted it will still put a log out even with it crashing

Why not turn on logging and then go to the Machine Diagnostics page and just reference the A axis? You can reference axis individually on the diagnostics page.

thanks Chaoticone did not think of that one.

KingKerf please try that