[yzhang]

Hi Harrison!

Thank you for your suggestions!
I tried to establish communication while unplugging the reactor from control board. This is what I saw. It seems to be working but once I plugged in the reactor, the same error message showed up again.
So I guess the problem originated from the reactor? Lab Maker rep said they will fix the problem after we send it back. Can I requested a replacement for the reactor while the old one is being fixed?

login as: root
Pre-authentication banner message from server:
| Debian GNU/Linux 10
|
| BeagleBoard.org Debian Buster IoT Image 2020-08-25
|
| Support: https://bbb.io/debian
|
| default username:password is [debian:temppwd]
|
End of banner message from server
root@192.168.7.2’s password:

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sun Jun 6 14:36:50 2021 from 192.168.7.1
root@beaglebone:~# ls
chibio
root@beaglebone:~# cd chibio
root@beaglebone:~/chibio# bash cb.sh
[2021-07-06 14:42:34 +0000] [3291] [INFO] Starting gunicorn 20.1.0
[2021-07-06 14:42:34 +0000] [3291] [INFO] Listening at: http://192.168.7.2:5000 (3291)
[2021-07-06 14:42:34 +0000] [3291] [INFO] Using worker: sync
[2021-07-06 14:42:34 +0000] [3294] [INFO] Booting worker with pid: 3294
2021-07-06 14:42:41.886960 Starting watchdog
2021-07-06 14:42:44.369160 Initialising devices
2021-07-06 14:42:44.463984 Start Up Complete

[yzhang]

Tried that and it seemed that we can still communicate with the beagle board using PC. But still the same error message.

[yzhang]

Nothing out of the ordinary happened. The reactor was running OK for 36h but the OD sensor started to become unstable. It eventually threw off the automatic OD maintenance algorithm due to the instability. Once this sudden jump of the OD was observed, we had to stopped the program and the error occurred after trying to reestablish communication.
Yes, I have only one reactor but planning on getting more if we could get it to work. Any suggestions to fix the problem? Do we have to need to send the reactor back to lab maker to get it fixed? or can we borrow one from the lab maker while we are trying to figure out the problem? Thank you!

[yzhang]

Thank you for your suggestions. I tried to use ethanol to clean the sensing track and the rest of the reactor chamber carefully, but the problem persisted. It gave the same error message when I tried to establish communication. Any other suggestions? I reinstalled the latest image for the beagle board but it did not help either. Is there we could know whether this is a software problem or a hardware problem? Thank you!

Best,
Yi

• This reply was modified 3 years, 4 months ago by yzhang.

[yzhang]

Yes. Communication was once established using a newer PC where the beaglebone driver was not installed probably due to security issue. Logging in info was requested back then and it seemed that we can enter the system but the chi bio operation system was not there. I had to use a older computer where the driver for beaglebone could be successfully installed and we also have the micro SD card ready this time. But surprisingly, now I cannot establish communication in either computer I had.

[Author]

Posts