After following this thread, and posting about my watch that stopped 3 times when activating the chronograph, but working perfectly afterwards I did try the little experiment others have.
So I usually fully wind my watch every day between 0900 and 1000 in the morning. When I say fully wind, I take of the watch, turn the crown clockwise until I feel that it stops. But I wanted to try the experiment others have, so I fully wound the watch on Tuesday, and let it run until it stopped.
Tuesday morning I wound the watch fully and started the chronograph. When I woke up Thursday, the watch had stopped, I took a picture and the time showed 05:28:58. The chronograph showed that 7 hours, 23 minutes and 58 seconds had elapsed. So by my calculation, the watch had run for a total of 43h, 23min, 58 sec.
I then stopped the chronograph, and the watch started, I let it run for about 1 minute, and started the chronograph again, it started, but stopped not long after. I took a new picture, now the chronograph showed 7h, 35min, 58 sec. Again I stopped the chronograph, and the watch started running again.
I then let the watch run for the rest of the day, with the chronograph stopped. Before bed I pushed the top button to start it again, but then the watch stopped again. I stopped the chronograph and the watch starter running. So I let it run through the night and when I woke up Friday, the watch had depleted it power reserve and was completely stopped.
To calculate approximately how long the watch had run combining the time with and without the chronograph being activated, I looked at the time the watch showed.
At the picture where the watch had stopped for the first time, and we already knew that the watch had run 43h 23min and 58sec, the time was 05:28:58, the actual time was 08:25. I took another picture before I went to bed, at 23:22, then the watch showed 08:26:03, that means the watch had run for additional ~15h. When I woke up at Friday 08:52 the watch showed that the time was 01:45:05, that means another ~5h and 20 min.
So in total, the watch had run for about 43h 20 min with the chronograph activated, and adding 15h plus 5h and 20min, the grand total was approximately 63h 40min.
So I take away three main points based on the discussions in this thread.
- Note that after the 43h, the chronograph seconds hand stoped at 58 sec both times. This tells me that I also have an issue that is similar to the original issue described by @stevec14
- The power reserve with the chronograph running is below the advertised 50h, but way above with the chronograph disabled.
- As @Archer mentions in the quote below, the issue I experience does indeed seem to be this:
Since it seems I need to keep saying this, yes I agree. I understand completely that people expect something to work as it should, and that they are disappointed when it doesn't.
This is a fundamental misunderstanding of what the problem actually is. This is not a "chronograph" problem, so "pushing buttons" during the testing isn't relevant. It's an "excess load" problem created by the deterioration at the center wheel and the black debris generated. I'm not allowed to show Omega internal communications, but the photos they have sent make it clear what the problem is.
This adds drag to the movement, and brings the balance amplitude down. Once the chronograph is started, it adds even more load, and the watch stops. The problem is not the starting of the chronograph, but the lack of power from the center wheel issue. The fact that the watch stops when the chronograph is started is just the symptom.
I actually talked about this once already in this thread...
Since I made this post Omega released additional information, including the photos I spoke of above., This confirms to me that this is an amplitude problem, and not a chronograph problem.
Good luck with your emails to Arnaud, but Omega already knows what the problem is and how to fix it. They don't really need your help.
Cheers, Al
So to conclude, I will be taking my speedy back to the AD and hope they can resolve it fairly quickly. It does suck, since this is my first expensive watch, and It is barely a month old, but then again, it does seem that a fix is in place and it is possible to solve.