Tommy
As always: Top!
While I started to use touch screens a couple of years ago, I reverted back to non touchscreen setups. I do mostly foam and wood stuff. Although I have a pretty efficient dust extraction system, there is sill a lot of dust landing on the touchs. Wipe them them off while chipmaking, and I guess you see the troubles. I use industrial grade Keyboards now
I have a yoga 370, some yoga 260, the mentioned T440p (should be as good as the X240). I'll test them and post results, placing the link to my findings in a later edit here for reference.
Greez
Chris

After the macro runs, I believe the machine is in MDI mode.
I bet HALUI needs the machine in manual to allow jogging.

Hi everyone! 
This machine was an old emco, retroffite with new electronics, designed and built a subspindle where tailstock was and designed a cnc bar loader for 6meters longs bar.
As you can see in the videos, the spindle and subspindle rotates simultanseously for cutting the part off


Video

Hope you like it and have a nice weekend!

Yes, trixie uses python3.13. I guess it would be fine in bookworm with 3.11.
It turned out the tool_db issue was just a setting in xyz.ini. The tool program is in /usr/bin.

I have played around a bit and yes it looks very very nice.
The material handling looks awesome.
So I'll turn it into a real machine, for my plasma cutter.

What a neat little turret! Cool company too, I've got one of their booster pumps.

That turret is too small unfortunately. Will be taking some decent cuts on this lathe so I ordered a tormach turret. Pricey, but those guys are so great with tech support... one call and they were willing to explain all of the electrical details I needed to integrate it.

This line in the ini was the problem "TOOL_CHANGE_POSITION = 0 0 410". My z limit is 300....

It’s been 9months since I got near this project. But back at it again.
I’ve been working my way through pnc config and inputting all the axis info from the manuals and finally starting to wire up the mesa boards.

Big thanks to the feral engineer on YouTube with his Linux cnc bare bones series as this helped me understand what data needs to go where..

Linear scales are now connected up and reading in the correct directions.

I have finally decided on what way to wire each axis and name each axis. I’m sticking to the original Maho horizontal spindle configuration with the y axis moving the table up and down. This way in the future trouble shooting in the future will be less confusing as everything will match the original manuals.

Once if got as far as I can with pnc configuration I’ll make a second configuration for the vertical spindle which I will use the most.

Hallo tommy ,

vielen Dank, das hat funktioniert....

karlhe

At least got it up and running. 
1. Had to replace "import imp" in  /usr/lib/python3/dist-packages/qtpyvcp/app/application.py 
with "import importlib.util"
and on line 159


This comes from the python3-qtpyvcp apt package.
Is it qtpyvcp to blame or trixie that doesn't provide the imp module?

2. Missing [PLASMAC]SLAT_TOP in ini file. Added
SLAT_TOP=0.0 in PLASMAC section.
I guess it could be given a default value as is done for so many variables when they are missing.

3. Locale problems. <string>:1: SyntaxWarning: invalid decimal literal
Started linuxcnc with


and it gives me a Monokrom screen.
 

Edit.
The LC_ALL=C wasn't needed.
But this one needs attention:

Yes I forgot to mention this. I have tested with the Plasamac postprocessor as well (the one I normally use with my QtPlasmac setup) with the same result. It works, if I deactivate the plasma_gcode_preprocessor in the Filter section of the INI but then I can obviously not use any of the advanced Monokrom features like hole detection.

Try this command and review results when complete The max reading is usually the first entry as it connects so look at average and standard deviation.
 

tommylight wrote:

@Rod,
We can not edit your youtube videos on your youtube studio!
-
how is the html code for grin?

That's quite an old video now. There are more reasons  in 2.10  to grin
In  2.10 there is a change to how Deb files are built by doing it the Debian way which installs all the dependencies for you. It is described in the building linuxcnc docs for 2.10. I do remember testing it prerelease and it was sooo simple,,, except for building the docs.