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.

After Disable secure boot and enable legacy, I got a new error screen with similar message, about not finding the the boot disk. The USB drive is good.

The top left one.
Netinst CD image for AMD64

What image or installer at
"www.debian.org/devel/debian-installer/" should I try? Best fit for my system?

You are on a very old version, chances are you have the wrong subroutines for the version you are on. Update to the latest stable version to resolve.

Have just completed a rebuild and rewire of our shop built CNC router.
Rebuild required, amongst other things, a replacement of breakout board which is now a cheap 5-axis parallel port board.
Switches on either end of each axis are wired, in series, to a separate input.
Using Step Config all axes pass test movement and jogging appears fine on all axes.
Switches on all axes stop motion as expected and at present no spurious joint errors occur during jogging.
If I run an aircut using a "no limits" config file motion seems to be fine.
The problem comes when I attempt to manually home any axis using a config file with "min limit + home" configuration (actually most other configs I have tried do the same) - pressing the home  key appears to engage the axis motor (I can hear iy humming) but there is no motion.
I attach the ini and hal files for the current config but I am unable to determine if there is a software issue causing this.
Any advice would be appreciated.

Very cool, Are you using internal homing and limits on the drives?
I finally worked on a homing component for the ECT60 over the weekend but have not got as far as connecting up a hal file to it. I ran out of energy!

I decided to go back to basics and control the homing using the Ethercat pins direct. In fact I added a bunch of pins because I did some work previously before the current homecomp was released. I'm sure there are a bunch that need deleting once I get it working. Long term I'd like to get rid of the cia402 component. I'm not sure if I can do that in a home comp.

Have a look. any help appreciated
github.com/rodw-au/cia402_homecomp

I did try "Disable secure boot, enable legacy" options. I think that may have been the default setting, but I will try anything a few more times just incase it works this time. The internal hard drive was the first thing I tried to install to. but I started using the USB HD because it is newer and I new it was in good shape, also just to try another drive.