With the recent surge in Omicron cases, shipping may be slower than stated times. We are working to build, ship and respond to everything as quickly as possible. Please see all COVID-19 updates here. Thank you for your continued support.


Member Since: May 7, 2011

Country: United States

  • For about $20 more, this basic digital camera does 20.1 megapixel stills, 720p video at 30fps, etc, etc, etc... Included in that price is a >~1000mAh battery, 2.7" LCD, the plastic enclosure, etc, etc, etc... http://www.bestbuy.com/site/sony-dsc-w800-20-1-megapixel-digital-camera-black/4349004.p

    How then, does this slower and lower-fidelity camera with no storage, lights, usb, etc, etc, maintain this price? Not intended as a dig at sparkfun, because I find no significantly better and/or cheaper cameras available.

    Where does one purchase the comparatively well-featured cameras they put in every ~$20 cell phone nowadays? I realize the phone manufacturers buy 1000000000000 cameras at a time but even with adding the onboard encoder to make the camera 'standalone', the price-feature ratio seems way off.

    Could you not (summarizing) add a <$20 SD sniffer to the above BestBuy camera and outperform this in every way? Besides being tiny and low-power, please spell out for me where the value in this is?


  • You don't see many 3D armadillo's here in Texas..

  • http://oshpark.com/shared_projects/kcVjN7cA

  • http://oshpark.com/shared_projects/kcVjN7cA

  • http://oshpark.com/shared_projects/kcVjN7cA

  • http://oshpark.com/shared_projects/kcVjN7cA

  • Breakout Board: http://oshpark.com/shared_projects/kcVjN7cA

  • Getting ready for Christmas - $.$


    Sometimes the lights appear to have latency but it is purely cell-phone-camera related.

  • I thoroughly read the datasheet and saw the obvious intent with the board to provide daisy-chaining, but didn't notice the entirely alternate wiring shown in the schematic. Per the datasheet, this board could have had a single 5x2 header in, and a single 5x2 header out, with no extra one-wires. It will work, but the daisy-chaining could be greatly simplified by conforming to the datasheet. :( (first-ever frowny face @ sparkfun)

    From AutoDriverSupport.cpp - // SPIXfer()...A very important // note regarding chip select- holding the CS line low results in data being // shifted THROUGH the chip, not into it. To latch data, CS must be released // after each byte. I can't find a reference to this in the datasheet, which // is AWESOME, and I've personally discovered it at least twice."

    This was intentional and expected behavior per the datasheet: Page 37: CS lines should all be tied together; MISO should return to CPU from last driver in chain Page 54: NOP = 0x00

    To command the n-th driver in the chain: 1) Hold CS 2) Transmit (CommandForNthModule + (NOP * (n - 1))) 3) Release CS

  • These appear to be daisy-chainable, except that CS is not connected per the datasheet example. Please recommend a method for addressing modules in the chain after the first.

No public wish lists :(