configuring a "spindle-on" output

I am a newbie, configuring my Fireball V90 with a Super-PID speed controller. I used stepconf to add a PWM output for speed control. This worked, but did not provide for the separate "run" signal needed by the Super-PID. After considerable research, I found a solution that works, but it seems overly complicated. Is there a simpler solution? I added the following to custom.hal:

# parallel port pin 16 is connected to the "run" pin on the Super-PID.
# the following causes that pin to be lo when the AXIS spindle button (motion.spindle-on)
# is "on" and hi when the AXIS button is "stopped." The two "unlinkp statements were
# needed because the existing HAL connects motion.spindle-on to pwmgen.0.enable.
# The new code re-connects these, but also connects them to not.0.in.
loadrt not count=1
addf not.0 servo-thread
unlinkp motion.spindle-on
unlinkp pwmgen.0.enable
net spindle-power <= motion.spindle-on => not.0.in => pwmgen.0.enable
net spindle-power-not <= not.0.out parport.0.pin-16-out

This is a bug.
One should be able to select spindle pwm and spindle-on signal.

But You could connect spindle-enable to the parport pin in your custom HAL file:

net spindle-enable => parport.0.pin-16-out
parport.0.pin-16-out-invert

What is a bug? I'm guessing that the "bug" is that selecting spindle-PWM as one of my outputs prevents me from then selecting spindle-on as another one of my outputs, because selection of spindle-PWM "consumes" the spindle-on "Pin" from the motion component.

A bug is a programmer's term - it means that the program doesn't work as expected.

Yes you pretty much got it. I'm looking in to fixing it.

My post had a bug. I said "what is a bug." I meant "What part of this behavior to you consider to be a bug?"

I am far, far too familiar with the definition of the word "bug." I have been a systems architect (arch dude) for more than three decades, and there have been times when most of my interactions with co-workers have been via bugzilla.

cmorley wrote:

This is a bug.
One should be able to select spindle pwm and spindle-on signal.

But You could connect spindle-enable to the parport pin in your custom HAL file:

net spindle-enable => parport.0.pin-16-out
parport.0.pin-16-out-invert

Interesting. From the first statement, I infer that HAL will let me add a signal to an existing net: I do not need to define the entire net in a single statement.

The second statement is more difficult. It is a single name. Is this a function call?

got it:

setp parport.0.pin-16-out-invert 1

works just fine.,

sorry about that.. glad you figured it out.

I have pushed a fix for this problem thanks for bringing it our attention