Non-blocking analogRead()'s for Arduino

The goal of this project is to get non-blocking analogRead()'s added to Arduino core libraries.

Jacob Christ

Following Follow project

Liked Like project

Become a Hackaday.io member

Just one more thing

To make the experience fit your profile, pick a username and tell us what interests you.

OK, I'm done! Skip

Similar projects worth following

The 2017 Hackaday Prize

View Gallery

Description

The goal of this project is to get non-blocking analogRead()'s added to Arduino core libraries. I recently made a change to chipKIT-core libraries to add this feature. It had the surprising effect of making existing hardware 2.5 to 5 times faster.

1. The primary challenge this project addresses is the ability to wrangle hardheaded Arduino developers into taking pushes from down stream
2. I'm not sure I can solve this problem of hardheaded developers, not am I sure I want to being one myself, but I'll try.
3. This project makes the world better by breathing new life into old hardware!
4. See picture to the left.
5. These changes have already been published in the chipKIT-core repo, but a Arduino version is needed. https://github.com/chipkit32/chipKIT-core/
6. BSD 3-Clause

Files

chipKIT-core 1.4.0 Non-Blocking Analog Reads.pdf Original foils I created after implementing in chipKIT-core Adobe Portable Document Format - 662.13 kB - 03/23/2017 at 20:29	Preview	Download

Project Logs

Collapse logs

Started a Discussion
Jacob Christ • 03/23/2017 at 20:31 • 0 comments

Last night I submitted a suggestion to try to impliment this on the Arduino Developers form...
https://groups.google.com/a/arduino.cc/forum/#!topic/developers/eTFLXvUiVZA

View project log

Discussions

K.C. Lee wrote 03/31/2017 at 12:17

If you only need a single channel, just need to turn on the free running mode in the ADC, then you can grab the latest results anytime you want. Most microcontrollers have something like this. On chips with DMA, just grab and process whole block of data. Some might even let you specify the channel sequence.

For a PID loop, you want to take the ADC snapshots from a hardware timer and not a software timing loop. Jitters in the sampling time affects the D term in a PID controller. Faster isn't necessarily better.

https://www.chiefdelphi.com/forums/archive/index.php/t-83734.html

Are you sure? yes | no

Jacob Christ wrote 03/31/2017 at 17:03

I rarely use a D term but good to know. Had never thought about this but a good point.

Are you sure? yes | no

K.C. Lee wrote 03/31/2017 at 17:18

I use the D term quite a bit. It gets you a faster settling time while controlling the oscillations/overshoots. As with finite derivatives, it is unfortunately prone to noise. :(

Are you sure? yes | no

Jacob Christ wrote 03/27/2017 at 17:57

Sounds like a blocking mental-block.

Are you sure? yes | no

esot.eric wrote 03/31/2017 at 06:02

Are you sure? yes | no

esot.eric wrote 03/24/2017 at 03:44

ah hah! "Non-Blocking" is the word that was on a mental-block for me

Are you sure? yes | no

Similar Projects

117

My somewhat odd and random project of building a racing mower( was brought on by my arduino ecm )

Non-blocking analogRead()'s for Arduino

Become a Hackaday.io member

Just one more thing

Description

Files

chipKIT-core 1.4.0 Non-Blocking Analog Reads.pdf

Project Logs Collapse logs

Started a Discussion

Enjoy this project?

Discussions

Become a member

Similar Projects

Racing Mower

XBee and FPV cam spy car

Debugging Arduino Uno in VScode

Does this project spark your interest?

Report project as inappropriate

Send message

Remove Member

Project Logs

Collapse logs