o2it12017 [A Practical Gude for Connecting LabVIEW tothe Industal oT - National Instuments ‘A Practical Guide for Connecting LabVIEW to the Industrial loT Overview In this white paper, learn about the three most prevalent communication protocols to connect to cloud-based development platforms for Internet of Things (IoT) applications, You can also find information on some of the most common oT cloud development platforms such as Amazon Web Services, IBM Bluemix, PTC ThingWorx, and Microsoft Azure. Plus, lean how t connect an NI embedded system, such as CompactRIO, to these cloud platforms through the LabVIEW open graphical development environment Table of Contents 4. The loT Will Change the World 2.MQTT 3. AMQP 4, DDS '5, Amazon AWS oT 6. IBM Watson loT for Bluemix 7. PTC ThingWorx 8 Microsoft Azure loT Suite 41. Tho oT Will Change the World The world economy will greatly change in the next decade as new Internet-enabled applications are rolled out. Some of these applications are likely to be disruptive and innovative as well as have a large economic impact. This will affect, ‘many industries and sectors, as already seen in consumer sectors ike hatels (Airbno) and taxis (Uber). This trend is also noticeable in the industry for example, Germany's Industry 4.0 initiative. Within Industry 4.0 or the Industral loT (lloT), the focus is on integration and better use of existing technologies. In this sense, industry, machines products, and people are all digitally connected. Manufacturers are mass producing bespoke products in quantities of ‘one, Inteligent software in the cloud connects enterprise IT systems with the operational world, machines, devices, and ‘sensors to control and optimize production flow: 2 [Sie = | Figure 1 Common Architecture of the Industrial loT:Inteligent Edge Nodes Connect Sensors, Actuators and Devices tolT Systems Because of the decrease in cost of connectivity, processing devices and sensors adoption of IloT has grown tremendously. Sensor data can be captured and preprocessed close to the machines by a smart edge device such as a CompactRI0 or a PXI automated test system. The edge device can send the data in real time to the virtual world (IT cloud platform) where it can be stored, monitored, and analyzed or trigger an action ‘The value of the loT is not in the connectivity ofthe devices, but in what a company unlocks from the stream of data the smart devices supply. Cloud computing platforms and their services help provide this insight, ‘Many significant challenges need to be taken into account when implementing an IoT solution, Challenges such as standardization, interoperabilty, Big Analog Data™ handling, security, and privacy. Itis important to be aware of these challenges and give special care to security. Security is a crucial component for any IoT application. lloT devices should enforce a strong security policy and be updated regularly withthe latest security patches. To leam more about best practices for security on CompactRIO and receive the latest security announcements from NI, visit ni.com/supportisecurity (http:/hvww.ni.com/support/securiy). All cloud computing platforms securely send and receive data, use strong authentication and authorization methods, and use encryption. The majority also have audit capabilities. Cloud Computing Cloud computing refers to a flexible way of delivering hardware, software, or data resources via the network on a user's request. This is opposite to the use of running a software application on a local computer. hntp:wwwn.comivhite-paperis3954/en! aoart12017 ‘A Practical Gude for Connecting LabVIEW tothe Indusval oT - National Instuments a& Application Bo « Platform D — a>hs% OB onic sorage runtime otabase Infrastructure a2 2 Cloud computing Figure 2 - Overview of Cloud Computing Elements (image source: Sam Johnston https:ficommons. wikimedia orgiwiklFile:Cloud_computing.svg) ‘The table below shows three service levels of cloud computing that are commonly encountered, SaaS —_| Software as a Service Provides a full business service. The service provider runs and manages the complete platform. Examples: Gmail, Salesforce.com PaaS _| Platformas a Service Provides a platform. You need to build and deploy your own cloud applic ation, leveraging the run time and services the vendor provides. Examp! es: IBM Bluemix, Microsoft Azure, AWS loT laaS | Infrastructure as a Service _| Provides the basic building blocks such as server hardware, storage, an ‘d network capabilities. You may need to instal the OS and applications. Examples: Amazon £C2 (a virtual machine that Amazon provides to yo Uy), IBM SoftLayer Clouds can be deployed as public—all services run in @ secure environment hosted in the cloud, where servers may be shared with others—or private, which is available only to the user's organization and may exist on or off premises. In ‘addition, clouds can be deployed as hybrids, where parts are on premises and other services are in the cloud. loT Application Protocols ‘Communication protocols are responsible for the network connectivity to the server. Protocols like Wi-Fi, Ethernet, cellular, and LoRaWAN are all communication protocols that provide this level of connectivity. Application protocols sit on top of them to communicate application-specific messages. Multiple standards handle the communication between devices and the cloud. As application requirements diffe, specific loT protocols have been developed and therefore the confusion is understandable. Protocols may even have multiple Implementations and loT platforms may have proprietary loT solutions. To provide a universal solution, devices, applications, and platforms need to be interoperable. NI embedded systems provide an excellent solution by being open and flexible. This is achieved through the NI Linux Real-Time OS, suppor for LabVIEW graphical and Eclipse C programming environments, as well as several Linux packages available through the vibrant ecosystem, Ata high level, there are three main use cases for the application protocols: device to device (D2D or M2M), device to ‘server (D2S), and server to server (S2S) communication, loT application protocols have different levels of real-time behavior and other characterstics. The table below provides an overview. ‘Common Application Protocols for loT Connectivity HTTPIHTTPS | WebSocket Dos Mart ‘AMP htpslwwo.n.comivhite-paperis3954ien anoart12017 [A Practical Gude for Connecting LabVIEW to the Indusval oT - National Instuments Description | Transmit data ove | Transmit data ove | Communication b | Lightweight protoc | Queue system to ‘Internet from ap |r internet from ap |us to connect intel | o! for collecting da | reliably transfer m plications, website | plications, website | igent machines | ta and publishing | essages between S.andsoon |8,and-so.on {to sorvers ands. applications and p ubseribers rocesses (server 3) typical Use Cas | Web Web 20 pas 828, (028) ° Real-Time Behav | No No ‘Yes, us-ms range |No, ms-srange | No, seconds rang ior ° Messaging | Request/Respons | RequestRespons | Databus PublishSubseribe | Publsh/Subseribe transport Top top oP, UDR, shared | TCP Top memory, and 80.0 Security Yes: HTTPS (SSL | Yes: wssi (SSUT | Yes Possible: SSL or | Yes: TLS or SASL orTLs) Ls) ms (Simple authentic ation and Security layer) LabVIEW Suppor Yes, native _|Yes, via VI Packa |Yes, via VI Packa | Yes, implemertat! | Implementations ie ge Manager (Medi | ge Manager (RTI) | ons on VI Packag | on VI Package M aMongrels) © Manager, LabVI | anager (LabbitM EW Tools Networ | Q) and GitHub and GitHub Quality of Servi Yes, over 20 level Yes, 3 levels = No I" The next section describes the most common protocols, MATT, AMQP and DDS, in further deta, 2.marr Message Queueing Telemetry Transport (MQTT) is an loT connectvity protocol. MATT is used in applications with thousands of sensors, including power usage monitoring and oil pipeline monitoring. MQTT is efficient in terms of bandwidth, battery, and resources. MATT uses a publish/subscribe model. The loT devices publish data to an MOTT broker over TCP as a topic. An authorized client can subscribe to any topic and receive the value from the broker as they arrive from the publisher. The publisher (device) does not need to know about any of the subscribers, which makes the management easier at the device level. The broker can support multiple concurrent connections from many devices. Atopic is a simple string that can have hierarchical levels and supports also wildcards. An example of atopic is GothamCityPlan¥Building /Pump7/Power. The message data is transmitted in JSON format and may be specific to the cloud platforms’ loT service, MQTT ~ Message Queue Telemetry Transport MOTT pubishers MOTT broker MOTT subscribers Eanes I ottadinnd = * ih = la Ti g soap ae Figure 3 — Edge Devices Sent MATT Messages over the Internet to a Central Broker Which Distributes the Messages to Authorized Subseribers MATT supports three qualty-of-service levels: + QoS 0—At most once + QoS 1—At least once + QoS 2—Exactly once htpslwwo.n.comivhite-paperis3954ien an