Difference between revisions of "Python Solution to Dimension Tracking"
Jump to navigation
Jump to search
Russ hensel (talk | contribs) (Created page with "= The Problem = To make FreeCad work you often need to enter values of various dimensions. There does not seem to be a method internal to FreeCad ( and probably there should...") |
Russ hensel (talk | contribs) |
||
| Line 7: | Line 7: | ||
* Design decisions. | * Design decisions. | ||
| − | You more or less need some notes to keep track of this stuff. Some of this may be paper sketches, paper notes, and digital documents ( many may choose spreadsheets ). I find spreadsheets to be very error prone so I looked for a python solution. The very simple version of this is shown in: [[FreeCad Gear Box]] | + | You more or less need some notes to keep track of this stuff. Some of this may be paper sketches, paper notes, and digital documents ( many may choose spreadsheets ). I find spreadsheets to be very error prone so I looked for a python solution. The very simple version of this is shown in: [[FreeCad Gear Box]] This has now evolved, and this document will describe the solution. For the actual code contact: [[User:Russ_hensel]] |
Revision as of 08:23, 17 February 2017
The Problem
To make FreeCad work you often need to enter values of various dimensions. There does not seem to be a method internal to FreeCad ( and probably there should not be ). These dimensions come from various sources:
- Spec. sheets.
- Measurements
- Calculations
- Design decisions.
You more or less need some notes to keep track of this stuff. Some of this may be paper sketches, paper notes, and digital documents ( many may choose spreadsheets ). I find spreadsheets to be very error prone so I looked for a python solution. The very simple version of this is shown in: FreeCad Gear Box This has now evolved, and this document will describe the solution. For the actual code contact: User:Russ_hensel
