i am going to do a 8052 based project in which we must be interface two s-series 8052 with each other but we have no idea about it. can anybody help me to suggest me how to interface two 8052 together.
forgot satellite ^-^
Lunar bounce.
RFC 2549 - IP over Avian Carriers:
www.faqs.org/.../rfc2549.html
You could instrument a suspended doll with servos allowing one 8051 to transmit information through the doll via interpretative dance. The receiving 8051 can interface to a standard web cam to view, decode, and interpret information from the dance video stream. That 8051 can then transmit via Morse code through an industry standard 60W light bulb. In that case, the receiving 8051 can monitor a temperature sensor that detects when the bulb is powered or not, thus decoding the Morse code characters.
This would probably be really easy to do. I've provided links to web sites where you can get source code, hardware, and ideas to complete this project.
www.instructables.com/.../
www.cs.cmu.edu/.../home.html
" href= "http://www.8051projects.info/expC121.asp">www.8051projects.info/expC121.asp
Note that there MAY be patent infringement issues with some of this technology (believe it or not) so, be careful. Contact all patent holders before going into production!
Jon
That 8051 can then transmit via Morse code through an industry standard 60W light bulb. In that case, the receiving 8051 can monitor a temperature sensor that detects when the bulb is powered or not, Bad idea, in a few years you will not be able to buy "an industry standard 60W light bulb". use a xenon laser instead
Erik
Oh, Jon - for an ARM, maybe; but, for an 8051, that's just silly!
Clearly, what they really need is a semaphore system - much more appropriate to an 8051!
personal.ee.surrey.ac.uk/.../
en.wikipedia.org/.../Semaphore_line
www.douglas-self.com/.../telegraf.htm
Or, maybe, fire beacons:
en.wikipedia.org/.../Beacon
the above responses illustrate what answers a vague question may get. suggest me how to interface two 8052 together as you see above there are many ways. Yes, we are having fun, but better that than a sub-optimum suggestion. To make an optimum suggestion all must be known
now, try to repost with EVERYTHING you know such as distance between the two amount of data environment (industrial, home, office ....) required speed SPECIFIC chip type (ALL the letters and numbers) production volume (weighing between cost and ease of development) are you locked in our chip selection or can you use better alternatives
as said before: "more words do not make you appear stupid, they make you appear precise"
hello sir, your reply shows that you have no idea about microcontroller at all. yaa, i am search about that and get idea that the two microncotroller are interface with each other through serial port(i.e. TXD and RXD pin) of both microcontroller. where one can transmit and another acn receive through serial interfecing and vice verca.
why didnt any of us think of that one
Maybe our minds are just too highly trained...?
Wow. So how much work did you have to spend until you figured that two UART could be used?
Did you at the same time manage to get the required information how to implement serial communication using a UART? What problems did you see? What alternatives did you see how the software could be implemented? Does baudrate matter? Buffer sizes? Response times? Retransmission? Noise immunity?
Did you notice the difference in hardware if using a UART for short-distance communication with another processor on the same PCB in relation to communication over a 5m cable or in relation to a 1000m cable or potentially over the phone network?
thank you for your suggetion and comment. and also sorry for my last comment because i feel that my last comment is not appear in a good manner. so again sorry and thanks ,sir.
you still have not answered
distance between the two amount of data - how much, how often environment (industrial, home, office ....) required speed SPECIFIC chip type (ALL the letters and numbers) production volume (weighing between cost and ease of development) are you locked in your chip selection or can you use better alternatives
yes, UARTs can be used, but are not necessarily the optimum solution, what is depends on the answers to the above.
actually we have to go to do gsm and rfid based automation and security system."In this project there will be sensors inside the home, if anybody comes forcibly to home the sensors output will give information to the system that somebody had came, then it will send the SMS to the owners mobile or make a call to police. Also in this project RFID is used to access or open the door. Controller will check whether the tag identification number provided by the RFID reader have the access permission or not. If have, access permission will be provided to that particular person, i.e. door control signal enabled. Otherwise an alert message will be sent to a predetermined mobile number and alarm will be activated. Each person’s access permissions can be seen on the LCD/ screen. EEPROM is used to keep the owner mobile no.,and also RTC is used to operate the devices automatically in case of mobile faillure. keypad is used to write the mobile no. and edit that one."
thus our problem is that we are unable to join all that one in one microcontroller due to lack of I/O port and space. so we have try to use two microcontroller but two microcontroller can be used through serial interfacing (TXD and RXD) pin which is also needed for GSM and RFID. finally we have decided to use only one microcontroller by removing RTC and some sensors.
now we need your suggetion and comment about that.
Thank you!!!
thus our problem is that we are unable to join all that one in one microcontroller due to lack of I/O port and space. sure you can if you want to stay with a '51 there are 8-porters giving you 64 I/Os, not to mention MMIO or port expanders. Or go for an ARM where the sky is the limit
1) SPI consumes one extra pin (slave select) for each extra peripherial device you connects. May be EEPROM, RFID reader, bus expansion ... You can even connect external UART, or Ethernet over SPI.
2) I2C consumes zero extra pins for connecting more hardware. So if EEPROM uses I2C then you can get a bus expansion with zero extra processor pins.
3) It is trivial to connect latched shift registers, consuming 3 bits (latch,shift,data out) to drive any number of output signals. Or you could instead use shift registers for reading lots of input signals. And they are cheap.
4) 40-pin DIL isn't the only alternative out there.
5) 8051 isn't the only alternative out there.
There are many, many options available when designing a system. A large part of the design is to consider what processor to use and what peripherial hardware. Many times, you same money by getting a bigger processor since you pay very little for the extra peripherial support that gets included with the bigger chips. That is one of the reasons why the ARM chips have taken lots of market ground.