I have asked three questions on the motors section of the forum. The answers were under whelming. The people who respond appear to be more interested in nit picking rather than helping. As my last post illustrates, titled "Linear actuator reverse conflict in code", in which the responders want to fix my hard ware which works fine, instead of helping me fix my code where the problem lies. I have a lot of expertise in a variety of fields which I hope to use to help people on the forum, coding is not one of them. So are there some protocols that I am not aware of to solicit better answers?
Hi.
I have taken a short look at the thread mentioned in this one.
You are asking for help here, keep that in mind.
You are also asking for help over there, keep that in mind too.
If someone asks for specific information, do not tell them that that is not where the problem is.
Give them the information they are asking for, and tell them why you think your problem can't be in there.
If you would have done so at the first request, you would have saved yourself 7 of 12 replies, and embarrassing yourself by getting rude.
Telling them you tested it without giving any details, will not help you.
Calling names or getting rude after 2 attempts by a responder isn't going to help you either.
If you are going to assume anything, assume that these questions have some purpose (which you might yet have missed).
In short:
Take any advise given, and be thankful for it.
If you are asking a question, do not assume everybody knows what you are talking about, assume they don't.
So you have to provide ALL information that might be of any help to get the help you need.
Be polite and thankful (you do not have to express your thanks for every bit of help per se, but that won't harm either).
Ater all, YOU are the one that needs help and depends on others to get it.
Hi MAS3,
You make some excellent points and they will hopefully help me in getting better answers to my questions in the future, thank you. In my replys I was trying to highlight and focus the respondents to the code where my problem lies and I have very little expertise in, as opposed to the hardware where I have a lot of expertise in. But your main point of explaining the hardware in more detail to begin with is a good starting protocol.
When I am trying to diagnose a problem it is important to me to have a full picture even if it happens that lots of the stuff in that picture is ultimately irrelevant.
My brain does not focus properly on a problem if it is concerned that there is missing information - even if the missing info is irrelevant. At the initial stages I cannot know that it is irrelevant.
If you read through 20 or 30 Threads you should easily see many cases in which the problems were not where the questioner thought they were. Your case might be the exception - but I don't know that.
...R
Hi Robin2,
Thank you for your response, your reasons for a full description are very logical. I had started my thread with a general description but by reply #10 I had rendered a very detailed explanation of my hardware. Perhaps if you have the time you might take look at my code in my post on the motors forum under the title "Linear actuator reverse conflict in code".