Advanced Search

the repo in the github configured like this:

you get:
4 step-generator
1 encoder-counter
gpio input pins (10, 11, 22, 26, 27, 28)
gpio output pins (12, 13, 15)
1 pwm channell (gp14)

so you can use it with a cheap printerpot breakout board. i currently working on a breakout board mixed with the io-samurai project to add +8 digital output and 16 digital inputs to this ().

but you can configure other ways if you want, more encoders for less inputs or no ecoder for extra 2 input or output. the hal driver uses the same configuration file so only 1 place change is need to change the configuration.

The configuration file is in the repo (firmware/w5100s-evb-pico/inc/config.h)

or if you want much more inputs and outputs use my io-samurai project, open source with the PCB production files. (only works with the W5100S-EVB-PICO or equivalent pico + w5100s breakout board)

if you want faster response please use the discord link in the repo.

 

 

Yes, that could definitely be the case. It's a very old machine—27 years old—but I decided I want to give her a new life. The structure is really solid, plus it has vacuum and lubrication for aluminum, which is great.
So, I want to do this retrofit, and I think the setup I posted here should get the job done. The only thing I have to do is adapt the old motor frames (they have a small gearbox), because the old motor is 89x89mm and the Leadshine is 80x80mm. I hope it won’t be too difficult.
Once the machine is up and running and I’ve done some work with it, I can swap the spindle and install an automatic tool changer. That would be so cool!

Do you have any general advice? Does the setup look good to you guys?
By the way, I’ve installed the LinuxCNC ISO on an old PC with an Intel i5. Now I’m just waiting to buy the Mesa board and start configuring everything.

Thanks for the replies, but some misunderstanding here.
The system is fine, up and running LinuxCNC 2.9.3, configured for the X-axis with joint0 and joint1 as it should be (cutting a big slab of 5 mm Alu while I am typing this). The only thing I am adding is a racking detector (for which I use encoder_ratio looking for a mismatch on encoder disks on both X axis).

While browsing through the HAL functions I ran into Matrixkins, and I wondered if this is not an easier way than changing some HAL values to square the axes. Since it does not apply to a tandem axis, I'll drop the issue.
But thanks for the replies anyway.

Robert