As greater numbers of OpenROVs are getting built, we're getting more data on the kinds of technical challenges people encounter during construction and operation. As the various causes for anomalies are figured out, we're also getting data on how those problems can be solved. Well understood failures are an excellent source of data, so I thought it would be good to start organizing common failures modes and their causes. In the short term, these data can be used for simple troubleshooting, but as the network of failures and causes gets more complicated, I think we'll also start being able to construct an "anomaly model" that gives us an overarching idea of the vulnerabilities of the ROV and ways to manage and prevent failure in general.
As an example, I've constructed a (still quite incomplete) flow chart of possible causes for one specific failure- namely, not being able to connect to OpenROV Cockpit. I'm sure that even this tree of problems and solutions can be greatly expanded based on observations we have all made so far. My dream is that we'd be able to have a sort of 'living anomaly management flow chart' that everyone can contribute to as problems and solutions are identified.
By the way, if you already have a specific modification to this flow chart, you can edit it as a Google Doc here (you'll have to install lucidchart first). Also, if anyone can suggest a better cloud-based, corroboration-friendly flow chart system to use, let me know!