Advanced Search

Major update 1 Nov 2025

First image I feel is suitable for testing.
After much frustration "the eye candy stuff" is sorted. Background was edited to the best of my "artistic" skills, and first attempt at inkscape, using a standard xfce background with a Linuxcnc logo found on forum member's KurtJacobson's git hub page. 
Splash screen artwork was found on the forum.
Artwork for the background of the Login screen was also found on the forum (robertspark I think was the poster)

If anyone is familar with the rights regarding the artwork it would be appreciated.

Linuxcnc 2.9.7 is pulled from the Linuxcnc repos.
There is still some software that could be pruned, cups is a major one which will also not have the various cups services running. Avahi is another that could be turned off.

Thanks to all who help and gave input

Cheers
Rob

Yup, that's what's not working as expected. It has zero effect on homing.

The section after that is what ill try that tomorrow. That hopefully at least will tell me if linuxcnc is causing the motion, or the drive.

ihavenofish wrote:

so if i home and crash, is there something in the controlword and statusword i should see? it happens in a few ms.
 

Use halscope to record, it catches every ms.
If I look at cia402 code the only reason I can see (but I might miss of course)
is that it does an auto fault-reset due to it receiving a fault code.
Halscope.
And thumb on e-stop.

immediate homing is covered here linuxcnc.org/docs/stable/html/config/ini...ml#_immediate_homing
But spending an hour wiring home switches will be well worth it!
I could not use a machine without home switches and yes I tried!

Nothing seems to change when i home other than the joint error from the crash (i've blocked the axis). So maybe its not the drive homing after all.
still makes zero sense.

Sounds like you are set for internal homing. If you want to do Linuxcnc homing, use generic pin types which you can set in your XML and don't load a homemod. This still works well.

ok, so

machine off:
controlword = 4
statusword = 2672
opmode = 8

machine on:
15
6711
8

press home all and instant crash and fault

saw something about forcing opmode 8, however this changes nothing. still full speed into the end stops.

another suggestion is to just inhibit motion, but that seems not right either. Need to find out WHY it is moving.

so if i home and crash, is there something in the controlword and statusword i should see? it happens in a few ms.

halscope and record statusword and controlword.

well we sorta already did that. there is no setting that doesnt either flicker the drives or slam the axis. like it does't respect search or latch vel at all.

that has to be a clue. something ELSE is making it home. maybe it IS doing internal drive homing?

"Divide and conquer".
Comment out everything except one single axis and try until you find it.

Hakan wrote:

Yes it does have ethercat drives. And modbus nonsense as well.

 

bah!
haha. clearly i've botched something somewhere. i just cant see it.

Hakan wrote:

I don't think it is a good idea to combine homing on current position with HOME_OFFSET.
That means is set's zero exactly where it is and immediately after moves to HOME_OFFSET.

ive removed that now, now, no change. also that offset is + direction and it is slamming the thing full speed into the table.

Yes it does have ethercat drives. And modbus nonsense as well.
 

does your lathe use ethercat drives?

this is what i had before with the pulse drives. everything was fine. And i could have sworn in my first ethercat program *before* all this modbus nonsense it was fine as well.

I don't think it is a good idea to combine homing on current position with HOME_OFFSET.
That means is set's zero exactly where it is and immediately after moves to HOME_OFFSET.