Hello and thank you for the explanation - but my thought was only to the logic of the LinuxCNC - how can i be sure the Pin is not true if i want drive spindle forward in case the Pin should be false? If there is some crashing of Softwre or Mesa there is not an safety concept to say forward set pin false and backweards set pin true.
The setting is only one thing:
Set the pin false if spindle backward
Do nothing with the pin if spindle forward
spindle.0.forward will only be true when the spindle is on and non-zero
forward spindle speed is requested and LinuxCNC is not in a fault state.
spindle.0.reverse will only be true when the spindle is on and non-zero
reverse spindle speed is requested and LinuxCNC is not in a fault state.
If you have a spindle drive setup for FWD/REV control you would typically
connect the drives FWD and REV pins to 2 separate outputs controlled by the
spindle.0.forward and spindle.0.reverse hal pins.
spindle.0.on will be true when a non-zero spindle speed is requested
and LinuxCNC is not in a fault state.
For safety with a DIR/ENA setup as you seem to have, you should always control
your drives spindle enable with LinuxCNC's spindle.x.on pin.
This way the spindle is forced off:
1. Before LinuxCNC starts
2. If the PC crashes
3. If LinuxCNC is in a fault state
@PCW
The VFD have only one Enable Input and One Reverse-Input. And Speed is over 0-10V.
Enable is set like LinuxCNC is set this by default. On my Mesa-Card on ENA+ and ENA- and is working fine also Speed from 400rpm to 40.000 RPM is working fine. Correct scaling - the same speed value on LinuxCNC in comapiring to the VFD-LCD.
Have only problem to drive it reverse and i figure out why..
