WatchUSeek Watch Forums banner

Tissot Powermatic 80 suddenly lost accuracy?

1 reading
22K views 29 replies 9 participants last post by  BenchGuy  
#1 ·
Greetings! I have a Tissot "Luxury" Automatic with the Powermatic 80 movement. It was running fine at around -2 seconds per day. Now it's suddenly losing about 10-15 seconds per day. It's better dial up (seems to either not lose any time or only lose a couple seconds) but on the wrist or crown down it's gotten terrible. Any advice on what to do? I'd like to get it back to where it was if possible.

The watch is fully wound.
 
#6 ·
A little over a year ago. I think I might send it back unless someone recommends something. It's still under warranty. Was it magnetized maybe? Double checked and it's a solid 16 seconds or more slow per day on the wrist. It was fine.
This is a relatively "new" caliber. It is not outside the realm of possibility that it now requires service. Curious: Has your wear pattern changed? As a metric, these cumulative dynamic timing observations are of limited diagnostic value. Instantaneous rates, in static positions with known winds are optimal.

. . . My Omega tends to lose more when the mainspring is low. . . .
What model timing machine are you using to measure this? What caliber is your Omega?
 
#12 · (Edited)
Ok....So you are saying that is not possible? Maybe it has more to do with the watches position and not it's mainspring? Your name is pithy but maybe you could expound on this little. Edit- now I found a better explanation of isochronism- you saying that my watch is out of whack and needs adjustment.
In general, the greater the remaining wind, the greater the amplitude and the slower the rate. Hence, as the wind dissipates and the amplitude drops - the rate increases. Got you thinking, huh?
 
#16 · (Edited)
Of course after I posted this it lost 5 seconds over 12 hours and one second overnight, dial up. After looking back at my records after I noticed the issue it was losing about 15-20 seconds for 3 or 4 days. And before that it literally was losing between 2-4 seconds per day. I'll keep an eye on it for the next week or so. Any reason why it gets wonky like that?
 
#17 ·
. . . Now it's suddenly losing about 10-15 seconds per day. . . .
. . . Double checked and it's a solid 16 seconds or more slow per day on the wrist. . . .
. . . I just wound it about 40 times last night and another 20-30 today and it's still going that slow.
. . . Of course after I posted this it lost 5 seconds over 12 hours and one second overnight, dial up. After looking back at my records after I noticed the issue it was losing about 15-20 seconds for 3 or 4 days. And before that it literally was losing between 2-4 seconds per day. . . .
That's got to be driving you crazy. :-d
 
#18 ·
. . . Now it's suddenly losing about 10-15 seconds per day. . . .
. . . Double checked and it's a solid 16 seconds or more slow per day on the wrist. . . .
. . . I just wound it about 40 times last night and another 20-30 today and it's still going that slow.
. . . Of course after I posted this it lost 5 seconds over 12 hours and one second overnight, dial up. After looking back at my records after I noticed the issue it was losing about 15-20 seconds for 3 or 4 days. And before that it literally was losing between 2-4 seconds per day. . . .
That's got to be driving you crazy. :-d
 
#25 ·
I don't know the Watchville app but yes, it probably does synch with an atomic clock. Most (if not all) internet time services do.

But problems can occur in two ways:

If, for any of the reasons I mentioned, an app fails to synch. Then you're entirely reliant on the local timebase in the phone / pc / tablet / whatever to keep the clock right, and these local timebases can be surprisingly inaccurate. So, if it fails to synch for a day or two, you can be several seconds out.

The quality of the ntp or sntp implementation on the device itself. As an example, Windows uses sntp instead of ntp (a simpler version with less rigorous error checking) and Microsoft only specify the Win32 Windows Time Service as reliably synching within 1 - 2 seconds of GMT. For that, you'd do better with most ordinary quartz watches! I have no idea what the iPhone's implementation is like, whether Watchville has its own implementation, or whether it uses full ntp or sntp as Windows does, so can't comment on the quality of synch you might get.

The bottom line is that, without knowing exactly how the whole system has been specified, simply "synching to an atomic clock" doesn't necessarily mean atomic clock accuracy at any given time.

That's why I'd suggest getting a cheap digital alarm with "atomic" synching. That way, even with the cheap ones, you have a local timebase that's within 0.5 sec / day and 2 or 3 attempts at synching each day to a completely reliable radio source with virtually no latency - it doesn't take long for the signal to get to you when it's travelling at the speed of light direct from the nearest transmitter!
 
#23 ·
Not that anyone cares anymore but earlier I posted that I though my watch was getting slower as the spring wound down. Pithy pointed out that that was the opposite of what normally happens. Thanks to that info, I investigated further and found out that I was completely wrong in my observation and had made a really stupid mistake in monitoring my watch's performance (I don't want to get into it but it was stupid.) Thanks to Pithy I learned two things- 1) why a watch tends to speed up as the reserve goes down and 2) my own watch was behaving much better than my initial measurements showed. Cool. Thanks.
 
#24 ·
You are welcome. It's obvious that you are a seeker of knowledge and that's a good thing. There is a great deal of it available here in the F6 - not only with regard to watches but to life as well. And I have learned something from virtually everyone that posts here.

While the F6 is above average in its generosity it is also absolutely unforgiving with regard to having the manner in which it bestows that generosity questioned. The sooner that this is understood and accepted the more positive and beneficial one's relationship with the F6 can be.
 
#27 ·
I purchased the watchtracker app ($5) on my iPhone and before measuring my watch it syncs to atomic clock (even tells you it's accuracy, usually like .001s). So every time you do this its going to be as accurate as using the radio signal as they would be also synced to the atomic clock. And it's so convenient as you have a full log and graph of all the watches you monitor.

i seriously should get a kickback from watchtracker ��
 
#28 ·
Any time system synchronizing across a complex packet driven network has delays as Joe has detailed. As mentioned. Just because your iDoodah gives you a number does not make it true - even if the original time is based on an atomic clock. It may however, sync to the GPS time stamp (if the signal is available) and therefore be a good reference. That depends on the software and how well it is written.

Incidentally, each GPS satellite has 3 atomic clocks which are averaged, they then are all corrected many times each day by the ground station (US Military controlled) which again has a minimum of three atomic clocks that are also then averaged. So as actually four (three theoretically, but in practice a minimum of four are needed) satellites are used to find a position, including the base station - the final time/position source has used a minimum of (5*3) 15 atomic clocks to establish a time/position reference :)

Tom
 
#29 ·
Any time system synchronizing across a complex packet driven network has delays as Joe has detailed. As mentioned. Just because your iDoodah gives you a number does not make it true - even if the original time is based on an atomic clock. It may however, sync to the GPS time stamp (if the signal is available) and therefore be a good reference. That depends on the software and how well it is written.

Incidentally, each GPS satellite has 3 atomic clocks which are averaged, they then are all corrected many times each day by the ground station (US Military controlled) which again has a minimum of three atomic clocks that are also then averaged. So as actually four (three theoretically, but in practice a minimum of four are needed) satellites are used to find a position, including the base station - the final time/position source has used a minimum of (5*3) 15 atomic clocks to establish a time/position reference :)

Tom
Fairpoint about the packet delays!

Had to be the US military controlling that too :( (as if they don't control enough in the world)

Sounds good in theory but in practice would there be a tangible (more than a second) difference between the both?
Im guessing there wouldn't be. If I have 20ms ping to my internet and they had a better ping, it still wouldn't equate to 1000milliseconds or 1second difference.

Well it could be proven I guess if I purchase one and compare every 24hrs for a week or so. Whats the cheapest one I could get? Any radio controlled watch?