I was trying to test the sensor applet with the CO2 sensor, to make sure it was working since that was one of the sensors that InquirySpace was specifically interested in supporting. It's not going so well.
I was sent 2 different CO2 sensors.
One is this (I'll call this the newer style): http://www.vernier.com/products/sensors/co2-bta/
One has that same part code, but looks like this (I'll call this the older style): https://github.com/concord-consortium/vernier-sensor-map/blob/master/Sensor%20Images/sensor_CO2.bmp?raw=true
The newer one works with the LabQuest. It reports sensor id of 75 or 76, depending if the toggle switch is in low or high mode respectively.
The newer one does not work with the GoLink, however. When open() gets called on the GoLink, it throws a RuntimeException complaining that the device can't be opened (GoIOSensor.java, line 47). The online product page for it implies that GoLink is supported.
The old one isn't working either place. On the LabQuest, it reports a sensor-id of 14, which in our code (and also according to the xml maps that Stephen just posted) corresponds to a Raw Voltage device. At that point, the config doesn't match the request, so it won't collect data from it.
On the GoLink, it reports as id 11, which is mapped to TEMPERATURE_F in our code (and is explicitly unsupported in the code), and id 11 isn't even a device according to those xml maps. Same problem with the config not matching the request.
So... what's the story on the CO2 sensors? What should I worry about trying to support, and what should I just punt on?
Looking into this, I also encountered a couple of other things:
- Some of our low-level (< 20) sensor ids don't match up with what's in the xml file Stephen posted. Do we want to try to get updated versions of those maps and update our code to match?
- There's an updated GoIO dll/dylib that supports 64-bit. Any interest in updating? I didn't see any mention of supporting the newer CO2 sensor, unfortunately...
This page had some useful info:
Perhaps you are experiencing one of those problems.
excuse my brevity, this is from my phone