- Status Assigned
- Percent Complete
- Task Type Feature Request
- Category QCAD/CAM
-
Assigned To
andrew - Operating System All
- Severity Low
- Priority Very Low
- Reported Version 3.22.1
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
Attached to Project: QCAD Bugtracker
Opened by Harms2015 - 13.06.2019
Last edited by andrew - 13.06.2019
Opened by Harms2015 - 13.06.2019
Last edited by andrew - 13.06.2019
FS#1901 - CAM Traverse Toolpath
Hallo Andrew,
Still busy on the never ending G-code story. Urgently needed the very common Traverse Toolpath.
Example added as pdf.
Greetings
Loading...
Available keyboard shortcuts
- Alt + ⇧ Shift + l Login Dialog / Logout
- Alt + ⇧ Shift + a Add new task
- Alt + ⇧ Shift + m My searches
- Alt + ⇧ Shift + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + ⇧ Shift + e ↵ Enter Edit this task
- Alt + ⇧ Shift + w watch task
- Alt + ⇧ Shift + y Close Task
Task Editing
- Alt + ⇧ Shift + s save task
Just a friendly / honest assessment: this is unlikely to be implemented anytime soon from our side.
I'd suggest to implement this in your post processor as a toolpath for a point entity (perhaps on a special layer). Parameters could be attached to the point entity as custom properties.
Hallo Andrew,
I had already figured out a work around for myself, for the issue of not being able to specify the Toolpath's Initial Startpoint -coordinate. (See the attachment).
My proposal not only solves that issue, it also makes CAD/CAMming more easy, logical and consistent, and it prepares QCAD/CAM for milling and turning. As a bonus it also adds G-code-controller synchronisation, to avoid tool collisions. To me it seems pretty odd not implementing the first and most basic toolpath used by every CAM/CNC-operator. Why???
As for programming a toolpath in the post processor myself; I do need the example of an already functional toolpath for figuring out how to achieve such a thing.