kopia lustrzana https://github.com/vilemduha/blendercam
More Docs Updates
rodzic
87bc0ed493
commit
d692f32063
Plik binarny nie jest wyświetlany.
Po Szerokość: | Wysokość: | Rozmiar: 48 KiB |
Plik binarny nie jest wyświetlany.
Po Szerokość: | Wysokość: | Rozmiar: 44 KiB |
Plik binarny nie jest wyświetlany.
Po Szerokość: | Wysokość: | Rozmiar: 33 KiB |
|
@ -13,6 +13,21 @@ CNC replaced CAM in the name as it seemed more widely recognizable, and avoids a
|
|||
**Fabex** was **BlenderCAM** (now it is **Fabex** _not_ **BlenderCAM**), it hasn't been a long time now, since **BlenderCAM** and still a machinist's delight, on a moonlit night.
|
||||
```
|
||||
|
||||
## What do I do with the Gcode file that **Fabex** outputs?
|
||||
That will need to be sent to your machine so that it can be run.
|
||||
|
||||
The specifics of how to do it will vary between manufacturers, but, generally the Gcode file will be loaded into a Gcode sender which then connects or transmits the file to your CNC.
|
||||
|
||||
Some free, open-source Gcode senders include:
|
||||
- [UGS - Universal Gcode Sender](https://github.com/winder/Universal-G-Code-Sender)
|
||||
- [CNCJS](https://cnc.js.org/)
|
||||
- [Gsender](https://github.com/Sienci-Labs/gsender)
|
||||
- [bCNC](https://github.com/vlachoudis/bCNC)
|
||||
|
||||
```{note}
|
||||
There is also a prototype Gcode sender Extension for Blender called [gControl](https://github.com/SpectralVectors/gControl) for grbl-based machines - it allows for connection, jog control and sending simple jobs and commands, but should be considered Experimental until further notice.
|
||||
```
|
||||
|
||||
## When will you have full support for 4 and 5 axis Operations?
|
||||
None of the developers currently have access to a 4+ Axis machine, so until one of the developers acquires a 4th axis, or someone with a 4+ axis machine joins the development team, 4 and 5 axis Operations will remain officially unsupported (outside of manual indexing).
|
||||
|
||||
|
@ -107,18 +122,3 @@ If you have installed **Blender** from a package manager and you want to make **
|
|||
|
||||
## What do I do if I have a question that isn't covered in the FAQ or elsewhere in the docs?
|
||||
Your best bet is to ask in the chat.
|
||||
|
||||
## What do I do with the Gcode file that **Fabex** outputs?
|
||||
That will need to be sent to your machine so that it can be run.
|
||||
|
||||
The specifics of how to do it will vary between manufacturers, but, generally the Gcode file will be loaded into a Gcode sender which then connects or transmits the file to your CNC.
|
||||
|
||||
Some free, open-source Gcode senders include:
|
||||
- [UGS - Universal Gcode Sender](https://github.com/winder/Universal-G-Code-Sender)
|
||||
- [CNCJS](https://cnc.js.org/)
|
||||
- [Gsender](https://github.com/Sienci-Labs/gsender)
|
||||
- [bCNC](https://github.com/vlachoudis/bCNC)
|
||||
|
||||
```{note}
|
||||
There is also a prototype Gcode sender Extension for Blender called [gControl](https://github.com/SpectralVectors/gControl) for grbl-based machines - it allows for connection, jog control and sending simple jobs and commands, but should be considered Experimental until further notice.
|
||||
```
|
|
@ -244,3 +244,22 @@ The **[ Cutter ]** panel allows you to select a pre-defined cutting tool, or def
|
|||
The **[ Chains ]** panel allows you to combine multiple operations. It is useful for simulating more operations or exporting a chain of operations if you have automatic toolchanger or use the same tool for several operations.
|
||||
|
||||

|
||||
|
||||
## Menus
|
||||
Many of **Fabex**'s Tools can be accessed through the **Fabex CNC** menus located in the 3D viewport.
|
||||
|
||||

|
||||
|
||||
## Pie Menu
|
||||
**Fabex**'s entire panel, tool and menu layout can also be accessed through a multi-level Pie Menu system.
|
||||
|
||||

|
||||
|
||||
```{note}
|
||||
The Pie Menu is bound to the shortcut - `Alt + C` by default, but can be changed in Preferences.
|
||||
```
|
||||
|
||||
## Search Operator (F3)
|
||||
Any of **Fabex**'s Operators can be searched and executed using Blender's built-in Search Operator, activated with F3.
|
||||
|
||||

|
|
@ -86,7 +86,7 @@ Python wheels - executable binaries packed in for all supported systems.
|
|||
The wheels are for Python version 3.11, and will not work with other Python versions
|
||||
```
|
||||
|
||||
# Complete Addon Layout
|
||||
## Complete Addon Layout
|
||||
```
|
||||
scripts/addons/
|
||||
└── cam/
|
||||
|
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
This is a step-by-step tutorial on generating your first toolpath with Fabex.
|
||||
|
||||
For detailed descriptions of Panel options go [here](interface.md).
|
||||
For detailed descriptions of User Interface options go [here](interface.md).
|
||||
|
||||
## Setup your Scene
|
||||
You can use any object to generate toolpaths, but for the purpose of this guide we will use Suzanne, the monkey.
|
||||
|
|
|
@ -158,6 +158,6 @@ Projects any 2d curve on 3d surface
|
|||
- Add Pocket
|
||||
- Add Medial Mesh
|
||||
|
||||
# **Overview of Principle Strategies**
|
||||
## **Overview of Principle Strategies**
|
||||
|
||||

|
||||
|
|
|
@ -142,7 +142,7 @@ The way the detection works is each face in the mesh is checked to see if it is
|
|||
Operator option **z limit** controls which horizontal surfaces are considered a pocket. If the horizontal surface z location is below the z limit then the surface is considered a pocket. Setting z limit to 0.0 (default setting) should work for most situations if mesh top is at z=0.0.
|
||||
|
||||
## [ Curve Creators ]
|
||||
This operators will create shapes directly from the panel.
|
||||
These operators will create shapes directly from the panel.
|
||||
|
||||

|
||||
|
||||
|
|
Ładowanie…
Reference in New Issue