Chi.Bio stopped working

[JLSaid]

Hello everyone. I have been using the Chi.Bio system for two months and it has always worked well for me. However, today I have tried to start two cultures and I keep getting the message below. The detail is that I am not connecting the reactor to the M0, but to the other connections in the beaglebone, but it always points to a failure in M0. I have already dried the reactor, restarted multiple times, tested with all the 5 reactors that I have and this error persists. When I start the beaglebone with no reactor connected, it works, but then when I connect a reactor, the system does not work. has anyone ever faced a similar problem or knows how to solve it?

Thanks in advance.

[2024-09-30 13:45:01 +0000] [2156] [INFO] Starting gunicorn 20.1.0
[2024-09-30 13:45:01 +0000] [2156] [INFO] Listening at: http://192.168.7.2:5000 (2156)
[2024-09-30 13:45:01 +0000] [2156] [INFO] Using worker: sync
[2024-09-30 13:45:01 +0000] [2159] [INFO] Booting worker with pid: 2159
2024-09-30 13:45:08.411612 Starting watchdog
2024-09-30 13:45:10.895480 Initialising devices
2024-09-30 13:45:10.998140 Failed Multiplexer Comms 1 times
2024-09-30 13:45:11.054235 Failed Multiplexer Comms 2 times
2024-09-30 13:45:11.162090 Failed Multiplexer Comms 3 times
2024-09-30 13:45:11.197935Failed to recover multiplexer on device M0
2024-09-30 13:45:11.306142 Failed Multiplexer Comms 4 times
2024-09-30 13:45:11.341882Failed to recover multiplexer on device M0
2024-09-30 13:45:11.398155 Failed Multiplexer Comms 5 times
2024-09-30 13:45:11.433865Failed to recover multiplexer on device M0
2024-09-30 13:45:11.686785Did multiplexer hard-reset on M0
2024-09-30 13:45:11.782084 Failed Multiplexer Comms 6 times
2024-09-30 13:45:11.817863Failed to recover multiplexer on device M0
2024-09-30 13:45:11.874729 Failed Multiplexer Comms 7 times
2024-09-30 13:45:11.949929Failed to recover multiplexer on device M0
2024-09-30 13:45:12.006064 Failed Multiplexer Comms 8 times
2024-09-30 13:45:12.097960Failed to recover multiplexer on device M0
2024-09-30 13:45:12.154036 Failed Multiplexer Comms 9 times
2024-09-30 13:45:12.229930Failed to recover multiplexer on device M0
2024-09-30 13:45:12.286058 Failed Multiplexer Comms 10 times
2024-09-30 13:45:12.373929Failed to recover multiplexer on device M0
2024-09-30 13:45:12.626986Did multiplexer hard-reset on M0
2024-09-30 13:45:12.722224 Failed Multiplexer Comms 11 times
2024-09-30 13:45:12.809917Failed to recover multiplexer on device M0
2024-09-30 13:45:12.866048 Failed Multiplexer Comms 12 times
2024-09-30 13:45:12.953959Failed to recover multiplexer on device M0
2024-09-30 13:45:13.050065 Failed Multiplexer Comms 13 times
2024-09-30 13:45:13.085858Failed to recover multiplexer on device M0
2024-09-30 13:45:13.194585 Failed Multiplexer Comms 14 times
2024-09-30 13:45:13.229866Failed to recover multiplexer on device M0
2024-09-30 13:45:13.286100 Failed Multiplexer Comms 15 times
2024-09-30 13:45:13.361904Failed to recover multiplexer on device M0
2024-09-30 13:45:13.614943Did multiplexer hard-reset on M0
2024-09-30 13:45:13.710917 Failed Multiplexer Comms 16 times
2024-09-30 13:45:13.745889Failed to recover multiplexer on device M0
2024-09-30 13:45:13.854158 Failed Multiplexer Comms 17 times
2024-09-30 13:45:13.889863Failed to recover multiplexer on device M0
2024-09-30 13:45:13.998084 Failed Multiplexer Comms 18 times
2024-09-30 13:45:14.033860Failed to recover multiplexer on device M0
2024-09-30 13:45:14.090105 Failed Multiplexer Comms 19 times
2024-09-30 13:45:14.165927Failed to recover multiplexer on device M0
2024-09-30 13:45:14.222121 Failed Multiplexer Comms 20 times
2024-09-30 13:45:14.257968Failed to recover multiplexer on device M0
2024-09-30 13:45:14.314100 Failed Multiplexer Comms 21 times
2024-09-30 13:45:14.401918Failed to recover multiplexer on device M0
2024-09-30 13:45:14.403421Failed to communicate to Multiplexer 20 times. Disabling hardware and software!
[2024-09-30 13:45:14 +0000] [2156] [INFO] Shutting down: Master
[2024-09-30 13:45:14 +0000] [2156] [INFO] Reason: App failed to load.

[harrison]

Hello
So are you saying that if you have only one reactor connected, to a port that it is NOT M0, that it still fails in this way? Further, that this behaviour is replicated for each of the different reactors? If yes it would imply potentially some mess/short/broken part on the control computer.

Is there any combination of connectionrs/reactors (except from nothing connected) that gets this to happen?

Some things to note – you shouldn’t have any reactors connected and not have them powered, as this leads to crashes. Another – try swapping out the USB cables for a given reactor in case it is borked. Also, _maybe_ you have some unhappy reactor you don’t know about, so I would try each of them individually connected to e.g. M1 and see if ANYTHING works – because if one combination works it implies it is not the control computer…!

[JLSaid]

Hello Harrison, thank you for your reply.

So, I have performed tests with one and two reactors connected, to ports that are not M0, and it still points to that error. And yes, this behavior is replicated with all the 5 reactors that we have. As an update, I have borrowed another control computer from another group that also uses Chi.Bio, and it worked perfectly with our system. So it is probably a problem in the control computer that you mentioned. I just don’t know what may have caused it (there was no liquid spill in it, and we can still access all files and the user interface through it) and how to fix it. I am trying to contact Labmaker, but they are not replying to my emails.

If you know anything that can help it would be great.

Thank you!

[harrison]

Hello! Try support@labmaker.org if you haven’t already.
Something you could do is take off the blue PCB (one with microusb connectors) from the beaglebone, and look at it closely to see if anything seems off. If there is any dried residue etc try to clean it with a cotton bud and ethanol.

[JLSaid]

I have already sent 5 emails in the last 10 days and haven’t received any reply at all, not even a confirmation that they received my emails. I find it really disappointing and not the treatment I was expecting from them.

[harrison]

It is unfortunate, I can try to email them as well and cc you. Are you happy for me to do that with your @rug.nl email?

[Author]

Posts