Old Grey wrote:PSIG wrote:I'm thinking a new Wiki section along the lines of "Board Testing and Troubleshooting" or some such.
I was just thinking about that. If nothing goes wrong you don't need to know much, like the basics of Arduino, but if something does go wrong, then it is a super hard slog if you don't know the basics. Either way a troubleshooting would be good, but could also end up massive.
Yeah, there's a lot to go through, if you wanted to go back in time and bring issues forward for the Wiki.
Maybe, in parallel, forum topics could be set up under a "Troubleshooting" forum section, broken out into sub-sections based on OS, Speeduino board revision and such.
Code: Select allSpeeduino
|
+- Existing topics
|
+- Troubleshooting (section header)
\
+- Speeduino Hardware (sub-section header)
| \
| +- V0.3.x (topics)
| +- V0.4.x (topics)
| +- V0.X.x (topics)
|
+- Speeduino Firmware (sub-section header)
| \
| +- V0.3.x (topics)
| +- V0.4.x (topics)
| +- V0.X.x (topics)
|
+- Tuner Studio (sub-section header)
|
+- OS (sub-section header)
| \
| +- Linux (topics)
| +- Windows (topics)
| +- OSx (topics)
|
+- General (sub-section header)
\
+- Arduino (topics)
+- Vehicle / Engine (topics)
If the users would cooperate, the Wiki might write itself. Otherwise, might need some active administration / moderation. And by "cooperate", I mean that if a user has a project going on and encounters an issue, start a topic in the "Troubleshooting" section most appropriate for the issue and post a link in their project to that "Troubleshooting" topic they started, maybe even linking back from the "Troubleshooting" topic to their project. Also, ask questions about "this" or "that" in troubleshooting... may be too complicated....