Introduction: Connect Your RevPi Core + RevPi DIO to Ubidots

About: Community manager @Ubidots, a startup empowering makers and hardware engineers to create applications for the Internet of Things #IoT

Revolution Pi is an open, modular, and durable industrial PC based on the established Raspberry Pi while meeting the EN61131-2 standard. Equipped with the Raspberry Pi Compute Module, the RevPi Core base can be expanded seamlessly using appropriate I/O modules and fieldbus gateways for energy management, process monitoring, machine health and more.

The Rev Pi Core is the foundation to any application and depending on your I/O requirements expansion modules such as RevPi DIO, RevPi AIO, RevPi Gates can be attached as digital, analog, or gateway modules.

In this tutorial we detail the integration of a the RevPI DIO to visualize and control output signals to your machines or applications with Ubidots. The RevPi DIO digital I/O module comes with 14 digital inputs and 14 outputs, PWM (puls width modulation), and counter inputs. For a detailed list of functionalities for the RevPI DIO, check out the Revolution Pi product brochure.

Step 1: Requirements

Step 2: Hardware Setup

As per any new device setup, we recommend becoming familiar with the RevPi Core + RevPi DIO official quick start guide by Revolution Pi. Then be sure your to assemble the RevPi Core + DIO correctly referencing the below articles for additional details, as needed.

Once your RevPi Core + RevPi DIO are configured, powered correctly, and connected to the Internet, we can continue with Firmware uploads.

Step 3: Firmware Setup

1. First we must have access to the inputs and outputs of the Revolution Pi. The "python3-revpimodio” module provides all access to the IOs of the Revolution Pis, and can be programmed very easy with Python3.

Based on the image installed in your RevPi Core reference this guide to make the installation properly. If you have the Jessie Image on your core, simply install the module from the Kunbus repository running the commands below in the RevPi Terminal:

  • Update system packages: sudo apt-get update
  • Install: sudo apt-get install python3-revpimodio2
  • Update Distribution (all): sudo apt-get dist-upgrade

2. Next, install the requests module for python3 by running the command below in the RevPi Core terminal:

sudo apt-get install python3-requests

3. Once each of the commands above have finished, verify everything as accurate by opening Python3 into your RevPi Core terminal and importing the module previously installed. Open the Python3 by running the command below into the RevPi Core terminal:

python3

Once you have access to Python3, import the modules ''revpimodio2" and "requests" as is shown below:

import revpimodio2

import requests

If receive and error messages after importing the module, verify the issue shown and try again.

Step 4: PiCtory Setup

PiCtory lets you link up several RevPi modules, alongside the PiBridge that physically links the modules with one another, creating a configuration file. The file has to inform to your RevPi Core which modules are to be found in which position and which basic settings that the modules have. To get a better idea how it's work check out this video.

1. Open your web browser and enter the IP address of your RevPi Cores in the address bar of your browser. Then, you will see the login windows, to enter assign the username and password where is indicated. The login credentials can be found on the side of your RevPi.

  • username: admin
  • password: You will find it on the sticker on the side of your RevPi Core.

Then, enter to the "APPS" section.

2. To start with the PiCtory settings, press the green button called "START".

3. From the device catalog select the version of your RevPi Core and assign it to the configuration boards. Then, assign the RevPi DIO at the right of the RevPi Core. Remember connect the RevPi Core to the right of your RevPi Core using the PiBridge.

IMPORTANT NOTE: The position of the modules assigned in the PiCtory configuration have to be the same assigned in the physical world to be able to generate the configuration file properly.

3. Now that you have the modules needed assigned into the configuration boards, lets verify the name of the pins that we are going to use below. You will find two sample codes provided, one is for send a value from a reading input of the RevPi DIO, and the other one is for control an output of the RevPi DIO.

  • The input that we are going to use is the Input 1, see above for pin-out diagram.

From the Value Editor section, verify if the name assigned for the Input 1 is "I_1" as is shown on the image below, if not please assign it. If you skip this step the firmware code will miss reading this pin.

  • The output that we are going to use is the Output 1, see above for pin-out diagram.

From the Value Editor section, verify the name assigned to Output 1 is "O_1" as is shown on the image below, if not please assign it. If you skip this step the firmware code will miss this output and you will not be able to relay controls.

Step 5: Sending Data to Ubidots

1. To begin writing your firmware, create a Python script in the RevPi Core terminal. We are going to use nano editor, in order to create the new script. To do this run the command below:

nano ubidots_revpi.py

As you will see, the nano editor terminal will automatically populate and you can begin your code.

2. Copy and Paste the sample code below into the nano editor. Once pasted, assign your Ubidots Token where indicated in the script. Reference here for help locating your Ubidots token.

In this sample code we are going to read the Input 1 (I_1) of the RevPi DIO module to send its status to Ubidots cloud to be able to monitor and establish alarms based off its data values received.

NOTE: To save the script into the nano editor - press Ctrl+o, confirm the file name to write (ubidots_revpi_di.py) and press enter. To close the nano editor press Ctrl+x.

3. Now let's test the script. Run the script previously created in the RevPi terminal:

python3 ubidots_revpi_di.py

Once the script begins to run, you will see the successful status code response from the Ubidots Server.

4. Go to your Ubidots account and verify the data has been received. You will see a new device automatically created in the Device section with the device name being the MAC address of your RevPi Core. Keep reading for name changes.

Don't like the MAC address as your device's name in your Ubidots display? Don't worry! You can change the name to a more friendly one, but the device label will be stay as the MAC address to never get confused which device is which. Reference to Ubidots Help Center for more on Device Labels and Device Name changes in Ubidots.

Click on any device in your Device section to visualize the variable being recorded and sent to Ubidots from our sample firmware. As you can see, our sample code has provided a motion-detector variable.

Step 6: Unit Counter Application Development

Now that the status of your Input is updating in your Ubidots account. Let's start playing with the Ubidots features to design and deploy your application. In this tutorial we will deploy a Unit Counter for boxes moving across a supply line

At first, we are going to create a rolling windows variable which let us compute the average, maximum, minimum, sum, and count of other variable; in this case the variable previously created (motion-detector). For this guide, we are going to compute a sum of the variable motion-detector every minute to know how many boxes were detected as they passes along the supply line.

To create the variable, press "Add Variable". Then, select "Rolling Window":

Now select device created > motion-detector > sum > every 1 minute to finish press save. Then assign the name desired by you, in this case, we named ours "boxes".

Now that we know how many boxes our sensor is detecting, we can create an event based on the "boxes" variable to keep pace with production and be alerted if production falls behind.

Our production goal is 10 "boxes" a minute. In order to maintain this goal, the RevPi will need to detect 10 boxes minimum per minute. To be alerted to falling production we will simply create an alert letting us know when less than 10 boxes were detected.

Go to the Event section of your Ubidots account and press "Add Event". Then, select the device and the variable, and assign the condition of the event. In this case, if the variable boxes is less than 10 set the event. Now that the parameters of your event are configured, assign the action that you desire. I configured the event with an e-mail action. And as you can see above, when the event is triggered I receive the message above.

IMPORTANT NOTE: The code provided above is only reading the input 1 without establishing any sensor configuration. Based on the sensors used, add the configuration of the sensor into the code as needed.

Step 7: Receiving Data From Ubidots

In this sample application we are going to control an output of the RevPi DIO module to be able to turn ON/OFF a light from the Ubidots cloud.

1. To be able to control an output form an Ubidots variable you have to create it first the variable. Enter your RevPi device and create a new variable by selecting "Add Variable" and press "Default". Then, assign it the name "light". Once the device is properly created.

2. Go to your main Ubidots Dashboard and create a control widget. Click the yellow plus(+) icon and follow the on screen options to deploy new dashboard widgets. Select Control > Switch > RevPICore(MACAddress) > light (variable just created) > Finish. After constructing your new widget, the Dashboard will reload and be populated with your new light control widget.

This "control" widget will send its status to the RevPi DIO output to control the status of a light or any other device connected to Output 1.

3. Create a new python script using nano editor. To do this run the command below in the RevPi terminal:

nano ubidots_revpi_do.py

4. Please copy and paste this sample code into the nano editor. Once pasted, assign your Ubidots Token where indicated in the script. Reference here for help locating your Ubidots token.

In this sample code we are going to control an output of the RevPi DIO module to be able to turn ON/OFF a light from the Ubidots cloud.

NOTE: To save the script into the nano editor - press Ctrl+o, confirm the file name to write (ubidots_revpi_di.py) and press enter. To close the nano editor press Ctrl+x.

5. Now let's test the script. Run the script previously created in the RevPi terminal:

python3 ubidots_revpi_do.py

Once the script begins to run, you will see the light status message.

6. Now change the status of the "Control" widget from your Ubidots Dashboard and visualize the status of the RevPI DIO output.

Step 8: Results

In just a few minutes you've integrated the RevPi Core + RevPi DIO with
Ubidots, received data from your supply line for unit count, built an application to track and alert you to production requirements, and control the lights of your factory floor - all by using the RevPi Core + DIO with Ubidots. To learn more or deploy new Industrial solutions for monitoring or management, check out the full lineup of RevPi expansion modules.