LatheEasyStep – experimental QtVCP macro for step-by-step lathe programming

More
10 months 2 weeks ago - 8 months 12 hours ago #340123 by aDm1N
Repository:
github.com/peter-pan08/LatheEasyStep LatheEasyStep is an experimental QtVCP panel for LinuxCNC that enables step-by-step conversational lathe programming directly at the machine — without external CAM software.The goal is fast, safe, and practical programming for typical workshop jobs.PurposeLatheEasyStep is designed for:
  • Programming simple to medium turning operations directly at the machine
  • Repetitive standard jobs (facing, contouring, grooving, drilling, threading, roughing)
  • A workflow-focused approach:
    Enter parameters → Verify preview → Generate G-code
It aims to bring an industrial-style conversational workflow to LinuxCNC.Current Feature SetProgram Structure
  • Program header with stock/workpiece parameters
    (diameters, lengths, units, safety values)
  • Step-based program building with sortable operation list
  • Save/load for single steps and full programs
  • Bilingual UI (DE/EN)
Supported Operations
  • Facing
  • Contour
  • Groove / parting-style operations
  • Drilling
  • Threading
  • Roughing (material removal)
  • Keyway (macro-based)
Preview & Visualization
  • Live X/Z preview including reference geometry
  • Dedicated chuck safety zone visualization (color-coded with legend)
Safety & Motion Logic (Core Focus)
  • Context-aware retract/free-travel behavior per operation
  • Material-aware retract decisions
  • Extended chuck / no-go safety parameters:
    • Chuck size
    • Workpiece type
    • Clamping mode
    • Chuck profile
  • Machine/workshop profile presets for faster setup
Project Status
  • Experimental
  • Actively developed
  • Designed for real machine workflows
  • Iterative improvements based on practical use
Known Limitations
  • Not a full CAM replacement
  • Complex freeform geometry is intentionally limited
  • Machine-specific adaptation may be required
Target Direction
  • Fast conversational programming at the machine
  • Clear and understandable geometry visualization
  • Safer default behavior for common turning tasks
  • Continuous refinement driven by community feedback
Feedback WelcomeIf you test it, helpful reports include:
  • Brief machine/configuration info
  • Reproducible steps
  • Expected vs. actual behavior
  • Optional screenshots, preview images, or G-code snippets


 
Last edit: 8 months 12 hours ago by aDm1N. Reason: add pic
The following user(s) said Thank You: tommylight, besriworld, COFHAL

Please Log in or Create an account to join the conversation.

More
10 months 2 weeks ago #340127 by cmorley
This should be moved to the Qtvcp section.
Looks promising! Keep is updated! If you get stumped with the programming i can try to help.

Please Log in or Create an account to join the conversation.

More
10 months 2 weeks ago #340128 by aDm1N
I've never moved anything in a forum before, how do I do that?

Please Log in or Create an account to join the conversation.

More
10 months 2 weeks ago #340129 by tommylight

Please Log in or Create an account to join the conversation.

More
10 months 1 week ago #340302 by Surmetall
Hi,
this looks really cool, thanks for sharing! I’ll definitely be testing it once my lathe is ready.

I really like the idea of solid onboard solutions. If this works well, you could do around 90% of lathe parts without external CAM, which would be a real improvement.

It reminds me a bit of Native CAM. Do you know it?
If so, I’d be interested in what made you decide to develop a completely new macro. From my point of view, Native CAM on the turning side is mainly missing proper G71 support and a polyline tool (which already exists in Native CAM Mill).

This is not meant as criticism, I generally find new developments very exciting. I’m not a programmer myself and can’t really judge the effort involved, which is why I’m asking.

Either way, very promising project. Looking forward to seeing how it develops

greetings 
Tom

Please Log in or Create an account to join the conversation.

More
10 months 1 week ago #340328 by cmorley
I note you use the qtpy abstraction layer. This is not pulled in for our linuxcnc package, so could trip some people up. I would suggest adding a descriptive warning to the terminal if the module is not found.

Please Log in or Create an account to join the conversation.

Moderators: cmorley
Time to create page: 0.082 seconds
Powered by Kunena Forum