Service time or design flaw

[drgoro]

Something peculiar happened the other night. I pulled my AP brick 26470OR, out wound it up and went on my business; bored I started the chrono; it stopped after 30sec, so did the regular time keeping. So I just pulled the stalk out and wound it again...it didn’t restart. So I reset the chrono, and tried to wind...again nothing. I rotated the watch in a figure 8 and that got the time keeping back. I set the watch down to intentionally let it die, and after it did, I wound it and the time keeping started fine. Is this normal? Does having the watch die while using the chrono prevent the stalk from winding the movement? Or is it a defect?

[othertbone]

Originally Posted by drgoro

Something peculiar happened the other night. I pulled my AP brick 26470OR, out wound it up and went on my business; bored I started the chrono; it stopped after 30sec, so did the regular time keeping. So I just pulled the stalk out and wound it again...it didn’t restart. So I reset the chrono, and tried to wind...again nothing. I rotated the watch in a figure 8 and that got the time keeping back. I set the watch down to intentionally let it die, and after it did, I wound it and the time keeping started fine. Is this normal? Does having the watch die while using the chrono prevent the stalk from winding the movement? Or is it a defect?

Could be time for a visit to Clearwater after the Hurricane my friend!

Maybe a rooted rotor? lol

[TheDude]

Dr G and I are friends IRL - when he told me about this I wondered if it’s ever possible to wind the movement when the chrono function is engaged. This could be something to try - if it’s a lockout imposed by the design it may have nothing to do with the fact that it was stopped when he tried.


Sent from my iPhone using Tapatalk