By Steve Hechtman
By Steve Hechtman
Okay, you’ve tackled PLCs, and now you can program them with one hand behind your back. So what’s next? What’s the next logical challenge?
Think SQL and relational databases. Why? You’d be amazed the similarity; it’s the next logical progression.
You might ask how it is they’re even related. For one thing, relational databases can sort of be an extension of PLC memory. There, live values can be mirrored bi-directionally. Historical values and events can be recorded there as well. But operators and managers can interact with them, too. I’ve spent more than 20 years of working, living, breathing and thinking PLCs, but during the past six years, I’ve delved heavily into SQL and learned a lot about relational databases. I’ve discovered that working with SQL is remarkably similar to working with PLCs and ladder logic.
SQL has four basic commands and about a hundred different modifiers that can be applied to each, which can be applied in various ways to achieve all types of results. Here’s an example: Imagine effluent from a wastewater plant with its flow, PH and other things being monitored and logged. That’s what you typically see. But now let’s associate other things with these, such as discrete lab results, the name of the persons who did the lab work, the lab equipment IDs and calibration expiration dates, who was on shift at the time and the shift just prior, what their certification levels were, what chemicals where added and when, who the chemical suppliers were, how long the chemicals sat before use, and so forth ad infinitum. All of this becomes relational data, meaning that if it’s arranged properly in tables, you can run SQL queries to obtain all types of interesting results. You might get insight into the most likely conditions that could result in an improper discharge so it could be prevented in the future.
In my explorations of SQL, I found myself looking at the layout of my tables and evaluating the pros and cons of each layout. I massaged them, turned them on their side, upside-down, and finally ended up with the most appropriate arrangement for my application. And similar to PLC programming, I explored innumerable what-if scenarios. I was struck by the amazing similarity in my approach to developing solutions for PLCs. This has been a lot of fun — in fact, exhilarating — just like PLCs used to be. It’s the next logical progression, you know.
SQL is a high-level language that isn’t very hard to learn, and you can be very clever with it. I prefer to think of it as a natural extension to my PLC programming skills. Now that you have the machinery running, what did it do? Furthermore, relational databases and SQL pull people and processes together. Machines don’t run alone; they’re merely part of a containing process and that process was devised by people. SQL and relational databases form the bridge to integrate processes, machinery and people together. I don’t believe a COTS (commercial-off-the-shelf) package can do it any more than you could offer a COTS palletizer program and have it be of any use. It just doesn’t work that way. Every machine is different, and every business process is different.
That’s where the SQL comes in: it has to duplicate or augment existing process flows and these are intimately connected to the machinery. And that’s why the PLC programmer is best suited to implement solutions involving PLCs and relational databases.
So where do you start? I would suggest picking up a book at the bookstore, like one of those Dummies books, then download and install the open-source MySQL database server along with the MySQL Administrator and Query Browser. It only takes a few minutes to install and then start playing. At the end of an evening, you’ll probably be very excited with all of your newfound knowledge and be thinking of endless ways to employ it in your own field of practice.
Steve Hechtman is the president of Inductive Automation.