Troubleshooting guide - #73

ok i committed mostly small syntactical/grammar or otherwise minor edits.

my review also contains some ideas for bigger changes. feel free to take them or leave them.
If you think there is a comment that is a good idea but not within the scope of this current PR (e.g. if you want to get this done quickly to merge before the miniscope workshop), then feel free to make an issue for that comment so that it can be addressed later.

one more thing - perhaps this has been fixed in more recent hardware revisions of the daq, but it might be worth mentioning adding how to troubleshoot issues relating to a burnt L13 part.

Great work here, Maggie. Thank you for putting this together!

I'm approving b/c this is extremely helpful as is.
I will be doing a more extensive review after I get back in a couple of weeks, as I think there is some room to make things clearer.

A couple things I picked up that I can think of now (and notes for my next review):

• Use only one of the "has the OS detected the daq properly" options. I prefer the Bluetooth & other devices. The device manager can be additional troubleshooting and it is extensively dsecribed in the fw manual.
• There seem to be two different angles on this page: checking things, and errors/artifacts and their resolution. Separating this more, perhaps with a title will be helpful.
• if excess power doesn't damage the daq, then we should edit this: Hardware-Guide/miniscope-daq/data-acq-hardware.html#external-power
• the stripes: if they are caused by a frame mismatch due to a serialization issue, why does the daq need to be restarted? I thought it was just the tether. Also, Cai lab has code to fix this post-hoc in case it happens during acquisition in the middle of an experiment. It would be helpful to mention and link to that.