[prev in list] [next in list] [prev in thread] [next in thread] 

List:       owfs-developers
Subject:    Re: [Owfs-developers] Temperature from humidity sensor
From:       Colin Law <clanlaw () gmail ! com>
Date:       2016-10-14 15:06:55
Message-ID: CAL=0gLscgw9tzO4LE7KUwjTVyh9pUtV4s0_BVv1pXx+i8SnF0w () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On 14 October 2016 at 13:47, Jan Kandziora <jjj@gmx.de> wrote:

> Am 14.10.2016 um 09:36 schrieb Colin Law:
> > On 14 October 2016 at 00:25, Jan Kandziora <jjj@gmx.de> wrote:
> >
> >> Am 14.10.2016 um 00:01 schrieb Michael Hughes:
> >>> If I read the humidity from:
> >>>
> >>> /uncached/1F.49D100000000/main/26A829150000002E/humidity
> >>>
> >>> and then read the temperature from:
> >>>
> >>> /1F.49D100000000/main/26A829150000002E/temperature
> >>>
> >>> will I get the temperature that was used to calculate the
> >>> humidity?
> >>>
> >> No. Reading "temperature" will start another temperature conversion. You
> >> have to read "latesttemp" to read the contents of the temperature
> >> register from last conversion (which was triggered by the humidity
> >> conversion in this case.)
> >>
> >
> > What is the difference between ../temperate and uncached/../temperature?
> >
> The "normal" cached tree, under some circumstances, will return a cached
> value from the latest access to that particular node.
>
> However, as Michael did not read .../temperature but ../humidity, there
> should be no cached value for the temperature node. (Well, in reality,
> it is, because reading .../humidity in fact reads .../temperature
> internally and *does not* bypass the cache. Good riddance.)
>

OK, thanks

Colin

[Attachment #5 (text/html)]

<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 14 October 2016 \
at 13:47, Jan Kandziora <span dir="ltr">&lt;<a href="mailto:jjj@gmx.de" \
target="_blank">jjj@gmx.de</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span \
class="">Am 14.10.2016 um 09:36 schrieb Colin Law:<br> &gt; On 14 October 2016 at \
00:25, Jan Kandziora &lt;<a href="mailto:jjj@gmx.de">jjj@gmx.de</a>&gt; wrote:<br> \
&gt;<br> &gt;&gt; Am 14.10.2016 um 00:01 schrieb Michael Hughes:<br>
&gt;&gt;&gt; If I read the humidity from:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; /uncached/1F.49D100000000/<wbr>main/26A829150000002E/humidity<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; and then read the temperature from:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; /1F.49D100000000/main/<wbr>26A829150000002E/temperature<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; will I get the temperature that was used to calculate the<br>
&gt;&gt;&gt; humidity?<br>
&gt;&gt;&gt;<br>
&gt;&gt; No. Reading &quot;temperature&quot; will start another temperature \
conversion. You<br> &gt;&gt; have to read &quot;latesttemp&quot; to read the contents \
of the temperature<br> &gt;&gt; register from last conversion (which was triggered by \
the humidity<br> &gt;&gt; conversion in this case.)<br>
&gt;&gt;<br>
&gt;<br>
&gt; What is the difference between ../temperate and uncached/../temperature?<br>
&gt;<br>
</span>The &quot;normal&quot; cached tree, under some circumstances, will return a \
cached<br> value from the latest access to that particular node.<br>
<br>
However, as Michael did not read .../temperature but ../humidity, there<br>
should be no cached value for the temperature node. (Well, in reality,<br>
it is, because reading .../humidity in fact reads .../temperature<br>
internally and *does not* bypass the cache. Good \
riddance.)<br></blockquote><div><br></div><div>OK, \
thanks<br><br></div><div>Colin<br></div><div>  <br></div></div></div></div>



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot

_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic