Re: [Owfs-developers] Best way to represent multi-sensor data

2011-11-07 Thread Eloy Paris
Hi Paul, On 11/06/2011 08:13 AM, Paul Alfille wrote: > Eloy, > > You can set up an "array" -- a property that have several (indexed) > values. Assuming that you are reading data that is all the same type > (floating point in this case) and you keep track of the position of the > values, and you i

Re: [Owfs-developers] Best way to represent multi-sensor data

2011-11-06 Thread Paul Alfille
Eloy, You can set up an "array" -- a property that have several (indexed) values. Assuming that you are reading data that is all the same type (floating point in this case) and you keep track of the position of the values, and you ignore the automatic temperature scale conversion this would work w

Re: [Owfs-developers] Best way to represent multi-sensor data

2011-11-05 Thread Vincent Danjean
Hi, Le 05/11/2011 20:38, Eloy Paris a écrit : > In my particular case I was mostly thinking along the lines of "easier > to implement on the microcontroller and in less space". Performance-wise > I am sure there is a tiny advantage of doing an N-byte data transfer > than N 1-byte transfers, esp

Re: [Owfs-developers] Best way to represent multi-sensor data

2011-11-05 Thread Eloy Paris
Hi Mark, On 11/05/2011 09:25 AM, Mark Richards wrote: > Hello Eloy, > > A few thoughts. > > OWFS already provides data in a single-file-format, such as branch.ALL, > volt.ALL... > > These .ALL registers appear to be grouped by a logical and common > purpose. If future device support were to be fa

Re: [Owfs-developers] Best way to represent multi-sensor data

2011-11-05 Thread Eloy Paris
On 11/05/2011 09:17 AM, Colin Law wrote: > On 5 November 2011 12:33, Roberto Spadim wrote: >> [ snip of ideas for how owfs could produce more intelligent output ] >> >> well i think that´s enought to don´t work with external bash scripts, right? > > I don't agree. OWFS should be just about produ

Re: [Owfs-developers] Best way to represent multi-sensor data

2011-11-05 Thread Mark Richards
Hello Eloy, A few thoughts. OWFS already provides data in a single-file-format, such as branch.ALL, volt.ALL... These .ALL registers appear to be grouped by a logical and common purpose. If future device support were to be fashioned against what may be considered an existing "standard", gr

Re: [Owfs-developers] Best way to represent multi-sensor data

2011-11-05 Thread Colin Law
On 5 November 2011 12:33, Roberto Spadim wrote: > [ snip of ideas for how owfs could produce more intelligent output ] > > well i think that´s enought to don´t work with external bash scripts, right? I don't agree. OWFS should be just about producing the data. It has to be kept as light as poss

Re: [Owfs-developers] Best way to represent multi-sensor data

2011-11-05 Thread Roberto Spadim
well some problems since this is very interesting (remove some work from final user) it´s a bit loss of work from owlib, maybe at a client side could be easy... let´s give a example of what could be usefull to implement... for example... reading voltage from a ADC give you just a voltage... if

Re: [Owfs-developers] Best way to represent multi-sensor data

2011-11-05 Thread Colin Law
On 5 November 2011 11:41, Eloy Paris wrote: > Hello developers, > > I am working on a 1-Wire device that provides multi-sensor data, i.e. > temperature, humidity, luminosity. I'd like to be able to have an OWFS > file that allows me to do this: > > $ cat /owfs2/uncached/99.010203040506/environs; e

[Owfs-developers] Best way to represent multi-sensor data

2011-11-05 Thread Eloy Paris
Hello developers, I am working on a 1-Wire device that provides multi-sensor data, i.e. temperature, humidity, luminosity. I'd like to be able to have an OWFS file that allows me to do this: $ cat /owfs2/uncached/99.010203040506/environs; echo temp=25.2 RH=48% light=252 This would allow for ea