NavList:
A Community Devoted to the Preservation and Practice of Celestial Navigation and Other Methods of Traditional Wayfinding
Re: Allowing a chronometer to 'run out'
From: Zvi Doron
Date: 2012 Apr 19, 06:18 +0100
From: Zvi Doron
Date: 2012 Apr 19, 06:18 +0100
Thanks Alex The info I quoted came from some website, not from Bill. -----Original Message----- From: Alexandre Eremenko Sent: Wednesday, April 18, 2012 11:20 PM To: zvidoron@btinternet.com Subject: [NavList] Re: Allowing a chronometer to 'run out' Zvi, > I have just read somewhere that: > a. If one cannot be there to wind the chronometer regularly > and therefore it would ?run out? of spring power and stop, it is better > to stop it before leaving, when there is still some power left in the > spring. This is what Bill says in his book. And he also advised me not to leave it unwound. I am not sure that I fully understand the reasons, probably to leave some parts under tension, "locked", so that they will not move accidentally. My chronometer lives in a closet, and it is unlikely to move, wound or not, unless I start it or an earthquake happens. > b. Once stopped, the balance wheel should be locked, > either with cork or with the provided mechanism, > even if the chronometer is not going to be moved. As I understand if you leave it wound, it must be locked to exclude that it starts when you accidentally move it. After it starts it will certainly run down. In one way or another you want the balance fixed. > Is this true? or just Grandma?s tales? Bill's tales:-) I also checked my Hamilton manual (I have a Hamilton manual and Polet chronometer, but no Polet manual and no Hamilton chronometer:-) Let me cite: "...they are allowed to run down, then stopped, corked or locked, placed in the shipping container, sealed and stored. While in storage, they should be inverted every 30 days in order to redistribute the oil on the lubricated surfaces." So they recommend fixing the balance by corking rather than winding. Alex. : http://fer3.com/arc/m2.aspx?i=119155 ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1913 / Virus Database: 2411/4944 - Release Date: 04/18/12