We also exhibited at the IoT Summit last year. It’s a great chance to connect with the Linux developer community and get their perspective on things, since it’s so much different from what a typical industrial automation professional is exposed to.
In a recent developer survey conducted by the Eclipse IoT Working Group, IEEE IoT, and Agile IoT, 40.8% of respondents indicated the Internet of Things (IoT) solutions they were either currently building or planning to build were IoT platforms or IoT middleware.
Almost every large IT or OT company today has some form of IoT platform or middleware, with the current number of self-described IoT platforms exceeding 150.
Almost everyone in the industrial automation, process control, and factory automation industries is concerned with keeping their equipment up and running.
Overall equipment effectiveness (OEE) is a key metric for understanding how the factory is performing. And part of keeping things running is keeping things communicating.
Did you watch the Big Game on Sunday, February 5?
Not only was it a great game, with the outcome in doubt till a first-ever overtime settled it, but also... power for the Fox Sports television broadcast never failed.
Pretty important, right?
Announcing the release of PAC Project R9.6000, with new features, enhancements, and bug fixes—available now.
Here's good news for system integrators, OEMs, and others who build PAC Control strategies for users who don't have PAC Control on their systems. PAC Control now provides a command-line interface (CLI)
As the Internet of Things (IoT) gains momentum, this conference brings together system architects, firmware developers, software developers, and application developers.
Our developer.opto22.com site gets a lot of traffic from developers working with SNAP PACs, groov, Node-RED, and industrial I/O for Raspberry Pi.
Since all Opto 22 products are designed on open standards, you have a variety of ways to interact with them and integrate with other systems. The developer site helps you do that.
As noted in Opto 22’s recent edge computing technology primer, one of the key problems currently facing the IIoT is Internet bandwidth limitations. We’re talking about connecting billions of sensors to networks that were never designed to handle that kind of traffic.
I can remember the painful days of dial up Internet connectivity when millions of people started connecting their PCs to the Internet through tiny little phone lines, watching file transfers drag on and on for hours.
Ethernet networks have taken over as the prominent bus architecture for industrial automation networks. And for good reason.
Ethernet simplifies and homogenizes connectivity between industrial devices. We don’t have to worry about male or female DB9 and DB25 serial connectors, no concern for DTE or DCE devices, and forget about straight-through vs. null-modem cables. In general, the world is a much happier place.
However, even with the added simplicity Ethernet offers, troubleshooting Ethernet networks can be a bit more involved than serial networks.
Let’s assume you’re trying to establish communication with an industrial Ethernet device that for whatever reason has dropped off the network. Here are a few tips I always use when starting to troubleshoot an industrial Ethernet network.
La reducción de la complejidad es esencial para que la IIOT funcione, especialmente para obtener datos de sensores, equipos y dispositivos que existen y funcionan bien en campo, pero los cuales no tienen en si capacidades de IoT.