Paul Alfille-2 wrote:
Interesting idea. I've been tempted to build a special owserver that has
plug-in sensor code -- owexternal.
The plug-in would get a separate mane space (perhaps
/external/sensor43/humidity) and have to report a few properties like
length, type, read/write and
very very nice!!!
maybe we could use json or another language to send and receive informations?
maybe a txt or csv or xml(i don´t like xml... txt and csv can run in
any bash program, json is more usable in php,perl,python scripts)
do you have any idea about the implemention?
Em 29 de fevereiro
i have some ideas, maybe could not work maybe could...
i was reading http://owfs.org/index.php?page=external-sensor-design
Configuration will be by text files
Two layers of config
First layer has the list of devices (unique names)
Second layer describes the device's family
i was
Hi all,
beside using 1-Wire devices I would like to use other sensors as well.
Currently I play with an temp-sensor getting data very simple by a serial
port.
So writing all this polling, retry, alias, fuse (and a lot of other
functionality) again is a lot of effort - so maybe there is a way to
Interesting idea. I've been tempted to build a special owserver that has
plug-in sensor code -- owexternal.
The plug-in would get a separate mane space (perhaps
/external/sensor43/humidity) and have to report a few properties like
length, type, read/write and volatility.
Plugins could be written
On 02/27/2012 09:13 PM, Paul Alfille wrote:
Interesting idea. I've been tempted to build a special owserver that has
plug-in sensor code -- owexternal.
The plug-in would get a separate mane space (perhaps
/external/sensor43/humidity) and have to report a few properties like
length, type,
