Thanks Paul. That answers some of my questions. I know you are busy. Perhaps as I learn more I could write something for the neophytes.
I see the explanation of trim, trim blanket, and trim valid but it still leaves me in the dark as how to set or calibrate them. My die apparently does respond to changes as my trim valid is yes and changing trim values drastically changes the resulting temperature. But is there a formula for doing that? Changing trim by just one digit - xxxxx0 to xxxxx1 for instance drastically changes the temperature and there is no apparent pattern to the changes. I get close but not right temp readings with trim blanket checked which puts a (calculated?) value in for trim Doug --- On Thu, 10/29/09, Paul Alfille <paul.alfi...@gmail.com> wrote: > From: Paul Alfille <paul.alfi...@gmail.com> > Subject: Re: [Owfs-developers] Chip specific directory listings > To: owfs-developers@lists.sourceforge.net > Date: Thursday, October 29, 2009, 6:55 AM > On Thu, Oct 29, 2009 at 2:03 AM, Mr Doug > - <dsc3...@yahoo.com> > wrote: > > > > I am a little confused about how and why items appear in > the chip directories. As a for instance in the DS18S20 > directory (10.xxxx) where does trim and trim blanket come > from? I do not see anything in the Maxim docs about that. > Now should they be set? What is the method for calibrating > temperature? > > > > > > > For the DS2438 (26.xxxx) there are check boxes CA, EE, IAD, > settings trim and udate. Where is this all documented? > > > > There is a humidity reading and I do have the hobby boards > temp/hum/solar board but how does owfs make the calculation > and is it trim-able. There are two sensor? numbers listed > HIH4000, HTM1735. The hobby board is an HIH3610. > > > > > > > So without reading through the source code how does one > understand all this? > > > > > The humidity issue is a > little different. When the OWFS project started, the only > use of the DS2438 was in a humidity sensor based on the > HIH3610 (this was the Dan Awbry published design) so I > included it directly in the file structure. Now we use a > more sophisticated approach of including > implementation-specific properties in their own > subdirectory. I didn't want to break existing code... > > > > > Paul Alfille > > > -----Inline Attachment Follows----- > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference > in SF, CA > is the only developer event you need to attend this year. > Jumpstart your > developing skills, take BlackBerry mobile applications to > market and stay > ahead of the curve. Join us from November 9 - 12, 2009. > Register now! > http://p.sf.net/sfu/devconference > -----Inline Attachment Follows----- > > _______________________________________________ > Owfs-developers mailing list > Owfs-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/owfs-developers > ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
