| ??? 11/20/08 08:13 Read: times Msg Score: +1 +2 Good Answer/Helpful -1 Overrated |
#160143 - How to interface anything to anything else Responding to: ???'s previous message |
The following procedure is universally applicable:
1. Study the documentation for the "peripheral" device This will tell you what the device requires for its operation; 2. Study the documentation for the "controller" device This will tell you what features and facilities the device provides for you to use; 3. Study the documentation for any tools, etc, that you will be using eg, assemblers, compilers, etc 4. Do it! Armed with the above information, you know what your "peripheral" device requires, what your "controller" device provides, and how to use your tools - now it's just a question of putting them all together to make your application. Note: The "documentation" includes the Datasheet(s) and/or Manual(s) plus other supporting information available from the supplier - such as application notes, examples, tutorials, etc... Obviously, if you are a newcomer to any (or all) of these things, you will need to spend a significant amount of time in becoming sufficiently familiar with them. The best approach is to start with simple examples before jumping-in to your complete application! Nobody can do this work for you, but you can ask for help when you have specific doubts or questions... |
| Topic | Author | Date |
| Interfacing OF ADC ICL7135 | 01/01/70 00:00 | |
| How to interface anything to anything else | 01/01/70 00:00 | |
| Why not using an ADC with a real ... | 01/01/70 00:00 | |
| ADS7816 is much better | 01/01/70 00:00 | |
| Hardly... | 01/01/70 00:00 | |
| Let him do his assigned task. | 01/01/70 00:00 | |
| We don't know that | 01/01/70 00:00 | |
| That is never the correct answer, though. | 01/01/70 00:00 | |
| probing questions are often preferable | 01/01/70 00:00 | |
That is not the right sort of quesiton either | 01/01/70 00:00 | |
| Almost never a best. | 01/01/70 00:00 | |
| Why not search first? | 01/01/70 00:00 |