{"id":276,"date":"2020-04-29T01:09:26","date_gmt":"2020-04-29T01:09:26","guid":{"rendered":"https:\/\/dxhelpdev.wpengine.com\/?post_type=epkb_post_type_1&p=276"},"modified":"2023-01-27T23:04:50","modified_gmt":"2023-01-27T23:04:50","slug":"mtconnect-communication-as-a-source","status":"publish","type":"epkb_post_type_1","link":"https:\/\/dxhelp.scytec.com\/?epkb_post_type_1=mtconnect-communication-as-a-source","title":{"rendered":"MTConnect Communication as a Source"},"content":{"rendered":"\n

Overview<\/h2>\n\n\n\n

DataXchange supports the MTConnect standard allowing the retrieval of equipment information from supported controls. A MTConnect enabled control can be setup as a Source for data with DataXchange.<\/p>\n\n\n\n

Setting up MTConnect as a Source is done by connecting to the DataXchange Service from the DataXchange tab, selecting the associated equipment in the tree list, then pressing the Communication<\/strong> button in the ribbon bar. After selecting Add<\/strong> in the Communication Information<\/strong> window, leave the Communication Role<\/strong> set as Source<\/strong> and select MTConnect Host<\/strong> from the Communication Type<\/strong> drop down.<\/p>\n\n\n\n

After closing the dialog, the IP Address or Host<\/strong> name needs to be specified along with the TCP Port<\/strong>. The host will be the machine where the MTConnect Agent is installed. The port must match the port setting within the MTConnect Agent configuration. The default port used by MTConnect Agents is typically 5000. The Device Name<\/strong> is used to narrow down to the specific equipment. The Poll Rate<\/strong> of 5 seconds can be modified if needed. This is the rate at which DataXchange will request information from the Agent.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

If the DataXchange client is able to successfully Browse<\/strong> to the MTConnect Agent host and port entered, the connection will switch to Online mode and the built in DataXchange variables will be assigned default mappings to the MTConnect device. If the machine cannot be reached, the mappings can still be added or modified but their status cannot be verified. When items are being mapped out, they will return a corresponding icon indicating the status of the mapping. Below is a list of icons as well as their results. If items are mapped incorrectly, use the\u00a0Custom<\/strong>\u00a0button and remap the variable.<\/p>\n\n\n\n\n\n\n\t\n\t\n\t\n\t\n\t
\"\"\/<\/td>Validated successfully<\/td>\n<\/tr>\n
\"\"\/<\/td>Connected and received results, but the data returns UNAVAILABLE<\/td>\n<\/tr>\n
\"\"\/<\/td>Connected and received results, but did not map successfully\u00a0 (no match)<\/td>\n<\/tr>\n
\"\"\/<\/td>Unable to connect<\/td>\n<\/tr>\n
\"\"\/<\/td>Custom mapping being used<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n\n\n\n

In certain cases two data items may be returned.  If there are multiple data items found  on the default mapping being used, then DataXchange will mark that variable with the \"\" icon so it is clear that it did not map successfully and needs to be mapped manually.<\/p>\n\n\n\n

In the scenario that a default mapping is not successful, it will be represented with the \"\" icon. These mappings will NOT be saved.  However, if a variable is mapped manually, and is not successful, it will once again be represented by the \"\" icon. The only difference is that it WILL be saved.<\/p>\n\n\n\n

MTConnect Mapping Options<\/h2>\n\n\n\n

Below the MTConnect mapping list are options that can be used to edit, clear, or change the default existing mapping. When navigating through the MTConnect mappings list, the following rules will apply to the buttons once a mapping is highlighted. Below is an image of the three configuration buttons.<\/p>\n\n\n\n

A brief description of the MTConnect mapping option buttons:<\/p>\n\n\n\n