vianouche1
·Happy Friday and thank you to all contributors in advance !
It is my first post, please kindly bear with me if this is a known topic or a misuse of my watch. Please also forgive me if there is already a thread on this topix, I had found one indeed woth a similar issue but not exactly the same.
Here is the story : my beloved Speedmaster 145.0022 from 1988 acdquired at a great seller (and the best) in Geneva, Switzerland, just came back from service at my trusted and certified (and also the best) watch maker. I had to send it for a service after treating it badly last summer. Poor thing but here we are.
Right after leaving the shop, I gave the 861 a full wind (wind until it stops), and tested the chronometer. It would start as expected, but not stop immediately. I had try it 4, 5 times and/or wait a bit for it to eventually stop. The reser was working fine. It had this behaviour during one hour. I left it rest a bit and since then, it works like a charm, the "bug" is gone.
Is this an expected behaviour after a full service ? Do we need to forgive a bit random functioning of the watch until it settles? Have any of you ever had the same issue?
Thanks again!
It is my first post, please kindly bear with me if this is a known topic or a misuse of my watch. Please also forgive me if there is already a thread on this topix, I had found one indeed woth a similar issue but not exactly the same.
Here is the story : my beloved Speedmaster 145.0022 from 1988 acdquired at a great seller (and the best) in Geneva, Switzerland, just came back from service at my trusted and certified (and also the best) watch maker. I had to send it for a service after treating it badly last summer. Poor thing but here we are.
Right after leaving the shop, I gave the 861 a full wind (wind until it stops), and tested the chronometer. It would start as expected, but not stop immediately. I had try it 4, 5 times and/or wait a bit for it to eventually stop. The reser was working fine. It had this behaviour during one hour. I left it rest a bit and since then, it works like a charm, the "bug" is gone.
Is this an expected behaviour after a full service ? Do we need to forgive a bit random functioning of the watch until it settles? Have any of you ever had the same issue?
Thanks again!