Hi Kate,
1) We can’t do this since the Beaglebone is actively sending digital commands via I2C to the reactors, hence there needs to be that intermediary there to format and control each reactor. This being said, people have worked on means to make the web interface more robust, in fact someone put an update on this on Github last week that might be worth checking out: https://github.com/HarrisonSteel/ChiBio/pull/12
2) We haven’t integrated this yet but it should be fairly straightforward. You could just put a hard-coded stop at a certain cycle count into the code. For example write a custom programme which takes as input a number of cycles (corresponding to number of minutes) you want the experiment to run for, then it does a logic check with each cycle of the main software loop and when it reaches the set number of measurement cycles it turns off experiment.
3) We have not tried adding this error logging, in practice it would be quite straightforward to just write to an external file; you could just re-define the print statements throughout to print_custom which writes into a file.
.
