Advanced Search

I was thinking, can we ask the kernel developers, how can we recompile the kernel, eliminating all the power optimizations, so as to optimize it for RT applications? If we continue like this, soon Linux will only be used for writing emails and using OpenOffice.

check this topic 

If it will not help you. let me know below

Hi Surmetall,

Thanks for the link to Talla83's Discord — I actually know Peter's
videos, really good content. I will join the Discord, sounds like
a great place for quick technical feedback.

And I completely agree about keeping both channels alive. Forum for
long-term knowledge base where people can find solutions years later,
Discord for quick "I am at the machine, something does not work"
situations. Different tools for different needs.

Sorry to hear about your Beckhoff struggles. That is exactly the
kind of retrofit work where LinuxCNC really shines — replacing
expensive proprietary controllers. If I can help with anything
regarding the driver side, let me know.

Regarding the lathe polyline — still polishing a few things, then
I will push to GitHub. I will post here and ping on Discord when
it is ready for testing.

Best,
CNC Proton

Hi,

The fix is now released in version 2.0b-1:

github.com/cnc-proton/nativecam-py3-gtk3/releases/tag/v2.0b-1

Download the new .deb and install it:

sudo apt remove nativecam

sudo apt install ./nativecam_2.0b-1_all.deb

This should resolve the python/python3 issue on Debian 12.

Please let me know if you run into any other problems.

Best,

Thank you, andrax. It seems that the absolute encoder would be a good solution and perhaps using them will prevent any homing failure. The batteries are installed in the boxes of each servo. From the servo manual, the default home offset is 0. Therefore this should be the absolute homing position that the servo knows about - 0x6064 should be around 0 or 2^32. When I execute a home procedure in LinuxCNC, the 0x6064h is indeed around 0, I check it via "ethercat upload" terminal command. Then I close and start LinuxCNC again and the motor does not arrive in the same position as the previous execution of homing. There is a different value on the axis/joint DRO. This is my joint configuration:

4.19 was good. Remember I struggled with 6.x when it came out.
Anyway, what I do now is to have an Intel network card, i210, i217 or i225/i226
and make a modest effort to reduce jitter and latency.
The way I determine it's good enough is when there are no messages in syslog of this kindAll such messages have to go, well one in the beginning is ok, but not more.

I may or may not need to go to isolcpus and so on. On my current plasma system I have no
such tweaks at all. It works good anyway.

I installed nativecam, but when I run ncam --help or another command I always get this error: /usr/bin/env: «python»: No such file or directory, apparently the path it is looking for is different, I am using DEBIAN 12.

I think I don’t fully understand how that would work. The variator is controlled by two contactors. The shortest time that has to be on to actually change the variator state is relatively long. And how would you turn the float from a PID into the contactor signals?

Did I understand you wrong?

Today I tried threading with G76. It did not go very well (see picture). It looks more like a very rough turning pass. I am not sure if I understand the parameters of the cycle. It is supposed to be M32x1.5.

The code I ran was:
With this, the material was not touched at all, so I started at X32.5 instead of X34 (that is where the picture comes from).

Are the parameters I and K relative (and in radius)? I thought starting at X34 is, in radius, 1 mm away from the nominal 32 mm I want, so I = 1, and the pitch is 1.5, so the final depth should be 0.75 mm lower.

The lines in the GUI looked just like “Figure 4. G76 Example” from:
linuxcnc.org/docs/html/gcode/g-code.html#gcode:g76

Can anyone give me the G76 line for an M32x1.5?

papagno-source wrote:

I have question at AI:

ethercat on debian 10 with kernel 4.19 and linuxcnc has less latency than debian 13 with kernel 6.12. Why?
 

Don't forget the hardware manufacturers have been adding  power saving features for years even back with Debian 10. But Linux simply ignored these features but now the kernel has caught up. It had to stay current. Generally, there are settings to disable them.  Also there are a lot of new network cards often part of the motherboard that do not have driver support until Debian 11 or 12 or 13.  So Debian 10 is an unsupported version now so you can;t continue to live in the past. Generally with proper tuning , 4 core and up hardware runs well on the later kernels.

Thanks, endian, for the converter. I tried to integrate my AX5125 into LinuxCNC. I converted the TwinCAT 3 export and tried to get it running in LinuxCNC. I can see the AX5125 as a slave and some of its pins. Unfortunately, I can’t get it from Pre-OP to OP mode. I’m definitely doing something wrong but I’m not sure where to look.

I hope someone can help. Which data do you need? I assume the .xml, .hal, and .ini files?

Is it okay if I post them here, or would it be better to start a separate thread? Thanks in advance.

Greetings
Tom

I don’t think there’s anything wrong with that. As far as I know, Tormach uses LinuxCNC with PathPilot as well, right? As long as the modifications are released again, like you said, everyone benefits!

Wow, I’m absolutely thrilled about the video I can’t wait to test it! Unfortunately, my machine isn’t operational yet; I’m still struggling with the Beckhoff driver. If you need multiple testers with real CNC lathes who can provide faster feedback than on the forum, Peter alias Talla83’s Discord (I assume you know him from his YouTube videos) might be an idea. It’s more like a chat there, and people reply quickly. There are also several lathe users and generally many smart, helpful folks.

This isn’t meant to poach users or replace this forum. I’m happy to be here, and in the long run, knowledge is better preserved here. So please post here as well so other users can find it more easily later. For faster feedback - for example, when you’re at the machine and need input from others - the Discord is hard to beat. Just an idea
The Discord mainly has German-speaking users from Germany, Austria, and Switzerland, but everyone understands and replies in English too.discord.gg/dyd8M9wJ

Hey everyone,

After years working with CNC machining and G-code (and seeing the same mistakes over and over again), I decided to put everything I’ve learned into something practical — not theory-heavy, but actually useful on the shop floor. So I created a complete 5-book path, covering everything from absolute beginner to professional-level programming. This is NOT academic stuff — it's built around real-world use, production safety, and hands-on workflows. Here’s the breakdown:

BEGINNER LEVEL

Unlock the Power of G-Code: Master CNC Machining and 3D Printing

www.amazon.com/dp/B0FBST2QXR

If you're starting from zero, this is where you begin.
It walks you through the fundamentals of G-code for both CNC and 3D printing — clearly and step-by-step.

MASTER LEVEL

The G-Code Mastery Guide: Your Practical Handbook for 3D Printing and CNC Machining

www.amazon.com/dp/B0FKBQ71D9

This goes deeper into real applications — not just syntax, but how to actually think in G-code.

PROFESSIONAL LEVEL

CNC Programming G-Code: Industrial Fanuc-Style Programming for Milling and Turning

www.amazon.com/dp/B0GR51Z9JC

This is focused on industrial programming, including:
- Production-safe code
- Crash prevention
- Full real programs
- Troubleshooting strategies

Basically, what you wish someone had told you before your first machine crash.

PRACTICAL COOKBOOK

The G-Code Cookbook: Over 100 Practical Recipes for CNC Machining and 3D Printing

www.amazon.com/dp/B0FDVGX7RC

No theory — just ready-to-use solutions.
Over 100 practical G-code “recipes” you can adapt immediately.

BONUS FOR MAKERS & ENGINEERS

Print Them All: 203 Ready-to-Use 3D Mechanical Components (STL + STP)

www.amazon.com/dp/B0GW5KBFZ9

A library of mechanical components ready for:

- prototyping
- CAD work
- real builds

WHY I MADE THESE

I kept seeing:
- beginners overwhelmed
- intermediate users stuck
- pros missing practical references

So instead of one giant confusing book, I split everything into a clear progression path.

HONEST FEEDBACK WELCOME

If you check them out, I’d genuinely love feedback — good or bad.
Also happy to answer any G-code questions here if you're stuck on something.

What’s the hardest part of G-code for you right now?

Hi Tom,

Your message really made my day, thank you for such kind words!

I completely understand what you mean — there is something special
about this community. People helping each other bring dead machines
back to life, sharing knowledge, no profit motives. It is rare and
valuable.

I want to be honest — I am not a pure altruist here. I do commercial
CNC work and NativeCAM improvements help my work too. But that is
exactly why open source makes sense to me: fix something for myself,
share it back, everyone benefits. Fern built this whole framework —
I am just adding pieces I need on top.

Good news to share: basic lathe polyline with G71 cycle is working!
Here is a short video showing a stepped shaft profile being generated.
Ø50 → Ø30 → Ø20 with chamfer and fillet. Toolpath renders correctly
in AXIS preview.



Still some minor bugs to polish before I release it on GitHub. Once
it is stable I will post here and invite everyone to test. A few more
things planned before release:

- G70 finishing pass after roughing
- Profile validation (prevent non-monotonic paths)
- Pocket cycles (G71.1 / G71.2)

Your feedback is exactly the kind of contribution that keeps this
alive. Users like you who test, report bugs, and cheer us on matter
just as much as the code. Thank you!

Best,
CNC Proton

Okay i where talking a little bit with chatgpt

my recomendation from chatgpt is something like that:

• 1x Mesa Electronics 7i95T 6-Axis STEP/DIR/Encoder Ethernet Controller (Chatgpt said this is better version?)
• 3x Leadshine CS-D808 30-80 V 8 A
• 3x Leadshine Closed Loop Schrittmotor mit 8Nm Typ: CS-M23480

My question would be, is 8Nm Torque for the Z-Axis enough because i think the head is quite heavy and i think there is no counter weight
 or should i get a bigger motor for the Z-Axis?

• 1x Closed Loop Schrittmotor Leadshine ES2-MH342120 mit 12,0 Nm
• 1x Closed Loop Schrittmotor-Endstufe Leadshine ES-DH2306 für 230VAC

 
 


 

axemas wrote:

...
Thank you so much for the kind words — it really motivates us to keep going!
...
Thanks again for the feedback — users like you make open source
worth working on!

Axemas

No no, WE open source users are the ones who should be thanking YOU!In a world where so much revolves around power, money, profit, and exploitation, it’s really great to see people like you and many other kind folks here on the forum working on such a huge and brilliant tool like LinuxCNC and making it freely available to everyone. And doing all of that in your spare time, simply to help others bring their machines to life or even rescue them, just to make people happy without expecting anything in return or having any hidden agenda.I can’t really contribute much myself, other than pointing out features I might be missing, testing things, and give feedback how well everything works. Or telling other hobbyists how great this community is and how much fun it is to be part of it. For me, it’s just a great hobby that brings me a lot of joy.As I mentioned, I’ve been using NativeCAM on my milling machine for years and I still absolutely love it. I’m very grateful to Fern and all the other developers who have contributed to it over time.When I started converting my lathe about a year ago, it was immediately clear that I wanted to use NativeCAM Lathe. I also quickly realized that for lathe work you don’t really need a separate CAD/CAM system, especially with that brilliant polyline function combined with tool compensation. Whats means a lot to me. So I was quite disappointed and sad for me to discover that this feature was never fully completed. Unfortunately it seems that development on it has stopped and we have to accept that. (Still hoping Fern is doing well and is just busy...)All the more reason why it feels like both Christmas and a birthday at once to hear that you’re planning to take this on and continue his great project that he put so much work into. Thank you very much in advance, I’m really excited to hear that!

Feel free to share your progress with the community while you’re working on it, or if you run into any issues or need someone to test things. I’m sure I’m not the only one who’s really excited about this and would be happy to help if possible. I’ll definitely be following the project on Git as well.

Greetings Tom