Search found 1715 matches

Go to advanced search

by sliptonic
Tue Jun 02, 2020 2:51 pm
Forum: Path/CAM
Topic: Exporting GCode for a BOSS5 Bridgeport CNC?
Replies: 6
Views: 138

Re: Exporting GCode for a BOSS5 Bridgeport CNC?

Just last month we went through this process for a Heidenhain post-processor and the original poster Zibibbo84 did a great job. Aside: Are these post-processors documented somewhere on the wiki ? There's a list of them on the path post page but the individual posts are not documented. Their usage i...
by sliptonic
Mon Jun 01, 2020 6:31 pm
Forum: Path/CAM
Topic: Prevent automatic list fill
Replies: 4
Views: 97

Re: Prevent automatic list fill

How to clear the list (Base Geometry) within Drilling operation? Select the rows in the geometry tab. (Not the tick selection, you actually have to select the rows. Or select one row and then do Ctrl+A Then use the 'remove' button What you mean by select holes before creating the operation? If I se...
by sliptonic
Mon Jun 01, 2020 4:41 pm
Forum: Python scripting and macros
Topic: Need some help with the math
Replies: 18
Views: 687

Re: Need some help with the math

I posted the first of a series of videos about this project. This is just the introduction so not much content yet. I've been able to do some very basic bends. I still have some issues to work out and I want to merge the b-code generating logic into master as a python module. I'm not sure what this ...
by sliptonic
Mon Jun 01, 2020 4:38 pm
Forum: Path/CAM
Topic: Prevent automatic list fill
Replies: 4
Views: 97

Re: Prevent automatic list fill

If you select holes before creating the operation, it should only use the selection. If you select nothing, it will autodetect drillable holes but you can always clear the list.
by sliptonic
Mon Jun 01, 2020 4:15 pm
Forum: Path/CAM
Topic: Exporting GCode for a BOSS5 Bridgeport CNC?
Replies: 6
Views: 138

Re: Exporting GCode for a BOSS5 Bridgeport CNC?

If you find limitations in the linuxcnc post, please take the time to really understand the issue before making a custom post. If the problem is a limitation of the existing post-processor that applies to more machines, you'll get plenty of help to improve the linuxcnc post rather than inventing a n...
by sliptonic
Sun May 31, 2020 10:54 pm
Forum: Path/CAM
Topic: Exporting GCode for a BOSS5 Bridgeport CNC?
Replies: 6
Views: 138

Re: Exporting GCode for a BOSS5 Bridgeport CNC?

The sample gcode you gave isn't too far off from the linuxcnc post. You might need to customize the post but probably not. For starters, your sample has line numbers turned on. That's the N20, N30, N40 bit on each line. From there, I'm seeing G0 and G81 moves so I'd guess this sample was a drilling ...
by sliptonic
Fri May 29, 2020 4:06 am
Forum: Path/CAM
Topic: Is it possible to nest parts / bodies for milling?
Replies: 8
Views: 307

Re: Is it possible to nest parts / bodies for milling?

There have been some experiments and some ideas batted around for a nesting tool but nothing that's ready for 'prime time'.

Sorry
by sliptonic
Thu May 28, 2020 3:05 pm
Forum: Path/CAM
Topic: Path Code Style Guide
Replies: 27
Views: 614

Re: Path Code Style Guide

flake8 --ignore=E226,E266,W503 file.py E226: spaces around arithmetic operators `*`, `/`, `+`, `-`; sometimes we don't need a space. E266: only one `#` for comments; we need two `##` for Doxygen documentation. W503: break lines before a binary operator like `and` and `or`. The W503 warning will be ...
by sliptonic
Tue May 26, 2020 8:32 pm
Forum: Path/CAM
Topic: Path Code Style Guide
Replies: 27
Views: 614

Re: Path Code Style Guide

I will not confuse camelCase and PascalCase ever again. I will not confuse camelCase and PascalCase ever again. I will not confuse camelCase and PascalCase ever again. I will not confuse camelCase and PascalCase ever again. I will not confuse camelCase and PascalCase ever again. I will not confuse c...
by sliptonic
Tue May 26, 2020 7:29 pm
Forum: Path/CAM
Topic: Path Code Style Guide
Replies: 27
Views: 614

Re: Path Code Style Guide

UPPERCASE are constants; camel_case for all variable and function names; PascalCase for classes. This are the basics. Initial underscore is for private entitities, _smal_function, _SmallClass. Essentially, Python heavily favors camel_case, except for classes. Even module names should follow this, m...

Go to advanced search