LibLathe - Lathe Path Generation

[WarrenkCash]

This is discussed on page 16 and 17 of this post. You need to replace the 4 files giving you the error with the ones on page 17.

This whole thread is worth reading if you are using LibLathe.

[PaPaSteve]

This is discussed on page 16 and 17 of this post. You need to replace the 4 files giving you the error with the ones on page 17.

This whole thread is worth reading if you are using LibLathe.

THX Warren
Your correct ... I haven't read the whole thread ... time to dig in properly.
Will all these changes be addressed with an update in the Turning addon manager ?

Thanks again
Steve

[GeneFC]

Will all these changes be addressed with an update in the Turning addon manager ?

You should understand that such addons are not part of the FreeCAD core. They are usually developed and maintained by a single person, in this case the user known as dubstar-04.

Dan has been very helpful for a long time, as seen by the many contributions in this topic and other topics.

In this case you might consider just adding the already proven fixes and get on with using LibLathe.

Dan may or may not decide to create an update.

Gene

[PaPaSteve]

You should understand that such addons are not part of the FreeCAD core. They are usually developed and maintained by a single person, in this case the user known as dubstar-04.

Dan has been very helpful for a long time, as seen by the many contributions in this topic and other topics.

In this case you might consider just adding the already proven fixes and get on with using LibLathe.

Dan may or may not decide to create an update.

Gene

A new FreeCAD user here still trying to learn the software and all the nuances.
There was no attempt to disrespect anyone.
My apology if that's how it was received.

[PaPaSteve]

I have as suggested by @mlampert added the parentjob to each of the libLathe turning Op's.It is the last function in each file. I commented out the original function and added the changed code below. The files are attached so others can test.
These files should work as intended with the origional PathOPGiu.py. Reading the code there is still a few things to implement but the operations are very usable for creating paths. Most of the code is way over my head though.

Warren
I've found the original PathOPGiu.py , navigated to line 1378 which, appears to read the same as your edit.
And downloaded your 4 files on page 17 and am now confused how where they are used.
Time to ask around town for someone with python coding experience.


Also noticed your part file is labeled "wheel spacer"
A wheel spacer is the project I'm currently trying to accomplish for an electric conversion of a KTM motorcycle.
THX for your contributions.

[GeneFC]

There was no attempt to disrespect anyone.
My apology if that's how it was received.

It was not received that way at all. Just explaining how things typically work.

Gene

[WarrenkCash]

Warren
I've found the original PathOPGiu.py , navigated to line 1378 which, appears to read the same as your edit.
And downloaded your 4 files on page 17 and am now confused how where they are used.
Time to ask around town for someone with python coding experience.

From memory just replace the four files with new ones. On my system they were located in C:\FreeCAD 0.20\Mod\FreeCAD_Turning_Addon-master\PathTurnScripts\

I think I originally modified PahtOPGui.py but was pointed in the right direction and ended up modifying each turning op instead.

Also noticed your part file is labeled "wheel spacer"
A wheel spacer is the project I'm currently trying to accomplish for an electric conversion of a KTM motorcycle.
THX for your contributions.

It was a rear wheel space for a YZ 250 Yamaha.

[PaPaSteve]

From memory just replace the four files with new ones. On my system they were located in C:\FreeCAD 0.20\Mod\FreeCAD_Turning_Addon-master\PathTurnScripts\

I think I originally modified PathOPGui.py but was pointed in the right direction and ended up modifying each turning op instead.

THX
Changing the 4 files pushed me a little further along but still getting " PathOPGui.py " error codes.
I'll need to focus on and understand those errors to move further.

*******************************

Now that I've transitioned from the daily grind to a hobby creator the life goal is to consider cost cutting away from costly CAD packages into more of the open source software for occasional use.
My first project experience with FreeCAD being a lathe job has left me bewildered.
A few minutes working in Solidworks and I'm ready to machine.
The Solidworks license will expire at some point which leaves me looking at FreeCAD again ... hopefully this " PathOPGui.py " error code issue will resolve one way or another.

Thanks for your patience ...

[runryder]

Is there a grbl post processor available to use for liblathe? I am only seeing the linuxcnc version?

Code: Select all

OS: Windows 10 Version 1809
Word size of FreeCAD: 64-bit
Version: 0.20.29177 (Git)
Build type: Release
Branch: releases/FreeCAD-0-20
Hash: 68e337670e227889217652ddac593c93b5e8dc94
Python 3.8.10, Qt 5.15.2, Coin 4.0.1, Vtk 8.2.0, OCC 7.6.2
Locale: English/United States (en_US)
Installed mods: 
  * A2plus 0.4.60k
  * Assembly4 0.12.6
  * Curves 0.6.8
  * fasteners 0.4.55
  * FeedsAndSpeeds 0.5.0
  * FreeCAD_Turning_Addon-master 0.1.0
  * Manipulator 1.5.0
  * sheetmetal 0.2.62
  * ThreadProfile 1.84.0

[runryder]

Is there a grbl post processor available to use for liblathe? I am only seeing the linuxcnc version?

I'm using IO Sender and I noticed that the Y0.000 is in the Gcode

Code: Select all

OS: Windows 10 Version 1809
Word size of FreeCAD: 64-bit
Version: 0.20.29177 (Git)
Build type: Release
Branch: releases/FreeCAD-0-20
Hash: 68e337670e227889217652ddac593c93b5e8dc94
Python 3.8.10, Qt 5.15.2, Coin 4.0.1, Vtk 8.2.0, OCC 7.6.2
Locale: English/United States (en_US)
Installed mods: 
  * A2plus 0.4.60k
  * Assembly4 0.12.6
  * Curves 0.6.8
  * fasteners 0.4.55
  * FeedsAndSpeeds 0.5.0
  * FreeCAD_Turning_Addon-master 0.1.0
  * Manipulator 1.5.0
  * sheetmetal 0.2.62
  * ThreadProfile 1.84.0