Advanced Search

LCNC 2.9.6
tool_touch_0ff 6.0.0
ProbeBasic neuste Version

Werzeugtab nur 1 Werkzeug neu angelegt
tool_touch_0ff ich habe es auch mit der Version 0.3 Von Cris und Dir

Happy to hear that!
And to get feedback that the dkms driver really helps.

I haven't had a chance, honestly I don't think I could justify one ATM. The old tech budget has taken a beating already this year.
The Intel NICs sounds like a good idea.

If it's this one www.stahlwerk-schweissgeraete.de/plasmas...t70-pilotzuendung-en 
I would look at one that doesn't use HF start. You don't want HF start in cnc table.
Generally, blowback start is what you want.

I got pretty reasonable results on the RPi5 even with Wayland and LXDE.
Enough that software step generation might be an option for a mill. I was surprised by that.
I've had to go back to the basics with pi-gen, was having issues with it deciding to switch from the graphical target to multiuser.
I've got a bunch of images to test, so stay tuned.
But I think once this is nailed it will be easier to get reproducible results. You've convinced me regarding the kernels. So much easier. Thanks

Ok cool, git gets a bit over my head. I ain't real smart, but I used to lift heavy things .

Hi,I'm currently on my journey to build a CNC Plasma Cutter. For the plasma source I'm looking into the Stahlwerk Line-Up of Plasma Cutters (Cut70 or Cut100). All Stahlwerk Cutters have a build in THC Connector. What I can't figure out is if this connector is already divided. Or if an external divider circuit is needed. The Manual just says that it is used to connect the cutter to a CNC controller. Does anyone have detailed information? Or own such a device at has already checked the voltage levels? Greetings
Nils  

EDIT: I see there is already a workflow, but it doesn't build for arm64 or trixie, nor does it publish a github release with built packages. I'll see if I can fix that.

github actions/workflows support both amd64 and arm64, and are free to use for public repositories. I'll see if I can cook up something to build the packages using that, and pull-request it if it works. it could also potentially replace the buildbot altogether - I'm not sure if that's a good idea or not.

that said, I'm a bit short on time at the moment, so don't expect the PR tomorrow.