I just created some trouble reporting forms to use with the call center agents at work when they report problems to my team because we always need to go back to them and ask questions to clarify what the issue is. I see the same thing happen here all the time where someone will write a post tjat "x doesn't work" or "y crashes" and we always need more details. I thinking we should list some of the most common questions here and at tje end I'll either write a short trouble reporting tutorial with a section that cam be copied and pasted, or maybe DJ could create a form that generates a new post with the questions and answers.
I'll get us started with a couple from just the last few days:
Is there an error message displayed in the debug window?
Did the EZ-B make the disconnect sound or reboot?
Please post a copy of your project.
What are the steps to repeat it?
Is your battery charged?
Did you check the fuse?
Are you in AP or Client mode?
Can you access the EZ-B's web page?
Have you tried the servo on a different port?
If we get enough questions, we could even build a self help flowchart to get users through some of the most common issues or determine that a bug report or warranty claim is really needed.
Alan
The n/a may require a unique approach. As we have seen by the previous posts in question, people ignore the options.
Let's try with na to begin with and cross our fingers that it's not the option that everyone will select
I don't want people to feel intimidated to post - specifically if they're just looking for a way to join the community, even if it is in the form of questions that already have answers in the learn section.
I suspect this approach will produce awesome results
Loving the sound of this idea. There may be the odd N/A choice that gets chosen when it shouldn't, but I think overall it will reduce the amount of basic question asked, and as Alan says, the N/A idea leaves it open for new upgrades or changes made to the platform that maybe new to new and seasoned members.