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.
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.
New release adds Data Store device
With the new Data Store device in groov R3.3, you can put data into groov from anywhere—like a database, another device or system—and monitor or change it in your mobile operator interface.
- For example, your company’s SQL database could place production or maintenance data into a groov Data Store for managers or technicians to see in their interface.
This time we'll show you how you can use the REST API with a Microsoft® Access® database.
What does the new built-in RESTful API in Opto 22 SNAP PAC S-series and R-series programmable automation controllers mean to you?
It means you can use a variety of programming languages to easily access data in the PAC.
Have you wanted to share I/O point or variable data from your SNAP PAC controller with a Microsoft® Excel® spreadsheet or Access® database?
- Maybe you're tracking sales in a spreadsheet and want to adjust production to match projections.
- Maybe your PAC is monitoring equipment on-time and energy usage, and you want to add that data to an equipment maintenance database.
If you've heard about our Opto 22 SNAP PACs with their built-in RESTful API (application program interface), you may be wondering how you'd use that API to send real-world data to the IBM Watson IoT platform.
I'll show you how, step-by-step, in this blog post. It's a long post, but it includes everything you'll want to know. (You can print this page as a PDF if you like.)
Join us in Utrecht, Netherlands, next week and explore the World of Technology & Science (WOTS) Exhibition. This is the technological venue for everyone in the industrial, science, and healthcare fields.
OptoDistributor Mulder-Hardenberg will welcome you there at stand 10F051 and demonstrate:
Here's the latest Code Samples and Tips contribution in our new OptoForum: an example of easier peer-to-peer communication between PAC controllers.
This example takes advantage of the new RESTful API in SNAP PAC hardware controllers (both the standalone S-series and the rack-mounted R-series).
I'm extremely excited about the new capabilities of the 9.5 firmware and, in particular, the new RESTful interface (REST API and HTTP/S server) for SNAP PAC controllers. I have several PACs throughout my home for various tasks like lighting, A/C, irrigation, energy management, monitoring, and surveillance. The new RESTful interface allows me to take my home automation system to completely new levels, including interacting with my other home automation/IoT products, like my Nest thermostats, smoke alarms, and NestCams; my Philips Hue lighting; my Wemo switches; and much more.
This post isn’t about home automation, however. It’s about getting the firmware upgrade done and configuring the HTTP/S RESTful server. And in doing so, it was important to me (and my application) that I preserved the persistent control system variables used in my control strategies. So...the following are the steps I took to upgrade my firmware while preserving important data and getting started with REST.