Thanks for all the replies.
*Suggestion :*
*IF *reading == 85 *then *ignore reading
I will now implement something like this for each reading of the OWFS
server.
Most probably I will add the following else branch :
*else *reading = last_reading
Even if there is a valid 85 degree measurement,
I don't know if this will help to explain the operation, but my code
runs in a continuous loop -
* Read all temperatures
* Set the simultaneous/temperature bit
* Perform logic operations, setting outputs to devices based upon
temperatures read, etc
* Log values to database
* repeat.
Am 08.01.2017 um 19:39 schrieb Roland Franke:
>>
>> It's still in there, as Stefano found the real bug causing problems with
>> .../latesttemp.
>
> But this has also an problem (For me). I will read over OWLIB from the
> OWSERVER values out (Let me say the program collectd will read it with
> the
Hello,
>>> ...
>>> This has all been taken care for already, OWFS repeats a
>>> .../temperature triggered conversion for the case 85°C is the result.
>>> When you still have stray 85°C readings, it means your power failures
>>> are so serious you should check your hardware setup.
>>
>> Is that
If there is no way to distinguish 85 error/power up from 85 valid, you cannot
filter it. Period. It must all be done on the other side of owfs, and the user
strategy for this depends on application and expected results.
You could add flags like last_was_85, or a time stamp last_non_85, but
Am 08.01.2017 um 11:25 schrieb Ritchie:
> Dear all,
>
> I know this is not a common owfs problem, but I would like to know some
> information about the communication to the ds2450 and how to debug it
> with the owserver.
>
Please look at the source code. module/owlib/src/c/ow_2450.c has most
Am 08.01.2017 um 17:05 schrieb Colin Law:
>
> It is surely undeniable that this is a design flaw in the chip. Much
> more sensible would have been to make it default to full scale (or
> full negative scale), then it would have been much easier to program
> around.
>
Full scale values mean there
Would someone Please help me with accessing OWFS using C. I have owserver
working. I can type “localhost:2121” in a browser and access all my OW devices.
There is an example program “owcapiexample.c”on my pi. How do I call this
program to access owserver. I have tried “./owcapiexample
On 8 January 2017 at 14:59, Jan Kandziora wrote:
> Am 08.01.2017 um 14:54 schrieb Ekkehard Pofahl:
>>
>> I am using OWFS since more than two years in different versions on a Raspi
>> 2. This alone shows, that I think it is a very good program.
>>
>> From time to time there is the "85
Am 08.01.2017 um 14:54 schrieb Ekkehard Pofahl:
>
> I am using OWFS since more than two years in different versions on a Raspi
> 2. This alone shows, that I think it is a very good program.
>
> From time to time there is the "85 degree" discussion. It is a clear design
> flaw of the DS 18xxx
Hello,
I am using OWFS since more than two years in different versions on a Raspi
2. This alone shows, that I think it is a very good program.
>From time to time there is the "85 degree" discussion. It is a clear design
flaw of the DS 18xxx chips to sent out a valid temperature reading, when an
Dear all,
I know this is not a common owfs problem, but I would like to know some
information about the communication to the ds2450 and how to debug it
with the owserver.
Wright now I am working on a Ds2450 Slave, based on a attiny45 and
I get the values "Error: Invalid argument" on "PIO.*"
12 matches
Mail list logo