Product Description #

The RevPi Connect 5 is a 24 V industrial PC for IIoT and automation projects based on the Raspberry Pi Compute Module 5. The RevPi is a base module from the Revolution Pi product family. All devices in the Revolution Pi product family are developed in accordance with EN 61131-2.

Components #

revpi-connect-5-aufbau
Note

The components of the RevPi may vary depending on the variant.
Position Component Application

1

X2 RS485[1]

RS485 Serial interface

X2 CAN[1]

CAN interfaces

2

6 × status LED

RevPiLED

3

2 × RJ45 Ethernet

RJ45 Ethernet interfaces

4

2 × USB A 3.2 Gen 1

USB interfaces

5

RP-SMA[1]

WLAN and BT

6

USB-C

Save image / Reinstall image

7

X3 CAN[1]

CAN interfaces

8

X4 PWR

Connecting the Power Supply

9

2 × locking clip

Mounting the Device on a DIN Rail

10

Ventilation Slots

Mounting the Device on a DIN Rail

11

2 × PiBridge

Connecting Expansion Modules

12

X1 HDMI

Setting up Desktop Mode

Variants #

Item no: RAM eMMC Memory WLAN BT RS485 CAN

100412

4 GB

32 GB

–

✔

–

100413

4 GB

32 GB

✔

✔

–

100414

4 GB

32 GB

–

✔

✔

100415

4 GB

32 GB

✔

✔

✔

100416

8 GB

32 GB

–

✔

–

100417

8 GB

32 GB

✔

✔

–

100418

8 GB

32 GB

–

✔

✔

100419

8 GB

32 GB

✔

✔

✔

100420

8 GB

32 GB

✔

–

✔ (2 ×)

For available variants see Revolution Pi Shop.

Compatibility #

The RevPi Connect 5 base module can be expanded by up to 10 expansion modules to create a Revolution Pi system:

Left side Base module Right side

5 × RevPi I/O module or
1 × RevPi Gateway + 4 × RevPi I/O module

RevPi Connect 5

5 × RevPi I/O module or
1 × RevPi Gateway + 4 × RevPi I/O module

RevPi I/O Modules #

RevPi Gateways #

RevPi Gateways can only be connected to the far right or far left of the system via a PiBridge plug connector.

  • RevPi Gate PROFINET

  • RevPi Gate EtherNet/IP

  • RevPi Gate EtherCAT

  • RevPi Gate PROFIBUS

See RevPi Gateways

Virtual Devices #

The Virtual Devices are delivered as components in PiCtory:

Operating System Images #

The RevPi Connect 5 is compatible with:

Scope of Delivery #

The scope of delivery includes

  • RevPi Connect 5 (base module)

  • X2 connector RS485 or CAN, see Variants

  • X3 connector CAN, see Variants

  • X4 connector PWR

  • 2 × blind plug for PiBridge

  • Product insert

Mounting and Connecting #

The RevPi was developed for use in a control cabinet. Observe the specifications for Intended Use and all Safety Instructions.

Warning
Danger to life due to electrical shock

There is a risk of fatal electrical shock when working on devices in the switch cabinet with 230 V mains voltage.

▷ Operations in the switch cabinet may only be carried out by qualified electricians.

▷ Before carrying out any operations in the switch cabinet, switch off the power supply properly.
Caution
Damage to the device due to overheating

The ambient temperature in the switch cabinet must not exceed the maximum permissible operating temperature.

▷ Keep ventilation slots clear.

▷ Observe the installation clearances.

▷ Mount the device in the intended orientation.

▷ Do not place appliances with high input power directly next to each other.

▷ Regularly remove dust and dirt from the area around the appliance.

Carry out mounting and connection in the following order:

  1. Mount the RevPi base module and all expansion modules on a DIN rail.

  2. Connect all expansion modules via PiBridge plug connector.

  3. Connect all other devices such as sensors and actuators. The interfaces available to you for this can be found in the section Components.

  4. Connect a monitor and a keyboard if you want to operate the RevPi in the desktop mode. This is not necessary if you have a network connection to access the RevPi.

  5. Finally, connect the power supply.

Access to the Device #

The RevPi is accessed in two steps:

  1. Establishing a Network Connection.

  2. Login on the device.

Install all available updates as soon as the RevPi is connected to the internet. This ensures that the system is always up to date with security-relevant features.

See also:

Alternatively, access is possible without a network, see Setting up Desktop Mode.

Configuration #

The RevPi is configured in two steps:

  1. As of RevPi Bookworm (10/2024) you configure the RevPi base module via the application Cockpit.

  2. You configure the Revolution Pi system, i.e. a RevPi base module with expansion modules, using the application PiCtory or, if applicable, directly in your development environment, e.g. via CODESYS.

Note

CODESYS and PiCtory cannot be used in parallel for configuration. An existing configuration via PiCtory will be overwritten by a configuration via CODESYS.

The virtual devices OPC UA Server and MQTT Client can only be used via PiCtory.

Parameterization #

The following parameters, inputs (INP) and outputs (OUT) can be configured:

RevPiStatus (INP) #

Uses bits to represent different states of the piControl driver.

Bit Function

0

piControl driver is running.

1

At least one connected I/O module has not been configured.

2

At least one I/O module has been configured but not connected. The bit is also set if a RevPi Gateway has been configured.

3

An I/O module occupies more or fewer bytes in the process image than specified in the configuration.
This means that the version of the configuration file or the device description files used does not match the firmware in the I/O module.
See also: Updating Firmware.

4

A RevPi Gateway is connected to the left side of the RevPi.

5

A RevPi Gateway is connected to the right side of the RevPi.

6

The limit value of the first error counter RS485ErrorLimit1 has been reached.

RevPiIOCycle (INP) #

Displays the cycle time of the PiBridge communication between the base module and expansion modules in milliseconds (ms) as an integer value.

RS485ErrorCnt (INP) #

Counts the errors in the communication with the RevPi I/O modules and outputs their number as an integer value.

Core_Temperature (INP) #

Displays the CPU temperature as an integer value in degrees Celsius (°C).

Core_Frequency (INP) #

Displays the CPU frequency in MHz / 10, e.g. 2400 MHz = value 240.

RS485ErrorLimit1 (OUT) and RS485ErrorLimit2 (OUT) #

RS485ErrorLimit1 and RS485ErrorLimit2 serve as threshold values for error handling in the communication between the RevPi device and the I/O modules.

At the end of each communication cycle, the error counter RS485ErrorCnt is compared with these two limit values:

  • RS485ErrorLimit1: When this value is reached, a message is generated in the log file kern.log. In future piControl versions, the default values defined in PiCtory will also be written to the process image.

  • RS485ErrorLimit2: If the error counter reaches this value, PiBridge communication is terminated completely.

Note

The communication via the serial interface RS485 to the outside is not affected, only the internal PiBridge data traffic.

The respective check is deactivated by setting the corresponding value to 0. If, for example, RS485ErrorLimit1 is set to 0, no warning messages are generated in kern.log.

The default values are:

  • RS485ErrorLimit1: 10

  • RS485ErrorLimit2: 1000

These values offer a good balance between fault tolerance and system stability for most applications.

RevPiLED (OUT) #

The freely programmable LEDs can be controlled via RevPiLED, see Configuring LEDs.

Bit Component Status information

2:0
5:3
8:6
11:9
15:12

LED A1
LED A2
LED A3
LED A4
LED A5

000 = off
001 = red
010 = green
100 = blue
011 = orange
110 = cyan
101 = magenta
111 = white

RS485 Serial Interface #

Serial devices such as sensors can be connected to the RevPi via the potential-free RS485 interface on the X2 connector. The socket has differential data line terminals for P (positive) and N (negative), which may also be designated D/D- or A/B.

The RS485 interface is not available for the product variant with X2 CAN, see variants.

RS485 Connection via X2 Connector

▷ Make sure that all devices are disconnected from their power supplies.

▷ Connect the positive data line to pin P of the X2 connector.

▷ Connect the negative data line to pin N of the X2 connector.

▷ Connect the Ground (GND) pins to the RS485 ground.

▷ Connect the power supply.

revpi-connect-5-x2-rs485-pinout

Configuring the RS485 Interface

Under Linux, the interface can be addressed via the device driver node with :

  • /dev/ttyRS485-0

  • to RevPi Bullseye (4/2024): /dev/ttyRS485

▷ Log in to the RevPi via a terminal.

▷ Use ls /dev/ttyRS485-0 to check whether the RS485 interface is available.

Activating Termination Resistor

✓ The integrated 120 Ω terminating resistor of the RS485 interface is switched off after a restart.

▷ Log in to the RevPi via a terminal.

▷ Check out the Git repository of the command line tool rs485_config from GitLab with the command:

git clone https://gitlab.com/revolutionpi/rs485_config.git

▷ Build the tool with the command:

cd rs485_config; make

▷ Activate the resistor with the command:

./rs485_config <SERDEV> --set-bus-term

Replace <SERDEV> with the name of the interface, e.g. /dev/ttyRS485.

▷ Check whether the resistor has been activated and display the settings of the RS485 interface with the command:

./rs485_config <SERDEV>

❯❯ If the resistor is activated, Bus termination: Yes is output.

See also:

CAN Interfaces #

Depending on the variant, the RevPi has one potential-free CAN interface on the X3 connector (2) or a second one on the X2 connector (1).

revpi-connect-5-2-can

The CAN FD Controller MCP251863 is used as the CAN transceiver.

CAN Connection via X3 or X2 Connector

▷ Make sure that all devices are disconnected from their power supplies.

▷ Connect the CAN H bus to pin H (High) of the connector.

▷ Connect the CAN L bus to pin L (Low) of the connector.

▷ Connect the Ground (GND) pins to the CAN ground.

▷ Connect the power supply.

revpi-connect-5-x3-can-pinout

Configuring CAN Interfaces

Under Linux, the interfaces can be addressed with:

  • X3 CAN: can0

  • X2 CAN: can1

▷ Log in to the RevPi via a Terminal.

▷ Query the status of the interfaces with:

ip link show

▷ For example, activate can0 and set the bit rate to 500,000 baud (500 kBit/s) with the command:

sudo ip link set can0 up type can bitrate 500000

▷ Activate the 120 ohm termination with the command:

sudo ip link set dev can0 type can termination 120

These two possible operating modes are supported:

Mixed CAN 2.0B and FD mode CAN mode CAN 2.0B mode

Simultaneous operation of classic CAN messages (CAN 2.0B) and CAN FD messages (Flexible Data Rate) on the same bus

Communication exclusively via classic CAN protocol (CAN 2.0B)

User data of up to 64 bytes and higher bit rates for the data part (up to approx. 8 Mbit/s)

Messages only with 11-bit or 29-bit IDs. Data rates and user data lengths limited to CAN 2.0B

Compatible for networks with mixed requirements

Greater interoperability and stability with older control units

RJ45 Ethernet Interfaces #

The RevPi can be connected to a network via the RJ45 interface.

Two Gbit Ethernet connections are available on the RevPi, which are independent of each other. This allows the RevPi to be integrated into two different networks. The MAC addresses are printed on the front of the housing. Under Linux, the interfaces can be addressed via:

  • Socket A: eth0

  • Socket B: eth1

WLAN and BT #

WLAN Interface

✓ RevPi base module with WLAN interface

✓ DHCP-enabled WLAN router

▷ Use ip link to check whether a Wi-Fi interface is available.
In Linux, the Wi-Fi interface is displayed as wlan0, provided that no other Wi-Fi device is available.

▷ Activate the WLAN interface via Cockpit[2].

▷ Set up the WLAN connection via NetworkManager.

BT Interface

A BT interface[3] is available from standard 5.0.
▷ Activate BT via Cockpit in order to connect Bluetooth peripheral devices such as keyboards or audio devices to the RevPi.

See also:

USB Interfaces #

The RevPi has two USB A 3.2 Gen 1 interfaces. The maximum output current per USB interface is 900 mA and is only guaranteed if the RevPi is supplied with 24 V DC -15 % / 20 %.

In the event of an overload, the power is switched off at the corresponding USB interface.

Date and Time / Real Time Clock (RTC) #

The RevPi is equipped with the Real Time Clock NPX PCF2131. If no power supply is connected to the RevPi, the RTC is supplied with power via a backup battery. The lithium battery has a service life of approx. 10 years.

The system time and the RTC are synchronized with an NTP server via the systemd-timesyncd service. Synchronization can be deactivated in Cockpit, for example, in which case the system time is set by the RTC.

Configuring System Time

The command line tool timedatectl can be used to query and change the current system time, the RTC and the configured time zone.

▷ Log in to the RevPi via a terminal.

▷ Check the current settings with the command:

sudo timedatectl status

▷ Set the RTC to the coordinated universal time UTC with the command:

sudo timedatectl set-local-rtc 0

▷ Set the RTC to a local time zone (e.g. UTC01:00) with the command:

sudo timedatectl set-local-rtc 1

▷ To configure your own system time, deactivate NTP synchronization with the command:

timedatectl set-ntp false

▷ Then redefine the system time with the command:

timedatectl set-time "YYYY-MM-DD HH:MM:SS"

Configuring RTC without NTP Synchronization

The RTC can be set directly using the command line tool hwclock . NTP synchronization must be deactivated for this, as otherwise a synchronized system time will overwrite the set RTC again.

▷ Log in to the RevPi via a terminal.

▷ Deactivate NTP synchronization with the command:

timedatectl set-ntp false

Alternatively, you can deactivate synchronization in Cockpit via the setting Set clock from NTP server .

▷ Check the current settings with the command:

sudo hwclock

▷ Synchronize the system time with the RTC using the command:

sudo hwclock --systohc

▷ Set the RTC to its own time with the command:

sudo hwclock --set --date "dd mmm yyyy HH:MM"

Changing Battery

The lithium battery cannot be replaced by the customer. In this case, contact the customer service at support@kunbus.com.

Trusted Platform Module (TPM) #

The RevPi is equipped with an Infineon OPTIGA™ TPM SLB 9670 Trusted Platform Module. It fulfills the requirements of TPM 2.0.

Under Linux you can address the module with /dev/tpm0.

Watchdog #

A watchdog is a timer that restarts the RevPi after 60 seconds. To prevent this from happening, the watchdog must be reset regularly as long as the system is running without errors. In the event of an error, such as a crash of the application process, there is no reset and the watchdog triggers a restart of the RevPi.

The RevPi has two independent watchdogs. There are various ways to use a watchdog under Linux. Revolution Pi and Raspbian Pi use the system manager systemd.

Integrated Watchdog

The watchdog integrated on the processor behaves like other watchdogs under Linux and can be addressed with:

  • /dev/watchdog0

  • /dev/watchdog (as standard watchdog)

External Watchdog

A second watchdog is available via the RTC module and can be addressed under Linux with:

  • /dev/watchdog1

See also:

Technical Data #

Item No.: 100412, 100413, 100414, 100415, 100416, 100417, 100418, 100419, 100420

Housing dimensions (H × W × D)

96 × 45 × 115 mm (incl. RP-SMA socket)

Housing type

DIN rail housing for TH35 according toDIN EN 60715

Housing material

Polycarbonate

Weight

Approx. 290 g (incl. connectors)

Protection class

IP20

Power supply

Typ. 24 V DC (10.8 … 28.8 V DC)[4]

Maximum power consumption

22 W (incl. 2 × 900 mA USB load)[5]

Approved operating temperature

-25 … +60 °C[6]

Approved storage temperature

-40 … +85 °C

Max. relative humidity (at 40 °C)

93 % (non-condensing)

Interfaces

  • 0 / 1 × RS485 (see Variants)

  • 0 / 1 / 2 × CAN (see Variants)

  • 2 × RJ45 Gbit Ethernet

  • 1 × RP-SMA socket for WLAN + BT (see Variants)

  • 2 × USB A 3.2 Gen 1

  • 1 × USB-C (solely for image transfer to eMMC)

  • 1 × Micro-HDMI 2.0a (4K)

  • 2 × PiBridge (connectors at the left and right side)

Connectors

  • 1 × 4-pole screw-type terminal (X2 connector) for RS485 (see Variants)

  • 1 × 4-pole screw-type terminal (X2 and X3 connector) for CAN (see Variants)

  • 1 × 4-pole screw-type terminal (X4 connector) for power supply

Processor

Broadcom BCM2712, quad-core Arm Cortex-A76

Clock rate

2.4 GHz

Processor cooling

Passive with heat sink

RAM

4 / 8 GB LPDDR4 (see Variants)

Flash memory

32 GB

Trusted Platform Module

TPM 2.0 Infineon OPTIGA™ TPM SLB 9670

RS485

  • Data rate: max. 921 600 baud

  • Electrically isolated

  • Termination resistor controllable via software

CAN

  • Data rate: CAN FD 5 Mbps max., CAN 2.0 1 Mbps max.

  • Modes: mixed CAN 2.0B and CAN FD mode, CAN 2.0B mode

  • Electrically isolated

  • Termination resistor controllable via software

WLAN / BT

2.4 GHz, 5.0 GHz IEEE 802.11 b/g/n/ac wireless; BT 5.0, BLE (see Variants)

Hardware Watchdog

Watchdog in RTC device, freely configurable watchdog character device

Compatible RevPi Modules

  • All RevPi I/O modules, RevPi gateways, and the RevPi Ethernet-Adapter can be connected via the PiBridge system bus.

  • Up to 5 modules can be connected to both the left and right side of the device.

EMC interference emission

According to IEC 61000-6-4, emission standard for industrial environments

EMC immunity

According to IEC 61000-6-2, immunity standard for industrial environments

RTC buffer

CR2032 lithium battery, lifetime approx. 10 years

Optical display

6 status LEDs; 5 × red/green/blue, freely programmable, 1 × red/green

Conformity

CE, UKCA

UL certification

UL File No. E494534
NOTE: The device may only be supplied from circuits that comply with Class 2 or Safety Extra Low Voltage (SELV) according to Class 9.4 of UL 61010-1.

Further Resources #

1. Depending on variant
2. Up to RevPi Bullseye, WLAN is activated via RevPi Status.
3. Up to RevPi Bullseye, BT in the terminal via the HCI interface activated
4. The maximum USB output current is only guaranteed when supplied with 24 V DC −15 % / +20 %.
5. The average power consumption without USB load varies greatly depending on the use of the interfaces, GPU, and CPU. It is usually well below 6 W without HDMI.
6. The maximum operating temperature applies to typical device usage, but not to maximum device load.