Failing to detect Reactor

This topic has 5 replies, 2 voices, and was last updated 3 years, 2 months ago by harrison.

Viewing 6 posts - 1 through 6 (of 6 total)

Author

Posts
September 10, 2021 at 9:34 am #1330
lachlan
Participant
I set up my Chi.Bio and managed to get it running, however during the first run it stopped after around an hour due to the “Failed Multiplexer Comms” error that a few other people have posted about.
Now whenever I start up with the bash cb.sh command, it successfully connects to the beaglebone but can’t detect the reactor at all. The GUI will load, however all the channels are greyed out and “Scan Devices” doesn’t do anything.

Have tested all inputs (T0 – T7) and none of them are working.
Output when I connect is:
```
root@beaglebone:~/chibio# bash cb.sh
[2021-09-10 11:29:08 +0000] [4321] [INFO] Starting gunicorn 20.1.0
[2021-09-10 11:29:08 +0000] [4321] [INFO] Listening at: http://192.168.7.2:5000 (4321)
[2021-09-10 11:29:08 +0000] [4321] [INFO] Using worker: sync
[2021-09-10 11:29:08 +0000] [4324] [INFO] Booting worker with pid: 4324
2021-09-10 11:29:16.267687 Starting watchdog
2021-09-10 11:29:18.750319 Initialising devices
2021-09-10 11:29:18.845154 Start Up Complete
```
Do you have any troubleshooting tips or things I should be checking not listed in the operations manual? I have inspected and wiped down the moisture detection tracks with ethanol already.

Thanks
September 10, 2021 at 9:40 am #1331

harrison
Keymaster

Hi Lachlan,

I’ll assume everythign is plugged in and powered on etc.
Maybe one approach would be to try a different 12V power supply, and different USB cables in case they are broken somehow.

Failing that I would have to say the most likely application is a fault in the hardware/assembly which is somehow preventing it from communicating with the reactor. I don’t think moisture is the issue (as you said) since usually if that is the case it wouldn’t reach the “start up complete” message without error.

Unless you want to get in the device and start soldering connections etc probably the best approach is to reach out to labmaker and ask if they can replace/fix it.

September 10, 2021 at 9:47 am #1332

lachlan
Participant

Hi Harrison,

Thanks for the quick reply. Yes, usb cables I have tried swapping around etc.
I will try to hunt down another 12 V power cord to test, but if that doesn’t help I’ll contact labmaker.

Best,

Lachlan

September 10, 2021 at 9:48 am #1333

harrison
Keymaster

Alternatively you could measure the power supply with a multimeter to check if it is as expected.
Probably this is an unlikely cause – given it worked previously, it seems more likely that the reactor/hardware might have broken (probably there is a bad solder connection) rather than the 12V packing in.

September 13, 2021 at 7:39 am #1334

lachlan
Participant

Hi Harrison,

It seems to be working again now with the same setup, despite several restarts last week not doing anything. Based on your suggestions I guess it is possibly a loose connection that came on or off?
I will see how it goes now and contact labmaker if the issue comes back.

Thanks again,

Lachlan

September 13, 2021 at 8:23 am #1335

harrison
Keymaster

It does seem suspicious that it would stop working then magically start up later. My best guess would therefore revert back to the moisture sensors – perhaps the one half-way down inside the device was tripped.
Or, it might indeed be a hardware issue, perhaps temperature changes etc helped it re-make a good connection. Hopefully it keeps operating as expected…
Author

Posts

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.