Member Since: February 1, 2010

Country: United States


Rocket Scientist…

  • For what it’s worth, mine has been sitting outside in Hawaii for 16 months and about 120" of rain and has held up fine. The red is a bit bleached on the top side, but the plastic does not look compromised, there is no corrosion on the screws and the seal has held. (That is in stark contrast to the SparkFun solar cell powering the unit.)

  • A heads up for people planning to use this for permanent outdoor mounting: The epoxy coating is not UV protected. After 6 months outside in Hawaii, mine has become completely opaque. It’s still functioning, but I have no idea how much power I’m losing.

  • I did cover the board, except for the sensor package, with hot glue to protect the pads. It’s possible that wasn’t enough. For my next one, I think I’ll pot the entire board in epoxy (after mounting a filter cap.)

  • I second this. Mine just died after being outside (in an enclosure but still exposed to mist and moisture) in Hawaii for 6 months. I haven’t found a place that carries these filter caps either.

  • After a few months in the very humid Hawaii climate, my sensor now basically says 119% humidity all the time. I wonder if this is a condensation issue.

  • I’ve now also added a pretty detailed how-to about how to do wireless bootloading with series 2 XBees and avrdude. It’s at my blog.

  • I double checked by looking at the read-out values of the channels instead of just the lux values. With 100ms integration, 1x gain, the channels increase in value until they peg at 37177. ch0 will saturate first, since it has the highest count rate, at about 40,000 lux. From that point, any increase in light level actually brings the calculated lux down, because the only channel that keeps going up is ch1. When they both saturate at 37177, the calculated lux value is about 805.

  • Actually, does anyone know if setting a new integration time interrupts the ongoing integration? If not, it’s hard to know when to read out the data. Supposed it’s set to an unknown integration time and I want to use 14ms. If I then have to account for the possibility that it could be running a 400ms integration first, I could have to wait up to 414ms before the correct result shows up. The datasheet doesn’t seem to specify this, it just says “when the device is powered up, it will start doing continuous 400ms integrations.”

  • I think the library is correct except that it looks for 0xffff readouts as evidence of channel saturation. I’ll submit a bug fix. But I can’t get any measurements above ~40k lux, and in direct sunlight the sensors saturate.

  • Oh sweet. I don’t suppose I can “upgrade” mine? ;-)

No public wish lists :(