Open Automation Software’s latest update now includes a new interface for Sparkplug B Edge of Network Nodes and Host Applications.
The OAS IIoT platform has recently added support for Sparkplug B as an Edge Network Node and a Host Application. Sparkplug B is an industry-standard that enables common topic and payload definitions for MQTT data transport.
As an Edge of Network (EoN) Node for Sparkplug B, OAS can offer bi-directional communications to all tags in the OAS Engine using any combination of Sparkplug B identifiers. This is achieved using four new properties to define the hosting Group ID, Edge Node ID, Device ID, and Metric name in each OAS tag.
This interface supports all data sources of OAS, including Allen Bradley ControlLogix, CompactLogix, GuardLogix, Micro800 MicroLogix, SLC 500, PLC-5 PLCs, Siemens S7 controllers, Modbus TCP, RTU, and ASCII masters and slaves, OPC UA clients and servers, OPC DA clients and servers, MTConnect, custom MQTT payloads, .NET interfaces, REST API, and databases.
In addition, OAS provides a Sparkplug B Host Application interface to control and consume data from the EoN Node to receive and extract NDATA and DDATA automatically to tag values and write data to EoN Node Metric values through NCMD and DCMD Sparkplug B commands. OAS tags can also be created automatically based on the NBIRTH and DBIRTH data received from an EoN Node.
You can connect to any third-party MQTT Broker that supports MQTT V3.11 or V5.0, including HiveMQ, Mosquitto, or OAS built-in MQTT Broker. OAS supports Sparkplug B versions 2.2 and 3.0.
For step-by-step instructions for setting up Sparkplug B communications, watch the video below:
You can also utilize the OAS Data Route feature to enable server-to-server data transport and additional protocol translation, including Sparkplug B EoN Node to EoN Node data transfer.
Open Automation Software has optimized it’s encryption methodology in Version 17 and in a nutshell it is stronger, lighter and faster! Data encryption may not be an exciting topic for everyone but fortunately for our users, the developers at OAS get really excited about it!
Security needs to be built in, not bolted on. Open Automation Software has spent a good part of this year re-writing it’s entire encryption algorithm from the bottom up. Every aspect of the software includes this change and has been meticulously tested. The results exceeded our own expectations.
Packet sizes are 3-9 times smaller depending on the type of data being transported, resulting in increased speed.
The time to encode a packet is now up 2 to 8 times faster while decoding can be up to 10 times faster than previous versions of OAS.
Additional encryption methods implement a unique seed value for each client connection to encrypt the user credentials, removing clear text for the username and eliminating the possibility of sniffing user credentials.
Client and server packet handshake with a 64-bit unique identifier.
Live Data Cloud networking is now 6 to 18 times faster as previous versions, almost as fast the updated basic networking.
Version 17 of OAS also includes pre-configured security groups and mandatory use of security features.
Security has always been a top priority at Open Automation Software and we are continually reviewing and enhancing our security practices to stay current with the latest technology. Version 17 of the software has included some next-level enhancements to ensure that we are THE platform you will want to trust your SCADA system to.
Secure software relies both on the developer and the end user. Security must be built into the software foundation and the end user must use the security features provided. OAS has always provided that secure foundation and Version 17 has upped the game and also made end user utilization of security features a priority.
Pre-Configured Security Groups
The software now loads with a pre-configured Admin Security Group. Upon installation, users are prompted to create an admin user and access is prohibited until that admin user has been created. Security is now only configurable by an authenticated user with assigned access to this feature. The Default security group, for unauthenticated users, is now locked down allowing only limited functionality. OAS has always allowed the creation of multiple Security Groups where administrators can secure any feature, even down to the individual tags and tag groups. This remains and continues to allows end users to customize security to meet their needs.
User Credential Encryption
Version 17 of OAS has widened encryption strategies to include database authentication, user credentials and all configuration calls. V17 implements a new encryption methodology that allows it to provide extended encryption utilizing AES encryption while increasing the speed of data transfer.
Secure Client Server Handshaking
Each client server transaction now includes a unique 64-bit identifier allowing OAS to securely transport your data.
New Data Packet Encryption
In addition to broadening the scope of encryption, V17 of OAS had entirely reworked its encryption process. Data packets are now 3-9 times smaller allowing for much faster transfer speed. This new method provides superior security and gets it done faster!
Open Automation Software has Released OAS Version 17 with Security Enhancements.
Open Automation Software has been updated to notify users to setup security on the OAS Engine if the default security has not been updated to protect against unauthorized access. OAS version 17 also includes ironclad protection from packet spoofing, faster byte stream compression, updated encryption, and new client server handshaking for packet validation.
All OAS client interfaces have been updated to include this new transport including all .NET assemblies, OAS Configure application, Excel Connector, and service to service communications for Windows and Linux.
Secure Client Server Handshaking Each data packet now includes an ironclad transport that cannot be reproduced externally, both the client and the server will reject the packet if replicated from a sniffed packet. Each packet from client to server is unique and must pass an algorithm verification from previous transport for validation.
User Credentials Encryption The data within the byte stream no longer shows the username as clear visible text. An updated encryption method implements a unique seed value for each client connection to encrypt the user credentials.
New Data Packet Encryption The data within the packet is encrypted with a different method that prevents all data within the packet from being extracted with sniffing the network connection.
Security Access The default installation now automatically adds an Admin security group to make it very easy to assign an administrator user. Users are also prompted to disable the Default security group after the administrator user is created. Security Groups and Users configuration can no longer be accessed with the default credentials after an Admin user is created. Users are now prompted to setup security when connecting to the service. REST API calls for configuration access is no longer permitted under the default security with a blank username and password. View the Getting Started – Security guide to setup security for all versions of OAS to protect against unauthorized access to configurations, live data, and historical data.
Open Automation Software is excited to announce it’s new IoT Publish feature for Azure IoT, AWS IoT Gateway and MQTT
With Open Automation’s IoT Publish you can configure tags from a single or multiple data sources in OAS and publish them to Azure IoT, AWS IoT Gateway or an MQTT Broker. Tags can be published to a single topic or to multiple topics (one for each tag). Publishes can be scheduled to happen at a certain time of day, be event driven with a trigger tag and can also be continuous. The configurable publish interval setting allows you to publish at a specified rate.
Data is sent to Azure, AWS or MQTT as JSON packets which include device id, topic, tag id, quality and timestamp. Options are available to change the key names and to send without quality and/or timestamp. Timestamp can be formatted in ISO 8601, Unix seconds or milliseconds, Ticks or you can customize your own. Additional options are available to publish the latest value only and to include all tags in each publish or only those whose value has changed.
The Store and Forward feature of OAS can be turned on to prevent data loss in case of communication failure. If a communication failure occurs, OAS will buffer the data on your hard drive in the directory that you specify until communication is restored. Then it parses the data out to your destination.
For step by step instructions for the IoT Publish, watch the video below:
Supported Data Sources
Allen Bradley
Modbus
Siemens
OPC UA
OPC DA
MTConnect
OPTO-22
Rest API
Database
HMI
Other IoT Endpoints
Below are some examples of what the published data will look like with different options selected:
A comparison of features and benefits of an open architecture platform vs. an off-the-shelf solution for Industrial Automation and IoT
In Information Technology it has become almost axiomatic that it’s cheaper to purchase an off-the-shelf solution instead of building your own application from scratch. A custom piece of software can very expensive because it is being built for a single purpose and with one customer in mind. It usually takes much longer to get up and running and to work out all of the bugs. But developing custom software is still embarked upon because it comes with some significant benefits, especially if you are an OEM, interested in reselling the solution.
What if there was a software platform that provided the benefits custom development, but also mitigated the risks of rolling out your own solution, and even dramatically reduced costs over time?
So let’s explore this a bit further, breaking down the pros and cons of both custom development and off-the-shelf products. We’ll then demonstrate how the OAS Platform is unique in the IIoT space and what an open architecture can do for you.
Off-The-Shelf Products
The pros and cons of off-the-shelf (OTS) or “canned solutions”, which may still include some tools for designing HMI screens and logic, but within proprietary environments.
PROS
Rapid configuration
One of the most attractive features is the relative ease at which OTS products can be configured and deployed since the feature set and tools are well-defined.
Built-in tools and applications
In order to speed up and simplify deployment, most OTS products include many tools for creating things like HMIs, and often have full-blown applications ready to be used in production.
Generally well-supported
Coming from many well-established companies, these products usually come with a team of support personnel and documentation, which usually comes at an additional cost.
Great for demos or proofs-of-concept
When an OTS platform is narrowly focused on a solution domain, and when tools and applications are proprietary, these products are impressive during tightly controlled demos. Little or no programming is required to get up and running.
CONS
Difficult (or impossible) to customize
Once you start using these products, you’ll quickly find that you need some functionality that they do not provide within the basic toolset. So then you must resort to using APIs with some custom development to
extend them. Other times, customization is not even possible.
Strict licensing, difficult for OEMs
To protect their intellectual property and branding, software vendors tend to limit OTS platforms by the number of users connected to them, and it can become very expensive and restrictive very quickly for OEMs, making it difficult to fit these products into your business model.
Proprietary data format
Another way license restrictions are enforced is to lock down the data within the system. OTS vendors provide tools for importing or exporting data, but the data is usually stored in a proprietary format.
Proprietary tools and user interfaces
If your requirements are to generate an application with a specific user interface, you may find an OTS solution limiting. Many of them provide a large library of symbols and objects, but your application will
look like many others, and will unlikely include your own company branding. You’re also required to use the vendors tools for configuration and modification.
Specialists are expensive and scarce
OTS vendors generally sell to a niche market, so while the install base and investments may be large, the actual number of individuals with the skills to use the software is a small pool relative to the global software and IT community. Few consultants have the necessary skill to work with each OTS product, and if so, come at a high price even when they are available.
You’re paying for features you don’t need
Most of these products have wide variety of features, but since they’re developed for most situations and not just yours, you end up paying for features you will never use. During an evaluation of an OTS product, the number and depth of features is a selling point, but are rarely ever used in production.
Custom Development
The classic alternative to off-the-shelf products is a fully customized application developed from the ground up. Like a well-tailored suit, this can be the best fit for your needs, but comes with its own challenges. And just like a well-tailored suit, custom software development doesn’t always respond well to size and scope changes.
PROS
Fully Customizable
Since the solution is developed for your specific needs, it can contain any feature you require and nothing else
Open data formats
You can choose your data store, and are not locked into proprietary tools for import/export, or license restrictions on your own data.
Affordable and highly available resources
Choosing your own development languages and tools also means that you can create your custom solution using ubiquitous technologies. Software engineers and consultants are abundantly available at reasonable prices.
No licensing restrictions
If the solution is yours, your only licensing restrictions would come from any contracts established with your development team and any underlying technologies utilized in the development of the architecture.
Use any data source and data store
Utilizing APIs and communication protocols within custom development means that almost any device and data source can be integrated. Also, every open data store can be used and even mixed within a custom solution. This makes the underlying data available at any time for real time monitoring, historical analysis, and reporting using the tools of your choice.
Can host any user interface
Since the data is open, this also means any possible user interface can be developed, with your own company branding, which is necessary for OEMs and software resellers.
CONS
Upfront development may be required
With a custom solution, there’s no avoiding it. The software needs to be developed and tested before it can be rolled out into production.
No built-in user interface or apps
Because you’re starting with a blank slate, you can have any interface you would like, but that means none exist. All of the interfaces and tools need to be created.
Requires customization when requirements change
If your company grows, your requirements change, or you realize that your original assumptions were not entirely correct, the solution must be modified. Whenever a custom solution needs modification, that usually means more custom development, unless the modifications were planned upfront.
A Third Way: The Open Architecture
The OAS Platform is a robust alternative for building an Industrial Automation or IoT solution. The Platform mitigates many of the risks of pure custom development, while still offering all of the advantages of a custom solution. How is this possible? OAS provides a robust and scalable networked platform that can be connected to data sources and data stores, all through a set of configuration applications. At the same time, the OAS platform exposes a series of APIs and developer tools for the creation of custom applications and the complete automation of the entire system. The following are just a few of the features OAS offers:
Universal Data Connector
The UDC is a server platform that manages connectivity to devices, databases, file systems and more. It also includes native drivers for many standard PLCs and IoT components that can be connected and configured with no programming required. The UDC is able to be networked with other instances, distributing and aggregating data as needed at the fastest speeds possible.
The OAS Platform offers flexible licensing. Whether you are an automation engineer, systems integrator, or software developer looking to use the platform as a component of your own products, OAS licensing can be adjusted to meet your needs. Licenses are based on the number and type of data sources being connected, not the number of clients connected.
Your data is your data, so when the OAS platform moves data between source and destination, or when the data is stored in a database, it is always available in open formats. No proprietary tools are required, and no additional licenses are needed just to read or even move that data using other tools that you prefer.
Every aspect of the server configuration can be automated using the various APIs that are exposed for .NET and REST clients. This means an OAS Platform can be programmatically configured and deployed, dramatically reducing costs for rolling out new installations when your organization or install base grows.
Infinitely customizable using open development tools and APIs
Access to the OAS APIs and development components is available using open tools and with popular development environments and languages. Desktop applications can be written in any .NET language using Visual Studio. Many visual components are provided for both WinForms and WPF for real time data access and control, as well as for Trend and Alarm visualization. Web application developers can use the Web HMI, Web Trend, and Web Alarm products to deploy web-based visualizations on any web platform and any web browser, desktop or mobile. And using the .NET Core Components, native iOS and Android applications can be integrated into your solution.
The UDC also exposes several APIs for automation and customization. Software developers are free to build their own user interfaces using completely custom code, or they can use the many tools and controls provided for desktop, web, and mobile applications.
Because the OAS Platform can be configured and automated using open development tools and popular languages, it becomes much more affordable to apply resources to your next project. The pool of .NET and web developers available is one of the largest in the IT market, so ongoing maintenance risks are greatly reduced as well.
Are you constrained by your current HMI builder tools?
Are you facing burdensome licensing costs with your current solution?
Is it difficult to customize your visualizations to meet your specific needs?
These are but a few problems you may be faced with when you’re locked into using a proprietary or “canned” HMI solution. Of course, every product has its benefits, and your current solution is no exception. Proprietary solutions do a great job of getting you up and running quickly, and are geared towards developing visualizations with little or no programming skills. But these benefits come with a cost: lock-in.
In order to develop these drag-and-drop or non-programmatic HMIs, vendors supply proprietary tools and deployment platforms. You’re often restricted on what type of visualization you can create within their sandbox, limited on what applications you can share data with, and you can rarely integrate with your own custom graphics and applications.
The solution? An open architecture such as the OAS Platform.
When a product uses an open architecture, you can use commodity servers, development tools, and they are built from the ground up for integration. The OAS Platform even exposes multiple APIs for automation and visualization development in ANY application platform and language.
Benefits of Open Visualization
Ubiquitous or common skills needed to develop a visualization With an open platform, you can build a team from the millions of developers and consultants with .NET and web application development experience. Common languages and popular development tools are all supported such as C#, VB, Javascript, Python, Visual Studio and your favorite code editor.
Licensing and distribution costs are dramatically lower Incremental costs can typically be capped when adding new clients or screens. The OAS Platform allows for unlimited client connections with no additional fees or per-seat charges, so you’re free to expand without breaking the bank.
No limitations on the type of visualizations possible Using common tools for developing your own symbols and screens, or using any 3rd party set of graphics, you can now create the screen you need and not just settle for what your HMI builder supports. Create images and symbols in popular graphics editing suites, 3D modeling packages, or anything that can produce standard files such as JPG and PNG to be used in Windows, web, and native applications.
No vendor lock-in You are free to integrate existing products for the best solution. Don’t get rid of what you already have, enhance and improve it by integrating an Open Visualization.
How-to Develop an Open Visualization
Step 1:Connect your data to the OAS Platform
The OAS platform supports connectivity to virtually any data source through options such as native device drivers, database access, or API integrations
Configure, aggregate, and organize your data points within the OAS Platform allowing you to expose them through APIs and Developer Tools for .NET, web, and REST API clients on any platform.
Display dynamic, real time and historical data in your custom visualizations. Build native apps for Windows as well as iOS and Android mobile devices in .NET and Xamarin. Build cross-platform web visualizations using any web application environment and any browser. Build custom integrations and visualizations on any platform using the REST API.
With OAS, OEMs and systems integrators can build custom solutions for automation and monitoring
Original Equipment Manufacturers (OEMs) and system integrators need a platform that minimizes integration efforts while maximizing flexibility. When developing a solution for resale, it must meet the individual needs of many customers. Each installation comes with its own unique challenges. Many other products allow for connectivity between systems and provide tools for doing so. Yet they often lack either full customization options or licensing that hinders products from being viable. The OAS Platform is a clear advantage in terms of connectivity, customization, and flexible licensing.
Unparalleled Connectivity
Native Device Drivers
OAS includes native drivers for Allen Bradley, Siemens, and MODBUS devices, as well as the ability to move data from OPC servers and clients. Using native drivers, data transfer speeds are maximized over the use of intermediate OPC servers.
Databases
Built into the OAS Platform are database drivers for high speed logging to MS SQL Server, Oracle, MySQL, PostgreSQL, MongoDB, SQLite and more. Additionally, using the Recipe feature, OAS can consume data from any supported database for real time data access
Non-standard or Proprietary Interfaces
Using the OAS Universal Data Interface (UDI) you can write drivers that read and write data from proprietary or non-standard APIs and applications. These are first-class drivers within the OAS Platform and can then be configured visually or programmatically within the built-in tools.
Customization Features
SDKs for Any Development Platform
Whether you are a .NET or Web developer, and no matter what language or development platform you prefer, OAS has solutions for the creation of fully customizable HMIs or user interfaces. Included with every installation of the OAS platform are components and libraries, and with the OAS REST API real time and historical data can be delivered to any client. Additionally, the full platform can be programmatically configured to ease rollouts or to support your own custom configuration tools.
Private Labeling for Configuration Tools
With a simple configuration file, the built-in configuration applications can be branded with your company logo, documentation, and titles. This allows you to ship a packaged product to your customers that maintains your company brand and messaging.
Deployment Flexibility
Networking is at the core of the OAS Platform, so you’re free to build a solution that features independent installations at customer sites. You can also deploy OAS so that data is centrally managed within your own company. Or, you can choose a hybrid approach to get the best performance and control of your data. OAS even has server runtimes for both Windows and Linux so you can work with the greatest number of customers and cater to their architectural preferences.
Licensing
The OAS Platform is licensed at the data source and based on the features and number of data points being tracked. This means that unlimited clients and applications can access the data with no additional cost. Also, all of the configuration tools can be used from any number of local or remote clients with no additional cost.
Learn More
If you’d like to discuss how OAS can be an integral part of your custom solutions, contact us at any time to schedule a demo or to speak with our sales team for more information.
Projects can be difficult to manage, especially when you are working on several at the same time or you have a complex project with many working parts or different elements.
The good news is that there are a multitude of tools designed specifically to help you manage and organize your projects effectively today. The diversity and overall capability of these tools are increasing all of the time, which is great news for businesses around the world.
However, the tough part is deciding what tools to use! Too many cooks spoil the broth, as they say, so you need to narrow down your selection with care.
Modbus is a serial communication protocol that was developed by Modicon. It was first published in 1979 for use with the company’s programmable logic controllers (PLCs). In basic terms, it is one of the methods used for information transmission over serial lines between electronic devices. The Modbus Master is the device that requests the information while Modbus Slaves supply the information. In a typical Modbus network, there will be one Master and as many as 247 Slaves, with every Slave Address being unique, from 1 to 247.
A Brief History Of Modbus
Before we get into the particulars regarding the use of Modbus, let’s take a look at the brief history of this platform. In the early days of industrial automation, factories required an approach for the first Programmable Logic Controllers (PLCs) to communicate with each other. The first PLC was developed in 1968 by Modicon, as per General Motors’ request. After this started to showcase effectiveness at General Motors, the device was called Modicon 084, and mass production began. This resulted in several new competitors entering the market toward the end of the 1970s, for example, Allen-Bradley was one of the main competitors that started to create such solutions, and PLCs were highly common in factories. However, information was still not being communicated via the PLCs, and there was an arms race to find out who would be the first to innovate their technology so that communication could take place between the devices. Around the same time, Modicon created Modbus while Allen-Bradley released Data Highway. However, many viewed Modbus as the grandfather of the industrial communication protocol field. When it comes to connecting automated electronic devices in industrial settings, this is the
most common method used. When Modbus was released by Modicon, the company did so without their standard licensing protocol being kept. This enabled any developer to incorporate Modbus into their products as it is a universal standard that many devices can support. It is also very easy and straight foward to understand and set up, even by those who do not have an engineering background.
What Is Modbus Used For?
Modbus is an open protocol platform, meaning, manufacturers can build their equipment free of charge without needing to pay royalties. It has become a standard communications protocol in the sector, and it is a common means for connecting industrial electronic devices. Manufacturers across a number of industries use Modbus. It is typically utilized for the purpose of transmitting signals from control and instrumentation devices back to the chief controller or data gathering system. For instance, this could be a system that measures humidity and temperature, and then communicates the results back to a computer.
Understanding How Modbus Works
Modbus is generally transmitted over serial lines between devices. The most straightforward setup involves a single serial cable that is connected to serial ports on two devices; a Slave and a Master. The data will be sent as a series of zeroes and ones called bits. Each bit is sent as a voltage. Zeroes are sent as positive voltages, and ones are sent as negatives. The bits are sent very high quality. A standard transmission speed is typically 9600 baud (bits per second).
The Modbus Organization, Inc.
The Modbus Organization has managed the development and any needed updates to Modbus protocols in an association of users and advocates of the technology ever since Schneider Electric bequeathed the rights to them in 2004. It is an independent, non-profit organization that requires membership to join. Their mission is to build the infrastructure needed for full adoption of Modbus across multiple industries by sharing information and educating users on the best practices for successful implementation.
Modbus Protocols
Several protocols for Modbus exist and are constantly evolving through experimentation and innovation from users within the Modbus Organization. Three are most commonly used, with Modbus TCP being the protocol that the Modbus Organization favors in its development and universal implementation objectives.
Modbus RTU Modbus RTU is a type of serial Modbus. This transmission mode encodes messages as bytes that are sent one after the other without any spaces between them – though a 3-½-character space inside acts as a delimiter between messages. For each eight-bit byte: one start bit, eight data bits, one bit for parity, and one stop bit are sent, for a total of 11 bits per byte. Every Modbus RTU message is ended with an accompanying error checksum in what is called a cyclic redundancy check (CRC).
Modbus ASCII The Modbus ASCII protocol initiates every message with a colon “:” character. An ASCII carriage return/line feed (CR/LF) character ends every message transmission. This provides variability in what is being communicated with more spacing in between the bytes, giving it the ability to transmit through certain modems. ASCII characters are used to communicate this data. For each eight–bit byte: one start bit, seven data bits, one bit for parity, and one stop bit are sent, for a total of 10 bits. Modbus ASCII messages are ended with an error checksum called a longitudinal redundancy check (LRC).
There are pros and cons to be weighed when using either of these two types – Modbus RTU and Modbus ASCII – as Modbus ASCII is much simpler to read by just looking at the message, but the RTU messages are much smaller, allowing for an enormous amount of data to be communicated in the same amount of time. Modbus RTU is used most commonly.
Modbus TCP Modbus TCP is different in that it does not require a checksum, but is basically the RTU protocol running on Ethernet and a TCP interface. The TCP port 502 is reserved for Modbus, while the new Modbus/TCP Security uses Port 802. Much more on this can be found at Modbus.org.
Modbus Protocols and IoT
The Modbus Protocols may be older than most people reading this article, but its simplicity and efficiency at powering many sectors of the manufacturing industry is still transitioning along with new advancements and innovations like the Internet of Things. Programmable Logic Controllers (PLC), Industrial Control Systems (ICS), Distributed Control Systems (DCS), and/or Variable Frequency Drivers (VFD) are all frequently seen in factories around the world. They perform actions and transmit data in real-time to manufacture many of the common household items you possess, from vehicles to breakfast cereals, and it is all communicated with Modbus Protocols. Essentially, Modbus, being by now so pervasive and adopted into millions of devices – and not just on the factory floor, but in millions of products from absolute encoders to zero-point thermometers – has already been doing what the Internet of Things (IoT) and IIoT (Industrial Internet of Things) is only now doing. The difference between them is that IoT is faster, more efficient, and more accurate at communicating information, which leads to more productivity, more cost-effectiveness, and more profits.
But this does not mean that Modbus is heading to the trash heap as IoT takes over – not for a while, anyway. Its wide adoption across so many industries all over the world cannot be dispensed with so quickly, or so easily. There are now several software companies providing solutions for Modbus and IoT integration, but only one of them has the experience and reliability to liberate your data with unparalleled connectivity, Open Automation Software.
Open Automation Software Modbus IoT Data Connector
The OAS Modbus IoT Data Connector provides a direct connection to Modbus slave devices and the ability to host data to Modbus masters with the built in Modbus Driver Interface. The Modbus Driver Interface supports communications over Ethernet and Serial interfaces with Modbus TCP, Modbus RTU, and Modbus ASCII protocols.
With Modbus Automation Software from OAS, businesses will find the easiest process for adding Modbus communications in Real-Time Automation on the market – with one click of a button! Three of the most widely used Modbus Protocols can then be seamlessly implemented –
Modbus TCP, Modbus RTU, and Modbus ASCII protocol – onto both Ethernet and Serial Port interfaces with the Modbus Master connection. Modbus TCP over Ethernet and Modbus RTU and ASCII over Serial Ports with the Modbus Slave connection.
After a quick and easy setup, the communication speeds you experience while running multiple Ethernet connections are at the fastest possible, with update rates averaging 15 milliseconds per packet. Data from anywhere, to anywhere, are sent in real-time with direct access to Modbus compatible devices. A PC and standard internet connection are all that is required to host live Modbus data. Remote data logging is also made highly secure, and backup devices can be optionally defined with Automated Communications Failover.
The ease of access for Modbus IoT Data Connector isn’t limited to only a few operating systems, either. Supported systems include Windows PC/Server, Windows Embedded,
Windows IoT, Linux Server, Virtual Machines (Win/Linux), Raspberry Pi 4, and Docker Containers (Win/Linux).
The OAS Platform: Full Connectivity
Open Automation Software began 28 years ago with the philosophy that user interfaces and database archiving software should be open, far-reaching, and provide easy implementation and cost-effectiveness for consumers. An Open Architecture plan allows unparalleled customization with open accessibility to third party reporting systems, .NET applications, web interfaces, open standards like OPC UA and MQTT, and even remote Microsoft Excel workbooks.
The nature of the OAS Platform empowers you with flexibility. Purchasing the Universal Data Connector in combination with connectors for devices, databases, applications, IoT services and more, will give you the most powerful and versatile framework for enterprise systems integration. The built-in compatibility with other developer tools and APIs give you an unlimited amount of options for customization and automation.
The full range of products include:
Universal Data Connector
The core of the OAS Platform, the UDC is a Windows based program allowing it to be implemented in several different ways. Enable data connectivity, server-to-server networking, and more.
Data Historian
Log data in open format to MS SQL Server, Oracle, mySQL, PostgreSQL, InfluxDB, MongoDB, SQLite, MariaDB, Access, SQL Azure, Amazon Aurora, Amazon RDS, and CSV files.
Alarm Logging & Notification
Log events to open databases, and send notifications via SMS, email, and voicemail.
Device & Data Connectors
Read and write data to Allen Bradley, Siemens, and Modbus devices, Universal Drivers, OPC, OPC UA, databases, and Excel. Read MTConnect.
IoT Connectors
Connect to cloud-based IoT gateways such as AWS, Azure IoT, and MQTT Brokers.
Visualization Tools
Build custom Visualizations, User Interfaces, HMIs and Dashboards for Windows, web, as well as native iOS and Android devices.
SDKs & APIs
Develop custom automation apps for Windows, web, and mobile devices. Integrate with .NET and REST APIs. Build custom integrated device drivers.
Networking Features
Provides the most robust, scalable, and reliable distributed networking platform for IIoT solutions.
You might have heard of the Internet of Things, but you might not yet be familiar with the Industrial Internet of Things. It’s to do with how devices used in industrial processes communicate with one another and collect data. It’s an emerging idea in the industrial world, and it’s set to change things even more in the years ahead.
Of course, it’s a big concept with a lot to understand. If you want to find out all about it and what it means, you’re in the right place because we’re going to talk more about it today. Read on to find out all about the Industrial Internet of Things (IIoT) and what it all means, both now and moving forward.
What is the Industrial Internet of Things (IIoT)?
At the most simple and fundamental level, the Industrial Internet of Things refers to lots of industrial devices, such as machines, sensors, gadgets, networks, and motors, that are connected to each other. The devices contain sensors that are connected to networks that then gather data. They also communicate with one another as data is shared and transferred.
Because of the advances in technology seen in recent times, the sensors used for these devices can be made smaller than ever. This means that now even very small industrial devices of various kinds can be connected, allowing for ever greater levels of monitoring, tracking, and data collection as they communicate with other devices.
The point of all of this is that businesses can take that data and analyze it to better understand how their functions are operating and how their business processes are performing. The more data you have, the more complete picture you get of those industrial processes and performance levels. And that’s one of the key reasons why the Industrial Internet of Things is so valuable.
What Can It Do for Businesses?
So what can IIoT do for businesses in a practical sense? What needs do businesses have that can be addressed through the Industrial Internet of Things? One of the most important things it can help with is the making of decisions and the most efficient ways of doing that. By collecting and analyzing data, insights can be found that inform the next decisions that need to be made.
The level of detail provided in this data can be very high. Businesses and business owners can then understand their processes better than ever before, and in turn, this helps them to make their processes more efficient. As they make decisions, they can be led by the data rather than less tangible estimations that might not offer the same accuracy.
The Industrial Internet of Things also helps when it comes to managing supply chains better and coordinating directly with other businesses. When businesses work together better in a more carefully coordinated way, they can be made even more efficient. And that’s something that benefits both businesses.
How Does it Differ from IoT?
As we mentioned earlier, lots of people have heard of the Internet of Things or IoT, so how does that differ from the Industrial Internet of Things or IIoT? There certainly is some overlap between the two, and the two concepts can become confused in certain ways as well. But it’s important to make clear that IIoT and IoT are not the same and there are key differences.
The consumer standard IoT can cover things such as electronic devices like TVs, speakers, and smartwatches and even home appliances such as refrigerators and security systems. The technology behind IoT is the same as IIoT. They both use sensors and networks to allow devices to communicate with one another to deliver efficiency and/or performance benefits.
The lifestyle efficiencies IoT offers, however, are more about small matters and making things more convenient for users in their day-to-day life. IIoT, on the other hand, is more about planning, analysis, and business efficiency. As a result, there’s more analysis and data crunching that goes into IIoT.
Which Industries are Beginning to Adopt IIoT?
There are already lots of companies out there that are using and benefiting from IIoT, and there are some industrial niches that are using it more than others. As we’ve mentioned, the Industrial Internet of Things is particularly useful when it comes to coordinating companies, so it makes sense that a lot of supply chain management and logistics companies are already using the Industrial Internet of Things.
It’s also true that the world of manufacturing is starting to embrace IIoT. When manufacturing companies use the Industrial Internet of Things, it allows them to make projections about the most optimal and efficient timing of machinery servicing and things like that. This might not seem like much, but it can reduce the amount of downtime the company experiences.
Any business that wants to make sure that they don’t run out of stock and don’t have to store stock for too long before using it can benefit from using the Industrial Internet of Things. And many already are. Public sector sectors, such as health departments, can also benefit from what the Industrial Internet of Things can offer.
How Well Established is this Technology Right Now?
The Industrial Internet of Things is already very big, and although there are lots of companies already making use of these technologies, there are plenty of others who aren’t doing so yet. That means the technology hasn’t yet reached its apex and there remains plenty of room for growth, which can only be seen as a positive thing for what’s to come.
The Industrial Internet of Things is already being heavily invested in, with hundreds of billions of dollars being poured into it by businesses in a variety of industries and sectors every year. In recent years, those numbers have been growing, suggesting that IIoT is on an upward trajectory in terms of business spending.
There are many different things that businesses are spending this money on at the moment. A lot of the money is being spent on logistics and transportation to make supply chains better integrated with IIoT technology. That’ll make it possible for companies to benefit in the ways discussed above.
The Components Used in the IIoT
The Industrial Internet of Things is simply the term used to refer to the three main components used to gather data and interpret it. The first of these three components is sensor technology. Sensors have become much cheaper and more scalable in recent years, and that’s made it easier to use them on a variety of different devices.
The next component is network technology. The networks are what make it possible for the different devices to connect and share data. And the final component is the technology that makes it possible to analyze the analytics data. How these three components combine and integrate will depend on the particular situation.
The specific devices used will also differ depending on the company and the aims of the project. Some will focus on machinery, others will focus on transportation. There are so many different kinds of devices, both big and small, that can be incorporated into an Industrial Internet of Things system. That flexibility and simple customization are among the things that make it so appealing.
Security Matters
Security is one of the things that you need to think about if you’re going to start using the Industrial Internet of Things. The devices usually used to create an IIoT setup are not ordinarily intended to be connected with other devices and networks. They certainly can be, but you also have to accept that this brings with it an increased threat and risk level.
To ensure you don’t end up being hit by some sort of cyber hack or attack, you need to put in place the proper security measures. Basic things like strong password protection are key, but there needs to be a broader security strategy in place that can back you and your systems up.
Research has found that one of the main reasons making businesses hesitant to implement IIoT systems are the security worries that they have. That doesn’t need to be something that prevents businesses who would benefit from the Industrial Internet of Things from using it; it should just mean that extra security planning takes place.
Better Speed and Reliability for IIoT with OAS
The Industrial Internet of Things is a new revolution, but requires an enormous amount of data to be transferred and stored, and only edge solutions can provide the performance, reliability, and speed required to do this efficiently. Open Automation Software (OAS) has been so valuable in this type of efficient computing for accessing, logging, and displaying data closer to the source from which it’s generated – as well as for its speed, accuracy, and design philosophy as an open network that is easy to implement and cost-effective – that it is utilized for many high-volume systems, such as in Intel’s manufacturing plants and by the U.S. Navy on its nuclear submarines and aircraft carriers.
OAS and Its Many Applications In IIOT
With the OAS platform almost every industry can find the best-in-class IIoT solutions for high-speed and reliable data logging and transfer, device management and control, and security across network communications.
Building Automation Systems (BAS) have been developed through the OAS Platform by customers for years, being used in commercial property for lighting, HVAC, safety and security, and in ways that control building operations in more efficient, cost-productive solutions. With the OAS Data Historian, time series data and event based data can be collected over an entire building automation data spectrum to observe and act in predictive maintenance, detected downtime, and asset management for a level of advanced control more proficient than ever before in productivity and cost efficiency.
Open Automation Software offers complete operational visibility and connectivity between assets for businesses in the manufacturing industry. With real-time insights and accurate data, AI and human abilities are more efficiently merged, operational costs can be reduced, and customer/product interaction can be enhanced for enhanced marketing and product development.
IIoT integrated with the OAS platform offers endless possibilities. But its applications extend far beyond smart buildings and manufacturing. This system is being effectively implemented in a wide range of industries, such as in the:
Marine industry
Mining industry
Packaging industry
Shipping industry
Water industry
Chemical industry
Recycling and waste management industry
Telecommunications industry
Construction industry
Robotics industry
Transportation industry
And the list goes on…
Getting Started with IIoT
If you want to get started with the Industrial Internet of Things, the first thing you’ll need to do is identify your goals and what it is you want to achieve. Every business and every project is unique, so only you can identify the goals and needs that have to be addressed as you implement your first Industrial Internet of Things system.
Some projects will be all about monitoring for efficiency or operational performance, others might be integrated with automation and others will be about predicting future maintenance needs and minimizing downtime as much as possible. You need to identify the specific technologies that you want to make a part of your Industrial Internet of Things system.
From there, you should learn about how to store and analyze data if that’s something that you plan on being a part of your IIoT setup. It’s something that most businesses will want to do in some form or another. It’s also important to remember that it’s a process and that you can make tweaks and changes in the future.
Universal Data Connector
Infinitely customizable using open development tools and APIs
With OAS, OEMs and systems integrators can build custom solutions for automation and monitoring
