You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Part of what I'm trying to achieve is to be able to send a manufacturing job to a printer in a fleet of printers that has the right material currently loaded for the job.
In order to achieve this, I need to know as much as possible of the mechanical properties of the currently loaded material, given the fact that there are thousands of commercial names for materials and it will be near-impossible, if even desirable, to classify them in a centralized reference database.
My proposition is not to change the required fields, but add many more optional fields. Using a serialization format to store the data should allow still using 1K NFC chips, but if at some point optional data become too powerful, 2K/4K support should be possible while still supporting 1K for required and some optional data.
In this proposition I've also included a section to track the usage of the spool dynamically, and an abrasiveness level that will be discussed in another issue. This is only an initial draft, but it could look something like this:
Part of what I'm trying to achieve is to be able to send a manufacturing job to a printer in a fleet of printers that has the right material currently loaded for the job.
In order to achieve this, I need to know as much as possible of the mechanical properties of the currently loaded material, given the fact that there are thousands of commercial names for materials and it will be near-impossible, if even desirable, to classify them in a centralized reference database.
My proposition is not to change the required fields, but add many more optional fields. Using a serialization format to store the data should allow still using 1K NFC chips, but if at some point optional data become too powerful, 2K/4K support should be possible while still supporting 1K for required and some optional data.
In this proposition I've also included a section to track the usage of the spool dynamically, and an abrasiveness level that will be discussed in another issue. This is only an initial draft, but it could look something like this:
The text was updated successfully, but these errors were encountered: