Support physicallymodified sensors
Posted: Thu Jul 16, 2009 5:53 pm
Hi,
As some (many?) others I jhave physically modified some sensors to do something else then what they originally do.
For example I have build my own solar (Lux) sensor by removing the actual temperature sensor from a Oregon Scientific TH sensor, and connecting a solar sensor from Conrad (Hygrotec) to it. That works great, but now Meteohub receives a temperature from the Oregon Scientific sensor, classified as THx, but that value between -30 and +70 degrees (or recalculated to for example 0-50 degrees) actually represents the amount of sunshine.
I would like to have the ability to say the output of a sensor actually means something entirely different then expevected, so for example a percentage (0-1000% light) or a nuber (#lux or #watt/m2).
I am now working an modifying another sensor to register rainfall. Not with a normal rain-volume collector, but with a sensor where rain drops make contact between metal plates, representing rainfall. This reacts much faster then a normal rain collector (which only responds if enough rain has fallen to tip the little collector inside).
Again here the 'temperature' form the Oregon THx sensor would actually represent a percentage (0-100% wet/dry) or an number. Or even binary: dry v.s. wet with some kind of border number (higher is wet, lower is dry).
Regards, Jan.
As some (many?) others I jhave physically modified some sensors to do something else then what they originally do.
For example I have build my own solar (Lux) sensor by removing the actual temperature sensor from a Oregon Scientific TH sensor, and connecting a solar sensor from Conrad (Hygrotec) to it. That works great, but now Meteohub receives a temperature from the Oregon Scientific sensor, classified as THx, but that value between -30 and +70 degrees (or recalculated to for example 0-50 degrees) actually represents the amount of sunshine.
I would like to have the ability to say the output of a sensor actually means something entirely different then expevected, so for example a percentage (0-1000% light) or a nuber (#lux or #watt/m2).
I am now working an modifying another sensor to register rainfall. Not with a normal rain-volume collector, but with a sensor where rain drops make contact between metal plates, representing rainfall. This reacts much faster then a normal rain collector (which only responds if enough rain has fallen to tip the little collector inside).
Again here the 'temperature' form the Oregon THx sensor would actually represent a percentage (0-100% wet/dry) or an number. Or even binary: dry v.s. wet with some kind of border number (higher is wet, lower is dry).
Regards, Jan.