I've been speaking with a community member in Mobile County, Alabama who has been struggling with...
Public Lab is an open community which collaboratively develops accessible, open source, Do-It-Yourself technologies for investigating local environmental health and justice issues.
As an open source community, we believe in open licensing of content so that other members of the community can leverage your work legally -- with attribution, of course. By joining the Public Lab site, you agree to release the content you post here under a Creative Commons Attribution Sharealike license, and the hardware designs you post under the CERN Open Hardware License 1.1 (full text). This has the added benefit that others must share their improvements in turn with you.
@Ag8n That's good idea and clever way to do the job. The problem is that, this will be very complicated to set up everything.
Reply to this comment...
Ok. Let's go through it step by step.
First, after a little digging, it looks like there are two frequencies used 315 mh z and 433 mhz. So it would take two rtlsdr dongIes. I'm more familiar with windows and sdr#. But, as long as you have two usb ports and two rtlsdr dongles, in Windows you could open multiple instances of sdr#. Both frequencies could be covered at the same time.
This program is based on gnu radio. That part, I don't know about. Maybe the Reddit rtlsdr could fill in the details. Or compile the program so it could run on Windows in multiple instances?
As for the cost, the dongles are often found on ebay for $10. You must be careful they are The right ones.
The programming changes for counting are beyond me. Sorry.
"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?"
And Tim Pickering just shared this:
"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..."
One option may be to use a computer vision system. Believe it or not its a fairly simple code. Not sure it would work at night but it could probably switch to counting (moving) lights if neded. You need to train a dataset but you could train it to only detect one type of truck (color or size). Google 'opencv' and 'car tracking' for more examples: