![]() ![]() Luckily the sensor comes equipped with both an on-chip FIFO that can store 32 sensor values. My problem is that when I use the Arduino SD library writing is slow: 25 ms per print() operation, which gives me a maximum of 40 Hz which is laughable compared to the 100-800Hz data rate of my sensor. Data should be logged to an SD-card found on a "Arduino Wireless SD shield". If you don't feel comfortable revealing more details as to what problem you are attempting to solve, then this is about the best non-specific advice that I can offer.I have need for a data logging application running on a "Arduino compatible" chipKit UNO32 board, with a connected sensor. If there are specific constraints particular to your project, post them. ![]() If you are looking for a lower level of understanding of the I2C protocol, start here and look into how the library really works on a low level ( Google it ) - but from what you have described, what /u/jzzsxm said is a sane way to way to tackle this problem. It abstracts the low level details of the I2C protocol out, which is something that you should look into for a deeper understanding of the "devil is in the details" issues specific to the I2C protocol the library offers a very simple, yet fairly extensible way of interfacing with the protocol to get you moving toward your goal in a relatively short amount of time. But I can tell you that for anything that has to do with PWM and other timing specific ( clock sync dependent ) issues, the Wire library makes I2C ( a very timing dependent protocol, and a robust one for turning things on and off as needed ) very easy to use. My understanding of what you ( OP ) are attempting to accomplish with regards to your problem is limited.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |