Path Workbench/ru: Difference between revisions

From FreeCAD Documentation
(Created page with "Верстак Path предоставляет широкий доступ через скрипты python. С их помощью можно создав...")
(Updating to match new version of source page)
Line 1: Line 1:
== Введение ==
== Введение ==


<div class="mw-translate-fuzzy">
Верстак Path используется для генерации [https://en.wikipedia.org/wiki/G-code G-кодов] для из моделей FreeCAD. Язык G-кодов используется [https://en.wikipedia.org/wiki/CNC_router станками с ЧПУ] и некоторыми [https://en.wikipedia.org/wiki/3D_printing 3D-принтерами] для производства реальных объёмных объектов.
Верстак Path используется для генерации [https://en.wikipedia.org/wiki/G-code G-кодов] для из моделей FreeCAD. Язык G-кодов используется [https://en.wikipedia.org/wiki/CNC_router станками с ЧПУ] и некоторыми [https://en.wikipedia.org/wiki/3D_printing 3D-принтерами] для производства реальных объёмных объектов.
</div>


The primary tool of the Path workbench is the Path object. A Path object describes the movement that a machine head must perform in order to cut through a block of material, in the case of CNC machines, or to add a layer of printing material, in the case of 3D printers. Path objects can contain not only movement information, but also other instructions for the machine, such as the rotation speed that the cutter must have, or the amount of material that must be used.


[[Image:pathwb.png]]
Path objects can be created in may ways, by giving them manually the points through which they must pass, or deriving them from a wire-shaped FreeCAD object, or, more interestingly, by deriving them automatically from an existing 3D object, or parts of it. This is a complex task, and the tools below are there to do this, or part of this, in different ways. It requires some use to know them all, and choose which one is more suited to the particular task you need. Sometimes, you might also prefer to build your paths step-by-step, using partial tools, instead of using the more complex tools.


Path objects can also be combined into Compounds or Arrays, allowing you to use different tools to do different parts of the whole cutting operation, and join them into one final path.


The FreeCAD Path Workbench Workflow creates these machine instructions as follows:
Project objects, finally, allow you to manage different cutting operations that have to be performed by a same machine, and add machine-specific information such as a table of cutting tools available on the machine, with their characteristics. Some Path tools will then be able to refer to that table to obtain information like the diameter of a certain cutting tool.
* A 3D model is the base object, typically created using one or more of [[PartDesign Workbench|Part Design]], [[Part Workbench|Part]] or [[Draft Workbench|Draft]] Workbenches.
* A [[Path_Job|Job]] is created in Path Workbench. This contains all the information necessary to generate the necessary G-Code to process Job on a CNC mill: there is Stock material, the mill has a certain [[Path_EditToolsTable|set of tools]] and it follows certain commands controlling speed and movements (usually G-Code).
* Tools are selected as required by the Job Operations.
* Milling paths are created using e.g. [[Path_Profile|Contour]] and [[Path_Pocket|Pocket]] Operations. These [[Path objects|Path objects]] use an internal agnostic FreeCAD G-Code dialect which is independent from the machine. This allows the Job to be output to any number of different real-world CNC Controllers by invoking different Postprocessors.
* Since each CNC Controller speaks a specific G-Code dialect, a Dialect-correct Postprocessor translates the internal agnostic FreeCAD G-Code to the machine's G-Code dialect. Several Postprocessors are included allowing direct use or as a template for modification. Postprocessors contain configuration flags and are designed to be tuned by adding G-Codes and M-Codes to provided definitions for:
**Machine initialization
**Job finalization
**Tool-Changes
**Cooling on /off
**Etc...


=== Links for the impatient ===
Finally, since each type of machine often speaks a different G-Code dialect, when exporting your final Paths to G-Code, you might want to use one of the included post-processing scripts, which translates the machine-agnostic FreeCAD G-Code into a particular flavor recognized by your machine.
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 [[Path Walkthrough for the Impatient|walk-through]] tutorial.
FreeCAD is also able to import G-Code files, for which a pre-processing script can also be used.
* If you have a special machine which cannot use one of the available postprocessors you may want to [[Write your own Postprocessor for the Path Workbench|write your own postprocessor]]
* As an experienced user you may want to write a [[Writing Macros for the Path Workbench|macro for the Path Workbench]]
* Power users may want to streamline processes.
* New Developers might want to understand core concepts.


== GUI tools ==
== 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 which is later translated to the appropriate dialect for the target CNC controller by selecting the proper Postprocessor.
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 adding Path Operations, Path Dressups, Path Partial Commands, and Path Modifications—from the Path Menu, or GUI buttons.


A summary of the contents of the Path Job includes:
{{Note|Warning|The Path workbench is still in early stages of development. Many of the tools below might not work as expected.}}
# A list of Tool-Controller definitions, specifying the geometry, Feeds, and Speeds for the Path Operations Tools.
# A Workflow sequential list of Path Operations.
# A Base Body—a clone used for offset.
# A Stock, representing the raw material that will be milled to Path Workbench.
# A SetupSheet, containing inputs used by the Path Operations, including static values and formulas.
# 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:
# 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.
# The Macro file path, and Geometric tolerances, are defined in the Edit->Preferences...->Path->Job Preferences tab.
# Colors are defined in the Edit->Preferences...->Path->Path colors tab.
# Holding tag parameters are defined in the Edit->Preferences...->Path->Dressups tab.
# 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 ==


{{Path_Tools/ru}}
{{Path_Tools/ru}}



== Скриптование ==
== Скриптование ==
Line 25: Line 63:
Верстак Path предоставляет широкий доступ через [[Path scripting|скрипты python]]. С их помощью можно создавать и модифицировать траектории из скриптов, или расширять функциональность верстака.
Верстак Path предоставляет широкий доступ через [[Path scripting|скрипты python]]. С их помощью можно создавать и модифицировать траектории из скриптов, или расширять функциональность верстака.


<div class="mw-translate-fuzzy">

[[Category:User Documentation/ru]]
[[Category:User Documentation/ru]]
</div>

===Why does my operation not produce output?===
===Can Path Workbench perform 3D surfacing machining?===
===Can I modify an existing, or make my own Postprocessor?===
===How I can set metric/imperial to my path object?===
===How I can simulate my strategies?===

===What is the significance of paths red and green colors?===
===How do I check that my G-Code sequence is right?===
[[Category:User Documentation]]
{{clear}}
{{clear}}
<languages/>
<languages/>

Revision as of 17:47, 17 January 2018

Введение

Верстак Path используется для генерации G-кодов для из моделей FreeCAD. Язык G-кодов используется станками с ЧПУ и некоторыми 3D-принтерами для производства реальных объёмных объектов.



The FreeCAD Path Workbench Workflow creates these machine instructions as follows:

  • A 3D model is the base object, typically created using one or more of Part Design, Part or Draft Workbenches.
  • A Job is created in Path Workbench. This contains all the information necessary to generate the necessary G-Code to process Job on a CNC mill: there is Stock material, the mill has a certain set of tools and it follows certain commands controlling speed and movements (usually G-Code).
  • Tools are selected as required by the Job Operations.
  • Milling paths are created using e.g. Contour and Pocket Operations. These Path objects use an internal agnostic FreeCAD G-Code dialect which is independent from the machine. This allows the Job to be output to any number of different real-world CNC Controllers by invoking different Postprocessors.
  • Since each CNC Controller speaks a specific G-Code dialect, a Dialect-correct Postprocessor translates the internal agnostic FreeCAD G-Code to the machine's G-Code dialect. Several Postprocessors are included allowing direct use or as a template for modification. Postprocessors contain configuration flags and are designed to be tuned by adding G-Codes and M-Codes to provided definitions for:
    • Machine initialization
    • Job finalization
    • Tool-Changes
    • Cooling on /off
    • Etc...

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 users may want to streamline processes.
  • New Developers might want 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 which is later translated to the appropriate dialect for the target CNC controller by selecting the proper Postprocessor.

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 adding Path Operations, Path Dressups, Path Partial Commands, and Path Modifications—from the Path Menu, or GUI buttons.

A summary 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/ru


Скриптование

Верстак Path предоставляет широкий доступ через скрипты python. С их помощью можно создавать и модифицировать траектории из скриптов, или расширять функциональность верстака.

Why does my operation not produce output?

Can Path Workbench perform 3D surfacing machining?

Can I modify an existing, or make my own Postprocessor?

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

How I can simulate my strategies?

What is the significance of paths red and green colors?

How do I check that my G-Code sequence is right?