Spinx1 to 7i85

Actually, you are really close...

The names=.... pid.0, pid.1 in the first HAL file is a clever way to make things work. All you need to do now is remove the loadrt pid from the spindle HAL file.

All instances of a component normally have to be loaded at the same time. There is a way round that using two-pass scanning.

Odd that the addf didn't work. Is there really as space in "servo- thread" ? There shouldn't be.

As a general rule, commenting-out a HAL line just defers the problem. You need to work it out, not mask it.

One problem is that every instance of each module type needs to be loaded at the same time, which somewhat limiting. You often need to go back to an earlier-loading HAL file and add some extras.

There is the option to name each component instance and use two-pass processing. It's nice, if you start off that way.
linuxcnc.org/docs/2.7/html/hal/twopass.html

andypugh wrote:

That pin will exist in the next 2.7 release. (I thought it was due in 2.8, until I checked)

This turns out to have been an accident, the orient.0.is-oriented pin won't exist until LinuxCNC v 2.8.

OT-CNC wrote:

Is there really as space in "servo- thread"

No , just a typo me trying to explain where to look in the hal. .

Well, actually, it is a _missing_ space that is the problem.

#addf abs.0.servo-thread

should be

addf abs.0 servo-thread

ie, add the abs.0 function to the servo-thread.

OT-CNC wrote:

Thank you, you saved me a few hours staring at the screen to fix that line.
It loads up but I'm still not getting spindle motion. I'm not seeing a status change on the spinx for ccw rotation. CW led is lit, also no enable or pwm led lit.

Time to fire up halmeter and see what is happening. You can start at either end, but I would make sure that the pwmgen.enable pin is going true when the spindle is on, for example.

(You can get halmeter from the Machine menu, it lets you look at signals and pins).