Now, as for standard RS-232-type serial done with TTL logic levels (ie: signal voltage levels 0 to 5V), via a UART (piece of hardware that allows this type of asynchronous communication protocol), I have written C++ code on a PC and on a standard Arduino (ex: Nano, Uno, or Pro Mini-under $10 cost + $2 external UART) which communicates at 250kbaud (though 2Mbaud is possible on an Arduino Uno-see Connor Wolf's answer here). Standard RS-232 0-5V (TTL) Serial, and example: USB3.1 serial communication, if a device supports it, however, can be done up to 10Gbps. Note that some Ethernet devices can communicate up to 1000 MHz (like the Orange Pi Plus), but the Intel Galileo only goes up to 100 MHz, according to the link above. Is what you mean simply that you want 10Mbps (megabit per second) transmission rates? If so, the Arduino Intel Galileo can do SPI serial communication at a rate of up to 25MHz, or you can do Ethernet communication with this board up to 10 MHz or 100 MHz (see previous link as well). Perhaps this is because when I hear "pulse train" I think you mean you want to read pulse widths in order to obtain data, ie: like the PPM pulse train used in Radio Control communication signals. Your phrasing of "receive a pulse train at a minimum speed of 10MHz" is quite confusing to me. For synchronous vs asynchronous and what that means, see Majenko's really good answer.
I'll also mention a few devices and show some comparisons. The other answers have really good info in them, but I'd still like to expound a bit on the different types of serial protocols, and how they vary in speed. The down side is that this usually means the maximum speed you can run at is actually slightly lower since the effective size of the data being transmitted is increased. This keeps the number of wires to a minimum yet allows high speed data transfer. Some synchronous systems (such as Ethernet), instead of providing the clock as a discrete wire, encode the clock into the data stream. Speeds in the tens of megahertz are common. This is how things like SPI and I☬ work, and very high baud rates can be achieved. The receiver uses the incoming clock to know precisely when it should look at the data line to receive a bit of data. The other kind of serial, synchronous, uses an extra wire for the transmitting (or master) end of the connection to send the clock to the receiving ( slave) end. So it's "safer" to use a lower baud rate which gives more reliable communication to a greater variety of devices. Lower baud rates are easer to get close to, but higher ones are much harder. That's due to the way that the internal UART hardware works - it divides the system clock into finer and finer bits to get as close to the requested baud rate as possible. Note that on many systems (Arduino included) when you ask for one baud rate you actually get a slightly different baud rate. The more accurately the two ends can agree on their baud rates the faster you can transfer data. Both ends of the line have to agree on the same speed (baud rate) and any deviation from that causes transmission errors. With asynchronous, which is what serial as in UART and RS-232 are, it's all down to how accurate a system's clock is. Do I need something faster than this? Or will this suffice? I'm more interested in the theory than the device it is more valuable for me to bolster my education than for me to solve my problem (though it needs to be solved).īasically there are two kinds of serial: Asynchronous and Synchronous. I just want to understand what I can do to receive this data stream.
#Serial communication protocol example how to
Programming in the Arduino language is not a problem, I already know how to do this. The system that I currently have to receive the data is an Arduino certified product: I will then program it to process this data.
I know that I need to have a system that can receive a pulse train at a minimum speed of 10MHz (hopefully up to 500MHz). I am new to electrical engineering and I am trying to teach myself some basic ideas for my research project - with much frustration. I know something is wrong with my understanding of it all. I don't know how these systems receive data at such a high speed if common baud rates are so low. These data streams are able to be read on simple computers that you can buy from Staples. I know that some serial configurations through Firewire or Ethernet can transfer data at speeds that are orders of magnitude higher than 115.2 kBaud. However, also from what I understand there are fast ways of transferring data serially.
By slow, I mean that the fastest common rate of transmission of data is 115.2 kBaud. Otherwise worded: How do I resolve my understanding about baud rates and high speed serial data transfer?įrom what I understand, serial communication is relatively slow.
0 kommentar(er)
