Forum Menu

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

More
9 months 9 hours ago #342280 by aDm1N
Replied by aDm1N on topic LatheEasyStep – experimental QtVCP macro for step-by-step lathe programming
I have adjusted the code accordingly.
With a bit of luck, this fixes the reported issue.In addition, I have extended the README with a basic usage guide to better explain the workflow and operation.There is now an integrated grooving cycle, which is written into the program automatically when required.Feedback on whether this resolves the issue would be appreciated.
The following user(s) said Thank You: tommylight, COFHAL, Surmetall

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

More
8 months 4 weeks ago #342306 by cmorley
Replied by cmorley on topic LatheEasyStep – experimental QtVCP macro for step-by-step lathe programming
It does load in master now, but it takes a long time to get Qtdragon to show.

Lots of messages about un found widgets:
Code:
[LatheEasyStep] shape combo candidate styleSheetCombo: ['as loaded', 'none', 'argentium.qss', 'qtdragon_lathe_ncam.qss', 'brushed_metal_color.qss', 'qtdragon_lathe.qss'] [LatheEasyStep] shape combo candidate : ['grayscale depth image', 'python script', 'all (*)'] [LatheEasyStep] shape combo candidate : ['grayscale depth image', 'python script', 'all (*)'] [LatheEasyStep] shape combo candidate cmb_gcode_history: [] [LatheEasyStep] shape combo candidate jogincrements_linear: [] [LatheEasyStep] shape combo candidate jogincrements_angular: [] [LatheEasyStep] no shape combo found in tree [WidgetResolver][WARNING] Widget 'btnAdd' (QPushButton) not found. root=VCPWindow [WidgetResolver][WARNING] Widget 'btnDelete' (QPushButton) not found. root=VCPWindow [WidgetResolver][WARNING] Widget 'btnMoveUp' (QPushButton) not found. root=VCPWindow [WidgetResolver][WARNING] Widget 'btnMoveDown' (QPushButton) not found. root=VCPWindow [WidgetResolver][WARNING] Widget 'btnNewProgram' (QPushButton) not found. root=VCPWindow [WidgetResolver][WARNING] Widget 'btnGenerate' (QPushButton) not found. root=VCPWindow [WidgetResolver][WARNING] Widget 'btnSaveStep' (QPushButton) not found. root=VCPWindow [WidgetResolver][WARNING] Widget 'btnLoadStep' (QPushButton) not found. root=VCPWindow etc

I'll now look at work flow to see what I can produce :)
 

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

More
8 months 3 weeks ago #342516 by Becksvill
Replied by Becksvill on topic LatheEasyStep – experimental QtVCP macro for step-by-step lathe programming
this looks awesome

and yes i agree its massively missing in linuxcnc

i have been trying for ages to get native cam running and can't

i find on semiens and fagor controls i use the contour cycle about 90 percent of the time

everything else like facing and shamfers etc i don't use as i can just do it in the contour cycle.

and of course threading is usefull

though the built in threading cycles are not too bad for that

cheers

Andrew

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

More
8 months 4 hours ago #343694 by aDm1N
Replied by aDm1N on topic LatheEasyStep – experimental QtVCP macro for step-by-step lathe programming
Hi all,
here is a short update on the latest changes in LatheEasyStep:

Step list loading issue fixed
In some embedded QtVCP scenarios, the operation list stayed empty after loading a single step or a full program. The operation list binding is now more robust.

Safer retract/free-travel logic (lathe-specific)
Retracts are now context-aware per operation:

simultaneous X/Z where safe
groove/keyway: retract X out of material first, then Z
drilling/threading: retract Z clear first, then X
Current tool position relative to stock/chuck is now considered.
Extended chuck / no-go safety model
The program header now supports chuck-related parameters (size, workpiece type, clamping mode, profile) with automatic no-go zone calculation.

New machine/workshop profiles
Quick presets apply typical parameter combinations automatically (e.g. chuck + clamping mode + profile).

Preview improvements
The chuck safety area is now shown in the preview as a dedicated colored zone, including a legend entry.

Save/load extended
New header fields (chuck/profile/no-go/machine profile) are now properly persisted and restored.
The following user(s) said Thank You: Surmetall

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

More
8 months 3 hours ago - 8 months 3 hours ago #343695 by aDm1N
Replied by aDm1N on topic LatheEasyStep – experimental QtVCP macro for step-by-step lathe programming
As a bit of background on the chuck/no-go safety model:At work I requested a machine with a control that includes an integrated safety zone around the chuck (something I had seen on Heidenhain controls).
In the end, I was assigned a lathe with a Siemens control, and I’ve been very satisfied with it — it works well in practice and I can program effectively on it.However, the concept of having the chuck geometry considered in the motion/safety logic stayed in the back of my mind.
Since that idea seemed useful for safe at-the-machine programming, it eventually found its way into LatheEasyStep’s design.
Last edit: 8 months 3 hours ago by aDm1N.
The following user(s) said Thank You: tommylight, Surmetall

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

More
3 months 3 weeks ago #347529 by aDm1N
Replied by aDm1N on topic LatheEasyStep – experimental QtVCP macro for step-by-step lathe programming
Hi all,

another short update on LatheEasyStep:

I continued working on the embedded QtVCP startup behavior and focused on the panel initialization path.

On my machine, the startup time with the panel embedded in LinuxCNC was reduced from about 49 seconds down to about 11 seconds.

The main work was cleaning up the widget lookup/initialization path, removing expensive startup overhead, and limiting panel-related searches strictly to the panel itself instead of doing broader lookups.

The panel is now usable again immediately after startup on my system, which is a big improvement compared to the previous state.

I will continue cleaning up the code step by step, but this was an important milestone because the panel is now much more practical to use in everyday work.

Regards
The following user(s) said Thank You: Surmetall

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

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