Blog: Mapping MTConnect Streams for Dashboard Visualization#4513
Blog: Mapping MTConnect Streams for Dashboard Visualization#4513sumitshinde-84 wants to merge 7 commits intomainfrom
Conversation
|
Images automagically compressed by Calibre's image-actions ✨ Compression reduced images by 67%, saving 749.3 KB.
|
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Images automagically compressed by Calibre's image-actions ✨ Compression reduced images by 71.7%, saving 194.3 KB.
1 image did not require optimisation. |
andreguerra7
left a comment
There was a problem hiding this comment.
@sumitshinde-84 Approved, added minor comments
|
|
||
| MTConnect organizes data into three categories: | ||
|
|
||
| - Samples - Continuous numeric measurements like spindle speed, axis position, temperature, power consumption. These values change smoothly and have units. |
There was a problem hiding this comment.
@sumitshinde-84 suggestion add "the" : Condition - Equipment health at the component level: normal, warning, fault, unavailable.
|
|
||
| ## XML Response Structure | ||
|
|
||
| Query `/current` and you get XML structured around machine hierarchy. A `Streams` container holds `DeviceStream` elements for each device. Each device contains `ComponentStream` elements for components like spindles and axes. Inside components sit the actual data—`Samples`, `Events`, and `Condition` elements. |
There was a problem hiding this comment.
@sumitshinde-84 I'm not familiar with MTC, but something to consider: "Condition entries are reported based on their condition state/type rather than a single generic element.”

Description
Related Issue(s)
Checklist