Hardware and operation
My Pioreactor isn't responsive anymore
If your Pioreactor stops being responsive (and was previously working),
- For Raspberry Pi 3A model, is the Pi's green LED constantly on?
- there should be a short, perhaps caused by damage. Power off, and disconnect the heater PCB's flat-flex cable from the HAT (unlock, and pull straight out), and power on. Is the Pioreactor responsive now? Investigate the heater PCB for damage.
I see a "Pioreactor HAT must be present" error, but the HAT is definitely attached.
- Is your HAT directly connected to the Raspberry Pi, or are you using a long cable to connect them? Long cables tend to degrade signals, which can cause communication problems between the HAT and RPi.
I see "The internal ADC/DAC is not responding. Exiting."
- SSH into the Pioreactor that's causing problems. Run
pio version -v. Does thefirmwaresection say0.0? If so, runsudo systemctl restart load_rp2040.service. Trypio version -vagain. Continue below iffirmwarestill says0.0. - Disconnect the heater PCB's flat-flex cable from the HAT (unlock, and pull straight out). Try
pio version -vagain. If this shows something other than0.0beside firmware, there could be a problem with your heater PCB. Email us at support@pioreactor.com. - See section above.
I see "Heating PCB must be attached to Pioreactor HAT" or Heating PCB must be present to measure RPM." errors.
Check the connection between the 3" flat-flex-cable and the HAT, and the connection on the heater PCB. It's possible that the connector could have been pulled out by accident.
I'm having trouble with Pioreactor's stirring.
See our stirring troubleshooting docs.
OD readings are zero, or optical self-tests fail
Start with the self-test results. A zero reading or division-by-zero error alone does not identify a faulty component.
- If all photodiodes fail to respond, check the shared IR light source first. Follow the optics assembly guide for your model (20ml v1.5 or 40ml v1.5): confirm the IR LED is in the IR pocket, connected to HAT channel A for the standard assembly, and that its exposed leads do not touch.
- If only one channel fails, inspect that channel's cable and board connectors for loose connections or damaged pins.
Power off and disconnect power before touching wiring or connectors. Contact support if pins are bent or damage is suspected. Support may suggest swapping a compatible, known-good Eye-Spy board: a fault that follows the board helps locate the problem, but does not identify the precise electrical failure.
After correcting a connection, rerun the self-test. If failures remain, send support the results, logs, configuration, and clear photos of the optical wiring.