The Industrial Raspberry Pi Forum

Hi All,

we are working on a custom IoT solution based on RevolutionPI for our customers. At the moment we have different hardware configurations with RevPICore and Connect using AIO modules and RTD/4-20 mA probes.

The operative system version is:

Linux IIOT_RT_Q_001_Core1 4.19.95-rt38-v7+ #1 SMP PREEMPT RT Tue, 16 Jun 2020 13:25:43 +0200 armv7l GNU/Linux

Recently we noticed several piBridges freezes with the classical error in kernel logs: "too many communication errors -> set inputs to default" on a configuration with a RevPiCore+ with 9 AIO modules , 5 on the left side and 4 on the right side.
On these modules we have RTD PT100 probes.

These errors apparently occur randomly and the only way to get back to working is a reboot of the core+.

As said the error in kernel log is:"too many communication errors -> set inputs to default" followed by 8 digits with a value from 0 to 255. What are related to and what is their meaning?

How can I investigate these errors further?

Where can I found more information on this topic?

If the piBridge is freezed the value of the channel "status" is consistent? I mean the status is updated with the error state? Can I use the status of the input channel as indicator of the error?

Many thanks in advance!

Hi please have a look at the following tutorial. There is described how the PiBridge communication reacts in case of an error.
Status bytes & LEDs on RevPi Core
https://revolution.kunbus.com/tutorials ... evpi-core/

Thank you Dirk but I already read many times that pages.
I'm asking for a little bit more detail and how to troubleshoot what's going on.
I'm able to understand that there are errors reading RS485ErrorCount value but once I know that too many errors occurred what can I do?

Hi xipherx, please check your setup
Are the PiBridge connectors connected stable?
Update your system Check if you can do a firmware update of the I/O. Just connect one I/O Module at a time.

How to Update Firmware of Modules

Hi Dirk,

we still have errors on kernel log regarding piBridge and desperately looking for a solution, the panel is in production in a customer's site hence we need work availability of the core without piControl stops.

firmware versions:
AIO 1.3
DIO 1.4
Core 1.2 + Stretch

This is the panel without IO connections: please tell me if the functional earthing E1 is correct: FE from core, connect and IO modules arrives to clamp E1 that is directly connected with the external power line Protection Earth. The clamp is also connected with the DIN bar and the chassis.

Many thanks in advance.

Fabio

xipherx wrote: ↑26 May 2021, 15:58 firmware versions:
AIO 1.3
DIO 1.4

There should be FW 1.4 and 1.5 out for those IO Cards where error handling was improved a lot.