On 05/28/2011 04:12 AM, Mark Sims wrote:
The spikes are due to an artifact in the way the Tbolt firmware reads the
temperature sensor chip. It reads two registers and combine the values to get
a high-res temp reading. But if the firmware accesses the registers in-between
the time that the
On 5/27/2011 10:58 PM, WarrenS wrote:
The Tbolt uses a special method to get high resolution data from its
temperature sensor by combining three things.
The first is the sensor's standard data output which is used for the most
significant bits. This gives about 1 deg resolution.
2nd an
On 5/27/2011 10:58 PM, WarrenS wrote:
The Tbolt uses a special method to get high resolution data from its
temperature sensor by combining three things.
The first is the sensor's standard data output which is used for the most
significant bits. This gives about 1 deg resolution.
2nd an internal
The problem is actually with all three parts: the 1620 sensor, TBolt
firmware, and with Heather. Let me explain.
1) While the root cause is an anomaly in the DS1620 chip, Dallas
identified (not solved) it and described a work-around after Weather
Station users noticed glitches in the late 90's.
I am glad someone finally said this, as after I read a few explanations, I
could see that the temperature reading would be off somewhat, especially in
the resolution used.
Thanks,
Will
*** REPLY SEPARATOR ***
On 5/28/2011 at 11:53 AM Tom Van Baak wrote:
The problem is
I left my Thunderbolt running with Lady Heather started. Returning after a few
hours in the room,
which is at a constant temperature (underground, no heating, no air
conditioning), I found the
following plot on the Lady Heather screen :
http://www.sdradio.eu/images/ladyheather.gif
which shows
Hi Alberto,
On Fri, May 27, 2011 at 8:45 PM, Alberto di Bene dib...@usa.net wrote:
I left my Thunderbolt running with Lady Heather started. Returning after a
few hours in the room,
which is at a constant temperature (underground, no heating, no air
conditioning), I found the
following plot
On 5/27/2011 8:59 PM, francesco messineo wrote:
since the plot has a step jump, seems only a few tens mC, and then it
comes slowly back to the normal track, I'd rule out at least an
external temperature change: the thunderbolt can easily detect an hand
in its proximity even for a few seconds,
Does anybody have a possible explanation for this ?
Ghosts, of course!
Likely an issue with the temp sensor, their conversion isn't necessarily flat.
___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
Hi
If you watch the thermometer on the TBolt for long enough, you will indeed see
narrow temperature spikes. The gif you posted is a very typical spike. They are
fairly rare and they don't repeat. I believe LH averages the readings it gets,
so they may simply be a noise burst. The initial jump
I have seen it, as a matter of fact two days ago I did see a straight jump
in excess of 1 C. I have seen it before. I do not monitor constantly, but
will keep an eye out.
Bert Kehren
In a message dated 5/27/2011 3:19:46 P.M. Eastern Daylight Time,
dib...@usa.net writes:
On 5/27/2011
I confirm Bob's statement.
Such spikes seem to be normal. I am running T-Bolts already since the
begin of the time nut action initiated by Tom (TvB) and with a temp
resolution of 20m°C. I observed always such spikes up to a few times a
day. I do not see a real practical problem.
Arnold
Am
controller has a special routine that cuts those
spikes out (does not average them in) so that they do not upset LH's S/W
temperature control PID loop .
ws
*
[time-nuts] Strange temperature peak
I left my Thunderbolt running with Lady Heather started. Returning after a
few
Maybe a nearby cell phone calling home?
Bob Camp wrote:
Hi
If you watch the thermometer on the TBolt for long enough, you will indeed see
narrow temperature spikes. The gif you posted is a very typical spike. They are
fairly rare and they don't repeat. I believe LH averages the readings it
Hi
Could easily be. The spikes seem to be random and that would be a source of
random RF.
Bob
On May 27, 2011, at 7:41 PM, Chuck Harris wrote:
Maybe a nearby cell phone calling home?
Bob Camp wrote:
Hi
If you watch the thermometer on the TBolt for long enough, you will indeed
see
The spikes are due to an artifact in the way the Tbolt firmware reads the
temperature sensor chip. It reads two registers and combine the values to get
a high-res temp reading. But if the firmware accesses the registers in-between
the time that the temp sensor chip updates them it can
Hello
In my case I think it's not a rf problem. I am far away from rf or cell
phone stations and the shack is well protected against rf from outside
and no cell phone nor other transmitters were used in this room at this
time. If it would be an emc problem - why is only the temperature output
17 matches
Mail list logo
