Advanced Search

No, not internal homing but I did get the following error issue when starting up.
I reckon it is the encoders that aren't starting at zero. At least when they have been running and restart QtPlasmaC, linuxcnc expects pos-fb to be zero, but the motors are where they are which is not zero usually. Also when the motors are enabled they move slightly.
I did two things for that
1. Zero the encoder just before starting by adding a startup commandNo encoder feedback on Z.

2. During the first five seconds after "machine on" there is a much larger following error limit, then it goes down to standard following error limit.
Used the timedelay and the ini component for that.

Hi Rodw,

Sorry, did not quite understand.

So to clarify, you are saying just pin to input as per the others and set to Invert and this will take care of the "non-default (i.e. NO)" position of NC? IN other words, it will set its default position to ON, whereas all the others are set to OFF. Is this correct?

Separately, is there any need to put a resistor in line as I have seen elsewhere when talking about using a alternate.

Is there anything I have missed?

"HDD? Perhaps its a legacy device" I think it is a legacy device with “UEFI: IPv4 Realtek PCIe FE family controller” and “UEFI: IPv6 Realtek PCIe FE family controller” on it somehow. I did reformat it a few times during the partitioning set up. Not sure how "Realtek" keeps coming back unless it is hiding somewhere else or remaining after reformatting.