Re: [DIYbio] $50 camera good for microscopy with machine vision code included

On Sun, Feb 1, 2015 at 7:32 PM, John Griessen <john@industromatic.com> wrote:
> On 02/01/2015 06:16 PM, Nathan McCorkle wrote:
>>
>> Pixy
>> CMUCam5, which also has Python interfaces... from looking at both this
>> and openMV I'd tend to say the Pixy might be more 'bang for your buck'
>
>
> There's a big ease of coding and debugging difference in "has python
> interface"
> and "has python command line" while running python internally.

True, I do think that 15 FPS could be limiting for some things like
live cell tracking. I wonder how easy it is to interface with the
CMUCam Pixy, I've been tinkering more and more with openCV's Python
library and am super happy to be able to bang out little apps. I don't
know if it would be possible or reasonable to try and get that running
on the MCU of the openMV... in which case I guess you'd just want the
frames getting to something else as fast as possible... so maybe
Cory's cameras then and a USB2/USB3 link... unless real-time
timestamps are required for processing (not sure if those cams would
provide that, but I doubt not, as you'd need an RTC I think).

> The price of the module is not the BOM cost either. BOM cost of micropython
> based on the ARM STM32 mcu is very good.
>
> But... if you want nice micro-photographs right away, I am sure Simon's
> recommendations of FOSS on Canon digicams is the way to go.

Well I looked up that firmware/addon and the camera it seemed to run
on goes for $900-1100 around here on craigslist... I'm mostly
interested in machine vision too, so super high-quality is not as
important I think right now.

> For machine vision based on python running on a $6 mcu, the
> particular image sensor chip is not even the main thing. If OpenMV Cam's
> chip is
> not perfect, a follow on will be closer to perfection since the inexpensive
> mcu hdwe + FOSS
> machine vision code makes a huge value, and the image sensors to go with it
> can evolve better
> over time.

Hmm, I wonder if you can get higher FPS with the openMV if you turn
off all/most on-board vision processing and throw timestamps on with
RTC for a PC to deal with.

I guess I need to look into openMV's available libraries/features.

--
-- You received this message because you are subscribed to the Google Groups DIYbio group. To post to this group, send email to diybio@googlegroups.com. To unsubscribe from this group, send email to diybio+unsubscribe@googlegroups.com. For more options, visit this group at https://groups.google.com/d/forum/diybio?hl=en
Learn more at www.diybio.org
---
You received this message because you are subscribed to the Google Groups "DIYbio" group.
To unsubscribe from this group and stop receiving emails from it, send an email to diybio+unsubscribe@googlegroups.com.
To post to this group, send email to diybio@googlegroups.com.
Visit this group at http://groups.google.com/group/diybio.
To view this discussion on the web visit https://groups.google.com/d/msgid/diybio/CA%2B82U9JSNuFqNB6OjS9jh%2BUK66mNAsgpmMrQ0t%3DaX8u0hdDtkg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.