Improve troubleshooting pages

docs/docs/Resources/troubleshooting.md

@@ -34,13 +34,13 @@ More comprehensive command line references can be found [here](http://www.comput
 
 `pip freeze`
 
-`sudo reboot`
+`sudo reboot` (Reboot the system)
 
 `sudo shutdown -h now` (The correct way to shut down the Raspberry Pi from the command line. Wait for the green light to stop blinking before removing the power supply.)
 
 `dmesg` (Displays all the kernel output since boot. It’s pretty difficult to read, but sometimes you see things in there about the wifi getting disconnected and so forth.)
 
-`uptime`
+`uptime` (Show how long the system is running and show load average of last minute/5 minutes/15 minutes)
 
 `crontab -l` (Display cron jobs)
 
@@ -142,8 +142,10 @@ Below is correct definition
 
 ### Could not get subg_rfspy state or version. Have you got the right port/device and radio_type?
 
-Basic steps using an Intel Edison with Explorer Board, checking with openaps mmtune to see if it is resolved yet:
+Basic steps using an Intel Edison with Explorer Board, checking with `openaps mmtune` to see if it is resolved yet:
   * Double check that your port in pump.ini is correct
+  * Check that your rig is in close range of your pump
+  * Check that your pump battery is not empty
   * Reboot your rig
   * Run `oref0-runagain`
   * Fully power down and start up your rig

docs/docs/walkthrough/phase-2/troubleshoot-oref0-setup.md

@@ -14,16 +14,17 @@ To stop cron'd jobs and enter an openaps command:  `killall -g openaps; openaps
 
 If you'd like to run multiple commands without having to do `killall -g openaps; ` before each one, you can run `sudo service cron stop` first.
 <br>
-To start cron: `sudo service cron start`
+To start cron: `sudo service cron start` or reboot your rig.
 
 To prevent cron running on initial boot, either clear the `crontab -e` file or "comment out" (`#`) each line of the crontab file.  If you've cleared the crontab file, but would like to enable cron'd tasks, rerun the initial setup script (step 2) and indicate you'd like to use cron.  This will regenerate the configuration.
 
 ## How do I know if it is working?
 
 * Check your pump to see if it is setting temp basals.
 * "Tail" the pump log to see what is is doing: `tail -F /var/log/openaps/pump-loop.log`
-* Check Nightscout to see if it is updating with your information
-* Run commands manually (check out the [openaps toolkit basics here](http://openaps.readthedocs.io/en/latest/docs/openaps-guide/core/medtronic.html#openaps-use-pump)) or see below for some manual troubleshooting steps.
+* A very basic test to see if the pump communication works is to issue a `openaps use pump model`. That should return your pump model. If it displays an error or an empty string your rig can't communicate with your pump.
+* Check Nightscout to see if it is updating with your information. Note: that if Nightscout is not showing your loop is running, it might be running but unable to communicate with Nightscout. In those cases check the pump-loop.log on your rig.
+* Run commands manually (check out the [openaps toolkit basics here](http://openaps.readthedocs.io/en/latest/docs/openaps-guide/core/medtronic.html#openaps-use-pump)) 
 
 ## It's not working yet:
 
@@ -35,7 +36,8 @@ Make sure to check through the following list before asking on Gitter if your se
 * Check to make sure your receiver is plugged in, if you're plugging a receiver in.
 * Don't have data in Nightscout? Make sure there is no trailing slash `/` on the URL that you are entering and that the API secret is correct. Check your Nightscout URL, too - it's one of the most common errors to mistype that. (And FWIW, you shouldn't be typing things like that in the first place: that's what copy and paste are for.)
 * Check and make sure your receiver is >50% charged (if battery low, it may drain the rig battery and prevent it from operating).
-* Check and make sure your pump is in range of the radio stick.
+* Check and make sure your pump is near your rig. Closer is better, e.g. check if it works when the pump and rig are at most 20 inches (50 cm) apart.
+* Check that your pump battery is not empty.
 * Check and make sure your pump is not suspended or stuck in rewind or prime screens. If it's a test pump, you don't even have to fill a reservoir, but put your pinky finger or eraser-end of a pencil in for slight pressure when priming so the pump will "sense" it and stop. Make sure to back out of the prime screen.
 * A reboot may be required after running oref0-setup if the Carelink is unable to communicate with the pump (e.g. you see "Attempting to use a port that is not open" errors in pump-loop.log). Additional Carelink troubleshooting steps can be found in [Dealing with the CareLink USB Stick](http://openaps.readthedocs.io/en/latest/docs/Resources/troubleshooting.html#dealing-with-the-carelink-usb-stick).
 * 512  users - make sure that you have created your static json files as outlined [here](https://openaps.readthedocs.io/en/dev/docs/walkthrough/phase-0/hardware/pump.html) for raw-pump/settings.json, raw-pump/bg-targets-raw.json, and raw-pump/selected-basal-profile.json. You will also have to remove the calls for them from the your get-settings alias.
@@ -60,8 +62,12 @@ You've probably run into an error in your setup where someone has recommended "r
 
  * Start by killing anything that's currently running. ` killall -g openaps`
  * Look and see what's running in your cron. `crontab -l`
+ * If you want to do more than one command of debugging, it's best to disable your cronjobs, use `/etc/init.d/cron stop`. Don't forget to start the cronjobs afterwards or reboot your rig to make sure the cronjobs will be running.
  * Run whichever alias is failing to see what commands it is running. I.e. if the pump loop is failing, it's `openaps pump-loop`, which you can run to show what's inside it by `openaps alias show pump-loop`. 
  * Run each of those commands next individually, and that should give you a better idea of where it's failing or getting stuck. Do this, and share back (if needed) with your troubleshooter about where you think it's getting stuck.  If that still doesn't give you or your troubleshooter enough info, keep drilling down further:
    * **For example**, if your pump-loop.log always shows `Error, retrying` after `Old pumphistory:`, then you'd want to run `openaps refresh-old-pumphistory` manually to reproduce the problem and see if you can get more error details.
    * If necessary, you can drill down further.  So in this example, you might want to run `openaps alias show refresh-old-pumphistory` to see what *that* alias does, and then `openaps gather` to drill down further.
+   * Don't use `2>/dev/null` or `>/dev/null ` parts of commands, because they will hide output of commands
+   * If a command does not return output, check with `echo $?` if the exit code returns `0`. That means OK (no error). If it returns non-zero (e.g. `1`) then the command failed and you need to drill down further. 
    * You can keep drilling down until you get through all the aliases to the actual reports, which can be run manually using a command like `openaps report invoke monitor/status.json` to see the raw unfiltered output with full error details.
+ * Still no luck? Try the [Troubleshooting](http://openaps.readthedocs.io/en/master/docs/Resources/troubleshooting.html) page or ask for help.