Raspberry Pi for Industrial Uses

Question

I am interested to know what experience others have had using a Raspberry Pi in industry? I would love to hear about:

Any issues with short and long term reliability?
Connectivity with Industrial control systems -
- Have add on boards been used?
- Have custom PCB's been made to interface 24V based I/O on PLC's / DCS systems etc?
- How has it been hooked up to power?
Issues with EMI?
Long term SD card reliability?
Has a Pi been used to actually control some industrial equipment rather than for monitoring or HMI?
What version of Pi was used - eg. Compute module
Why use a Pi vs a PLC or industrialised PC?
What were the biggest challenges?
Was there any challenge from peers or management in using something that could be viewed as an educational tool rather than industrial control equipment?
What OS has been used?
Have there been any concerns around security? Especially if connecting to a Process Control Network.
What security precautions have been taken?

I can see lots of advantages to using a Pi in industry - for example the amount of power and versatility for such a low cost!

Even if you don't have experience using a Pi in industry - it would still be great to hear people points of view!

I look forward to some interesting responses!

-------------------------------------------

Tony

Gough Lui · Answer

While a Pi might seem to be an attractive solution, I can't exactly advocate its use in true industrial circumstances for a number of reasons: Raspberry Pi is for the most part, a low-cost consumer product. While they could be applied in industrial situations, they're not designed to be as robust as true industrial solutions. When in industry, you might be controlling extremely expensive equipment, controlling something that could involve safety-of-life or you might be dealing with clients with high expectations, so failures are not acceptable. Further to this, the cost of providing support (e.g. a truck-roll to premises to fix the equipment) could very much outweigh any savings that you might get. Additionally, clients may demand systems which are built with reputable parts to alleviate risk regarding lack of support, satisfy their stakeholders that they're making an appropriate choice of equipment and allow service personnel from different companies to work on the equipment to bring it back into operation whenever a failure occurs. Consumer products typically do not cover the same level of operating temperature range, nor do they have things like conformal coatings to handle the dusty, greasy and sometimes humid environments encountered. They're also potentially not able to handle high vibration environments, along with potential voltage/current spikes/surges which can occur in automotive/industrial equipment settings. EMI from a heavy current-handling contactor could be sufficient to reboot or cause strange operating behaviour of microcontrollers/SBCs. Raspberry Pi SBC itself is very much "naked", so I suppose some of these points can be alleviated through careful treatment of the board with conformal coating, enclosure in an aluminium chassis for heatsinking and shielding, using specially designed HATs etc. But then that's a lot of work, it voids warranty and it's not guaranteed. Depending on how you utilise the Raspberry Pi - if you're just running a regular Linux OS, there are a few issues - for example: It's a fully-fledged operating system, it takes a while to start up which can be unacceptable. It also is based on open source code that evolves rapidly - this can break software as it is updated, and there can be security holes that need to be urgently patched at time without any centralized management mechanism. It is a multitasking operating system - so the delay involved when servicing requests can vary depending on CPU load and how the I/O is being performed (e.g. interrupt or polled) which could be unacceptable. The board itself also uses regular consumer RAM without any error correction - in case of memory corruption (which can happen organically due to charged particles, or due to power fluctuations), the board could crash or execute incorrectly - are there any failsafes that stop people from getting hurt or equipment from getting damaged? The board is pretty sensitive to power - how are you going to supply good quality power to the board at all times and ensure that it never improperly shuts down (at the risk of corrupting the SD card requiring intervention)? Even having a UPS is no guarantee as batteries fail and servicing can be missed. You might need to develop your own software to network them "safely" - a lot of existing proprietary solutions have evolved over time which have helped their safety, but of course, some process controls stuff is not safe by design (e.g. vulnerable to replay attacks) and is only safe due to air gapping, but you'd always hope to advance the state of the art. SD card issues can be common. Early Raspberry Pis had contact issues with full-sized SD cards, whereas the later push-push type sockets with microSD generally work well, at least when not being vibrated. The big issue is the variance in flash memory quality - many consumer SD cards are TLC/QLC flash with very low endurance, meaning that they cannot sustain more than about 100-500 full cycle writes before they fail. Many are also optimised for large block writes rather than small block writes, making for a slightly reduced user experience when it comes to updating the OS for example. Opting for a high-endurance MLC industrial flash card is a better option, but these cards often have to be specially ordered at a higher price. Sometimes you can be caught out by unexpected issues - e.g. use a small microSD card with slightly wrong settings and you might find your system logs somehow fill up the storage, making the system completely unworkable. Besides, even things like system logs often will eat at flash write cycles whenever the unit is operational and something happens. Long term reliability is an unknown - I've had no major issues with well made boards, but early Raspberry Pi Model B boards had some BGA soldering issues, and some late boards are seemingly having some through-hole soldering issues with some Pi 3 B+'s failing randomly ... but since most of my critical stuff still runs on the original Model B, I've had very good luck with most of my Pis with the 5V supply failing frequently before the board does. If you're looking to RPi as a money saving option, better think twice. In industry, the downtime could indeed eat up any savings, along with the need to engineer custom interfaces, treat boards specially, run updates, provide failsafes, provide documentation/support, ruggedize the unit and cover your legals. - Gough

peteroakes · Answer

Another alternate product is the Revolution PI, based on the Raspberry PI 3 compute module on a custom motherboard, this has 61131-2 compliant IO , DIN rail mount, with Real time patches though still running Raspbian and reasonably priced. See https://revolution.kunbus.com/ I have a set of these and am currently putting together a review (From a different distributor ) but in the mean time, I thought I would show you the vendors site, these are awesome units and utilize a distributed processing architecture as well as Real Time patches to Raspbian to achieve its processing needs, it also utilizes many fully compliant IEC 61131-2 components Definitely worth a look

mp2100 · Answer

I’ve been watching for this too. Searching around the ‘net ive seen a German company selling rPi Hardware as a PLC equivalent system. Sorry, the link is on my rPi, I’ll look for it. They have discrete and analog I/O cards. An rPi on it’s own only has discrete (on/off) control, and serial/i2c/spi communication, so you need additional components if you want analog control.

My concern is reliability in hot environments or vibration. I’d consider using an rPi for monitoring first, before trying it for controlling something. I’ve considered the BBBlack Industrial from element 14, it has a better temperature rating.

BeagleBone Black Industrial

tonydbeck · Answer

I would also be interested to know what methods are used to make a device such as a Single Board Computer more suited for an industrial use? Some methods I am aware of: More PCB layers for EMC compliance and better heat dissipation - as used on the netPi Components with larger temperature ranges Conformal coatings Use of Enteprise Multi-Level Cell (eMLC) or Single Level Cell (SLC) flash rather than Triple Level Cell (TLC) flash Isolation circuits - eg. Opto Isolation ESD protection cirucuits EMI shielding - eg. metal enclosure Ingress Protection - eg. High IP rated enclosure Hardened OS - Use of Docker containers, no SSH access etc ECC memory

Gough Lui · Answer

You might also consider adding an RTOS to the list, as properly written software for RTOS can meet critical latency and jitter requirements. In addition to ECC memory, some of them will also have separate OS level fault tolerance, say by modularising the OS kernel and being able to hot reload any module on the fly for downtime-free updates (e.g. think telecommunications equipment often is capable of this). Sometimes, what makes something industrial may simply be the use of parts with a known long market lifetime - i.e. commitments from suppliers that the components will remain available so that you can offer assurance to integrators that your solution may still be serviced 15-20 years down the track. Cherrypicked unit testing may also be used to qualify units met required standards prior to shipping as industrial. Sometimes this entails better inspection as well (e.g. Xray). Sometimes there are design differences to allow for better (more rapid) field service testing/debugging through LCDs, test points and integration of better cooling solutions. But otherwise, it seems you've covered all of the main ones I'm aware of. - Gough

peteroakes · Answer

you might find this useful https://www.youtube.com/playlist?list=PL_atu5RtEPi72ubTe0c7rr1xJWhBSXted

You don't have permission to edit metadata of this video.

Edit media 
 
 
 
 
 
 Dimensions 
 
 
 
 x 
 
 
 
 
 Small 
 Medium 
 Large 
 Custom 
 
 
 
 
 Subject (required) 
 
 
 Brief Description 
 
 
 Tags (separated by comma) 
 
 
 Video visibility in search results 
 
 Visible 
 Hidden 
 
 
 
 Parent content 
 
 
 Portable Multi-Channel Recorder 
 Project14 | The Birthday Special: Open Arduino: The Winners Announcement! 
 Digilent Digital Discovery with High Speed Adapter - Review 
 Project14 | Making Time: Anything that Uses or Alters Time such as Clocks, Timers, Egg Timers, and More! 
 OpenScope MZ Development Kit - Review 
 Project14 | The Birthday Special: Open Arduino Projects: Part 4! 
 3D CAD Homeschool 
 Project14 | Winners Announcement: Beautiful Works of Electronic Art! 
 Animatronic talking Tiki twins centerpiece 
 IoT on Wheels | Grand prize & Finisher prizes [Completed] 
 Project14 | The Birthday Special: Month of Robots: Robot Prizes for Giving Birth to Robots! 
 Project14 | Energy Harvesting: Meet the Projects that Scavenge Energy from Wasted Energy Sources! 
 A Treasury of Vintage Holiday Commercials 
 Comment on Project14 | Modernize Time with Smart Alarm Clocks! 
 Soil Battery for Forest Fire Detection System 
 New PSoC 6 101 Videos Out! 
 Arduino Projects 
 Do you like Nixie tubes ? 
 HARTING Han Modular Assembly Video 
 Project14 | Open Arduino: You Decide: Meet the Projects: Part 4! 
 Traffic Predictor #10 - Evading traffic like a Bat 
 Arduino Powered MSE-6 (Mouse Droid) - Droid in Action 
 Arduino | Birthday Wishes for Arduino Day 2018! 
 Project14 | The Birthday Special: Arduino Projects for Arduino Day! 
 Stuck Inside This Pi Day? Here's a Raspberry Pi Playlist for you! 
 Traffic Predictor #6 - Into the traffic [Part 1 of 2] 
 Arduino Powered MSE-6 (Mouse Droid) - Arduino Yun UI 
 Arduino | The MKR Contest Series: Show Us How You Would Use the Arduino MKR Line! 
 Project14 | Winners Announcement: Owning Time With Smart Alarm Clocks! 
 Project14 | Volunteer to Judge the Energy Harvesting Competition! 
 PCB Tips: Hairline Short Circuits 
 Project14 | Volunteer to Judge the Electronic Art Competition! 
 Project14 | Clustered MCUs:  Anything Goes with Two or More MCUs! 
 RE: Raspberry Pi for Industrial Uses 
 TI Hercules RM46 Three-Phase Generator With IGCM15F60GA Part 2 
 Project14 | Electronic Art: Meet the Projects that Add Beauty to Electronics! 
 
 
 
 
 
 
 
 
 Poster 
 
 
 
 Upload 
 Preview 
 
 
 
 
 
 
 
 
 
 
 
 
 Ok 
 
 
 
 
 
 Cancel

rsc · Answer

Hi Tony, We have deployed the raspberry pi as a motion stabilization platform controller for a ship based LiDAR system. I'm using a 5VDC 4A power supply that I can adjust to 5.3 along with the new Pi3 B+ running Raspbian lite. There have been 3 revisions in 2 years, with many little issues resolved such as weather-proofing, networking, start-up, fault and emergency-stop conditions. The RPi has done a good job so far, and has survived several months at sea running 24/7 Scott

tonydbeck · Answer

Hi Allen and Shabaz,

Thankyou for your responses!

I had come across the netPI in the past - it looks like a fantastic product where they have almost thought of everything. One thing that does appear to be missing on this board is the CSI camera interface, although I guess there is potential to connect a USB camera. The ability to take and analyse pictures is something that I believe could be very useful in machine vision applications.

This device looks very geared up for interfacing and communicating with control systems. The RS232, RS485, Digital IO add-on boards are a brilliant addition.

That is a really great point with regard to how a standard Pi could be used - it may be ideal for monitoring something, but maybe not for use to actually control something.

With regard to the BeagleBone Black Industrial - I had not come across the industrial version - but again this looks like a great device! I have been aware of the BeagleBone SBC's for a while, but have not ever delved into them - this community is probably a great place to start! Have you used them for any projects? Does the BeagleBone board have any distinct advantages over the rPi?

Another board that I have come across and am actually looking into using for a project I am working on is the: MyPi Industrial IoT Integrator Board from Embedded Micro Technology.

This board uses the Compute Module and has been designed for integrating into industrial equipment. There is an extended temperature range version for use in very hot or very cold environments.

It has 2 CSI camera connectors and a host of add on I/O boards. They will also design and supply custom I/O boards for a specific requirement. They have made a custom I/O board for me to aid in the project development phase.

Perhaps one disadvantage is they do not offer a hardened software platform such as the Yocto based Docker host platform on the netPi, although there is nothing to stop someone taking this approach themselves and using a similar software platform or using the Ubuntu Snappy core.

Cheers

-----------------------------------------------------------

Tony

tonydbeck · Answer

Hi Shabaz,

My understanding is that it is the components that are used that are extended temperature versions. I agree that the literature is a little misleading.

As stated in the Compute Module data sheet this would be the max for the silicon die and does not take into account heat generated by itself....

Of course, not all industrial uses are subject to extremes of temperature so this may not necessarily be a critical requirement.

Another plus for the netPi is that it comes in a really nice DIN rail mountable package.

I would argue that the two products are aimed at slightly different end uses - netPi is a fully finished product with tests/approvals and can be used as-is, whereas the myPi is designed to be integrated into something and is not a stand-alone item.

Another product I have come across and have purchased to test out is the Siemens IoT2040. It can be purchased here:

https://uk.rs-online.com/web/p/iot-development-kits/1244038/ It seems that element14 do not currently stock it unfortunately.

Here is the Siemens Support Page link:

https://support.industry.siemens.com/cs/products/6es7647-0aa00-1ya2/simatic-iot2040?pid=815412&mlfb=6ES7647-0AA00-1YA2&mfn=ps&lc=en-WW

I believe it is based on the Intel Galileo Gen 2 - which is interesting as Intel have now discontinued this board.

Like the netPi it uses Yocto and natively supports Node-Red. It also has connections for mPCLe cards and Arduino shields which is pretty cool. I have got an I/O module with mine that plugs into the Arduino shield connector and has 5x24V DI, 2x24V DO - up to 300mA, 2x0-10V AI and 2x4-20mA AI. As the module is made by Siemens for the device, it fits in really well and has a very neat cover plate.

Cheers

-----------------------------------------------------------

Tony

Jan Cumps · Answer

I’ve used the Siemens device - IOT2000 - and like it.

Jan Cumps · Answer

Yes, that video series helped me to get started. And for C/C++ native linux executables development, Intel’s Galileo MRAA github examples.

shabaz · Answer

Hi Allen, This is the device you're maybe referring to: https://www.netiot.com/netpi/industrial-raspberry-pi-3/ A preview of it from a trade show is here: A New Ruggedized Raspberry Pi 3 – netPI!

javiercalderon · Answer

Hi Tony I thank you for your valuable input, I've searched other alternatives and I have found three additional devices: https://www.balena.io/fin/ https://www.sferalabs.cc/strato-pi/ http://hasseb.fi/shop2/index.php?route=product/product&product_id=57 it would still be great to hear people points of view! ------------- Javier

tonydbeck · Answer

Hi Gough, Thankyou very much for your response - you have made some really good and valid points! I guess that there are a whole host of factors that would need to be taken into account when selecting some hardware for a particular task whether it be consumer based or industrial based. Following on from the points you have made, some considerations could be: Will it be used for monitoring and / or control? - If it is only monitoring, early failure may be acceptable risk, for control maybe not. What environment would it operate in? - If it is operating in a semiconductor fab plant the conditions are going to be pretty good, if it is on an oil rig in the North Sea then probably quite the opposite! Does it interact with any safety-of-life functions and does it need to meet SIL requirements? A pi in its standard form certainly does not meet any SIL requirements. Where is the board going to be mounted - will it be housed in a control panel, metal enclosure or would it be exposed? If it can be mounted in a good quality metal enclosure then perhaps some environmental issues could be alleviated. What sources of EMI are nearby? As you say there is risk from EMI causing issues - certainly on a 'naked' board and in a factory where there may be noise generated from large drives, contactors, switchgear etc. EMI would be a big issue. What software / OS will it run? - There are a number of options that could be used on a Pi - Rasbian, Ubuntu Mate, Ubuntu Snappy Core, Windows IoT Core, Risc OS. As is in the case of the netPi board highlighted above, a customised hardened platform could be used based on Yocto and Docker. I guess software selection again depends on a number of factors: What start up time is acceptable? - in some scenarios it may be left running for years. In the plant I work in, some of our machinery can take days to start up - which is acceptable as it is only taken down for overhaul every few years and start-up times are factored into machine startup planning - it is otherwise left running all the time. What I/O response time is required? Some machinery will require very quick sub second response times, other equipment may only need a response within a minute or more. What would be the consequences of software failure due to a bug in the code or even RAM errors? If the device is used purely for monitoring a non critical system then this may not be a problem, but if it could lead to a safety incident or machine damage then operational reliability may be really critical. What power supplies are available? How robust are they? At the plant I work at, there is lots of process control equipment - PLC's, DCS controllers, bespoke controllers etc. that are sensitive to power supply issues. For anything that is critical, quite often it will be fed with 2 supplies where one supply might be UPS backed. As you say though, batteries can and do fail and as you have pointed out improper shut downs can be an issue. How would the board be connected to other systems? Does it need to be networked, or can it accomplish it's function as a standalone device? If used for an IoT application then probably not, but if used to give a discrete output based on some other input such as analysing an image from a camera then it may not need network connectivity. If it is not connected via ethernet / WiFi then the risk of attack through the network is virtually eliminated. There is of course always the risk of attack if someone has physical access to the device. What type of storage is required? In the case of the Raspberry Pi Compute module it has an on board 4GB eMMC flash chip which I believe is MLC memory so should offer better reliability and lifetime than a standard pi. What is the required life-cycle time? It may be expected to last for the lifetime of the plant - which could be 20 years or more, or it may only be required for a short term monitoring application to collect some data on a machine to determine a specific problem or optimise a process. This may require something quick, cheap and with high flexibility. I have based the above points on what you have highlighted, but I am sure that many more factors could be listed here. You make a really great point that downtime, engineering custom interfaces, covering legals, ruggedizing, running updates, providing failsafes and providing adequate support could soon eat away any savings that would be made in the cost of the device alone. IMHO I don't believe a device like this should be completely written off for use in industry however - I think it really does depend on the application and considerations above. Certainly in some circumstances, it would be a definite DO NOT USE - especially if it will effect safety, but others uses in industry may fall into a grey area. Also with the likes of the netPi, myPi and other industrialised versions, some of the issues with using a standard Pi in an industrial environment are solved. Thanks again for your response - it has been very thought provoking reading through your response and replying! Cheers -------------------------------------------- Tony

tonydbeck · Answer

Some other really good points - thanks! RTOS's can certainly be very beneficial on an industrial platform. This is an area I would really love to learn more about as my knowledge on the use of an RTOS is very weak. Some of the equipment (VFD's, DCS controllers / IO cards, PLC's etc) where I work will have a published lifecycle from the vendor, which in some cases could be 15 to 20 years Siemens will even take an excel list of your existing installed equipment and provide you with a report on where each item is on its lifecycle. With this information it is possible to create a life cycling plan for the equipment in the plant. It is funny though, that some industrialised equipment is so reliable that it ends up in service well beyond its supported life cycle! We still use a number of Siemens S5 PLCs and Simovert P drives installed - but because they are so reliable, they are kept in place. In some cases the engineering effort to update can be huge, and with limited resource, other projects can take priority. I had thought of one more things - Use of a hardware watchdog. Cheers ------------------ Tony

mp2100 · Answer

Jan, I just read through the user manual, from the Siemens web site. It’s all about installation, and not much else. Are there instructions on using the IOT2000?

Jan Cumps · Answer

... and join Siemens’ forum . Next to questions, it also has how-to guides.

shabaz · Answer

I've been collaborating with a colleague to build up a Pi-based edge compute device. It is not complete yet, but we've put a high-level story on Medium about VIKI to try to reach non-tech people too. V.I.K.I. is short for Versatile Intelligent Controller for Industry : ) Circuit diagrams and any source code will be published, once we've constructed it and tested (main board PCB arrived today). Here's what it should look like (we stole Jan Cumps and balearicdynamics diagram style):

Jan Cumps · Answer

shabaz wrote: ... Feature requests: - the middle upper lid hinged and/or removable. With CAD drawings published so you can 3D-print your own - access for wiring top and bottom (like the one below that has these access breakouts on both sides of the housing and that makes wiring easy) : - certified for industry automotive army deep-see

shabaz · Answer

Hi Enrico! Agree : ) I'm struggling giving that up, but will try!