Member Since: August 28, 2008

Country: New Zealand



Air quality Scientist


New Zealand National Institute of Water and Atmospheric Research

Spoken Languages

Spanish, English, Swedish

Programming Languages

LabView, Fortran


Instrument development

  • I'm not sure how it would differentiate between first and second hand but I'd say, yes, this sensor would respond to cigarette smoke. I have used it in an indoor air quality sensor pacman and it performs quite well. Now, there are others too that might be easier to interface with your system. This one is a little tricky in that it requires a "timed trigger" kind of approach (trigger on, wait Xms, read, trigger off) that can complicate the troubleshooting a little and others like the Grove Dust are easier and measure basically the same thing.

    Check Chris Nafis' site where he's tried this and other sensors and his kickstarter project

  • To me, open source is more a principle issue than a cost one.
    I've always had a love/hate relationship with EAGLE as it "seems" open because it has a free (limited) version but it is not, while on the other hand, it is such a common software!
    I totally see people's point of EAGLE being their preferred tool but often comparisons are only valid for the one making them. Kicad works for me (professionally and "philosophically") and I prefer it ... maybe if I had learned to use EAGLE first my opinion would be different, who knows.
    In the meantime, I "survive" having a crippled version of EAGLE just so I can use the ULP to convert libraries to Kicad format and work "properly" ;-)
    I share cjenkins' dream ... the one about Sparkfun using open source software for board documentation ;-)

  • I've used Fritzing several times and to everyone each own ... Fritzing is great to start from a breadboard and if your "call" is not about the schematics (i.e. the electronics is just a very small part of your project) this is a great way to speed up the design process!
    Now about "proper" CAD software ... I tried Eagle but I'm much more comfortable (both from a philosophical and UI point of view) with KiCad.
    In the end what I would recommend is to give things a try and pick what works for you (and everyone's requirements are slightly different)

  • I second that!
    I got the crimping tool and it does make life easier than crimping with needle nose pliers but it still takes about 10 to 20 (at least for me) crimping attempts until one can reliably make a cable without braking the wires inside ... Now I'm almost getting 2 reliable connectors every minute :-)

  • Also, even if you managed to make water pass through the sensing area, the light path has been designed for air, the refraction of the light through water will mean that there is not only scattering and the response of the sensor would be undetermined.

  • What I did was to remove the cover, lift the electronics/optics block and then drill a couple of holes on the back of it ... will try to find images.
    However, the sensor itself is pretty light so double sided tape might work for some cases.

  • From the Cylon development files: The road to go from a toaster to Number 6 was not always a pretty one

  • This is proof that nothing good can happen after the words "hold my bear and watch this ..."

  • 20 in New Zealand :-)

  • here, here