more troubleshooting

Pioreactor · Dec 5, 2023 · 1e68125 · 1e68125
1 parent f265eb9
commit 1e68125
Show file tree

Hide file tree

Showing 5 changed files with 32 additions and 5 deletions.
diff --git a/developer-guide/25-Calibrations/01-Calibrations.md b/developer-guide/25-Calibrations/01-Calibrations.md
@@ -3,6 +3,10 @@ title: Adding a new calibration type
 slug: /adding-calibration-type
 ---
 
+:::info
+This is subject to change! Currently we don't like how much a developer has to implement (or copy and paste) to create a new calibration. We want to make it easier to design new calibrations.
+:::
+
 Ideally, all calibrations, including od_calibration and pump_calibration, should behave similarly:
 
 1. Interface should have the following:

diff --git a/user-guide/01-getting-started/01c-software-set-up.mdx b/user-guide/01-getting-started/01c-software-set-up.mdx
@@ -79,7 +79,7 @@ What is an image file? It's a file that contains all the required software prein
 
     ![Insert the microSD card](/img/user-guide/place-micro-sd-card.JPG)
 
-8.  Plug power into your Raspberry Pi. LEDs onboard the Raspberry Pi may start to light up. After **a few minutes**, your Pioreactor HAT will briefly blink a blue LED, telling us it is ready.
+8.  Plug power into your Raspberry Pi. LEDs onboard the Raspberry Pi may start to light up momentarily. After **a few minutes**, your Pioreactor HAT will briefly blink a blue LED, telling us it is ready.
 
 <p align="center">
     <video width="520" muted loop="true" autoplay="autoplay">

diff --git a/user-guide/50-Troubleshooting/Hardware troubleshooting.md b/user-guide/50-Troubleshooting/Hardware troubleshooting.md
@@ -11,14 +11,17 @@ If your Pioreactor stops being responsive (and _was previously working_),
    - 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 often see a "Pioreactor HAT must be present" error, but the HAT is definitely attached. 
+### I see a "Pioreactor HAT must be present" error, but the HAT is definitely attached.
 
-Try the following, in order:
+ - 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.
 
- - [SSH](/user-guide/accessing-raspberry-pi) into the Pioreactor that's causing problems. Run `pio version -v`. Does the `firmware` section say `0.0`? If so, run `sudo systemctl restart load_rp2040.service`. Try `pio version -v` again. Move on if `firmware` still says `0.0`.
+### I see "The internal ADC/DAC is not responding. Exiting."
+
+ - [SSH](/user-guide/accessing-raspberry-pi) into the Pioreactor that's causing problems. Run `pio version -v`. Does the `firmware` section say `0.0`? If so, run `sudo systemctl restart load_rp2040.service`. Try `pio version -v` again. Continue below if `firmware` still says `0.0`.
  - Disconnect the heater PCB's flat-flex cable from the HAT (unlock, and pull straight out). Try `pio version -v` again. If this shows something other than `0.0` beside firmware, there could be a problem with your heater PCB. Email us at [email protected].
  - See section [above](/user-guide/troubleshooting-Hardware#my-pioreactor-isnt-responsive-anymore).
 
+
 ### 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.

diff --git a/user-guide/50-Troubleshooting/Networking troubleshooting.md b/user-guide/50-Troubleshooting/Networking troubleshooting.md
@@ -0,0 +1,20 @@
+---
+title: Networking
+slug: /troubleshooting-networks
+---
+
+### My Pioreactor activities start very slowly from the UI
+
+It is possible that your mDNS is being blocked or restricted. If possible, log into your router and enable settings that allow "multicast", or "mDNS", or "IGMP proxing". If you are using a the builtin [local access point](/user-guide/local-access-point), this solution is not the correct one. 
+
+Also, if you are able to provide a permanent IPv4 address to your leader, you can get a significant performance boost by setting the configuration parameter `leader_address` in section `[cluster.topology]` to the IPv4 address.
+
+```
+[cluster.topology]
+# below is an example, your IPv4 may differ:
+leader_address=192.168.0.3
+```
+
+### I can't connect to my Pioreactor's local access point anymore (previously I could)
+
+
diff --git a/user-guide/50-Troubleshooting/Power troubleshooting.md b/user-guide/50-Troubleshooting/Power troubleshooting.md
@@ -3,7 +3,7 @@ title: Power and restarts
 slug: /troubleshooting-power
 ---
 
-#### Brown-outs
+#### Brown-outs and restarts
 
 If you find that your Pioreactor is halting jobs (eg: the UI says _lost_ and stirring/motors have stopped), or you find that your Pioreactor is restarting itself often, this could be due to _brown-outs_.