[Home]History of LinesToArcs

LinuxCNCKnowledgeBase | RecentChanges | PageIndex | Preferences | LinuxCNC.org

Revision 9 . . June 16, 2013 5:07 am by Ftkalcevic
Revision 8 . . June 16, 2013 4:55 am by Ftkalcevic
Revision 7 . . June 16, 2013 4:54 am by Ftkalcevic
Revision 6 . . June 16, 2013 4:53 am by Ftkalcevic
Revision 5 . . June 16, 2013 4:52 am by Ftkalcevic
Revision 4 . . June 16, 2013 4:51 am by Ftkalcevic
Revision 3 . . June 16, 2013 4:50 am by Ftkalcevic
Revision 2 . . June 16, 2013 4:48 am by Ftkalcevic
Revision 1 . . June 16, 2013 4:41 am by Ftkalcevic
  

Difference (from prior major revision) (no other diffs)

Added: 9a10,15
The program works by taking the first two line segments and trying to fit an arc to it. If it can fit an arc, it tries to add the next point, and so on, until the next point no longer makes an arc. Those matching line segments are then removed and replaced with one arc. To ensure we really are matching an arc, the program also measures the accumulated length of the collected line segments and compares it to the length of the substitute arc (incorrectly called chord length in the code).

There are 2 tolerance tweaking parameters defined in g1tog23.py - point_tolerance and length_tolerance which are used to determine how far off the arc the next point is allowed, and how far off each line segment is allowed to be from the true length of the arc. The values are those that I use when exporting STL from Alibre Design and generating GCode from Slic3r.

Usage




LinuxCNCKnowledgeBase | RecentChanges | PageIndex | Preferences | LinuxCNC.org
Search:
Published under a Creative Commons License