Home Forums Assembly/Setup Failed to communicate to multiplexer (upon first set-up)

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #1563
    sophey
    Participant

    I am trying to set up the chi.bio’s for the first time and followed all instructions in the manuals. Still I can’t get the cb.sh software to run.
    I get the following error:

    ….
    2022-08-30 14:27:41.501374 Failed Multiplexer Comms 21 times
    2022-08-30 14:27:41.503269Failed to recover multiplexer on device M7
    2022-08-30 14:27:41.504693Failed to communicate to Multiplexer 20 times. Disabling hardware and software!
    [2022-08-30 14:27:41 +0000] [1825] [INFO] Shutting down: Master
    [2022-08-30 14:27:41 +0000] [1825] [INFO] Reason: App failed to load.

    Would appreciate any help.

    Thanks a lot,
    Sophia

    #1564
    harrison
    Keymaster

    Hello Sophey,

    I’d try unplugging and plugging everything back in. Then, also try starting the software with no reactors connected to the control computer.
    Assuming you have done that, double checked all the connections are correct, power is on, etc, then I’d say the most likely explanation is the reactor may have been assembled with a defect or picked up one during shipping. In that case there isn’t a whole lot you or I can do; I’d recommend emailing Labmaker and letting them know (send a screenshot of the error), and they should be able to sort it out for you

    harrison

    #1565
    sophey
    Participant

    I just tried to run the software without any reactor connected and that worked. I then connected one (m7) and that one I can see online but when I press the “start” button I get these error messages:

    2022-08-30 14:55:17.196885 Trying to communicate with absent device – bug in software!. Disabling hardware and software!
    [2022-08-30 14:55:17 +0000] [3254] [INFO] Shutting down: Master
    [2022-08-30 14:55:17 +0000] [3254] [INFO] Reason: App failed to load.

    I did download the newest release of both cb.sh and app.py from github and replaced teh old files as it was suggested.

    • This reply was modified 2 years, 2 months ago by sophey.
    #1567
    sophey
    Participant

    It seems to have resolved itself. I will come back if the error returns and persists – thanks for the super fast reply.

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