Salem
Posting Sage
11,531 posts since Dec 2005
Reputation Points: 5,862
Solved Threads: 953
Without having a circuit diagram or something, and a whole bunch of other details, there isn't a lot we can say. Even if you posted it all, it would still be tantamount to us doing your homework for you.
You need to have a nice long reading session of the links posted so far and have a go at it yourself.
Then perhaps you can post some code, and perhaps a comment like "this is supposed to send TX high, but it doesn't". Now that is something we could help you with.
But comments like "there's a keypad with 10 buttons" tells us nothing.
Salem
Posting Sage
11,531 posts since Dec 2005
Reputation Points: 5,862
Solved Threads: 953
There's a whole bunch of information (on IR and motors) on the site I posted way back in post #2, all for the sake of you showing some effort to read it.
You're not going to learn this stuff overnight, and we're not going to post it here over several hundred messages for you to digest one bite at a time.
It's like you're incapable of helping yourself.
I mean, if you posted "I've read , but "this sentence" is confusing me", that at least would show that you're showing some initiative. But all you're doing is posting the same old "help me, I'm lazy" posts.
TBH, this kind of low-level development requires a hell of a lot more enthusiasm to read up on and try things for yourself than what you're showing at the moment. You're going to need that to investigate what's happened when it all does wrong (as it will do). If the only debug you have is a flashing LED, then you've got to get creative!.
Unlike portable ANSI-C which will work pretty much anywhere, any code you produce will only work on YOUR hardware. Which pretty much means you're on your own, and all we can do is offer suggestions (rather than answers).
Do you even have a hardware kit to hand? If so, tell us which one.
And I don't mean something vague. Be specific, post URLs.
Here's another forum which has lots of info on low-level programming / hardware development.
http://www.avrfreaks.net/
Salem
Posting Sage
11,531 posts since Dec 2005
Reputation Points: 5,862
Solved Threads: 953
^ its presumptuous of you to tell him what his project needs or doesnt need. how do you know he's not building an array of IR detectors?
^^ if you want to connect with a commercial off-the-shelf IR sensor, its typically just three signal lines: RD (receive data), TD (transmit data), and SG (signal ground) *
use a DB-sub9 (aka DB-9) cable to connect the IR sensor to a RS-232 serial connector on the host computer. if you dont have DB-9 connectors on your computer you can use a USB - RS232 adapter, typically sold for ~$10 on any peripheral distributor's site.
you can also make your own cable if you need to, just get a female DB-9 connector for connecting to the PC (or the USB/RS232 adapter) , and connect a wire to each of the required signals: pin2=RD, pin3=TD, pin5=SG. the other end of the lines will connect to whatever connector allows you to connect with the RX , TX and GND of the IR device communication port.
if you're building your own IR sensor of of discrete and active components then you will need to use a UART in order to interface with the PC.
you will have to give more information about what you're trying to accomplish and what you've already done so far if you want more help.
one hint: please don't use abbreviations, or what you think passes as "chat speak". it's very hard to understand what you're saying.
(* note, RD/TD/SG is the standard configuration. some may also employ handshaking lines, which will use additional pins)
.
jephthah
Posting Maven
2,587 posts since Feb 2008
Reputation Points: 2,143
Solved Threads: 179
i'm sorry, what the hell do i what?
i don't know, i was just reading what you wrote.
You probably don't need lots of IR sensors.
jephthah
Posting Maven
2,587 posts since Feb 2008
Reputation Points: 2,143
Solved Threads: 179