westaust55
Moderator
This forum is run by Revolution Education and I believe they are relative lenient in what matters are discussed here including deviations and humour subject to complying with the requirements of the forum protocol to respect others, no spam, no advertising and active promoting of competitors microcontroller products. Most of this is outlined in the sticky ”ReadMe First!” thread at the top of the Active forum.
http://www.picaxeforum.co.uk/showthread.php?7679-Read-Me-First!
It has been noted by many newcomers that this forum has a very friendly approach to responses and a response time faster than many have expected. That is a good thing and something we as members can all be proud about.
The following is my personal opinion and open to challenge/comment but I put this forward as a basis for answering question. I acknowledge that everyone has their own style in answering questions on the forum.
I have noticed that from time to time when newcomers to this forum with minimal electronics and/or programming experience raise a question there can be a tendency for some to not answer the specific question but provide recommendations for alternative solutions.
There will be times when while the OP has been vague, we can make an educated analysis (guess) and provide a response based on typical past problems that may quickly resolve the question. (eg fresh batteries, interconnect ground/0V of multiple supplies, pull down for SeriaIn pin, etc)
Where the enquiring post does not provide adequate information but intimates to a particular set of components, rather than dive in and suggest an alternative line of hardware consider:
1. Asking for clarification about what is wanted, what are the operating parameters, space limitations, budgets , project urgency (school project), etc
2. If not clear first ask what the OP has already purchased – could make them feel dismal if told up front their purchase is inadequate
3. Try to answer the question originally asked and if the proposed hardware is totally inadequate, then explain clearly why not and how it can be resolve using recommended parts.
4. Keep in mind that what may be easy or simple to you may be confusing to someone with little or no experience in programming and more so in the case of electronics design/construction/faultfinding.
5. Respect others (and akin to religion) do not force you ideas onto others.
Some time ago now there was a thread (or two) on trying to have a proforma for those with questions to follow to explain exactly what they have in hardware and software.
Of recent newcomers seemingly are more vague about their actual project objectives, hardware and what code they have developed to date.
For those newcomers reading please try to explain clearly in plain English (without slang and abbreviations) what you have purchased, post your schematic diagram for the circuitry if something has already been assembled and your BASIC program code.
Also consider including a clear photo of the project hardware. For the best photos try to have a plain background, that the photo perpendicular to the boards/displays, include the wiring .
If it is a soldered board a photo of both sides.
If a breadboard then try to keep the wiring tidy so folks can trace through on the photo and try to use different colours for different signals where possible.
Include a link to the datasheet for the main and in particular troublesome components you have in the project.
If wanting recommendations on what (eg sensor/display) to purchase for a particular task try and indicate any physical restrictions, your budget, time to buy/complete project etc.
If you have not indicated in your forum profile, tell us where you are located (at least which continent) so folks can try to recommend a source relatively close to you. It may be cheap coming from the other side of the planet but not of much value if it takes 2 weeks to arrive and your school project is due in a week.
On that note, I open the discussion to other PICAXE forum members . . . .
http://www.picaxeforum.co.uk/showthread.php?7679-Read-Me-First!
It has been noted by many newcomers that this forum has a very friendly approach to responses and a response time faster than many have expected. That is a good thing and something we as members can all be proud about.
The following is my personal opinion and open to challenge/comment but I put this forward as a basis for answering question. I acknowledge that everyone has their own style in answering questions on the forum.
I have noticed that from time to time when newcomers to this forum with minimal electronics and/or programming experience raise a question there can be a tendency for some to not answer the specific question but provide recommendations for alternative solutions.
There will be times when while the OP has been vague, we can make an educated analysis (guess) and provide a response based on typical past problems that may quickly resolve the question. (eg fresh batteries, interconnect ground/0V of multiple supplies, pull down for SeriaIn pin, etc)
Where the enquiring post does not provide adequate information but intimates to a particular set of components, rather than dive in and suggest an alternative line of hardware consider:
1. Asking for clarification about what is wanted, what are the operating parameters, space limitations, budgets , project urgency (school project), etc
2. If not clear first ask what the OP has already purchased – could make them feel dismal if told up front their purchase is inadequate
3. Try to answer the question originally asked and if the proposed hardware is totally inadequate, then explain clearly why not and how it can be resolve using recommended parts.
4. Keep in mind that what may be easy or simple to you may be confusing to someone with little or no experience in programming and more so in the case of electronics design/construction/faultfinding.
5. Respect others (and akin to religion) do not force you ideas onto others.
Some time ago now there was a thread (or two) on trying to have a proforma for those with questions to follow to explain exactly what they have in hardware and software.
Of recent newcomers seemingly are more vague about their actual project objectives, hardware and what code they have developed to date.
For those newcomers reading please try to explain clearly in plain English (without slang and abbreviations) what you have purchased, post your schematic diagram for the circuitry if something has already been assembled and your BASIC program code.
Also consider including a clear photo of the project hardware. For the best photos try to have a plain background, that the photo perpendicular to the boards/displays, include the wiring .
If it is a soldered board a photo of both sides.
If a breadboard then try to keep the wiring tidy so folks can trace through on the photo and try to use different colours for different signals where possible.
Include a link to the datasheet for the main and in particular troublesome components you have in the project.
If wanting recommendations on what (eg sensor/display) to purchase for a particular task try and indicate any physical restrictions, your budget, time to buy/complete project etc.
If you have not indicated in your forum profile, tell us where you are located (at least which continent) so folks can try to recommend a source relatively close to you. It may be cheap coming from the other side of the planet but not of much value if it takes 2 weeks to arrive and your school project is due in a week.
On that note, I open the discussion to other PICAXE forum members . . . .