Path Workbench: Difference between revisions

From FreeCAD Documentation
No edit summary
mNo edit summary
Line 66: Line 66:
You cant find more detail info in [[Template:Depths/Heights| depths and heights]].
You cant find more detail info in [[Template:Depths/Heights| depths and heights]].


===Why does not my operation produce output?===
===Why does my operation not produce any output?===
===Does Path workbench can make 3d surfacing machining?===
===Can Path workbench be used for 3d surfacing machining?===
===Can i make my owm post processor?===
===Can i make my owm post processor?===
===How i can set metric/imperial to my path object?===
===How can I set metric/imperial to my path object?===
===How i can simulate my strategies?===
===How can I simulate my strategies?===


===What is the meaning of red paths?===
===What is the meaning of red paths?===
===How i could check my G code sequence is right?===
===How can I check my G code sequence for correctness?===
<!--T:15-->
<!--T:15-->
[[Category:User Documentation]]
[[Category:User Documentation]]

Revision as of 19:02, 15 January 2018

Introduction

The Path workbench is used to produce machine instructions for CNC machines from a FreeCAD model. This can be used to produce real-world 3D objects on machines like mills, lathes, lasercutters or alike. Usually these instructions are some kind of GCode dialect.



The FreeCAD process to create these machine instructions is as follows:

  • You create a 3D model of your object, probably using one ore several of Part Design, Part or Draft workbench.
  • You create a Job in Path Workbench. You can think of it as a job you have to do at a real mill: You have some stock material, the mill has a certain set of tools and it follows certain commands controlling speed and movements (usually G-Code).
  • You select the tools you need to get the job done.
  • You create milling paths using e.g. Contour and Pocket operations. These Path objects use a slightly abstract G-Code represention which is independent from the machine.
  • Finally, since each type of machine often speaks a different G-Code dialect, you use a machine dependent post processor to create G-Code which. This translates the FreeCAD G-Code into the particular flavor recognized by your machine. There are several postprocessors included which you can use directly or use as a template for creating your own.

Links for the impatient

Depending on your interest in the Path workbench there are different topics for further reading:

  • If you are a new new user trying to get familiar with Path, you might be interested in a fast walk-through tutorial.
  • If you have a special machine which cannot use one of the available postprocessors you may want to write your own postprocessor
  • As an experienced user you may want to write a macro for the Path Workbench
  • Power user wanting to streamline process
  • New Developer wanting to understand core concepts.

General concepts

The Path Workbench generates the G-Code defining the paths required to mill the Project represented by the 3D Model on the destination mill—in a simple agnostic G-Code dialect.

The G-Code is generated from directives and Operations contained in a Path Job. The Job Workflow lists these in the order they will be executed. The list is populated by invoking Path Operations, Path Dressups, Path Partial Commands, and Path Modifications—from the Path Menu, or GUI buttons.

A summery of the contents of the Path Job includes:

  1. A list of Tool-Controller definitions, specifying the geometry, Feeds, and Speeds for the Path Operations Tools.
  2. A Workflow sequential list of Path Operations.
  3. A Base Body—a clone used for offset.
  4. A Stock, representing the raw material that will be milled to Path Workbench.
  5. A SetupSheet, containing inputs used by the Path Operations, including static values and formulas.
  6. Configuration parameters specifying the output G-Code job's destination path, file name, and extension, and the Postprocessor—used to generate the appropriate dialect for the target CNC Controller, and customize Units, Tool Changes, Parking, etc...

The Path Workbench provides a Tool Manager (Library, Table), and G-Code Inspection, and Simulation tools. It links the Postprocessor, and allows importing and exporting Job Templates.

The Path Workbench has external dependencies including:

  1. The FreeCAD 3D model units are defined in the Edit-> Preference...->General->Units tab's Units settings. The Postprocessor configuration defines the final G-Code units.
  2. The Macro file path, and Geometric tolerances, are defined in the Edit->Preferences...->Path->Job Preferences tab.
  3. Colors are defined in the Edit->Preferences...->Path->Path colors tab.
  4. Holding tag parameters are defined in the Edit->Preferences...->Path->Dressups tab.
  5. That the Base 3D Model quality supports the Path WB requirements—passes Check Geometry.

FreeCAD Path Workbench internal G-Code dialect represents Feed rates in Units/Second—what the G-Code Inspection tool will show. The Postprocessor is configured to generate the appropriate Feed rates—either in Units/Second or Units/Minute for the target mill.

GUI tools

Template:Path Tools

Scripting

The Path workbench offers a broad python scripting API. With it, you can create and modify paths from python scripts, or extend the available functionality of the workbench.

FAQ

How many axis Path workbench is be able to handle?

At the moment Path workbench can handle up to 3 axis.

What is the difference between clearance height and safe height?

You cant find more detail info in depths and heights.

Why does my operation not produce any output?

Can Path workbench be used for 3d surfacing machining?

Can i make my owm post processor?

How can I set metric/imperial to my path object?

How can I simulate my strategies?

What is the meaning of red paths?

How can I check my G code sequence for correctness?