MIO and Too many communication errors

[mitchellday06]

We are having problems connecting to the modules of the RevPi. The dmesg from the PI is at the bottom of this post.
The NodeRed Pins kept dropping out, and the piTest -d Returns no modules.
It seems one of our MIOs keeps returning 10700 values for some of the sensors, although the sensors haven't changed.

Then it says at the end of the dmesg: no piControl reset possible, a firmware update is running.
But we never triggered that to happen.
Our setup from Reft to Right is: MIO, MIO (troubles), AIO, DIO, Connect SE
Thoughts on this?



[ 55.937834] revpi_mio_cycle_dio: 90 callbacks suppressed
[ 55.937838] piControl: talk with mio for dio data error(addr:28, ret:-70)
[ 55.937843] piControl: too many communication errors -> set inputs to default 0 200 200 201 201 0 0 0
[ 56.007815] piControl: recv len from pibridge err(got:0, exp:20)
[ 56.007825] piControl: talk with mio for dio data error(addr:29, ret:-70)
[ 56.037837] piControl: recv len from pibridge err(got:0, exp:20)
[ 56.037847] piControl: talk with mio for dio data error(addr:28, ret:-70)
[ 56.037853] piControl: too many communication errors -> set inputs to default 0 201 201 202 202 0 0 0
[ 56.107839] piControl: recv len from pibridge err(got:0, exp:20)
[ 56.107850] piControl: talk with mio for dio data error(addr:29, ret:-70)
[ 56.137840] piControl: recv len from pibridge err(got:0, exp:20)
[ 56.137850] piControl: talk with mio for dio data error(addr:28, ret:-70)
[ 56.137856] piControl: too many communication errors -> set inputs to default 0 202 202 203 203 0 0 0
[ 56.207820] piControl: recv len from pibridge err(got:0, exp:20)
[ 56.207829] piControl: talk with mio for dio data error(addr:29, ret:-70)
[ 56.237854] piControl: recv len from pibridge err(got:0, exp:20)
[ 56.237864] piControl: talk with mio for dio data error(addr:28, ret:-70)
[ 56.237870] piControl: too many communication errors -> set inputs to default 0 203 203 204 204 0 0 0
[ 56.307866] piControl: recv len from pibridge err(got:0, exp:20)
[ 56.307878] piControl: talk with mio for dio data error(addr:29, ret:-70)
[ 56.337829] piControl: recv len from pibridge err(got:0, exp:20)
[ 56.337840] piControl: talk with mio for dio data error(addr:28, ret:-70)
[ 56.337846] piControl: too many communication errors -> set inputs to default 0 204 204 205 205 0 0 0
[ 56.407834] piControl: recv len from pibridge err(got:0, exp:20)
[ 56.407844] piControl: talk with mio for dio data error(addr:29, ret:-70)
[ 56.437827] piControl: too many communication errors -> set inputs to default 0 205 205 206 206 0 0 0
[ 56.547818] piControl: too many communication errors -> set inputs to default 0 206 206 207 207 0 0 0
[ 56.647818] piControl: too many communication errors -> set inputs to default 0 207 207 208 208 0 0 0
[ 56.747812] piControl: too many communication errors -> set inputs to default 0 208 208 209 209 0 0 0
[ 56.847832] piControl: too many communication errors -> set inputs to default 0 209 209 210 210 0 0 0
[ 56.947830] piControl: too many communication errors -> set inputs to default 0 210 210 211 211 0 0 0
[ 57.047821] piControl: too many communication errors -> set inputs to default 0 211 211 212 212 0 0 0
[ 57.147816] piControl: too many communication errors -> set inputs to default 0 212 212 213 213 0 0 0
[ 57.247825] piControl: too many communication errors -> set inputs to default 0 213 213 214 214 0 0 0
[ 57.347833] piControl: too many communication errors -> set inputs to default 0 214 214 215 215 0 0 0
[ 57.447821] piControl: too many communication errors -> set inputs to default 0 215 215 216 216 0 0 0
[ 57.547828] piControl: too many communication errors -> set inputs to default 0 216 216 217 217 0 0 0
[ 57.647813] piControl: too many communication errors -> set inputs to default 0 217 217 218 218 0 0 0
[ 57.747813] piControl: too many communication errors -> set inputs to default 0 218 218 219 219 0 0 0
[ 57.857843] piControl: too many communication errors -> set inputs to default 0 219 219 220 220 0 0 0
[ 57.957831] piControl: too many communication errors -> set inputs to default 0 220 220 221 221 0 0 0
[ 58.057815] piControl: too many communication errors -> set inputs to default 0 221 221 222 222 0 0 0
[ 58.157817] piControl: too many communication errors -> set inputs to default 0 222 222 223 223 0 0 0
[ 58.257827] piControl: too many communication errors -> set inputs to default 0 223 223 224 224 0 0 0
[ 58.357822] piControl: too many communication errors -> set inputs to default 0 224 224 225 225 0 0 0
[ 58.457814] piControl: too many communication errors -> set inputs to default 0 225 225 226 226 0 0 0
[ 58.557816] piControl: too many communication errors -> set inputs to default 0 226 226 227 227 0 0 0
[ 58.657817] piControl: too many communication errors -> set inputs to default 0 227 227 228 228 0 0 0
[ 58.757834] piControl: too many communication errors -> set inputs to default 0 228 228 229 229 0 0 0
[ 58.857824] piControl: too many communication errors -> set inputs to default 0 229 229 230 230 0 0 0
[ 58.957821] piControl: too many communication errors -> set inputs to default 0 230 230 231 231 0 0 0
[ 59.057809] piControl: too many communication errors -> set inputs to default 0 231 231 232 232 0 0 0
[ 59.157815] piControl: too many communication errors -> set inputs to default 0 232 232 233 233 0 0 0
[ 59.257857] piControl: too many communication errors -> set inputs to default 0 233 233 234 234 0 0 0
[ 59.357824] piControl: too many communication errors -> set inputs to default 0 234 234 235 235 0 0 0
[ 59.457818] piControl: too many communication errors -> set inputs to default 0 235 235 236 236 0 0 0
[ 59.557813] piControl: too many communication errors -> set inputs to default 0 236 236 237 237 0 0 0
[ 59.657818] piControl: too many communication errors -> set inputs to default 0 237 237 238 238 0 0 0
[ 59.757815] piControl: too many communication errors -> set inputs to default 0 238 238 239 239 0 0 0
[ 59.857836] piControl: too many communication errors -> set inputs to default 0 239 239 240 240 0 0 0
[ 59.957827] piControl: too many communication errors -> set inputs to default 0 240 240 241 241 0 0 0
[ 60.057812] piControl: too many communication errors -> set inputs to default 0 241 241 242 242 0 0 0
[ 60.157842] piControl: too many communication errors -> set inputs to default 0 242 242 243 243 0 0 0
[ 60.257840] piControl: too many communication errors -> set inputs to default 0 243 243 244 244 0 0 0
[ 60.357832] piControl: too many communication errors -> set inputs to default 0 244 244 245 245 0 0 0
[ 60.457824] piControl: too many communication errors -> set inputs to default 0 245 245 246 246 0 0 0
[ 60.557824] piControl: too many communication errors -> set inputs to default 0 246 246 247 247 0 0 0
[ 60.657830] piControl: too many communication errors -> set inputs to default 0 247 247 248 248 0 0 0
[ 60.757826] piControl: too many communication errors -> set inputs to default 0 248 248 249 249 0 0 0
[ 60.857825] piControl: too many communication errors -> set inputs to default 0 249 249 250 250 0 0 0
[ 60.957820] revpi_io_talk: 90 callbacks suppressed
[ 60.957829] piControl: recv len from pibridge err(got:0, exp:20)
[ 60.957834] revpi_mio_cycle_dio: 90 callbacks suppressed
[ 60.957838] piControl: talk with mio for dio data error(addr:28, ret:-70)
[ 60.957842] piControl: too many communication errors -> set BridgeState to stopped
[ 60.958374] piControl: stop data exchange
[ 60.961522] piControl: piIoComm_gotoGateProtocol returned 0
[ 67.127781] piControl: problem at driver initialization
[ 67.127788] piControl: no piControl reset possible, a firmware update is running
[ 193.717373] piControl: problem at driver initialization
[ 193.717380] piControl: no piControl reset possible, a firmware update is running

[dirk]

Hallo mitchellday06, can you please create and send us an SOS report?

[dirk]

Hi mitchellday06, thanks for the SOS report by email. There is an updated kernel available, so can you please update your system?
You can do this with the following commands, for example.

Code: Select all

sudo apt update
sudo apt upgrade

Then please also check whether updates are possible for the IO modules you are using:
https://revolutionpi.com/en/tutorials/i ... are-update

Here is a table with the list of currently available firmware versions. I have noticed that it is possible to update the AIO module to version 1.5.
https://gitlab.com/revolutionpi/revpi-firmware

If errors still occur, try this fix for the MIO modules at the bottom of the FAQ
https://kunbus-gmbh.atlassian.net/servi ... 3052863645

[mitchellday06]

Hey thanks for that. I will be on site today and can do that. As the system is installed can I do the module upgrade as an entire system, or do I need to attach only the on module at a time?
This particular MIO seems to be giving invalid inputs for all the sensors. It varies from some sensors feeding back over 10v and some around the 1-5mV. Could there be module issue causing this?

[dirk]

Hi mitchellday06
> Hey thanks for that. I will be on site today and can do that.
Ok
>As the system is installed can I do the module upgrade as an entire system, or do I need to attach only the on module at a time?
Yes, you disconnect all modules but the one you want to update - here is the documentation:
https://revolutionpi.com/en/tutorials/i ... are-update
> This particular MIO seems to be giving invalid inputs for all the sensors. It varies from some sensors feeding back over 10v and some around the 1-5mV. Could there be module issue causing this?
There is a known issue, so take a look here at “FAQ”:
https://kunbus-gmbh.atlassian.net/servi ... 3052863645