DIY Traffic Counter

[Michael Kirk]

Hi!

I wanted to build a traffic counter to measure bicycle traffic in a few places around Los Angeles. 

I came across this:

http://tomorrow-lab.com/lab16

...which is just such a thing touting:

We have made the parts list and Arduino code available under a Creative Commons License. We have developed multilingual How-To guides to allow anyone to build a DIY Traffic Counter.

But then I couldn't find their plans anywhere. After contacting the site administrator I was told they are now selling a revised model here: http://waycount.com/

They've also built some nice tooling around uploading the data and aggregating it into a central portal. 

Which is all cool stuff - but I'm interested in building my own sensor, and was disappointed that they took down the original instructions.

The basic design is a pneumatic tube connected to a differential pressure sensor. Results are logged onto the device. And the whole thing runs on a 9v battery for around 8 hours.

I was able to go to the way back machine and find a guide (yay internet archive!):

https://web.archive.org/web/20160128041311/http://tomorrow-lab.com/traffic_counter/traffic_counter_guide.pdf

But haven't yet tracked down the parts list, which wasn't indexed due to it being a GDoc. There are some links to parts at the end of the aforlinked guide (last page). I'm also missing the arduino software that works with the sensor.

Anyway - anyone have experience with this or a similar design? Or *crosses fingers* have the software?

M

[Jeffrey Warren]

Hmm cool! nice find on the wayback machine :-)

I wonder if the upcoming Riffle board (which is a low power Arduino-compatible logger) could be paired with the pressure sensor? I know the Riffle team is working to get it production ready as we speak: https://github.com/OpenWaterProject/riffle

So maybe it's too early for using the Riffle but it depends on your timeline?

Jeff

--
Post to this group at publicla...@googlegroups.com
 
Public Lab mailing lists (http://publiclab.org/lists) are great for discussion, but to get attribution, open source your work, and make it easy for others to find and cite your contributions, please publish your work at http://publiclab.org
---
You received this message because you are subscribed to the Google Groups "The Public Laboratory for Open Technology and Science" group.
To unsubscribe from this group and stop receiving emails from it, send an email to publiclaborato...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Liz Barry]

Hey guys, 

I'm copying Frank Hebbert here who originally created the DIY Traffic Counter from Tomorrow Lab. 

--

+1 336-269-1539

@lizbarry

[timpick...@gmail.com]

I've just come across this thread, and with a bit of digging around, found https://github.com/codefordc/traffic_counter
which seems to be a fork of the original code, and a link to the instruction manual originally found on the wayback machine.

Just for anyone else looking. I've just ordered the parts, and will be testing it out asap...

[Stevie Lewis]

Ohh that's awesome! Thanks for finding this thread. I just posted a question along those lines recently, and @ag8n shared this resource as well. I'll compile these others on that question. Please post how it goes! 

Best,

Stevie

--
Post to this group at publiclaboratory@googlegroups.com

Public Lab mailing lists (http://publiclab.org/lists) are great for discussion, but to get attribution, open source your work, and make it easy for others to find and cite your contributions, please publish your work at http://publiclab.org
---
You received this message because you are subscribed to the Google Groups "The Public Laboratory for Open Technology and Science" group.

To unsubscribe from this group and stop receiving emails from it, send an email to publiclaboratory+unsubscribe@googlegroups.com.

[Liz Barry]

Hi!

I just added some more points on the question Stevie posted: https://publiclab.org/questions/stevie/07-13-2018/what-is-a-good-way-to-track-vehicular-traffic

How did the build go, timpickering98?

--

+1 336-269-1539 / @lizbarry / lizbarry.net