Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve Minimum Tensile Stress values in materials tables #926

Open
grumpyinca opened this issue Aug 31, 2024 · 1 comment
Open

Improve Minimum Tensile Stress values in materials tables #926

grumpyinca opened this issue Aug 31, 2024 · 1 comment
Assignees

Comments

@grumpyinca
Copy link
Contributor

Summary

Within spring design, this issue is being created to capture progress towards improvements in the Minimum Tensile Stress values (t010 & t400) contained in the built-in tables of material properties, both US Customary units and Metric Units (/ODOP/client/src/designtypes/Spring/mat_us.json and mat_metric.json).

Overview

This issue is visualized as the first of several steps towards improving and extending handling of material properties and standard wire sizes within ODOP:Spring. The steps may ultimately include:

  • revised Minimum Tensile Stress (MTS) values
  • imposing the exact (not interpolated) MTS value from the underlying standards document when a standard size is selected and FIXed
  • Expanding the number of standards supported for each generic wire material type. For example, when selecting MUSIC_WIRE, there would be sub-selections for ASTM (US), GB (British Standard), EN (European Union) and JIS (Japan). Each would carry its own standard size tables.

Background

This approach is driven by the understanding that, in making product planning decisions, wire manufacturers are strongly influenced by the standards mentioned above. This includes the specific wire diameters in the standard documents as well as the associated MTS values. There are specialty wire manufacturers with product offerings that go well beyond the standards, but the details are not currently well understood. There may be marketing opportunities in this area.

@grumpyinca grumpyinca added this to the Unassigned/Future milestone Aug 31, 2024
@grumpyinca grumpyinca self-assigned this Aug 31, 2024
@grumpyinca
Copy link
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant