Langdons read his post.

The OP did a fresh install.
If the checksum didn't match the install would have failed.

The GUI would not matter has this will be a hal issue.

Apologies to the OP, but the above poster is a nuisance.

The best thing to do is attach your hal & ini files and maybe your comp file as well.

I'm just wondering whether this thread may be of help.
forum.linuxcnc.org/qtvcp/52434-z-level-compensation#298898

Plain sailing this is not! I have been battling for days now to get LinuxCNC up and running. Resorting to building from source now. Hope to have it up and running by tomorrow morning.....ok, later this morning.

tommylight wrote:

Your ini file is a mess and very hard to follow, but:
Y axis/joint has unreasonably big ferror and min_ferror values, probably should be close to what X axis has
Backlash_speed is set at 6000 inch !!!
-
What is the drive train? Belt? Screw? Ball screw?
Since it is a laser, i would advise belt only on X and Y.

 

I not even sure if there Backlash_speed is used in the hal file, there doesn't seem to be anything related to backlash_spped or similar mentioned in the docs for motmod.

I'll try it tomorrow if I didn't remember to try jogging via the button on screen:) I'll also try in hal to edit the acceleration, etc., the next step is to connect the home switches for referencing.. when I set the motors well, there are two buttons on the panel, one is for starting the program, later I'll try it via ``halui'' and ``drive on'' should provide ``power`` to the drivers, than for ``enabling`` the driver works via the ena+ and ena - wire on the 7i77 when I turn it on machine via linux. the next steps are to connect the inputs and outputs to the 7i77, because now in the basic configuration I have made a connection with the 7i92+7i77 and I have no idea how I will use one of the step dir channels with the 7i96s as well as the whole 7i96s in general. thank you very much

In all honesty it may be worthwhile going back to you original setup. I generally think of the PC for a cnc setup as a "black box". As along as it doing everything you want leave it that way.
But it is quite curious as to why backlash is not working as expected. Maybe raising an issue on github may get better responses. The guys that do the coding will be answering.

I hate to say this but backlash comp should be a last resort after you have exhausted all mechanical ways to reduce it.

Sorry I haven't been able to solve this issue and I wish you all the best. If you do find a solution it would be great to describe the fix for anyone else in the future. Good luck as always.

I Tried with 'hal_pi_gpio.write base-thread' at the end of the base-thread, but it does not make any difference.
Thanks for the info anyways.

I can't find much on Ethercat homing. Maybe I'll be able to figure it out down the road. How would I set it up with Inputs on the EL1008 instead, in the meantime?

My drive have several homing method built in, and I recently solved to change the drive state druring the LCNC start, so I can initialize the drive to HM mode first, than CNP mode.

How?

youtube.com/shorts/JEPo7x18bOk?si=WyeXHpHts4dJgP9n

Translate it as complex . Import it as s32 or u32.. Then create simple component to cut it a pieces... Simple and effective