Show Posts
Pages: [1]
1  Using Arduino / Networking, Protocols, and Devices / Re: serial rate of 921600 bps with arduino due ?? on: January 29, 2013, 05:55:38 am
When you said serial I assumed the old RS232.  RS485 is a modern protocol designed to handle longer distances and higher speeds.  Provided the hardware is really RS485 compliant, you should be OK.  Does the Arduino DUE library support RS485?

No, it is not supported as far as I know. Thats why I intend to use a MAX485 converter.
2  Using Arduino / Networking, Protocols, and Devices / Re: serial rate of 921600 bps with arduino due ?? on: January 28, 2013, 05:33:10 pm

regarding spi, i2c:

the device that will send the data to my arduino DUE uses two wire rs485 (wires having a length of approx. 2m). it is an eye tracker camera that outputs the pupil coordinates and some additional information at a rate of 1000Hz (equidistant in time). In other words, I cannot use spi or i2c as suggested nor can I use any additional clock signals to make the transmission more reliable.

So far, I used a RS485/USB adaper to read the data with a windows pc. There were no problems. So the data quality seems to be ok. the only limiting factor appears to be the UART of the arduino due - to be more precise, the library functions dealing with the serial interface.  Would you agree? If not, what determines the maximum speed?

I plan to use MAX485 to convert the data to TTL level. Any bad experience with this circuit?
Do you see any problems arising when trying to send data with 921600bps on another serial line of the DUE?
3  Using Arduino / Networking, Protocols, and Devices / serial rate of 921600 bps with arduino due ?? on: January 26, 2013, 09:48:10 am

Hi,

before I buy an arduino DUE I would like to ask the following:

I intend to use an arduino DUE to read data on a serial channel (UART) at a rate of 921600bps, perform some easy calculations on them (e.g. a checksum calculation) and send them on another serial channel (UART) again with 921600bps. I cannot afford to "loose" bytes, so the connection has to be very robust. The data amount to be read is not very high: an external device is sending them in "bursts" to the arduino due, i.e. 15bytes at the beginning of every millisecond. In the same way the DUE has to output the data on onother serial channel.

Would you say that this task is very challenging for the arduiono DUE or is it rather an easy and feasible task?
Regarding the processor specs that mentioned rates are no problem but perhaps there are limitations caused by the implementation of the serial library.
 
Pages: [1]