Chi.Bio

Home › Forums › Assembly/Setup › Pump rate

Viewing 15 posts - 1 through 15 (of 19 total)
1 2
  • Author
    Posts
  • October 8, 2020 at 6:57 am #1001
    Nobuhiro
    Participant

    Hi Harrison,

    I experimented with constant OD(0.2 and 0.5). However, there is a problem with the input pump rate, there was too much input of fresh media and it was diluted significantly.

    I tried to measure the input amount for each pump rate by changing rate(0.001, 0.005…), sometimes the pump was up for the set rate, and sometimes it was up for obviously a long time.

    I use 4mm/2.5mm Outer/Inner diameter laboratory tubing, so I read Mechanical Assembly Guide and taped the pump.
    I think the peristaltic pump is sealed and working properly

    Is there any solution?

    Thank you.
    Nobuhiro

    October 8, 2020 at 7:44 am #1002
    harrison
    Keymaster

    Hi Nobuhiro,
    I’m trying to understand – so you set the target OD to something (say, 0.5), then when cells eventually reached this level it kept pumping continuously, even though their OD was below the target level?

    And, when you tried setting the pump to slow rates manually (e.g. 0.01) it actually pumped a lot more than this? (for reference, 0.01 rate means the pump should be on for approximately 0.01*60=0.6 seconds)

    If so – are there any messages in the Putty window from the system with errors etc?

    This sounds like a strange problem, and should not have anything to do with the tubing – if the system is set at a low pump rate (0.01) and pumps a lot more than this then it is likely a software/electronics issue. Have you made any modifications to either?

    Would it be possible for you to upload (e.g. via dropbox or something) a video of the problem so I can see?

    Harrison

    October 8, 2020 at 8:26 am #1003
    Nobuhiro
    Participant

    Hi Hariison,

    I uploaded a video and a slide of the result of OD regulation to the link below.
    https://keio.box.com/s/ypc2of3lltvuvlz061gzhtsge0mwdxxr

    I think the pump rate is higher than the displayed pump rate and the OD is excessively diluted when the OD exceeds the target OD. Input stops after dilution.
    The video is repeatedly switched ON and OFF.

    Thank you.

    Nobuhiro

    • This reply was modified 4 years, 1 month ago by Nobuhiro.
    October 20, 2020 at 7:42 pm #1033
    harrison
    Keymaster

    So, in IMG_9434 you are repeatedly switching the pump on-off-on with it set at 0.007 rate? Or, are you only switching it on-off-on when the camera pans to look at the screen?
    If you keep toggling the pump on-off-on manually then it will pump at a higher rate since each time you turn it on it will output a small amount.

    However, this does not explain what happens at t=~20 in that video. At this point it seemed the pump somehow stayed on for much longer. Something similar happens at the start of 9433. I think these correspond to the entries in your PuTTY terminal saying “Failed transmission test on Pumps 1 times…” This happens if the digital communications with the Pump PCB fail first time around. It seems the software has identified this and is trying to fix it, but is then struggling to disconnect the multiplexer when it comes back around to try doing that communication again. This a hardware problem.
    Do you ever see similar faults with turning on/off the LEDS? I.e. when you tell one to turn off/on and it doesn’t do so? If not, then it would indicate that the chip on the pump board is faulty, and so I would ask Labmaker to see if they can replace the pump board.

    Potentially we may be able to come up with a software fix that will mitigate the issue so long as it doesn’t happen all the time. It is good that the error is caught in the software, but it seems whatever is wrong with the communication to the pump is subsequently causing the multiplexer issues. Perhaps the following will help diagnose:

    1. Go to the function “def setPWM….” in the code.
    2. Immediately before the line “if sysDevices[M][device][‘startup’]==0:” (which is near the start of the function) add the following:

    if (ConsecutiveFails>0):
    print(str(datetime.now()) + ‘ Attempting to retry PWM Transmission’)

    Note that in the above there needs to be a tab space indent infront of the print statement.

    3. After the line “CheckHighON=I2CCom(M,device,1,8,channels[‘ONH’],-1,0)” inside “def setPWM” add the following:

    if (ConsecutiveFails>0):
    print(str(datetime.now()) + ‘ Completed retry of PWM Transmission’)

    4. Try running the new code and see what is shown in the Putty window when the excess pumping error occurs. I am puzzled by what you are seeing since it SEEMS that the self-correcting code is working (i.e. becasue it doesnt say it Failed the transmission test a second time), however it is evidently not having the desired effect (the pumps aren’t turning off as needed!).

    October 20, 2020 at 7:56 pm #1037
    harrison
    Keymaster

    Let me know when you get a chance to test that, in the meantime I will try to figure out what else could be done to fix it in software (though I think working hardware would be a better first step!).

    I can now see your other replies to this thread with logs for when the system worked. In these cases you can see the connection to the pumps is still causing issues, but nevertheless it is able to recover. So, it seems sometimes the recovery fails – perhaps this could be fixed by adding additional checks to the recovery procedure, but this will then slow down the entire system in general.

    • This reply was modified 4 years ago by harrison.
    October 20, 2020 at 8:13 pm #1030
    Nobuhiro
    Participant

    Hi,
    There were some error messages in the Putty window when pumps switched ON and OFF.
    II’m using a windows OS laptop.

    Thank you.

    root@beaglebone:~# cd chibio
    root@beaglebone:~/chibio# bash cb.sh
    [2020-10-08 17:17:49 +0000] [1414] [INFO] Starting gunicorn 20.0.4
    [2020-10-08 17:17:49 +0000] [1414] [INFO] Listening at: http://192.168.7.2:5000 (1414)
    [2020-10-08 17:17:49 +0000] [1414] [INFO] Using worker: sync
    [2020-10-08 17:17:49 +0000] [1508] [INFO] Booting worker with pid: 1508
    2020-10-08 17:18:02.460860 Starting watchdog
    2020-10-08 17:18:04.944644 Initialising devices
    2020-10-08 17:18:05.168685 Initialised M0, Device ID: 256045884079957548
    2020-10-08 17:18:05.795483 Start Up Complete
    http://192.168.7.2:50002020-10-08 17:18:29.888857 Set item: Pump1 to value 0.00 1 on M0
    2020-10-08 17:18:31.556710 Failed Pumps comms 1 times on device M0
    2020-10-08 17:18:35.344897 Failed Pumps comms 2 times on device M0
    2020-10-08 17:18:35.394005 Failed transmission test on Pumps 1 times consecutive ly on device M0
    2020-10-08 17:18:44.094091 Failed Pumps comms 1 times on device M0
    2020-10-08 17:18:45.652411 Failed transmission test on Pumps 1 times consecutive ly on device M0
    Failed to disconnect multiplexer on device M0
    [2020-10-08 17:19:22 +0000] [1414] [INFO] Handling signal: winch
    2020-10-08 17:19:34.349165 Failed Pumps comms 1 times on device M0
    2020-10-08 17:19:37.780527 Failed Pumps comms 1 times on device M0
    2020-10-08 17:19:37.804474 Failed transmission test on Pumps 1 times consecutively on device M0
    2020-10-08 17:19:38.992933 Failed Pumps comms 1 times on device M0
    2020-10-08 17:19:39.045386 Failed transmission test on Pumps 1 times consecutively on device M0
    2020-10-08 17:19:39.176477 Failed transmission test on Pumps 2 times consecutively on device M0
    2020-10-08 17:19:41.450525 Failed Pumps comms 1 times on device M0
    2020-10-08 17:19:42.512834 Failed Pumps comms 2 times on device M0
    2020-10-08 17:19:42.558500 Failed transmission test on Pumps 1 times consecutively on device M0
    Failed to disconnect multiplexer on device M0
    2020-10-08 17:19:48.128428 Failed Pumps comms 1 times on device M0
    Failed to disconnect multiplexer on device M0
    2020-10-08 17:19:52.529964 Failed Pumps comms 1 times on device M0
    2020-10-08 17:19:58.228853 Failed Pumps comms 1 times on device M0
    2020-10-08 17:19:58.274499 Failed transmission test on Pumps 1 times consecutively on device M0
    Failed to disconnect multiplexer on device M0
    Failed to disconnect multiplexer on device M0
    2020-10-08 17:20:06.897799 Failed Pumps comms 1 times on device M0
    2020-10-08 17:20:09.215635 Failed transmission test on Pumps 1 times consecutively on device M0
    Failed to disconnect multiplexer on device M0
    2020-10-08 17:20:14.236936 Failed transmission test on Pumps 1 times consecutively on device M0
    2020-10-08 17:20:18.104718 Failed Pumps comms 1 times on device M0
    2020-10-08 17:21:22.256816 Failed Pumps comms 1 times on device M0
    2020-10-08 17:21:22.302471 Failed transmission test on Pumps 1 times consecutively on device M0

    October 20, 2020 at 8:13 pm #1031
    Nobuhiro
    Participant

    Hi,
    There were some error messages in the Putty window when pumps switched ON and OFF.
    II’m using a windows OS laptop.

    Thank you.

    root@beaglebone:~# cd chibio
    root@beaglebone:~/chibio# bash cb.sh
    [2020-10-08 17:17:49 +0000] [1414] [INFO] Starting gunicorn 20.0.4
    [2020-10-08 17:17:49 +0000] [1414] [INFO] Listening at: http://192.168.7.2:5000 (1414)
    [2020-10-08 17:17:49 +0000] [1414] [INFO] Using worker: sync
    [2020-10-08 17:17:49 +0000] [1508] [INFO] Booting worker with pid: 1508
    2020-10-08 17:18:02.460860 Starting watchdog
    2020-10-08 17:18:04.944644 Initialising devices
    2020-10-08 17:18:05.168685 Initialised M0, Device ID: 256045884079957548
    2020-10-08 17:18:05.795483 Start Up Complete
    http://192.168.7.2:50002020-10-08 17:18:29.888857 Set item: Pump1 to value 0.00 1 on M0
    2020-10-08 17:18:31.556710 Failed Pumps comms 1 times on device M0
    2020-10-08 17:18:35.344897 Failed Pumps comms 2 times on device M0
    2020-10-08 17:18:35.394005 Failed transmission test on Pumps 1 times consecutive ly on device M0
    2020-10-08 17:18:44.094091 Failed Pumps comms 1 times on device M0
    2020-10-08 17:18:45.652411 Failed transmission test on Pumps 1 times consecutive ly on device M0
    Failed to disconnect multiplexer on device M0
    [2020-10-08 17:19:22 +0000] [1414] [INFO] Handling signal: winch
    2020-10-08 17:19:34.349165 Failed Pumps comms 1 times on device M0
    2020-10-08 17:19:37.780527 Failed Pumps comms 1 times on device M0
    2020-10-08 17:19:37.804474 Failed transmission test on Pumps 1 times consecutively on device M0
    2020-10-08 17:19:38.992933 Failed Pumps comms 1 times on device M0
    2020-10-08 17:19:39.045386 Failed transmission test on Pumps 1 times consecutively on device M0
    2020-10-08 17:19:39.176477 Failed transmission test on Pumps 2 times consecutively on device M0
    2020-10-08 17:19:41.450525 Failed Pumps comms 1 times on device M0
    2020-10-08 17:19:42.512834 Failed Pumps comms 2 times on device M0
    2020-10-08 17:19:42.558500 Failed transmission test on Pumps 1 times consecutively on device M0
    Failed to disconnect multiplexer on device M0
    2020-10-08 17:19:48.128428 Failed Pumps comms 1 times on device M0
    Failed to disconnect multiplexer on device M0
    2020-10-08 17:19:52.529964 Failed Pumps comms 1 times on device M0
    2020-10-08 17:19:58.228853 Failed Pumps comms 1 times on device M0
    2020-10-08 17:19:58.274499 Failed transmission test on Pumps 1 times consecutively on device M0
    Failed to disconnect multiplexer on device M0
    Failed to disconnect multiplexer on device M0
    2020-10-08 17:20:06.897799 Failed Pumps comms 1 times on device M0
    2020-10-08 17:20:09.215635 Failed transmission test on Pumps 1 times consecutively on device M0
    Failed to disconnect multiplexer on device M0
    2020-10-08 17:20:14.236936 Failed transmission test on Pumps 1 times consecutively on device M0
    2020-10-08 17:20:18.104718 Failed Pumps comms 1 times on device M0
    2020-10-08 17:21:22.256816 Failed Pumps comms 1 times on device M0
    2020-10-08 17:21:22.302471 Failed transmission test on Pumps 1 times consecutively on device M0

    October 20, 2020 at 8:13 pm #1028
    Nobuhiro
    Participant

    There were some message in the Putty window when pumps worked.

    login as: root
    Pre-authentication banner message from server:
    | Debian GNU/Linux 10
    |
    | BeagleBoard.org Debian Buster IoT Image 2020-05-18
    |
    | Support: http://elinux.org/Beagleboard:BeagleBoneBlack_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: Thu Oct 8 17:17:52 2020 from 192.168.7.1
    root@beaglebone:~# cd chibio
    root@beaglebone:~/chibio# bash cb.sh
    [2020-10-08 17:17:49 +0000] [1414] [INFO] Starting gunicorn 20.0.4
    [2020-10-08 17:17:49 +0000] [1414] [INFO] Listening at: http://192.168.7.2:5000 (1414)
    [2020-10-08 17:17:49 +0000] [1414] [INFO] Using worker: sync
    [2020-10-08 17:17:49 +0000] [1508] [INFO] Booting worker with pid: 1508
    2020-10-08 17:18:02.460860 Starting watchdog
    2020-10-08 17:18:04.944644 Initialising devices
    2020-10-08 17:18:05.168685 Initialised M0, Device ID: 256045884079957548
    2020-10-08 17:18:05.795483 Start Up Complete
    http://192.168.7.2:50002020-10-08 17:18:29.888857 Set item: Pump1 to value 0.00 1 on M0
    2020-10-08 17:18:31.556710 Failed Pumps comms 1 times on device M0
    2020-10-08 17:18:35.344897 Failed Pumps comms 2 times on device M0
    2020-10-08 17:18:35.394005 Failed transmission test on Pumps 1 times consecutive ly on device M0
    2020-10-08 17:18:44.094091 Failed Pumps comms 1 times on device M0
    2020-10-08 17:18:45.652411 Failed transmission test on Pumps 1 times consecutive ly on device M0
    Failed to disconnect multiplexer on device M0
    [2020-10-08 17:19:22 +0000] [1414] [INFO] Handling signal: winch
    2020-10-08 17:19:34.349165 Failed Pumps comms 1 times on device M0
    2020-10-08 17:19:37.780527 Failed Pumps comms 1 times on device M0
    2020-10-08 17:19:37.804474 Failed transmission test on Pumps 1 times consecutively on device M0
    2020-10-08 17:19:38.992933 Failed Pumps comms 1 times on device M0
    2020-10-08 17:19:39.045386 Failed transmission test on Pumps 1 times consecutively on device M0
    2020-10-08 17:19:39.176477 Failed transmission test on Pumps 2 times consecutively on device M0
    2020-10-08 17:19:41.450525 Failed Pumps comms 1 times on device M0
    2020-10-08 17:19:42.512834 Failed Pumps comms 2 times on device M0
    2020-10-08 17:19:42.558500 Failed transmission test on Pumps 1 times consecutively on device M0
    Failed to disconnect multiplexer on device M0
    2020-10-08 17:19:48.128428 Failed Pumps comms 1 times on device M0
    Failed to disconnect multiplexer on device M0
    2020-10-08 17:19:52.529964 Failed Pumps comms 1 times on device M0
    2020-10-08 17:19:58.228853 Failed Pumps comms 1 times on device M0
    2020-10-08 17:19:58.274499 Failed transmission test on Pumps 1 times consecutively on device M0
    Failed to disconnect multiplexer on device M0
    Failed to disconnect multiplexer on device M0
    2020-10-08 17:20:06.897799 Failed Pumps comms 1 times on device M0
    2020-10-08 17:20:09.215635 Failed transmission test on Pumps 1 times consecutively on device M0
    Failed to disconnect multiplexer on device M0
    2020-10-08 17:20:14.236936 Failed transmission test on Pumps 1 times consecutively on device M0
    2020-10-08 17:20:18.104718 Failed Pumps comms 1 times on device M0
    login as: root
    Pre-authentication banner message from server:
    | Debian GNU/Linux 10
    |
    | BeagleBoard.org Debian Buster IoT Image 2020-05-18
    |
    | Support: http://elinux.org/Beagleboard:BeagleBoneBlack_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: Thu Oct 8 17:17:52 2020 from 192.168.7.1
    root@beaglebone:~# cd chibio
    root@beaglebone:~/chibio# bash cb.sh
    [2020-10-08 17:17:49 +0000] [1414] [INFO] Starting gunicorn 20.0.4
    [2020-10-08 17:17:49 +0000] [1414] [INFO] Listening at: http://192.168.7.2:5000 (1414)
    [2020-10-08 17:17:49 +0000] [1414] [INFO] Using worker: sync
    [2020-10-08 17:17:49 +0000] [1508] [INFO] Booting worker with pid: 1508
    2020-10-08 17:18:02.460860 Starting watchdog
    2020-10-08 17:18:04.944644 Initialising devices
    2020-10-08 17:18:05.168685 Initialised M0, Device ID: 256045884079957548
    2020-10-08 17:18:05.795483 Start Up Complete
    http://192.168.7.2:50002020-10-08 17:18:29.888857 Set item: Pump1 to value 0.00 1 on M0
    2020-10-08 17:18:31.556710 Failed Pumps comms 1 times on device M0
    2020-10-08 17:18:35.344897 Failed Pumps comms 2 times on device M0
    2020-10-08 17:18:35.394005 Failed transmission test on Pumps 1 times consecutive ly on device M0
    2020-10-08 17:18:44.094091 Failed Pumps comms 1 times on device M0
    2020-10-08 17:18:45.652411 Failed transmission test on Pumps 1 times consecutive ly on device M0
    Failed to disconnect multiplexer on device M0
    [2020-10-08 17:19:22 +0000] [1414] [INFO] Handling signal: winch
    2020-10-08 17:19:34.349165 Failed Pumps comms 1 times on device M0
    2020-10-08 17:19:37.780527 Failed Pumps comms 1 times on device M0
    2020-10-08 17:19:37.804474 Failed transmission test on Pumps 1 times consecutively on device M0
    2020-10-08 17:19:38.992933 Failed Pumps comms 1 times on device M0
    2020-10-08 17:19:39.045386 Failed transmission test on Pumps 1 times consecutively on device M0
    2020-10-08 17:19:39.176477 Failed transmission test on Pumps 2 times consecutively on device M0
    2020-10-08 17:19:41.450525 Failed Pumps comms 1 times on device M0
    2020-10-08 17:19:42.512834 Failed Pumps comms 2 times on device M0
    2020-10-08 17:19:42.558500 Failed transmission test on Pumps 1 times consecutively on device M0
    Failed to disconnect multiplexer on device M0
    2020-10-08 17:19:48.128428 Failed Pumps comms 1 times on device M0
    Failed to disconnect multiplexer on device M0
    2020-10-08 17:19:52.529964 Failed Pumps comms 1 times on device M0
    2020-10-08 17:19:58.228853 Failed Pumps comms 1 times on device M0
    2020-10-08 17:19:58.274499 Failed transmission test on Pumps 1 times consecutively on device M0
    Failed to disconnect multiplexer on device M0
    Failed to disconnect multiplexer on device M0
    2020-10-08 17:20:06.897799 Failed Pumps comms 1 times on device M0
    2020-10-08 17:20:09.215635 Failed transmission test on Pumps 1 times consecutively on device M0
    Failed to disconnect multiplexer on device M0
    2020-10-08 17:20:14.236936 Failed transmission test on Pumps 1 times consecutively on device M0
    2020-10-08 17:20:18.104718 Failed Pumps comms 1 times on device M0
    2020-10-08 17:21:22.256816 Failed Pumps comms 1 times on device M0
    2020-10-08 17:21:22.302471 Failed transmission test on Pumps 1 times consecutively on device M0

    I’m using a windows OS laptop.

    Thank you.

    October 24, 2020 at 2:30 pm #1054
    harrison
    Keymaster

    From the look of the above it seems that there must be a faulty pump board. There should be very few such errors (maybe once every few thousand times you send the command, not EVERY time). It seems that in MOST of the logs you attached the system is able to correct the error (as it is designed to), but infrequently it fails to do this, which is why it then stays on for longer than expected. I expect the issue is a poor connection on the USB connector or circuitry on the Pump PCB, which Labmaker should be able to sort for you.

    October 24, 2020 at 3:33 pm #1055
    Nobuhiro
    Participant

    I’m sorry for the continuous throwing.

    Didn’t happen similar faults with turning on/off the LEDS.Switching the pump on-off-on, the error message ‘Failed to disconnect multiplexer on device M0’ was displayed when the pump stay on for much longer.

    I tried running the new code. Putty window shown the same error messages ‘Failed to disconnect multiplexer on device M0’ when the excess pumping error occurs.

    Before changing the program
    2020-10-23 15:28:50.337228 Set item: LEDA to value 0.0 on M0
    2020-10-23 15:28:56.559851 Set item: LEDA to value 0.1 on M0
    2020-10-23 15:29:05.105991 Set item: LEDB to value 0.0 on M0
    2020-10-23 15:29:08.593931 Set item: LEDB to value 0.1 on M0
    2020-10-23 15:29:21.036847 Set item: Pump1 to value 0.001 on M0
    2020-10-23 15:29:29.030794 Set item: Pump2 to value 0.001 on M0
    2020-10-23 15:34:09.264397 Set item: Pump1 to value 0.001 on M0
    Failed to disconnect multiplexer on device M0

    After changing the program
    2020-10-23 15:18:16.487664 Set item: LEDA to value 0.11 on M0
    2020-10-23 15:18:24.299767 Set item: Pump1 to value 0.001 on M0
    2020-10-23 15:18:28.740432 Set item: Pump2 to value 0.001 on M0
    2020-10-23 15:20:34.356793 Set item: Pump1 to value 0.001 on M0
    2020-10-23 15:20:35.160559 Set item: Pump1 to value 0.001 on M0
    2020-10-23 15:20:35.476730 Set item: Pump1 to value 0.001 on M0
    Failed to disconnect multiplexer on device M0

    It seems that the pump board is the cause.
    I’m thinking of replacing the cable and trying again. Should I contact Labmaker?

    Thank you.
    Nobuhiro

    October 24, 2020 at 3:34 pm #1056
    harrison
    Keymaster

    Yes, send them an email. Mention I sent you and it seems you have a faulty pump board. Attach the logs above so they can see it is causing continual errors.

    March 30, 2021 at 7:31 pm #1114
    harrison
    Keymaster

    Hi Nobuhiro,
    I came across a similar error to this and figured out a fix to hopefully catch these issues – check out the new version of app.py on the Github.
    Harrison

    May 21, 2021 at 11:03 am #1211
    Tatsuya
    Participant

    Hi Harrison,

    I took over Chi. Bio. from Nobuhiro.

    I replaced app.py with newly released one, and pumps come to work well!
    Thank you for updating!

    However, after several experiment, I bumped into another problem.
    When control board is connected with reactor and then execute “bash cb.sh” in putty terminal, it says “Failed to recover multiplexer on device M0”

    Start up is successfully complete if no reactor is connected.
    But I connect reactor and press “scan” in GUI, then the same error occurs.

    Do you know any solutions?

    Thank you.
    Tatsuya

    Below is error statements:

    root@beaglebone:~# cd chibio
    root@beaglebone:~/chibio# bash cb.sh
    [2021-05-20 16:55:11 +0000] [1797] [INFO] Starting gunicorn 20.1.0
    [2021-05-20 16:55:11 +0000] [1797] [INFO] Listening at: http://192.168.7.2:5000 (1797)
    [2021-05-20 16:55:11 +0000] [1797] [INFO] Using worker: sync
    [2021-05-20 16:55:11 +0000] [1800] [INFO] Booting worker with pid: 1800
    2021-05-20 16:55:19.602343 Starting watchdog
    2021-05-20 16:55:22.085918 Initialising devices
    2021-05-20 16:55:22.161820 Failed Multiplexer Comms 1 times
    2021-05-20 16:55:22.217919 Failed Multiplexer Comms 2 times
    2021-05-20 16:55:22.273809 Failed Multiplexer Comms 3 times
    2021-05-20 16:55:22.309732Failed to recover multiplexer on device M0
    2021-05-20 16:55:22.365795 Failed Multiplexer Comms 4 times
    2021-05-20 16:55:22.401661Failed to recover multiplexer on device M0
    2021-05-20 16:55:22.457796 Failed Multiplexer Comms 5 times
    2021-05-20 16:55:22.493649Failed to recover multiplexer on device M0
    2021-05-20 16:55:22.750045 Failed Multiplexer Comms 6 times
    2021-05-20 16:55:22.785651Failed to recover multiplexer on device M0
    2021-05-20 16:55:22.841842 Failed Multiplexer Comms 7 times
    2021-05-20 16:55:22.877651Failed to recover multiplexer on device M0
    2021-05-20 16:55:22.933769 Failed Multiplexer Comms 8 times
    2021-05-20 16:55:22.969711Failed to recover multiplexer on device M0
    2021-05-20 16:55:23.025787 Failed Multiplexer Comms 9 times
    2021-05-20 16:55:23.061646Failed to recover multiplexer on device M0
    2021-05-20 16:55:23.117817 Failed Multiplexer Comms 10 times
    2021-05-20 16:55:23.153646Failed to recover multiplexer on device M0
    2021-05-20 16:55:23.209845 Failed Multiplexer Comms 11 times
    2021-05-20 16:55:23.245678Failed to recover multiplexer on device M0
    2021-05-20 16:55:23.301800 Failed Multiplexer Comms 12 times
    2021-05-20 16:55:23.337695Failed to recover multiplexer on device M0
    2021-05-20 16:55:23.393778 Failed Multiplexer Comms 13 times
    2021-05-20 16:55:23.429713Failed to recover multiplexer on device M0
    2021-05-20 16:55:23.485780 Failed Multiplexer Comms 14 times
    2021-05-20 16:55:23.521698Failed to recover multiplexer on device M0
    2021-05-20 16:55:23.577792 Failed Multiplexer Comms 15 times
    2021-05-20 16:55:23.613753Failed to recover multiplexer on device M0
    2021-05-20 16:55:23.669803 Failed Multiplexer Comms 16 times
    2021-05-20 16:55:23.705644Failed to recover multiplexer on device M0
    2021-05-20 16:55:23.761918 Failed Multiplexer Comms 17 times
    2021-05-20 16:55:23.797656Failed to recover multiplexer on device M0
    2021-05-20 16:55:23.853813 Failed Multiplexer Comms 18 times
    2021-05-20 16:55:23.889649Failed to recover multiplexer on device M0
    2021-05-20 16:55:23.945795 Failed Multiplexer Comms 19 times
    2021-05-20 16:55:23.981645Failed to recover multiplexer on device M0
    2021-05-20 16:55:24.037788 Failed Multiplexer Comms 20 times
    2021-05-20 16:55:24.073643Failed to recover multiplexer on device M0
    2021-05-20 16:55:24.129788 Failed Multiplexer Comms 21 times
    2021-05-20 16:55:24.165646Failed to recover multiplexer on device M0
    2021-05-20 16:55:24.166848Failed to communicate to Multiplexer 10 times. Disabli ng hardware and software!
    [2021-05-20 16:55:24 +0000] [1797] [INFO] Shutting down: Master
    [2021-05-20 16:55:24 +0000] [1797] [INFO] Reason: App failed to load.

    May 21, 2021 at 11:20 am #1212
    harrison
    Keymaster

    Hi Tatsuya,
    You said it worked well, but then at some point it started showing this error – is that correct?
    Does this error come if one specific reactor is connected, or is it happening when any of your reactors are connected?

    If it is only happening with one specific reactor I think the most likely cause could be that there is some liquid that has dried on the top part of the reactor, where there is a circuit that is used to sense moisture overflow. If you have any liquid on this (or if it spilled and dried partially) it can trigger the circuit. To fix this I would suggest using a cloth with some alcohol and carefully wiping down the silver tracks on the top of the devices to make sure nothing is there that could be triggering it.

    May 21, 2021 at 12:50 pm #1213
    Tatsuya
    Participant

    Hi Harrison,

    Thank you for the reply.
    >You said it worked well, but then at some point it started showing this error – is that correct?
    Yes. It worked well until last Wednesday, and then every time I try to execute “bash cb.sh”, this error occurs.

    I can’t know if the cause is due to one specific reactor because I have only one reactor.
    However, even after wiping down the lid with alcohol, the same error happened.

    Is there another possible cause?

    Thank you
    Tatsuya

  • Author
    Posts
Viewing 15 posts - 1 through 15 (of 19 total)
1 2
  • You must be logged in to reply to this topic.
Log in/Register
Scroll to top