Hi ihavenofish,

I read through that entire thread, unfortunately I couldn't find anything specifically on the pinout. I think I am going to have to remove the ATC shroud and take a look at the board. Here are some relevant posts from that thread:

forum.linuxcnc.org/30-cnc-machines/32276...ure?start=360#172455
forum.linuxcnc.org/30-cnc-machines/32276...ure?start=470#258347
forum.linuxcnc.org/30-cnc-machines/32276...nture?start=10#87606
forum.linuxcnc.org/30-cnc-machines/32276...nture?start=60#96531

I did some more searching online, and stumbled on this Brother B521136-2 board. It's not labeled for a TC225, but it has what appears to be the same number of pins, so I might be able to at least look at this to cross reference to what I have. The harness I have is labeled as follows:

E - Green w/ Yellow Stripe
49 - White w/ Yellow Stripe
50 - White w/ Green Stripe
51 - Blue Solid
52 - White w/ Blue Stripe
53 - Yellow Solid
54 - White w/ Red Stripe
55 - Red Solid




I feel pretty good about setting up HAL to handle the four BCD encoder bits, the deceleration signal, and the limit switch swap; there is a ton of good information in your thread that I will certainly use as a starting point. When I got the machine, however, it was in mid-retrofit, and pretty much all of the original hardware is gone - the only thing left are the factory limit switches, the Oriental Motor SBR32-ZP brake pack, and the Oriental Motor gear motor.

Thanks,
Jeff

kello711 wrote:

I am trying to load up a 1" wood surfacing bit. I wanted to use the tool offset direction in the probing but it doesn't seem to work. I didn't find anything in the documentation to explain how. I added the diameter to the tool table to no avail. Also on the probing menu, what do "User Params" 1 and 2 do?

It should work. Using the diameter offset changes the coordinates of the touch point in the macro.

kcjengr.github.io/probe_basic/tool_lengt...f-parameter-settings

github.com/kcjengr/probe_basic/blob/main...ol_touch_off.ngc#L32

grandixximo wrote:

Honestly, waiting for Scott for some direction, he is not been replying any messages, so at the moment everything is stale, I don't really want to touch core functionality, I'm not sure about the uspace work by Sascha, should linuxcnc take that in as well? We would have to build Sasha's ethercat master as well to enable all of that. Not sure what the community needs

Thats a but disappointing. Its hard to keep commitment on projects like this. Sasha lost interest and it was badly broken. At one stage, I hosted the hal driver repo briefly when I built the initial 2.9 ISO then Bjarne at etherlab did a deal with Sasha to host it direct. I gladly gave it up. Then Scott did a deal with Sasha to host it and develop it (which he did). So I did some intros and Bjarne helped Scott build workflows to send builds to the etherlab repo so it was hosted and available so that was pretty cool. I see Sasha's page says use Scotts repo and he hadn't made any commits since 2024 until a mad flurry of commits in 2026! Whatever you do etherlab will be very supportive.

Its just a shame the Ethercat license does not allow linuxcnc to manage it.

Not sure if that helps....

phino wrote:

Is there stock available for purchase of the height sensor?

A couple of days ago, I saw 1 in stock, but when attempting to purchase, it said out of stock.

Send me private message plese.
or beter contact by WhatsApp +48 604 247 648 

andrax wrote:

Hi, 
here is my configuration.
It works. I use XYYZ.
 

Hello.
Just trying to set up simmilar machine configuration asyou have. I am trying to use your configuration, but run into weird problem - at hal, Ethercat to CIA402 driver mapping section, "joint.0.cia-statusword does not exist".
Also joint.0.request-cia-homing, joint.0.start-cia-homing,
What am I missing?

cserver1.multixmedia.org/config-modbus-cmd.json

github.com/multigcs/riocore/blob/dev/doc/MODBUS.md

Its actually very difficult to stop this. Been there done that.
You could try running this script with sudo. It creates some system settings that have been working for me.

Every few years I upgrade something on my stepper controlled knee-mill. I usually get sucked into upgrading linuxcnc at the same time. I just upgraded the stepper motors and put a new controller on. The new controller is using Mesa 5i25 and 7i76 cards with Gecko drivers. I was running linuxcnc 2.9.4 and decided to upgrade to 2.9.8. Rather than upgrade I did a new install with 2.9.8 (Debian trixie).

After install, and working though several problems, I have linuxcnc 2.9.8 working well with a Pncconf configuration. But, I am having great trouble with the computer logging out every 30-60 minutes. A very bad thing for a machine controller. I suspect this is in the XFCE environment but can not find a solution via Internet searching.

I did find, through searching, and have implemented the following changes:

I changed /etc/ligntdm/ligntdm.conf to implement auto login by un-commenting
  autologin-user-[my user name : hugh]
  autologin-user-timeout = 0

In the XFCE settings I disabled Lock Screen [disable "Lock screen when idle"] and disabled Screen Saver.

To prevent logout from /etc/syslogout I put an empty file as "$HOME/.nosyslogout"

In XFCE setting, under Power Management, assured the "Suspend When Inactive for" was set to never.

I did try, I believe, disabling the Display Power Management toggle in the setting menu. This caused a broken system. When a login was done the machine thought awhile then returned to the login screen. I could not figure out how to fix this via the terminal so had to re-install linuxcnc. I re-installed once without re-formatting the /home directory but the login loop was still present. Another re-install with re-formatting all partitions brought me back to zero. I'm trying to not repeat this error.

The computer now starts up without requiring a  login, that's fine. It works for 30-60 minutes and then logs me out. The result of the logout was a new login screen (user: & password). After the above changes, auto login, it automatically logs me back in. But for both of these, any running applications, like linuxcnc, are killed with the logout/login.

What am I missing? Is there a simple fix or should I step back to linuxcnc 2.9.4 and see if it still works?

I am surprised by this problem. I'd think a linuxcnc ISO should be set up for no screen saver and certainly no timed logout. This seems like death to a machine controller where a complicated program could run for a couple of hours. This tends to convince me I've done something wrong with this new clean install.

Thank you for any help you can provide.

Sorry guys. I'll look at the user exchange section.
 

The question is how far are you off dimension?
Are we talking about 0.005 mm? Or mor like 0.2 mm?
On the video it looks like your endmill sticks out "far too" long.
You probably can put it further up into the holder.
Follow suggestions of #344316, finish pass.

Take care with merging Sasha's code. The master linuxcnc-ethercat driver is now Scott Lairds repo  github.com/linuxcnc-ethercat as it has a workflow that pushes the driver when built across to etherlabs repo on gitlab so we can get the driver with sudo apt install 

georgio wrote:

thank you Peter,
That got rid of the error there but it points now to an error on Hal line 25: empty variable name. I don't know how lines are counted no matter how many ways I counted them it did not make sense to me.
I so very much appreciate your help, I have spending days with AI trying to get this figured out to no avail, you forum experts know this stuff!!!!
Grorge

If you open the file with geany which is part of the linuxcnc ISO. the  editor will show line numbers.

It may be less a case of “no results” and more a case of “the pieces exist, but there does not seem to be a complete worked example showing how to tie them together in LinuxCNC.”

If you already get the Z/C event, then it sounds like the remaining issue is LinuxCNC integration rather than the EL5101 itself.
Using the EL5101 for A/B and a separate optical sensor for Z into an EL1008 sounds like a practical workaround if you are looking for a known working threading setup to base yours on.