I am sitting in the Hyatt Regency in Cincinnati and am happy to be back at the MTConnect Working Group Technical Advisory Group. Day 1 (Nov 7) is where the data and working groups get to meet - tomorrow (Day 2) will be the summary day. We are in a process to vote on introducing MTConnect XML Schema Ver 1.2 which ends Nov 30, 2011. Day 3 will be the first MTConnect Trade show and conference called MC2 (that ends day 4 - Thursday).
Section 1 - Standards Overview by Will Sobel from System Insights, Inc.
Check out www.mtconnect.org for a free download of the the MTConnect standards
Ver 1.1 Brought in Sensor Data - device, data item or 2nd/3rd level component
Ver 1.2 Brought in Assets Detail
* Part 1 - Overview & Protocol
* Part 2 - Components & Data Items - work on sensors impacted this greatly
(moved from 76 data types, but after the statistics were put in with
30 different sensors - now have 2700 distinct data types
* Part 3 - Streams, events, Samples & Condition
Minor changes - rearrangement
Mobile Assets:
Mobile Assets are something asscoiated with the manufacturing process that is not a component of a device, can be removed without harming the function o fthe device, and can be associated with other devices during their life cycle. A mobile asset does not have computational capabilities.
Cutting Tool:
Cutting Tool is an assembly of items for removing material from a work-piece through a shearing action at the defined cutting edge or edges. Follows ISO 13399 Standard.
-> Cutting Tool = Cutting Item + Tool Item + Adapter Item + Assembly Item (screws, etc)
Pull Stud (retention knob) not yet incorporated as a data item.
Interestingly, grinding is not yet been worked on...
Section 2 - Proposed Product Directory - by Paul Warndorf, VP Technology AMT
- Current Identifiers = Hardware, software Applications, Development Tools, Consulting Services, Training
Getting Started with MTConnect Connectivity Guide now available (something that we helped helped with). Click here - http://www.mtconnect.org/media/7312/getting_started_with_mtconnect_-_final.pdf
This report identified 3 types of
1. Native Devices
2. Translation Dependent Devices
3. Data Connection Dependent Devices <--Nexas focus
Companies like Mazak have done a good job of describing how MTConnect can be implemented in Mazak Machine Tools - check out http://www.mazakusa.com/MTConnect/MTConnect_Brochure_7_15_2011_For_Viewing.pdf
Section 3 - Bar Feeding Group (MC2) - Randy Lewis, LNS America from Cincinnati, OH
Worked well with goals and deadlines - hard deadline for Mazak demo mid-October for integrating a LNS bar feeder via MTConnect to to a Mazak Machine Tool. Started with I/O, then more and more data. Demo went off without a hitch and the process led to enhanced automation possibilities.
Read - Read Concept = both bar feeder and machine tool cross read data simulates read/write as write is currently not supported. This format allows for equal automation components to cross-talk.
The I/O speed is quite fast - as fast as hard I/O - like 50 Milli-seconds, perhaps even faster with "push". Will Sobel pointed out that if you set the scan loop update to "0" no extra delays using a multi-threaded observer model (Report By Exception) rather than easier polling method. Randy was using local.host for this demo (one agent was handling both CNC and bar-feeder as the software was on the Mazak's PC).
Neil Desrosier from Mazak wrote the Mazak side of the bar-feeder and was impressed with the speed and openness and extensibility of the MTConnect solution. The MTConnect solution can add up the amount used and the amount available for better utilization and less scrap.
MACHINE TOOL BAR FEEDER
Read
Agent+Adapter -------> Client -------> PLC
| |
| Read |
CNC<----------Client <------Agent/Adapter
Overview Video:
Check out https://github.com/mtconnect for source code for all demos.
Section 1 - Standards Overview by Will Sobel from System Insights, Inc.
Check out www.mtconnect.org for a free download of the the MTConnect standards
Ver 1.1 Brought in Sensor Data - device, data item or 2nd/3rd level component
Ver 1.2 Brought in Assets Detail
* Part 1 - Overview & Protocol
* Part 2 - Components & Data Items - work on sensors impacted this greatly
(moved from 76 data types, but after the statistics were put in with
30 different sensors - now have 2700 distinct data types
* Part 3 - Streams, events, Samples & Condition
Minor changes - rearrangement
Mobile Assets:
Mobile Assets are something asscoiated with the manufacturing process that is not a component of a device, can be removed without harming the function o fthe device, and can be associated with other devices during their life cycle. A mobile asset does not have computational capabilities.
Cutting Tool:
Cutting Tool is an assembly of items for removing material from a work-piece through a shearing action at the defined cutting edge or edges. Follows ISO 13399 Standard.
-> Cutting Tool = Cutting Item + Tool Item + Adapter Item + Assembly Item (screws, etc)
Pull Stud (retention knob) not yet incorporated as a data item.
Interestingly, grinding is not yet been worked on...
Section 2 - Proposed Product Directory - by Paul Warndorf, VP Technology AMT
- Current Identifiers = Hardware, software Applications, Development Tools, Consulting Services, Training
Getting Started with MTConnect Connectivity Guide now available (something that we helped helped with). Click here - http://www.mtconnect.org/media/7312/getting_started_with_mtconnect_-_final.pdf
This report identified 3 types of
1. Native Devices
2. Translation Dependent Devices
3. Data Connection Dependent Devices <--Nexas focus
Companies like Mazak have done a good job of describing how MTConnect can be implemented in Mazak Machine Tools - check out http://www.mazakusa.com/MTConnect/MTConnect_Brochure_7_15_2011_For_Viewing.pdf
Section 3 - Bar Feeding Group (MC2) - Randy Lewis, LNS America from Cincinnati, OH
Worked well with goals and deadlines - hard deadline for Mazak demo mid-October for integrating a LNS bar feeder via MTConnect to to a Mazak Machine Tool. Started with I/O, then more and more data. Demo went off without a hitch and the process led to enhanced automation possibilities.
Read - Read Concept = both bar feeder and machine tool cross read data simulates read/write as write is currently not supported. This format allows for equal automation components to cross-talk.
The I/O speed is quite fast - as fast as hard I/O - like 50 Milli-seconds, perhaps even faster with "push". Will Sobel pointed out that if you set the scan loop update to "0" no extra delays using a multi-threaded observer model (Report By Exception) rather than easier polling method. Randy was using local.host for this demo (one agent was handling both CNC and bar-feeder as the software was on the Mazak's PC).
Neil Desrosier from Mazak wrote the Mazak side of the bar-feeder and was impressed with the speed and openness and extensibility of the MTConnect solution. The MTConnect solution can add up the amount used and the amount available for better utilization and less scrap.
MACHINE TOOL BAR FEEDER
Read
Agent+Adapter -------> Client -------> PLC
| |
| Read |
CNC<----------Client <------Agent/Adapter
Overview Video:
Check out https://github.com/mtconnect for source code for all demos.
No comments:
Post a Comment