Difference between revisions of "Device Functionality Groups"

From MTConnect® User's Portal
Jump to: navigation, search
(Okuma)
(Mazak)
 
(4 intermediate revisions by one user not shown)
Line 1: Line 1:
 
== Device Functionality Groups ==
 
== Device Functionality Groups ==
  
The MTConnect implementation that has been most closely tracking the MTConnect standard and is used in most production implementation is the C++ Agent that resides on the MTConnect project pages of github [http://github.com/mtconnect/cppagent C++ Agent] . As part of the effort, we also provide pre-built Windows x86 binaries that are statically linked and can be run on any Windows computer dating from around Windows XP SP2 and later. Earlier builds are possible, but these will be left up to the reader. The pre-built binaries can be found at: [http://github.com/mtconnect/cppagent/releases C++ Agent Releases].
+
Partial machine, control, and adapter support and functionality supplied by builders are listed here. Many additional devices are supported from the factory or via third party adapters, and the MTConnect standard may be extended to cover additional data items.
 
+
The C++ Agent provides the fullest implementation of the standard available at the time of release. The version number (Major, Minor, Patch, Build) are tied to the MTConnect standard. The first three (Major, Minor, Build) are based directly on the MTConnect standard release nomenclature and the build number will increment as new versions of the C++ agent is released. When the agent is in pre-release for a upcoming version of the standard, it will be suffixed with a RCn where this stands for Release Candidate n as in RC1.
+
 
+
The agent has a rich level of configuration and is capable of serving up content from the local file system and allowing changes to be pushed. To get the full details on the configuration, again, visit the [http://github.com/mtconnect/cppagent C++ Agent github page] and scroll down to the readme.md. There are many features built in to the agent, some documented better than others. We will try to document some of the more interesting capabilities on these pages.
+
  
 
==== DMG Mori ====
 
==== DMG Mori ====
Line 24: Line 20:
  
 
[[Media:Mazak_QTN_Matrix2_MTConnect Functionality.pdf]]
 
[[Media:Mazak_QTN_Matrix2_MTConnect Functionality.pdf]]
 +
 +
[[Media:Mazak_Smooth_CNC_MTConnect Functionality.PDF]]
  
 
[[Media:Mazak_VCN_Matrix_MTConnect Functionality.pdf]]
 
[[Media:Mazak_VCN_Matrix_MTConnect Functionality.pdf]]
  
 
[[Media:Mazak_VCN_Matrix2_MTConnect Functionality.pdf]]
 
[[Media:Mazak_VCN_Matrix2_MTConnect Functionality.pdf]]
 +
 +
==== NUM ====
 +
 +
[[Media:NUM_MTConnect Functionality.pdf]]
  
 
==== Okuma ====
 
==== Okuma ====

Latest revision as of 07:36, 11 September 2017

Contents

Device Functionality Groups

Partial machine, control, and adapter support and functionality supplied by builders are listed here. Many additional devices are supported from the factory or via third party adapters, and the MTConnect standard may be extended to cover additional data items.

DMG Mori

Media:DMG Mori-MAPPS_MTConnect Functionality.pdf

Doosan

Media:Doosan_MTConnect Functionality.pdf

Mazak

Media:Mazak_Integrex_eseries_Matrix_MTConnect Functionality.pdf

Media:Mazak_Integrex_eseries_Matrix2_MTConnect Functionality.pdf

Media:Mazak_QTN_Matrix_MTConnect Functionality.pdf

Media:Mazak_QTN_Matrix2_MTConnect Functionality.pdf

Media:Mazak_Smooth_CNC_MTConnect Functionality.PDF

Media:Mazak_VCN_Matrix_MTConnect Functionality.pdf

Media:Mazak_VCN_Matrix2_MTConnect Functionality.pdf

NUM

Media:NUM_MTConnect Functionality.pdf

Okuma

Media:OKUMA-Lathe_MTConnect Functionality.pdf

Media:OKUMA-MachiningCenter_MTConnect Functionality.pdf