I want to to use a non-digital analogon to explain:
imagine you want to do free-style BMX-biking:
Your momentary knowledge about riding a BMX-bike in an artistic way is:
- I can ride a bike on a street, I am a little shaky while riding but basically it works.
- I can visually distinguish between a street-racebike, a mountain-bike and a downhill-bike and a BMX-bike.
Your momentary approach is:
"can you please show me how you are doing back-flips in the half-pipe?
I will watch you driving and then I try on my own"
Well this won't work. You don't start artistic back-flips in the half-pipe if you are still a little shaky on bike-riding.
You start with much smaller and easier exercises.
Your own brain has to learn how to move your body for things like jumps.
It is very different to do jumps coming from the low-side jumping up in the air
or coming from the up-side jumping down a halfpipe.
Well this analogon does not work out in all details.
In programming you can't break your bones - of course
You don't need to do training on the braincells responsible for balancing
If a bug occurs you need knowledge about how programming works and what could cause this bug.
As you are working with electronic parts you need at least a basic knowledge about electronics because the parts are not superstandardised like ready to use USB- or blue-tooth-devices.
pre-programmed text that lists up what you have to do:
You are welcome on this forum! You are working on an informatic project and what is most needed in an informatic project is information imagine: do the other users here in the forum have a clear picture of what you are trying to do?
To speed up finishing your project you should invest some time into writing additional information I'm 100% sure that this WILL speed up finishing your project.
So please go through this checklist and if you find an item you haven't posted yet post it
- did you write which exact type of microcontroller you are using?
- description of your programming skills and knowledge
- description of your knowledge about electronics
- description of the functionality you want to have written in normal works avoiding programming terms
- do you have an oscilloscope? Yes / No
- do you have a digital multimeter (DMM) Yes / No)
- your age
- did you post your complete sketch?
- if relevant did you post a link to a datasheet of each component you are using?
- if relevant did you post a handdrawn schematic or your wiring?
- if you got a compiler-error. Did you post the complete compiler-output into a code-section?
If you don't post all this information because you want a "quick answer" to your detail problem It is very likely to turn out that all that happens is having mutliple waiting-times with mutliple asking back for details until the other users do have a clear picture of what you want to do.
best regards Stefan