Revolution Pi I/O Configuration Manual
Introduction
This document describes how to set up an application to use the RevPi_Flat, RevPi_Compact,RevPi_Core and RevPi_Connect components, and how to set up the system to communicate correctly with the Revolution Pi hardware.
Set up the Revolution Pi
To be able to use a Revolution Pi device with CDP Studio, it must first be set up correctly. Make sure to create an initial configuration in piCtory:
- Set up the real-time configuration, as explained in Linux Realtime Configuration
- Log into the IP-Address of the Revolution pi device (http) and start piCtory.
- Drag in the correct Revolution Pi device and any attached modules so that the configuration in piCtory matches the physical configuration.
- Save the configuration as 'Start-config.'.
In the CDP Studio application, add a RevPi_Flat, RevPi_Compact, RevPi_Core or a RevPi_Connect, depending on the device at hand. For the RevPi_Connect or RevPi_Core, add any additional I/O modules to reflect the physical configuration. Set the fs to specify how often the I/Os should be updated.
Note: Make sure that the configuration in CDP Studio matches the configuration in piCtory!
Principle of Operation
When the executable starts running on the target, the application reads the stored configuration in the xml-files (generated by CDP Studio), and compares this with the information in the target configuration-file ("/etc/revpi/config.rsc") that the system driver 'PiControl' uses to update the data.
If there is a module mismatch, or anything goes wrong, an error is printed and the I/O component will not perform any I/O. The steps in Set up the Revolution Pi must then be executed to attempt to resolve the problem.
About
The RevPi_Flat, RevPi_Compact,RevPi_Core or RevPi_Connect components must run on one of the RevPi Core variants. For RevPi_Core and RevPi_Connect, one or more of the I/O modules RevPi DIO/RevPi DI/RevPi DO/RevPi AIO can be connected. See RevPi KUNBUS for more information.
Terms and Definitions
| RevPi Flat / Compact / Connect / Core / Core 3 / Core 3+ | Industrial arm-based controller based around the Raspberry Pi Compute module. |
| RevPi DIO | A physical Digital I/O module which can be connected to RevPi Core, 14 digital inputs and 14 digital outputs, 24VDC. |
| RevPi DI | A physical Digital Input module which can be connected to RevPi Core, 16 digital inputs, 24VDC. |
| RevPi DO | A physical Digital Output module which can be connected to RevPi Core, 16 digital outputs, 24VDC. |
| RevPi AIO | A physical Analog I/O module which can be connected to RevPi Core, 2 analog outputs, 4 analog inputs and 2 temperature inputs for RTDs. |
Revpi_Core, Revpi_Connect Component Configurations
The RevPi_Core and the RevPi Connect components are essentially the same except for some minor differences that are hidden from the end-user.
Note: The RevPi_Core component handles all the different variations of RevPi Core / Core 3 and Core 3+.
Configuration elements
| Name | Description |
|---|---|
| RevPi_Core, RevPi_Connect, RevPi_Flat, RevPi_Compact | The IOServers that convert CDP Signals into data written to RevPi outputs, and from RevPi inputs to CDP Signals. |
| DIO | A configuration module that can be dragged into the RevolutionPiIOServer component, automatically adding CDP channels corresponding to Inputs and Outputs found on the physical RevPi DIO module. |
| DI | A configuration module that can be dragged into the RevolutionPiIOServer component, automatically adding CDP channels corresponding to Inputs on the physical RevPi DI module. |
| DO | A configuration module that can be dragged into the RevolutionPiIOServer component, automatically adding CDP channels corresponding to Outputs found on the physical RevPi DO module. |
| AIO | A configuration module that can be dragged into the RevolutionPiIOServer component, automatically adding CDP channels corresponding to Inputs and Outputs found on the physical RevPi AIO module. |
Note: DIO/DI/DO/AIO should be dragged/added into RevPi_Core or RevPi_Connect in the same sequence as they are stacked together physically.
When clicking into IOModules (DIO/DI/DO/AIO), the following configurations are found:
The Channel table lists all CDP channels corresponding to values found in the physical module. Some of the channel attributes can be edited/configured, but most settings are already configured.
| Name | Description |
|---|---|
| Export | If set, the channel will be updated (values will be read/written). If not set, the channel's configuration is sent to the RevPi driver and used there, but not updated. Note: Channels with Export set to 0 are ignored / not updated! |
| Input | In I/O Servers, When Input=1, The input value is retrieved from the CDP side and then written to the physical output. When Input=0, the value is read from the physical input and written to the value on the CDP side. |
| Routing | Can be configured on channels which have Input=1. The Routing is a dot-separated name string, like applicationname.componentname...signalname. The value that the routing refers to is put into this Channel just before each run. |
The Properties table lists all properties for this physical module. Some of the channel attributes can be edited/configured, but most settings are already configured.
| Name | Description |
|---|---|
| Position | Physical module position, Right or Left, relative to the RevPi_Core or RevPi_Connect (Position should have same value for all IOModules) |
Configuration procedure
To start configuring the IOServer it must be added to your application in configure mode. See Revolution Pi Setup Guide for tutorial.
Note: The application must use the Raspbian Toolkit
The following must typically be done to the added RevPi_Core or RevPi_Connect component to configure the i/o server:
- Add in one or more DIO/DI/DO/AIO elements, in the same order as they are physically stacked on the RevPi Core.
- The property Position must be set correctly on all IOModules, to the same value (Right/Left). If the modules are placed to the right, select 'Right', else select 'Left'.
- The Routing property should be set on all channels that have Input checked (physical outputs), and that you want to be updated with values from somewhere in the system.
Get started with CDP Studio today
Let us help you take your great ideas and turn them into the products your customer will love.