Home Forums Assembly/Setup Problem when setting up

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #940
    john.dowe
    Participant

    We are having what seems to be a simple problem, but nothing we try solves it. The system does connect to the reactor, but then it indicates failure in communication. We also tested without the pump, just to be certain that it detects the reactor. It seems to try looking for a multiplex that is not connected (in both cases the control board is connected to M1. I post both outputs here:

    Output with the reactor and pump:
    —–
    root@beaglebone:~/chibio# bash cb.sh
    [2020-03-11 17:37:42 +0000] [1850] [INFO] Starting gunicorn 20.0.4
    [2020-03-11 17:37:42 +0000] [1850] [INFO] Listening at: http://192.168.7.2:5000 (1850)
    [2020-03-11 17:37:42 +0000] [1850] [INFO] Using worker: sync
    [2020-03-11 17:37:42 +0000] [1853] [INFO] Booting worker with pid: 1853
    2020-03-11 17:37:49.864464 Starting watchdog
    2020-03-11 17:37:51.936634 Initialising devices
    2020-03-11 17:37:52.565227 Initialised M1, Device ID: 22544182901295245632
    2020-03-11 17:37:53.807722 Failed Multiplexer Comms 1 times
    2020-03-11 17:37:54.838512 Failed Multiplexer Comms 2 times
    2020-03-11 17:37:55.866184 Failed Multiplexer Comms 3 times
    Failed to recover multiplexer on device M4
    2020-03-11 17:37:57.902415 Failed Multiplexer Comms 4 times
    Failed to recover multiplexer on device M4
    2020-03-11 17:37:59.938399 Failed Multiplexer Comms 5 times
    Failed to recover multiplexer on device M4
    2020-03-11 17:38:02.174284 Failed Multiplexer Comms 6 times
    Failed to recover multiplexer on device M4
    2020-03-11 17:38:04.210552 Failed Multiplexer Comms 7 times
    Failed to recover multiplexer on device M4
    2020-03-11 17:38:06.246373 Failed Multiplexer Comms 8 times
    Failed to recover multiplexer on device M4
    2020-03-11 17:38:08.282485 Failed Multiplexer Comms 9 times
    Failed to recover multiplexer on device M4
    2020-03-11 17:38:10.318414 Failed Multiplexer Comms 10 times
    Failed to recover multiplexer on device M4
    2020-03-11 17:38:12.354480 Failed Multiplexer Comms 11 times
    [2020-03-11 17:38:12 +0000] [1850] [CRITICAL] WORKER TIMEOUT (pid:1853)
    [2020-03-11 17:38:13 +0000] [1853] [INFO] Worker exiting (pid: 1853)
    [2020-03-11 17:38:13 +0000] [1908] [INFO] Booting worker with pid: 1908
    2020-03-11 17:38:21.045143 Starting watchdog
    2020-03-11 17:38:23.118217 Initialising devices
    2020-03-11 17:38:24.150581 Failed Multiplexer Comms 1 times
    2020-03-11 17:38:25.178186 Failed Multiplexer Comms 2 times
    2020-03-11 17:38:26.206416 Failed Multiplexer Comms 3 times
    Failed to recover multiplexer on device M0
    2020-03-11 17:38:28.242362 Failed Multiplexer Comms 4 times
    Failed to recover multiplexer on device M0

    —-
    output of reactor without pump:

    [2020-03-11 17:36:02 +0000] [1836] [INFO] Starting gunicorn 20.0.4
    [2020-03-11 17:36:02 +0000] [1836] [INFO] Listening at: http://192.168.7.2:5000 (1836)
    [2020-03-11 17:36:02 +0000] [1836] [INFO] Using worker: sync
    [2020-03-11 17:36:02 +0000] [1840] [INFO] Booting worker with pid: 1840
    2020-03-11 17:36:09.833126 Starting watchdog
    2020-03-11 17:36:11.917594 Initialising devices
    2020-03-11 17:36:12.091846 Failed Pumps comms 1 times on device M1
    2020-03-11 17:36:12.114216 Failed Pumps comms 2 times on device M1
    2020-03-11 17:36:12.136633 Failed Pumps comms 3 times on device M1
    2020-03-11 17:36:12.158793 Failed Pumps comms 4 times on device M1
    2020-03-11 17:36:12.181177 Failed Pumps comms 5 times on device M1
    2020-03-11 17:36:12.203687 Failed Pumps comms 6 times on device M1
    2020-03-11 17:36:12.226070 Failed Pumps comms 7 times on device M1
    2020-03-11 17:36:12.248355 Failed Pumps comms 8 times on device M1
    2020-03-11 17:36:12.270638 Failed Pumps comms 9 times on device M1
    2020-03-11 17:36:12.292898 Failed Pumps comms 10 times on device M1
    2020-03-11 17:36:12.315275 Failed Pumps comms 11 times on device M1
    Failed to communicate to a device 10 times. Disabling hardware and software!
    [2020-03-11 17:36:12 +0000] [1836] [INFO] Shutting down: Master
    [2020-03-11 17:36:12 +0000] [1836] [INFO] Reason: App failed to load.

    The devices were acquired from LabMaker. We would appreciate any help
    Thanks

    #1041
    harrison
    Keymaster

    Hi John, it looks like a faulty Multiplexer PCB. Has Labmaker gotten back to you on this front?

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