Timeline for Sampling/transmission limits for USB and Arduino UNO R3
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 21, 2017 at 18:21 | comment | added | Chris Stratton | While this probably can be done on an ATmega328p + serial converter classic arduino, it may in practice be simpler with an ARM-based board having a faster ADC, more speed and resources, and native USB. The advantage of the ATmega solutions is their ubiquity and wide collection of code that works "well enough" for many needs. There's no actual cost advantage when considering comparable suppliers. | |
| Jun 21, 2017 at 9:23 | answer | added | Edgar Bonet | timeline score: 1 | |
| Jun 20, 2017 at 22:05 | answer | added | Jot | timeline score: 0 | |
| Jun 20, 2017 at 14:07 | comment | added | frarugi87 | You can make the arduino sample faster and use a fast enough serial link. For instance setting the prescaler to the value like in the linked post will give you 16us per analog read. You call the two analogread one after the other (32us), then send both data through the serial interface at 512kbps. For instance, if you send 3 bytes (one to sync, the other with the data) you will spend around 58us in the sending. Total: 90us. To achieve a 4.8kHz sampling rate you need to repeat sampling every 208us, so you have time for calculations too | |
| Jun 20, 2017 at 13:37 | review | First posts | |||
| Jun 20, 2017 at 14:10 | |||||
| Jun 20, 2017 at 13:36 | history | asked | Lucas Mol | CC BY-SA 3.0 |