@mathew sez:

Node.js interface for the Speck: https://github.com/CMU-CREATE-Lab/node-speck-sensor

node.js interface for SHT15 on Raspberry Pi https://github.com/keito/pi-sht1x

python interface for capturing serial output of the dylos monitor (this is the best one I could find but there are 11 dylos projects on github) https://github.com/louwrentius/airquality

alternate for Speck https://github.com/CMU-CREATE-Lab/node-speck-gateway

So, today I wrote an OPK driver using the Firmata Node library to access an Arduino over the Firmata firmware, but we discovered that the Shinyei needs us to work fast enough (if we're understanding properly) to actually measure individual particles passing the sensor -- which can take 10-90ms. Node and the USB interface just can't work fast enough, as we understand it -- I was getting notices that even a 10ms interval was not completing digitalReads fast enough.

So we're going to switch back to doing it on the Arduino, and my driver will adapt to just reading the sums reported by the Arduino.

BUT! (@rjstatic and @donblair - this may be of interest) This driver (https://github.com/jywarren/opk-shinyei-ppd42-cli) is a great example on which to base a generalized Firmata/Arduino driver. Basically, if you can plug a sensor into an Arduino (say, a $9 Arduino-compatible Digispark), you'd be able to connect it to Open Pipe Kit. Some more flags to the command line interface can let us specify which pins to poll.

It won't work for superfast sensors like the Shinyei -- the latency requirements are too great -- but for many many other sensors, this works great.

Finishd the OPK Firmata CLI for one-pin readings: https://github.com/jywarren/opk-firmata-cli/

@rjstatic and @donblair - pretty useful; basically anything you can plug into an Arduino you can now plug into OPK, I think? Might be good to add:

• auto-detection of attached sensors (i.e. scan digital and analog ports and see if anything's attached? This might not work if you don't have pull-down resistors, right?)
• listening on multiple pins at once (wouldn't be too hard, but wanted to keep this first version simple)
• a config file to set which ports to listen on and what to name them in the output, if JSON is specified

Here's some data from the Shinyei. We're still interpreting this: https://gist.github.com/jywarren/54453678f43a2c555f64

We now have live graphs from it -- looking good!

Mathew also did some good research on the ThermoFisher PDR-1500 http://www.thermoscientific.com/en/product/i-personal-i-dataram-pdr-1500-aerosol-monitor.html :

manual: http://www.geotechenv.com/Manuals/Thermo_Scientific_Manuals/thermo_pdr-1500_manual.pdf

we need to communicate with the pDR-1500 through UART serial, but it has a built-in serial to USB bridge, the Silicon Laboratories CP2102 this device runs at 19200 (page B-1) USB drivers are here and in the linux kernel. https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx

Before running the device must be zeroed

OUTPUT (or OUT or O) [conc or scat] [temp (C)] [RH (%)] [Pa (mmHg)] Returns the current values of the concentrations, temperature, RH and atmospheric pressure if the pDR-1500 is running.

LOGPERIOD [seconds] Returns, or programs, the logging period in seconds.

SD [Status] Returns, or programs, the streaming data status. Status = {“enabled” or “on”, “disabled” or “off”}

this function is unexplained we don’t know that it does.

CALFACTOR [float value] Returns, or programs, the user calibration adjustment factor. The value can range from 0.001 to 10.000.

RHCORRECT [status] Returns, or programs, the status of Relative Humidity correction to the computation of mass concentration. Status = {“disable” or “off”, “enable” or “on”}

DATE [day] [month] [year] Returns, or programs, the date in the RTC. Day, month and year are all integer values.

TIME [seconds] [minutes] [hours] Returns, or programs, the RTC’s current time.

FLOWRATE [flow rate] Returns, or programs, the flow rate [LPM] that is to be maintained. This cannot be changed while logging. Flow rate = {1.00, 1.01, 1.02, …, 3.50} [in LPM]

TEMP [temp] [RH] [Pa] Get current temperature, RH and atmospheric pressure. temp is in degrees Celsius RH is Relative Humidity in percent Pa is barometric pressure in mmHG

UNITS [integer] the current measurement units: Units = 0 = μg/m3 (Mass concentration) 1 = 1/Mm (880 nm scattering coefficient)

INLET [integer] Returns, or programs, the inlet selection from the choices integer = {0, 1, 2} 0 = TOTAL 1 = CYCLONE RED (PM 10) 2 = CYCLONE BLUE (PM 2.5)

SITE [site #] Returns, or programs, the description of site number sitenum. Sites are numbered 1–50. sites can have their own corrections, but these corrections may be better done on the server?

Thermofisher working! https://github.com/jywarren/opk-thermofisher-pdr1500-cli and https://data.sparkfun.com/streams/g6Gn19yp9yU6WaObjlYO

Leaving them both running on a 30 second cycle, next to one another.

And over a longer period -- 2/3 of the way through, i lit a piece of paper on fire.

Note that I did not zero out the TF, and the vertical scales are wrong. Just very very early testing of the drivers.

And the Speck too: https://github.com/jywarren/opk-speck-cli now running.

And taking note that for the Thermofisher and the Speck, we're only doing spot readings, not averages. This should change:

https://github.com/jywarren/opk-speck-cli/issues/2 https://github.com/jywarren/opk-thermofisher-pdr1500-cli/issues/1

Hey @mathew - wrote up a driver for the Dylos - it was very simple, just listening and it returns "0,0" every so often. If there's a manual or something I can set the units and perhaps change the sampling interval, but it seems to be basically working:

https://github.com/jywarren/opk-dylos-cli/issues

awesome!

Collecting notes on different sensors here! https://publiclab.org/q/15751