• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[INFO] Support for MTConnect standard confirmed
#1
MTConnect is a standard for exchanging information and data of factory automation equipment like machines, sensors, actuators across Ethernet using a standardizes device data format which is XML.

Today I wanted to proof if MTConnect can be supported by netPI too. MTConnect web site provides a source code containing an agent (master) to scan for adapters (slaves) and if found any to provide their informations on a simple HTML page.

Here is what I did.

  1. I installed the Raspbian Container https://hub.docker.com/r/hilschernetpi/netpi-raspbian/ on my netPI, but activated the container to run in host network mode
  2. I opened a terminal console with putty to access Linux command line
  3. I installed node.js including npm (cause it comes not preinstalled) command using the following commands
    sudo apt-get update
    sudo curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -
    sudo apt-get install -y node

  4. I cloned the agent from github using git clone https://github.com/mtconnect/mtconnect-agent command
  5. I was continuing to follow the README provided in this repo and called npm install in the created mtconnect-agent folder
  6. Then I called sudo npm start and the agent immediately started its work and was scanning for adapter periodically
  7. As the README is telling I opened another terminal console to start simulating an adapter on the same netPI (can be any second hardware too)
  8. In this console I had to install the fs-ext file system package first with sudo npm install -g --unsafe-perm fs-ext needed to run the simulator
  9. Then I started the adapter simulation using sudo npm run simulator2 command. I was able to follow a logging output on the screen
  10. I saw the agent logging quite more data since it found the adapter present in the current network
  11. He wsa preparing me an HTML site of the found adapter data in the background I am able to call under the URL http://<netPi's IP address>:7000/probe
This simple setup cost me 10 minutes of work to prove that netPI can be either MTConnect agent or adaptor or even both.

Of couse my examination proves just MTConnect connectivity on the lowest communication level only and for sure there is much more work to spent on realizing a user application on top of the agent or adapter, but it shows to me that MTConnect is indeed as open and interoperable as they proclaim on their web site.

Good luck for any MTConnect project you want to realize with netPI

Thx
Armin
You never fail until you stop trying.“, Albert Einstein (1879 - 1955)

  Reply
#2
Hello Armin,

I was trying to run MTconnect container , but get error on npm install command as attached , Is something wrong I am doing?

Thanks
Madhumati


Attached Files Thumbnail(s)
   
  Reply
#3
Updated the steps to get npm command installed in the Raspbian container cause it comes not preinstalled. So repeat at step 3
You never fail until you stop trying.“, Albert Einstein (1879 - 1955)

  Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
Information [INFO] - InfluxDB - Time series database under Windows Patrick@netPI 0 47 May-28th-2019, 02:10 PM
Last Post: Patrick@netPI
  [INFO] OPC UA Server MGharat 2 22 April-30th-2019, 08:09 AM
Last Post: Armin@netPI
  [INFO] Raspberry Pi Desktop under Windows Armin@netPI 0 23 January-24th-2019, 07:41 PM
Last Post: Armin@netPI

Forum Jump:


Users browsing this thread: 1 Guest(s)