[time-nuts] TBolt temperature sensor

[Tom Van Baak]

Dave,

The actual number is x.75 degrees but the program you're using (LH?) apparently truncates the display. TBoltmon doesn't have this problem. Regardless, there's much more to it than just which program you use.

I never finished this article, but it explains a few things about the TBolt 1620 temperature sensor that you will find interesting:
http://www.leapsecond.com/pages/tbolt-1620/

Most of this has been well covered on the list in years past. Search the archives.

/tvb

----- Original Message ----- 
From: "quartz55" <quartz55 at hughes.net>
To: "Discussion of precise time and frequency measurement" <time-nuts at febo.com>
Sent: Friday, September 13, 2013 8:54 PM
Subject: Re: [time-nuts] TBolt temperature sensor


> I've been observing my Temp trace for a week or so now.  Seems like my sensor, if I let the unit cool off to room temp, starts at a real temp say 25, then ramps up to about 37 or so degrees and then goes into this mode where it switches between 2 one degree levels, 35.7 and 36.7.  There is also some measurement changes when it transitions between 36.7 and 35.7 and the other way too.  Plus if I put a fan on the unit, the sensor responds and the reported temp drops like one would expect and below the 35.7 level.  I'm not understanding the issue about 'bad' sensors, or the discussion about small incremental changes.  Mine seems to respond fine between the 2 temps that it seems to ramp between once it's running.  For example, when it cooled off today, I opened the windows and the reported temp dropped to 35.7.  Then when it warmed up, it went back up to 36.7.  I just don't understand why it doesn't seem to report temps outside the 35.7-36.7 range unless it gets way out of that range. Any
> how, I've ordered the earlier chip to see if it helps, but seems like some say, it won't matter as long as I use the thing when it's locked.  It just bothers me when things don't work right.
> 
> Dave
> N3DT