Errors

[harrison]

Hello,

It seems there might be a few different things at play here.

For the Broken Pipe and winch errors – these are errors (If I recall correctly) arising from the actual connection between the Beaglebone Black and your computer controlling it (i.e. PuTTy is unhappy). For example, your computer might be set to de-power or shut down USB devices/connections after some period of inactivity. Hence it is causing issues (which would explain why your colleague is able to run things properly from the python but not the GUI). For this case I would strongly recommend trying another computer, or trying to figure out what it is that yours is unhappy with.

The above one would expect to be similar regardless of any hardware fault (i.e. same error would appear for every reactor).

The second thing you mention (those errors + M1 not working) is indicative of a hardware fault in that particular reactor, potentially due to liquid ingress, or bad hardware assembly in the first place. I would recommend taking the sides off that reactor and looking at the circuit to see if there is any obvious damage. If it is an assembly fault Labmaker might be able to replace it for you

Harrison

[Nuha]

I thought the same regarding the computer, but I disregarded it since (1) I’m using the same computer I used last year (which is an iMAC not PC) and it’s the first time I see the errors (2) if it has to do with inactivity I expect the disconnection to happen around the same time every time I run an experiment, but it is variable and it has only gotten worse (I ran an experiment before updating everything and it stopped after 26 hours, and after updating I’m getting these errors within an hour or less into the experiment).

Updates for the iMAC have also been installed recently, not sure if that plays a role. I’ll double check and try with a different computer just to be sure. Thank for the prompt response!

[harrison]

To be honest I have never used a mac myself and have no idea what rare/unexpected errors might occur. In our lab we have reactors on both windows and linux PCs without such issues.

[Nuha]

So it turned out there was downtime on the iMAC, when adjusted I stopped seeing the errors I mentioned thankfully. But, I do get one error not too often that stops the whole thing, “Failed to disconnect multiplexer”. This error also becomes more often when I connect more than 2 reactors to the beaglebone. I also get pump connection errors hours into the experiment sometimes, but rarely does it stop the experiment. Any suggestions to why that is happening? I’m thinking to try different beaglebones, and try a new computer afterwards to compare.

[harrison]

That error can happen if there is a bad connection somewhere in the electronics – or if the system overflows any liquid which lands on the moisture sensing tracks that causes it to crash (deliberately in that case). Note that it could even be that water condenses on the test tube exterior and then ends up on the moisture sensing (silver lines on top surface) and triggers it.
What version of reactors are you using? I assume as above you have the latest version of the Beaglebone software?

[Author]

Posts