Open loop ok, no operation in Axis

Cmd-pos is following feedback in lock step.

There are no enable inputs on the drives. They are wired into limit switches which shut the drives down when triggered. And there are override buttons on the original operator panel that orverride the switches to jog off.

I'm mentioning this because I do no "enabling" of any outputs or halpins (that I'm aware of) related to drives. I guess this is all just happening in the background when I launch axis? edit: My thought process here being when does the control actually look at the current position and close the position loop to it? Do I have an error preventing this from happening?

I included some e-stop ladder when I was first putting things together and deleted those ladders. Did a variable get introduced somewhere that is related to e-stop or something? Sorry for the rambling post. Just trying to shed light on the problem.

Are my pyvcp's with my classicladder tool changer holding things up?

My ladder is running looking at a pyvcp for a tool changer value for now. I will be calling that with an M6 command ultimately.

djs14 wrote: The function boxes in the axis gui are grayed out/not clickable if that means anything..

It may mean that you haven't turned the machine on?

You need to reset E-stop and then press the "machine on" button in Axis. (or press F1, F2)

Not having linuxcnc enable the drives is a safety issue
(a bad encoder connection/ drive /controller fault could lead to a undetected runaway)
I would get this fixed first

(this will also fix the drift since the drives will not be enabled until linuxcnc is in control)

andypugh wrote:

djs14 wrote: The function boxes in the axis gui are grayed out/not clickable if that means anything..

It may mean that you haven't turned the machine on?

You need to reset E-stop and then press the "machine on" button in Axis. (or press F1, F2)

This sounds like the problem, but it didn't work. It's like the E-stop is stuck in the held position on the Axis GUI.

I noticed some e-stop halbits which I commented out, but I have a feeling one of them is necessary to enable everything.

PCW wrote: Not having linuxcnc enable the drives is a safety issue
(a bad encoder connection/ drive /controller fault could lead to a undetected runaway)
I would get this fixed first

(this will also fix the drift since the drives will not be enabled until linuxcnc is in control)

Yes understood. As noted earlier the motors are off the machine so run away is a non issue for now.

I will wire the enable outputs to break the signal from the limit switches which will work as an enable/disable of sorts. These are old Yaskawa drives that have no "enable" that I'm aware of. It looks like they relied on the limit switches to disable the drives if they ran away.