If you’re curious, like me, about what software tools are being widely used in manufacturing, Okuma has given us a peek at the most popular machine tool apps in their app store. And number one on their list is… (spoilers)
This week I was working with TrakHound’s MTConnect.NET library again, but all my test connections were failing. I had been testing against the MTConnect Institute’s demo agent, which is now run by NIST. I opened it in my browser and got a 404 Not Found. So I went up one level and saw this…
Eight years ago when I first encountered MTConnect, I felt the technology would transform the machine shop. Today, support for MTConnect is commonplace in new machine tools, and often available for older tools through various upgrade options. Software packages exist to collect and analyze data on a server or on the cloud. However, I thought the technology could become a lightweight option not only for data analytics, but also for basic machine shop automation.
No. At least, I’ve had no luck running any of the TrakHound components on Linux. In a previous post I mentioned that I could not try the TrakHound community software, since I do not have a Windows machine. Afterwards I wondered how true that was. After all, Wine does a decent job running most Windows software, and .NET support on Linux has gotten much better in recent years. So I thought it was worth a shot.
If you are trying to implement basic machine monitoring in your shop on a shoestring budget, and your machine tools are already MTConnect aware, Raspberry Pi provides an inexpensive solution. * Cost of Raspberry Pi kit only. MTConnect adapter solutions, networking, etc. may cost extra.
A long time ago on a blog far, far away, I wrote an article called “Set up an MTConnect Agent in three or so steps”. This became one of the most visited articles I have ever written, and is still being viewed four years later. However, much has changed in the MTConnect world in the past four years, so I wanted to take another look at installing an MTConnect agent.