Thanks Cam.
I had forgotten that detail about the pump running extra to maintaining a constant volume (it had been a long week) but I never knew I could over ride that! Very helpful.
Now that I have a bit more of an understanding of the code from what you said, and updated info here Experiment profile schema and syntax | Pioreactor Docs it might be possible for Turbidostat to work if I can figure out how to track the dilution Turbidostat runs and use that to calculate density from the volume added.
Is there a lower limit to how short the duration can be between Turbidostat cycles (<=0.001hr or 0)?
Unfortunately I haven’t been able to test using Turbidostat further because the UI is not recognize any removing of liquid. I tried this but no luck Pioreactor not accounting for removed volume in turbidostat automation and hitting maximal volume and cancelling automation
max working volume = 15
Any suggestions? The only way I can get the UI volume down is rebooting the pioreactor (the manual initiated pumping or volume override in the dosing controls don’t seem to have effect) - Might need a new topic for the issues with the volume tracking
I think it would more logical for me to just write code to determine density directly (using a titration style dilution to a predetermined OD for more accuracy) and handle the liquid movement etc. but I haven’t had any success writing the code with my limited coding experience so I’m continuing to follow the advice I’ve gotten and trying to patch something together using existing dosing automations (which brings up new challenges of understanding the intricacies of the automations’ code and syntax)