Introduction
Motosize is an excellent tool to verify which robot or positioner will work with a tool, part, or fixture. However, it can feel intimidating for most people when trying to determine what data is needed to get the results needed. The following examples define which data the customer will need to provide to complete the analysis.
Always remember…the quality of the results will always depend on the quality of the customer data.
Evaluate a Robot: Customer Data Needed
Preferred Customer Data:
The best Data are native 3D CAD models. The original models contain the correct mass properties.
But to make sure, the following needs to be completed by the customer:
- All components (at least the major components) need to be present and need to be solid bodies (no surfaces).
- All components need to have their mass defined (either by material type or overriding the default mass).
- If the robot is picking and moving a part, the heaviest part model needs to be included.
- REMEMBER: The CAD model of the tool should represent the actual tool as closely as possible.
Once the data is ready to send, use the CAD software’s “Pack and Go” feature to collect and zip up all the relevant files.
For more information on sending CAD models, see the Whitepaper “How to Use Pack and Go”.
Fallback Customer Data:
If the native CAD models are not available, use a neutral CAD format of the tool/part.
It is important to know that there will be no mass data included, just geometry.
The customer will need to complete the following:
- Supply a STEP or Parasolid model of the tool/part.
- Markup screenshots visually showing each component’s material or what each component weighs.
- If the robot is picking and moving a part, the heaviest part model needs to be included.
- REMEMBER: The CAD model of the tool should represent the actual tool as closely as possible.
Please note that this method is less accurate and more time consuming.
Better than Nothing Customer Data:
If there is no 3D model, then the only other option is to rely on 2D drawings or manual measurements.
Note: These results are only useful in the early concept stage of design.
Data Needed:
- Estimated mass of the tool
- Estimated mass of the heaviest part
- Basic tool dimensions (Length, Width, and Height or Diameter and Height)
- Basic part dimensions (Length, Width, and Height or Diameter and Height)
- Estimated Center of Gravity (Cg) of the tool in X, Y, Z
- Estimated Center of Gravity (Cg) of the part in X, Y, Z
Note:
- All Cg dimensions start from the robot flange.
- Results are estimated and will report only on the B and T axis (5th & 6th axis)
- Results can be skewed if the tool has a lot of open gaps vs the estimated tool’s filled volume.
Evaluate Headstock / Multi-Axis Positioners / Tables: Customer Data Needed
Preferred Customer Data:
The best Data are native 3D CAD models. The original models contain the correct mass properties.
But to make sure, the following needs to be completed by the customer:
- All components (the fixture and the part) need to be present and need to be solid bodies (no surfaces).
- All components need to have their mass defined (either by material type or overriding the default mass).
- REMEMBER: The CAD model of the fixture and part should represent the actual tool as closely as possible.
Once the data is ready to send, use the CAD software’s “Pack and Go” feature to collect and zip up all the relevant files.
For more information on sending CAD models, see the Whitepaper “How to Use Pack and Go.”
Fallback Customer Data:
If the native CAD models are not available, use a neutral CAD format of the part/fixture.
It is important to know that there will be no mass data included, just geometry.
The customer will need to complete the following:
- Supply a STEP or Parasolid model of the part/fixture.
- Markup screenshots visually showing each component’s material or what each component weighs.
- REMEMBER: The CAD model of the fixture and part should represent the actual tool as closely as possible.
Please note that this method is less accurate and more time consuming.
Comments
0 comments
Please sign in to leave a comment.