"
- readings.RemoveAll
-
- ''''''''''''''''''''''''''''''''''''''''
- Set samples = item.SelectNodes(".//Samples")
- For Each sample In samples
-
- For Each child In sample.ChildNodes
-
- If Not child.Attributes.getNamedItem("name") Is Nothing Then
- readings.Add child.Attributes.getNamedItem("name").NodeValue, child.Text
- Else
- If Not child.Attributes.getNamedItem("dataItemId") Is Nothing Then
- readings.Add child.Attributes.getNamedItem("dataItemId").NodeValue, child.Text
- end if
- End If
-
- Next
- Next
-
-
- Set events = item.SelectNodes(".//Events")
- For Each e In events
-
- For Each child In e.ChildNodes
-
- If Not child.Attributes.getNamedItem("name") Is Nothing Then
- readings.Add child.Attributes.getNamedItem("name").NodeValue, child.Text
- Else
- If Not child.Attributes.getNamedItem("dataItemId") Is Nothing Then
- readings.Add child.Attributes.getNamedItem("dataItemId").NodeValue, child.Text
- end if
- End If
- Next
- Next
-
- Set events = item.SelectNodes(".//Condition")
- For Each e In events
-
- For Each child In e.ChildNodes
-
- If Not child.Attributes.getNamedItem("name") Is Nothing Then
- readings.Add child.Attributes.getNamedItem("name").NodeValue, child.nodeName & ":" & child.Text
- Else
- If Not child.Attributes.getNamedItem("dataItemId") Is Nothing Then
- readings.Add child.Attributes.getNamedItem("dataItemId").NodeValue, child.nodeName & ":" & child.Text
- end if
- End If
- Next
- Next
-
- SortDictionary readings,1
- readingKeys = readings.Keys
- for i = 0 to readings.Count -1
- updatetable = updatetable & "
"
- updatetable = updatetable & "
" & readingKeys(i) & "
"
- updatetable = updatetable & "
" & readings.Item( readingKeys(i)) & "
"
- updatetable = updatetable & "
"
-
- next
-
- updatetable = updatetable & "
" & vbCrLf
- k=k+1
- if k>3 then
- updatetable = updatetable & "
"
- k=0
- end if
- Next
-
- updatetable = updatetable & "
"
-
-SetDiv "Device", table
-
-j = j + 1
-
-if ie.HWND = 0 then
-'MsgBox "Bye"
-Wscript.Quit(0)
-end if
-
-Wscript.Sleep(sleepamt)
-
-Loop
-
-
-
-
diff --git a/install/Windows/src/RunAgent.bat b/install/Windows/src/RunAgent.bat
deleted file mode 100644
index 50eee4fad..000000000
--- a/install/Windows/src/RunAgent.bat
+++ /dev/null
@@ -1,3 +0,0 @@
-.\Agent.exe debug
-pause
-
diff --git a/install/Windows/src/SetFilePermission.exe b/install/Windows/src/SetFilePermission.exe
deleted file mode 100644
index 4e2851f88..000000000
Binary files a/install/Windows/src/SetFilePermission.exe and /dev/null differ
diff --git a/install/Windows/src/Uninstall.bat b/install/Windows/src/Uninstall.bat
deleted file mode 100644
index d8c058754..000000000
--- a/install/Windows/src/Uninstall.bat
+++ /dev/null
@@ -1,4 +0,0 @@
-
-cd /d %~dp0
-.\Agent.exe remove
-
diff --git a/install/Windows/src/icon1.ico b/install/Windows/src/icon1.ico
deleted file mode 100644
index e17467d2b..000000000
Binary files a/install/Windows/src/icon1.ico and /dev/null differ
diff --git a/install/Windows/src/install.bat b/install/Windows/src/install.bat
deleted file mode 100644
index 8bd52e729..000000000
--- a/install/Windows/src/install.bat
+++ /dev/null
@@ -1,5 +0,0 @@
-cd /d %~dp0
-
-.\Agent.exe install
-
-
diff --git a/install/Windows/src/license.txt b/install/Windows/src/license.txt
deleted file mode 100644
index c31edbbee..000000000
--- a/install/Windows/src/license.txt
+++ /dev/null
@@ -1,11 +0,0 @@
-* Licensed under the Apache License, Version 2.0 (the "License");
-* you may not use this file except in compliance with the License.
-* You may obtain a copy of the License at
-*
-* http://www.apache.org/licenses/LICENSE-2.0
-*
-* Unless required by applicable law or agreed to in writing, software
-* distributed under the License is distributed on an "AS IS" BASIS,
-* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-* See the License for the specific language governing permissions and
-* limitations under the License.
diff --git a/install/Windows/src/mtconnect.bmp b/install/Windows/src/mtconnect.bmp
deleted file mode 100644
index 0bf4fb0a0..000000000
Binary files a/install/Windows/src/mtconnect.bmp and /dev/null differ
diff --git a/install/Windows/src/orange-install.ico b/install/Windows/src/orange-install.ico
deleted file mode 100644
index 1db75f8e4..000000000
Binary files a/install/Windows/src/orange-install.ico and /dev/null differ
diff --git a/install/Windows/src/orange.bmp b/install/Windows/src/orange.bmp
deleted file mode 100644
index 4ac1413b3..000000000
Binary files a/install/Windows/src/orange.bmp and /dev/null differ
diff --git a/install/Windows/src/superuser.bat b/install/Windows/src/superuser.bat
deleted file mode 100644
index 96ec3d1f6..000000000
--- a/install/Windows/src/superuser.bat
+++ /dev/null
@@ -1,5 +0,0 @@
-cd /d %~dp0
-icacls . /t /c /GRANT Everyone:F
-
-
-
diff --git a/install/Windows/src/todo.txt b/install/Windows/src/todo.txt
deleted file mode 100644
index a99680c99..000000000
--- a/install/Windows/src/todo.txt
+++ /dev/null
@@ -1,10 +0,0 @@
-Todo:
-
-msvc dll install - silent?
-
-Devices.xml file generation
-Device type menu generation
-
-11/4/2014 2:35:29 PM
-* copy all Device templates in installation
-* finished SetFilePermission
\ No newline at end of file
diff --git a/install/Windows/src/uninstall.vbs b/install/Windows/src/uninstall.vbs
deleted file mode 100644
index 29fec30eb..000000000
--- a/install/Windows/src/uninstall.vbs
+++ /dev/null
@@ -1,25 +0,0 @@
-
-
-Dim strService, WshShell
-
-' Trick to elevate UAC from http://www.winhelponline.com/articles/185/1/VBScripts-and-UAC-elevation.html
-If WScript.Arguments.length =0 Then
- Set objShell = CreateObject("Shell.Application")
- 'Pass a bogus argument with leading blank space, say [ uac]
- objShell.ShellExecute "wscript.exe", Chr(34) & _
- WScript.ScriptFullName & Chr(34) & " uac", "", "runas", 1
-Else
- 'Add your code here
-
-
-strService = Inputbox ("Service that you would like to remove:", "Service", "MTConnectAgent")
-if strService = "" Then
- Wscript.Quit(0)
-End if
-
-Set WshShell = WScript.CreateObject("WScript.Shell")
-WshShell.Run "sc.exe stop" & strService
-
-WshShell.Run "sc.exe delete " & strService
-wscript.sleep 1000
-End If
\ No newline at end of file
diff --git a/install/Windows/src/x32/Dbgview.exe b/install/Windows/src/x32/Dbgview.exe
deleted file mode 100644
index 8d6c16dc0..000000000
Binary files a/install/Windows/src/x32/Dbgview.exe and /dev/null differ
diff --git a/install/Windows/src/x32/GenerateVersioningDocument.exe b/install/Windows/src/x32/GenerateVersioningDocument.exe
deleted file mode 100644
index d2c78c5ba..000000000
Binary files a/install/Windows/src/x32/GenerateVersioningDocument.exe and /dev/null differ
diff --git a/install/Windows/src/x32/GenerateVersioningHtml.bat b/install/Windows/src/x32/GenerateVersioningHtml.bat
deleted file mode 100644
index e6aa809a4..000000000
--- a/install/Windows/src/x32/GenerateVersioningHtml.bat
+++ /dev/null
@@ -1,5 +0,0 @@
-
-
-cd /d %~dp0
-.\GenerateVersioningDocument.exe %CD%\Agent.exe
-
diff --git a/install/Windows/src/x32/Versioning.htm b/install/Windows/src/x32/Versioning.htm
deleted file mode 100644
index 477d02143..000000000
--- a/install/Windows/src/x32/Versioning.htm
+++ /dev/null
@@ -1,143 +0,0 @@
-
-
MTConnect Agent VERSION DESCRIPTION DOCUMENT
-
-RELEASE DATE:
-2014-12-04
-
INTRODUCTION
PURPOSE
-This document describes the software configuration for the MTConnect Agent. The MTConnect Agent is based on C++ Open Source technology and is developed by the MTConnect Institute, but can be modified and redistributed by 3rd parties. The Agent software version -major, minor, revision, build - of the agent is ebmedded in the exe and is extracted and described in this document.
SCOPE
This document applies to the Product Acceptance Software of the Agent software.
-The agent is installed as an exe with the install version number emebedded in the name.
-The agent should install and run automatically (if installed correctly) as a Windows service.
-In the task manager the agent.exe is the executable file to look for.
-In the Windows Service Control Manager (SCM) the agent is launched automatically, and is given the service name on installation.
-The default agent service name is 'MTConnectAgent'.
- If running correctly, using the configured combination http and port, the agent should display XML describing the device:
-
-http://127.0.0.1:5000/current
-
SECURITY REQUIREMENTS
-An administrator or equivalent must install and configure the agent.
-
HARDWARE DESCRIPTION
-This agent distribution is PCs with 32 and 64 bit Microsoft Windows OS with Intel x86 chipsets.
-This agent will need a Ethernet Network Adapter to communicate device data to clients and to communicate with device Adapters.
-
SOFTWARE DESCRIPTION
-
SYSTEM SOFTWARE
-It has been validated to work on Windows 2000, XP and 7 platforms on Intel x86 chipsets.
-Depending on the underlying architecture, either a 64 or 32 bit agent.exe will be installed.
- Windows NT and Linux require a different distribution.
-
APPLICATION SOFTWARE
-
-
Product Name
Supplier
Version
-
MTConnect Agent
MTConnect Institute Mods NIST
1.3.0.6
-
-
-
SOFTWARE SUPPORT INFORMATION
- See https://github.com/mtconnect/cppagent/blob/master/README.md for more documentation on MTConnect Agent.
-
-Note, the installation describes installation of the MTConnect Agent on a Windows platform only. It is assumed to be a Windows 2000, XP, or 7/8 installation.
-It is known that this installation will not work on Windows NT system, and has not been tried on a Windows 95 or 98 or ME system.
-Before you process, installation of the MTConnect Agent will require administrator priviledges on a Windows 7 platform.
-
-
You will need to double click the agent install software, MTConnectAgentInstallxx.xx.exe, where xx.xx is the distributed version of the agent.
- The installation uses the NSIS software package. NSIS stands for the Nullsoft Scriptable Install System (NSIS) and is a script-driven installation system for Microsoft Windows with minimal overhead backed by Nullsoft, the creators of Winamp.
- NSIS is free software released under a combination of free software licenses, primarily the zlib license.
-The Install is divided into Pages, with each Page either prompting the user for intput, or being informative, or both.
-
The first screen that will appear is a Welcome page. Click Next. At any time you can stop the install by clicking the Cancel button.
-
The second screen is the License Agreement page. This outlines the terms of agreement for using the software.
-In effect there is no copyright. The License Agreement allows the right to distribute copies and modified versions of the Agent and but does NOT require that the same rights be preserved in modified versions of the work.
-
The third screen is the Installation Directory page. The user is prompted to select a installation directory.
-The default directory is C:\Program Files\MTConnect\MTConnectAgent for either 32 or 64 bit installs. The Instsall program will determine the underlying architecture.
-Note, unlike some application exe 32 bit agents will not run on 64 bit machines.
- Two agents could be installed at the same time, as long as they have different service names and installation diretories.
- The installation over an existing directory is not guaranteed to overwrite older versions (even though it should).
-
After the user clicks Next, the fourth page details the installation of all the file is done, but has not been configured.
- Again, the installation program determines whether to use a 32 or 64 bit installation exe.
-
The fifth page prompts the user to configure the Agent specific parameters.
-The User specifies service name, http port, delay, and debug level, which are agent specific parameters.
-Note, You have the option of starting the agent service by checking the start agent checkbox. If this is your first agent installatino, it may be preferable to uncheck the box, and manually check the installation parameters.
-The user clicks Next and now the adapter configuration installation will then be executed to configure the remaining portions of agent.cfg and devices.xml in the installation directory.
-
A flash screen alerts the user that the Adapter Wizard is going to run.
-Now, adapters will be configured. Adapter configuration is a NSIS install program that DOES NO INSTALLING. Instead, it prompts the users to specify the set of Adatpers that provide SHDR input to the Agent, and then creates a Devices.xml file and the Adapter configuration part of the Agent.cfg file.
- Advanced users should read https://github.com/mtconnect/adapter/blob/master/MTC_SHDR.docx for information on the SHDR protocol. Note, SHDR is not an MTConnect standard, but is widely used as a back-end for device communication.
-
A Welcome page offers the user a Adapter configuration greeting. Clicking Next is all that is needed.
-
The second Adapter configuration page, queries the user to select a vendor, machine type and version.
-You must select an MTConnect to match your machine tool vendor CNC, and for which MTConnect templates are available.
-Device descriptions are currently organized into MachineTools, Turning, or Robots. There are not many models, and it is unclear if this is the correct model for specifying MTConnect Adapters.
-
The next Adapter configuration screen asks the necessary information to configure an Adapter: Device Name, Type, IP and Port.
-The manufacturer and model have already been selected.
-When the users clicks Apply, an adapter.cfg entry and the devices.xml piece are saved, for later file writing.
-The user clicks Apply button to save the configuration, and will take you back a slide to append a new adapter to your configuration.
-The user clicks Done button completes the Adapter configuration process, writes the configuration files and returns to the Agent installation wizard.
-
-
The final Agent installation page is the Finish Page, which signals the end of the installation process.
-The user clicks Finish, and if the user selected start the agent, the agent service will be started.
-
-There are several steps to insure that the Agent installed correctly.
-
First, you will need to double check that the MTConnectAgent installed correctly in the Windows Service Manager (SCM).
- To check the service, right click ont he My Computer and select Manage. You may need to provide administrator credentials, so be prepared.
-Assuming you can manage My Computer, double click 'Services and Applications' and then double click 'Services'.
-At this point, you should see a list of all the services in your Windows platform. You will need to scroll down to the service name (or default name) provided during the Agent installation.
-We will assume the default name, 'MTConnectAgent', and scroll down to this entry, double click the name and a dialog popup describing the service parameters should appear.
-In the popup, you should be on 'General' tab and the see the following:
-
-
Service Name should say MTConnectAgent (default) or the service name provided when installing the agent.
-
Startup type as automatic
-
Path to executable as (the default assuming you didnt change the install directory) C:\Program Files\MTConnect\MTConnectAgent\agent.exe
-
Service Status should be stopped. If you had checked the service startup it should say started.
-
The tabs Logon, Recovery and Dependencies can be ignored.
-
-
If you see all the correct parameters, you can then start the Agent, by clicking the Start button. A popup dialog should appear and within a minute or so, the service should be started.
-Close the Properties popup, and iF the agent status has not changed to 'Started' problems occured.
-Assuming the Agent service started, you can now see XML data from your MTConnect Adapter(s) (really devices).
-To see the output, open a web browser, (such as Internet Explorer), and type into the address bar:
-
http://127.0.0.1:5000/current
-You should see data, as opposed to 'Unable to connect' or 'This page cannot be displayed' in the web browser.
-If you dont see data the service is not running, or you configured the HTTP port in the agent to something besides 5000.
-If you see data, but all the data is UNAVAILABLE, this is also most likely bad.
-You see all UNAVAILABLE data either:
-
-
No adapters were configured.
-
The adapters is down, and no data is available. To check this, telnet to ip/port of the adapter, you should see output.
-
The adapters data blocked by the firewall. Firewall can be on either the host or the remote adapter computer. To check this, telnet to ip/port of the adapter, you should see output.
-If you see data, the firewall is most likely preventing the agent from remote access.
-If you don't see data, (and you can 'ping' the remote computer, a firewall on the remote platform may be preventing an adapter from outputting SHDR to socket port 7878 (the default).
-
-
If you see data, then the agent has installed and been configured correctly. Now, just monitor the agent for a couple days to insure that it is booting correctly and operating properly.
-
-
UNINSTALLAION SOFTWARE INFORMATION
-There are two methods for uninstalling the Agent. Either use:
The Microsoft Windows Control Panel,
-or
navigate to the install directory (default C:\Program Files\MTConnect\MTConnectAgent) and click uninstall.exe.
-
The control panel uninstall procedure wil be described (although once the uninstall program is activated, the procedure is the same.)
-
Uninstall uses the Windows mechanism: Start->Control Panale -> Programs and Features to fetch all the installed programs on the platform.
-Scroll down and find the MTConnectAgentxx.xx installation. Double click uninstall, YOU WILL NEED TO HAVE ADMINISTRATOR priviledges to uninstall on windows 7 machines.
-Three uninstall pages will diplay: Click Next, then Uninstall and finally Finish, and the Agent will be removed.
-
Uninstalling using the control panel is preferrable, but often some quirks appear. It may be necessary to manually top the MTConnectAgent service before uninstalling.
-Also, the Control Panel programs and features may not remove the MTConnectAgentxx.xx entry even though it has uninstalled the agent. A refresh may take care of this.
diff --git a/install/Windows/src/x32/agent.exe b/install/Windows/src/x32/agent.exe
deleted file mode 100644
index 36f62f2a9..000000000
Binary files a/install/Windows/src/x32/agent.exe and /dev/null differ
diff --git a/install/Windows/src/x32/msvcr100.dll b/install/Windows/src/x32/msvcr100.dll
deleted file mode 100644
index fd91c89d8..000000000
Binary files a/install/Windows/src/x32/msvcr100.dll and /dev/null differ
diff --git a/install/Windows/src/x32/msvcrt.dll b/install/Windows/src/x32/msvcrt.dll
deleted file mode 100644
index ed68df5f2..000000000
Binary files a/install/Windows/src/x32/msvcrt.dll and /dev/null differ
diff --git a/install/Windows/src/x32/vc2010redist_x86.exe b/install/Windows/src/x32/vc2010redist_x86.exe
deleted file mode 100644
index d81f3f5ab..000000000
Binary files a/install/Windows/src/x32/vc2010redist_x86.exe and /dev/null differ
diff --git a/install/Windows/src/x64/Dbgview.exe b/install/Windows/src/x64/Dbgview.exe
deleted file mode 100644
index 9e840761b..000000000
Binary files a/install/Windows/src/x64/Dbgview.exe and /dev/null differ
diff --git a/install/Windows/src/x64/GenerateVersioningDocument.exe b/install/Windows/src/x64/GenerateVersioningDocument.exe
deleted file mode 100644
index b1768081c..000000000
Binary files a/install/Windows/src/x64/GenerateVersioningDocument.exe and /dev/null differ
diff --git a/install/Windows/src/x64/GenerateVersioningHtml.bat b/install/Windows/src/x64/GenerateVersioningHtml.bat
deleted file mode 100644
index e6aa809a4..000000000
--- a/install/Windows/src/x64/GenerateVersioningHtml.bat
+++ /dev/null
@@ -1,5 +0,0 @@
-
-
-cd /d %~dp0
-.\GenerateVersioningDocument.exe %CD%\Agent.exe
-
diff --git a/install/Windows/src/x64/Versioning.htm b/install/Windows/src/x64/Versioning.htm
deleted file mode 100644
index 477d02143..000000000
--- a/install/Windows/src/x64/Versioning.htm
+++ /dev/null
@@ -1,143 +0,0 @@
-
-
MTConnect Agent VERSION DESCRIPTION DOCUMENT
-
-RELEASE DATE:
-2014-12-04
-
INTRODUCTION
PURPOSE
-This document describes the software configuration for the MTConnect Agent. The MTConnect Agent is based on C++ Open Source technology and is developed by the MTConnect Institute, but can be modified and redistributed by 3rd parties. The Agent software version -major, minor, revision, build - of the agent is ebmedded in the exe and is extracted and described in this document.
SCOPE
This document applies to the Product Acceptance Software of the Agent software.
-The agent is installed as an exe with the install version number emebedded in the name.
-The agent should install and run automatically (if installed correctly) as a Windows service.
-In the task manager the agent.exe is the executable file to look for.
-In the Windows Service Control Manager (SCM) the agent is launched automatically, and is given the service name on installation.
-The default agent service name is 'MTConnectAgent'.
- If running correctly, using the configured combination http and port, the agent should display XML describing the device:
-
-http://127.0.0.1:5000/current
-
SECURITY REQUIREMENTS
-An administrator or equivalent must install and configure the agent.
-
HARDWARE DESCRIPTION
-This agent distribution is PCs with 32 and 64 bit Microsoft Windows OS with Intel x86 chipsets.
-This agent will need a Ethernet Network Adapter to communicate device data to clients and to communicate with device Adapters.
-
SOFTWARE DESCRIPTION
-
SYSTEM SOFTWARE
-It has been validated to work on Windows 2000, XP and 7 platforms on Intel x86 chipsets.
-Depending on the underlying architecture, either a 64 or 32 bit agent.exe will be installed.
- Windows NT and Linux require a different distribution.
-
APPLICATION SOFTWARE
-
-
Product Name
Supplier
Version
-
MTConnect Agent
MTConnect Institute Mods NIST
1.3.0.6
-
-
-
SOFTWARE SUPPORT INFORMATION
- See https://github.com/mtconnect/cppagent/blob/master/README.md for more documentation on MTConnect Agent.
-
-Note, the installation describes installation of the MTConnect Agent on a Windows platform only. It is assumed to be a Windows 2000, XP, or 7/8 installation.
-It is known that this installation will not work on Windows NT system, and has not been tried on a Windows 95 or 98 or ME system.
-Before you process, installation of the MTConnect Agent will require administrator priviledges on a Windows 7 platform.
-
-
You will need to double click the agent install software, MTConnectAgentInstallxx.xx.exe, where xx.xx is the distributed version of the agent.
- The installation uses the NSIS software package. NSIS stands for the Nullsoft Scriptable Install System (NSIS) and is a script-driven installation system for Microsoft Windows with minimal overhead backed by Nullsoft, the creators of Winamp.
- NSIS is free software released under a combination of free software licenses, primarily the zlib license.
-The Install is divided into Pages, with each Page either prompting the user for intput, or being informative, or both.
-
The first screen that will appear is a Welcome page. Click Next. At any time you can stop the install by clicking the Cancel button.
-
The second screen is the License Agreement page. This outlines the terms of agreement for using the software.
-In effect there is no copyright. The License Agreement allows the right to distribute copies and modified versions of the Agent and but does NOT require that the same rights be preserved in modified versions of the work.
-
The third screen is the Installation Directory page. The user is prompted to select a installation directory.
-The default directory is C:\Program Files\MTConnect\MTConnectAgent for either 32 or 64 bit installs. The Instsall program will determine the underlying architecture.
-Note, unlike some application exe 32 bit agents will not run on 64 bit machines.
- Two agents could be installed at the same time, as long as they have different service names and installation diretories.
- The installation over an existing directory is not guaranteed to overwrite older versions (even though it should).
-
After the user clicks Next, the fourth page details the installation of all the file is done, but has not been configured.
- Again, the installation program determines whether to use a 32 or 64 bit installation exe.
-
The fifth page prompts the user to configure the Agent specific parameters.
-The User specifies service name, http port, delay, and debug level, which are agent specific parameters.
-Note, You have the option of starting the agent service by checking the start agent checkbox. If this is your first agent installatino, it may be preferable to uncheck the box, and manually check the installation parameters.
-The user clicks Next and now the adapter configuration installation will then be executed to configure the remaining portions of agent.cfg and devices.xml in the installation directory.
-
A flash screen alerts the user that the Adapter Wizard is going to run.
-Now, adapters will be configured. Adapter configuration is a NSIS install program that DOES NO INSTALLING. Instead, it prompts the users to specify the set of Adatpers that provide SHDR input to the Agent, and then creates a Devices.xml file and the Adapter configuration part of the Agent.cfg file.
- Advanced users should read https://github.com/mtconnect/adapter/blob/master/MTC_SHDR.docx for information on the SHDR protocol. Note, SHDR is not an MTConnect standard, but is widely used as a back-end for device communication.
-
A Welcome page offers the user a Adapter configuration greeting. Clicking Next is all that is needed.
-
The second Adapter configuration page, queries the user to select a vendor, machine type and version.
-You must select an MTConnect to match your machine tool vendor CNC, and for which MTConnect templates are available.
-Device descriptions are currently organized into MachineTools, Turning, or Robots. There are not many models, and it is unclear if this is the correct model for specifying MTConnect Adapters.
-
The next Adapter configuration screen asks the necessary information to configure an Adapter: Device Name, Type, IP and Port.
-The manufacturer and model have already been selected.
-When the users clicks Apply, an adapter.cfg entry and the devices.xml piece are saved, for later file writing.
-The user clicks Apply button to save the configuration, and will take you back a slide to append a new adapter to your configuration.
-The user clicks Done button completes the Adapter configuration process, writes the configuration files and returns to the Agent installation wizard.
-
-
The final Agent installation page is the Finish Page, which signals the end of the installation process.
-The user clicks Finish, and if the user selected start the agent, the agent service will be started.
-
-There are several steps to insure that the Agent installed correctly.
-
First, you will need to double check that the MTConnectAgent installed correctly in the Windows Service Manager (SCM).
- To check the service, right click ont he My Computer and select Manage. You may need to provide administrator credentials, so be prepared.
-Assuming you can manage My Computer, double click 'Services and Applications' and then double click 'Services'.
-At this point, you should see a list of all the services in your Windows platform. You will need to scroll down to the service name (or default name) provided during the Agent installation.
-We will assume the default name, 'MTConnectAgent', and scroll down to this entry, double click the name and a dialog popup describing the service parameters should appear.
-In the popup, you should be on 'General' tab and the see the following:
-
-
Service Name should say MTConnectAgent (default) or the service name provided when installing the agent.
-
Startup type as automatic
-
Path to executable as (the default assuming you didnt change the install directory) C:\Program Files\MTConnect\MTConnectAgent\agent.exe
-
Service Status should be stopped. If you had checked the service startup it should say started.
-
The tabs Logon, Recovery and Dependencies can be ignored.
-
-
If you see all the correct parameters, you can then start the Agent, by clicking the Start button. A popup dialog should appear and within a minute or so, the service should be started.
-Close the Properties popup, and iF the agent status has not changed to 'Started' problems occured.
-Assuming the Agent service started, you can now see XML data from your MTConnect Adapter(s) (really devices).
-To see the output, open a web browser, (such as Internet Explorer), and type into the address bar:
-
http://127.0.0.1:5000/current
-You should see data, as opposed to 'Unable to connect' or 'This page cannot be displayed' in the web browser.
-If you dont see data the service is not running, or you configured the HTTP port in the agent to something besides 5000.
-If you see data, but all the data is UNAVAILABLE, this is also most likely bad.
-You see all UNAVAILABLE data either:
-
-
No adapters were configured.
-
The adapters is down, and no data is available. To check this, telnet to ip/port of the adapter, you should see output.
-
The adapters data blocked by the firewall. Firewall can be on either the host or the remote adapter computer. To check this, telnet to ip/port of the adapter, you should see output.
-If you see data, the firewall is most likely preventing the agent from remote access.
-If you don't see data, (and you can 'ping' the remote computer, a firewall on the remote platform may be preventing an adapter from outputting SHDR to socket port 7878 (the default).
-
-
If you see data, then the agent has installed and been configured correctly. Now, just monitor the agent for a couple days to insure that it is booting correctly and operating properly.
-
-
UNINSTALLAION SOFTWARE INFORMATION
-There are two methods for uninstalling the Agent. Either use:
The Microsoft Windows Control Panel,
-or
navigate to the install directory (default C:\Program Files\MTConnect\MTConnectAgent) and click uninstall.exe.
-
The control panel uninstall procedure wil be described (although once the uninstall program is activated, the procedure is the same.)
-
Uninstall uses the Windows mechanism: Start->Control Panale -> Programs and Features to fetch all the installed programs on the platform.
-Scroll down and find the MTConnectAgentxx.xx installation. Double click uninstall, YOU WILL NEED TO HAVE ADMINISTRATOR priviledges to uninstall on windows 7 machines.
-Three uninstall pages will diplay: Click Next, then Uninstall and finally Finish, and the Agent will be removed.
-
Uninstalling using the control panel is preferrable, but often some quirks appear. It may be necessary to manually top the MTConnectAgent service before uninstalling.
-Also, the Control Panel programs and features may not remove the MTConnectAgentxx.xx entry even though it has uninstalled the agent. A refresh may take care of this.
diff --git a/install/Windows/src/x64/agent.exe b/install/Windows/src/x64/agent.exe
deleted file mode 100644
index 01606d2b5..000000000
Binary files a/install/Windows/src/x64/agent.exe and /dev/null differ
diff --git a/install/Windows/src/x64/msvcr100.dll b/install/Windows/src/x64/msvcr100.dll
deleted file mode 100644
index fd91c89d8..000000000
Binary files a/install/Windows/src/x64/msvcr100.dll and /dev/null differ
diff --git a/install/Windows/src/x64/msvcrt.dll b/install/Windows/src/x64/msvcrt.dll
deleted file mode 100644
index b8b31af2d..000000000
Binary files a/install/Windows/src/x64/msvcrt.dll and /dev/null differ
diff --git a/install/Windows/src/x64/vc2010redist_x64.exe b/install/Windows/src/x64/vc2010redist_x64.exe
deleted file mode 100644
index 834133f8b..000000000
Binary files a/install/Windows/src/x64/vc2010redist_x64.exe and /dev/null differ