Replies: 8 comments 33 replies
-
Hi John, thanks for the comment! The intent is there but for the time being this one stays on my backlog. You might also be interested in fluent-experiments branch which has a CQ like experimental fluent API and various experiments leveraging OpenCascade algorithms. I worked on this during last summer (northern hemisphere..), unfortunately I ran out of vacation before I could finish anything. I did use fluent-experiments to do some machining though, also last summer, so it's proven to work with some caveats. If you have small fixes, you're welcome to open PR's and I can take a look. Just keep in mind that sooner or later I do intend to do some heavy handed refactoring/rewriting to get this project stabilized, so you might not want to put too much effort here yet. I do have hopes that I'll manage to do that during the upcoming summer season. Also, btw I'll convert this to a discussion. |
Beta Was this translation helpful? Give feedback.
-
I will start going through the codebase and I will write some documentation along the way. I will try to tackle #19, and #20 and then take it from there! |
Beta Was this translation helpful? Give feedback.
-
Documentation thread: |
Beta Was this translation helpful? Give feedback.
-
Proposed gcode format:
|
Beta Was this translation helpful? Give feedback.
-
No worries. Probably plenty of pitfalls ahead as you expand from jupyter, but live and learn.
Nothing to build. For local development I personally install the library straight from the git repo as editable like this: https://github.com/voneiden/cq-cam#install-locally-editable-development-version Currently there are no PYPI packages. I'll automate that at some point with github actions once this thing is stable enough for regular use.
It uses sphinx-build command. Looks like sphinx is missing from requirements, but you'll probably have it installed if you have cadquery installed. https://github.com/voneiden/cq-cam/blob/unstable/build-docs.sh
In cq-cam folder run (preferably with conda or virtualenv active to avoid polluting system python)
I suppose we'll figure those out on the way. Some general things/thoughts:
|
Beta Was this translation helpful? Give feedback.
-
The remaining of my plan is to:
|
Beta Was this translation helpful? Give feedback.
-
My plan for post-processor. cq-cam Commands will simply capture the intend and all the relevant gcode data (e.g. T, X, Y, Z, F, S, etc.) Then the post-processor will read the Command list and decide what gcode to output. Example 1 - ToolChange: Some machines don't support tool changes using the M6 command in this case you can just use M0 command |
Beta Was this translation helpful? Give feedback.
-
https://github.com/voneiden/cq-cam/blob/unstable/src/cq_cam/fluent.py#L144 post-review: overriding job values is sketchy and may lead to unexpected behaviour. The feed/speed precedence could be: Job < Tool < Operation That is: operation feed/speed would override tool default would override job defaults edit: pardon the brevity, typing with one hand 😄 |
Beta Was this translation helpful? Give feedback.
-
Hello there,
I have recently started using cq_cam and I am quite enjoying and I would love to help it develop further.
I have already fixed a bug that I found locally but documentation is lacking so I am not sure if the way I do it is the best. If you are willing to walk me through the code I am happy to update the documentation and fix any bugs that I find
Best wishes,
John
Beta Was this translation helpful? Give feedback.
All reactions