[diegort]

Hello,

I’m having exactly the same issue. I just upgraded to version 2 recently and did not have the problem before. Basically after a few hours the following error shows up. I tried different reactors and tried connecting at different position in the board already. After this error, a restart of the beaglebone is necessary to connect succesfully again to the reactors.

root@beaglebone:~/chibio# bash cb.sh
[2021-05-25 23:44:29 +0000] [1808] [INFO] Starting gunicorn 20.1.0
[2021-05-25 23:44:29 +0000] [1808] [INFO] Listening at: http://192.168.19.146:50                                                                             00 (1808)
[2021-05-25 23:44:29 +0000] [1808] [INFO] Using worker: sync
[2021-05-25 23:44:29 +0000] [1811] [INFO] Booting worker with pid: 1811
2021-05-25 23:44:37.407105 Starting watchdog
2021-05-25 23:44:39.888825 Initialising devices
2021-05-25 23:44:40.128411 Initialised M4, Device ID: 13328179951295245632
2021-05-25 23:44:40.730010 Initialised M5, Device ID: 20492179931295245632
2021-05-25 23:44:41.330431 Initialised M6, Device ID: 36877182841295245632
2021-05-25 23:44:41.932494 Initialised M7, Device ID: 30731182901295245632
2021-05-25 23:44:42.408232 Start Up Complete
2021-05-25 23:45:13.716769 Set item: OD to value 0.3 on M4
2021-05-25 23:45:28.547329Calibrated OD
2021-05-25 23:45:48.433007 Set item: OD to value 0.3 on M5
2021-05-25 23:45:50.344274Calibrated OD
2021-05-25 23:46:11.277548 Set item: Pump2 to value 1.0 on M6
2021-05-25 23:46:42.458999 Set item: Pump1 to value 0.3 on M6
2021-05-25 23:47:24.757056Calibrated OD
2021-05-25 23:47:26.238169 Set item: OD to value 0.3 on M6
2021-05-25 23:48:04.022843Calibrated OD
2021-05-25 23:48:07.219585 Set item: OD to value 0.3 on M7
2021-05-25 23:52:42.713755 OD Measurement exception on LASER650
2021-05-25 23:52:43.719083 OD Measurement exception on LASER650
2021-05-26 03:50:51.686861 Failed Multiplexer Comms 1 times
2021-05-26 03:50:51.708952 Failed Multiplexer Comms 2 times
2021-05-26 03:50:51.730926 Failed Multiplexer Comms 3 times
2021-05-26 03:50:51.732701Failed to recover multiplexer on device M6
2021-05-26 03:50:51.754886 Failed Multiplexer Comms 4 times
2021-05-26 03:50:51.756565Failed to recover multiplexer on device M6
2021-05-26 03:50:51.778473 Failed Multiplexer Comms 5 times
2021-05-26 03:50:51.780180Failed to recover multiplexer on device M6
2021-05-26 03:50:52.002358 Failed Multiplexer Comms 6 times
2021-05-26 03:50:52.004130Failed to recover multiplexer on device M6
2021-05-26 03:50:52.026185 Failed Multiplexer Comms 7 times
2021-05-26 03:50:52.027877Failed to recover multiplexer on device M6
2021-05-26 03:50:52.049914 Failed Multiplexer Comms 8 times
2021-05-26 03:50:52.051628Failed to recover multiplexer on device M6
2021-05-26 03:50:52.073609 Failed Multiplexer Comms 9 times
2021-05-26 03:50:52.075300Failed to recover multiplexer on device M6
2021-05-26 03:50:52.097247 Failed Multiplexer Comms 10 times
2021-05-26 03:50:52.099008Failed to recover multiplexer on device M6
2021-05-26 03:50:52.120956 Failed Multiplexer Comms 11 times
2021-05-26 03:50:52.122974Failed to recover multiplexer on device M6
2021-05-26 03:50:52.144971 Failed Multiplexer Comms 12 times
2021-05-26 03:50:52.146805Failed to recover multiplexer on device M6
2021-05-26 03:50:52.168780 Failed Multiplexer Comms 13 times
2021-05-26 03:50:52.170637Failed to recover multiplexer on device M6
2021-05-26 03:50:52.192613 Failed Multiplexer Comms 14 times
2021-05-26 03:50:52.194457Failed to recover multiplexer on device M6
2021-05-26 03:50:52.216590 Failed Multiplexer Comms 15 times
2021-05-26 03:50:52.218547Failed to recover multiplexer on device M6
2021-05-26 03:50:52.240536 Failed Multiplexer Comms 16 times
2021-05-26 03:50:52.242353Failed to recover multiplexer on device M6
2021-05-26 03:50:52.264334 Failed Multiplexer Comms 17 times
2021-05-26 03:50:52.266102Failed to recover multiplexer on device M6
2021-05-26 03:50:52.288144 Failed Multiplexer Comms 18 times
2021-05-26 03:50:52.289783Failed to recover multiplexer on device M6
2021-05-26 03:50:52.311702 Failed Multiplexer Comms 19 times
2021-05-26 03:50:52.313394Failed to recover multiplexer on device M6
2021-05-26 03:50:52.335340 Failed Multiplexer Comms 20 times
2021-05-26 03:50:52.337095Failed to recover multiplexer on device M6
2021-05-26 03:50:52.359108 Failed Multiplexer Comms 21 times
2021-05-26 03:50:52.360792Failed to recover multiplexer on device M6
2021-05-26 03:50:52.362062Failed to communicate to Multiplexer 10 times. Disabli                                                                             ng hardware and software!
[2021-05-26 03:50:52 +0000] [1808] [INFO] Shutting down: Master
[2021-05-26 03:50:52 +0000] [1808] [INFO] Reason: App failed to load.
root@beaglebone:~/chibio# i2cdetect 0
Warning: Can't use SMBus Quick Write command, will skip some addresses
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0.
I will probe address range 0x03-0x77.
Continue? [Y/n] Y
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:
10:
20:
30: -- -- -- -- 34 -- -- --
40:
50: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60:
70:
root@beaglebone:~/chibio# i2cdetect 1
Warning: Can't use SMBus Quick Write command, will skip some addresses
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-1.
I will probe address range 0x03-0x77.
Continue? [Y/n] Y
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:
10:
20:
30: -- -- -- -- -- -- -- --
40:
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60:
70:
root@beaglebone:~/chibio# i2cdetect 2
Warning: Can't use SMBus Quick Write command, will skip some addresses
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-2.
I will probe address range 0x03-0x77.
Continue? [Y/n] Y
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:
10:
20:
30: -- -- -- -- -- -- -- --
40:
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60:
70:

[Author]

Posts