![]() |
ROLEXROLEXROLEXROLEXROLEXROLEX
ROLEXROLEXROLEXROLEXROLEXROLEX
|
View Poll Results: Does your 32xx movement seem to be 100% ok? | |||
Yes, no issues |
![]() ![]() ![]() ![]() |
1,039 | 69.83% |
No, amplitude is low (below 200) but timekeeping is still fine |
![]() ![]() ![]() ![]() |
61 | 4.10% |
No, amplitude is low (below 200) and timekeeping is off (>5 s/d) |
![]() ![]() ![]() ![]() |
388 | 26.08% |
Voters: 1488. You may not vote on this poll |
![]() |
|
Thread Tools | Display Modes |
|
![]() |
#1 |
"TRF" Member
Join Date: Apr 2012
Location: USA
Posts: 1,526
|
32xx movement problem poll and data thread
We've got several other threads talking about this movement, but my goal here is to have a single source of real data, both the poll question - has your movement had an issue, yes/no - and actual timegrapher data to give us a feel for "normal" amplitudes. I didn't want to go overboard with poll options so I left it more yes/no. If you had an issue, but have sent it in to RSC and it seems to be better now, please mark this as having an issue as it still represents a problem data point in the field.
Please answer the poll even if/especially if you have not had any issues! If you don't have any amplitude data but you are still having significant timekeeping issues, please choose the 3rd option as well. Here is mine: Brand new 126613LB Sub, worn on and off for 2 weeks. Lift angle set to 53 degrees, Weishi 1000, 4 second period. Watch allowed to settle for 2 minutes after changing positions. Then monitored for another 3 minutes. Full wind (75 winds) DU: +2 to +3 s/d, 256-262 deg CU: -3 to -6 s/d, 208-218 deg DD: +2 to +4 s/d, 250-257 deg CD: 0 to -2 s/d, 216-224 deg For most of the full wind tests across all positions the beat error was 0.2ms. 24 hours later (not worn or moved) DU: +1 to +3 s/d, 231-237 deg CU: -5 to -9 s/d, 185-197 deg DD: +1 to +4 s/d, 222-226 deg CD: 0 to -9 s/d, 188-195 deg For most of the 24 hour tests across all positions the beat error was 0.0ms. |
![]() |
![]() |
![]() |
#2 |
2024 Pledge Member
Join Date: Dec 2009
Real Name: The Mystro ;)
Location: Central Pa.
Posts: 15,177
|
Good job.
You need to add 2 more categories. “amplitude is low (but above 200) and time keeping is slowing.” You are going to find many in that category with not crazy low amplitude but still low and movement is slowing. Then there is those without amplitude measurements and their time keeping is slowing. Lots of owners won’t own a scope and just report their time keeping is progressing getting slower. Every owner can vote to add data if you add those two more categories. |
![]() |
![]() |
![]() |
#3 |
"TRF" Member
Join Date: Feb 2008
Real Name: Chris
Location: .
Watch: Daytonas/Subs/GMTs
Posts: 12,609
|
No idea about amplitude .
DSSD JC 2018 (3235) was -5s/day . RSC (Only Rolex I have ever sent to RSC) Running perfect now . |
![]() |
![]() |
![]() |
#4 | |
"TRF" Member
Join Date: Feb 2008
Real Name: Chris
Location: .
Watch: Daytonas/Subs/GMTs
Posts: 12,609
|
Quote:
Checked for three days,but fully wound every day and resting dial up . It was constantly -5s/day for every day . |
|
![]() |
![]() |
![]() |
#5 | |
"TRF" Member
Join Date: Dec 2020
Location: .
Posts: 2,819
|
Quote:
Thanks for providing data, much acknowledged. Can you continue tests without winding every day? Just do the simple sequence I described in post #97. You can run this test with several watches in parallel. |
|
![]() |
![]() |
![]() |
#6 | |
"TRF" Member
Join Date: Mar 2012
Location: Brisbane
Watch: DSSD
Posts: 7,963
|
Quote:
For simplicity and accuracy. Shouldn't all tests be performed at full wind? What is the purpose of accepting a potential error factor of a partially wound down movement that's undefined, and where it has little bearing on what is deemed to be in the optimal state of wind/power reserve? |
|
![]() |
![]() |
![]() |
#7 |
2024 Pledge Member
Join Date: Apr 2022
Real Name: IDKY that well
Location: Alabama
Watch: Rolex 126660
Posts: 38
|
|
![]() |
![]() |
![]() |
#8 |
"TRF" Member
Join Date: Apr 2021
Location: West Chester PA
Posts: 399
|
|
![]() |
![]() |
![]() |
#9 |
"TRF" Member
Join Date: Dec 2018
Location: Georgia USA
Posts: 366
|
Dropped my 124060 off in NYC at the service center on Feb 1 for the same problem. I was originally quoted 4-6 weeks but when I got my confirmation email it said 9. A little disappointed in that turnaround time along with the fact I had to take my watch in on its 1 year anniversary. It ran slow out of the box from the AD and just got worse over the year.
|
![]() |
![]() |
![]() |
#10 | |
"TRF" Member
Join Date: Aug 2015
Location: London
Posts: 35
|
Quote:
Same as the ones I had. Something very wrong with those. |
|
![]() |
![]() |
![]() |
#11 | |
"TRF" Member
Join Date: Apr 2012
Location: USA
Posts: 1,526
|
Quote:
|
|
![]() |
![]() |
![]() |
#12 | |
2024 Pledge Member
Join Date: Dec 2009
Real Name: The Mystro ;)
Location: Central Pa.
Posts: 15,177
|
Quote:
|
|
![]() |
![]() |
![]() |
#13 |
"TRF" Member
Join Date: Sep 2020
Location: USA
Posts: 58
|
Super curious for the results on this! Just to confirm before I cast a vote, would you like results from all 32xx series movements, inclusive of all complications (i.e. 3285 and 3255)?
|
![]() |
![]() |
![]() |
#14 |
2024 Pledge Member
Join Date: Dec 2009
Real Name: The Mystro ;)
Location: Central Pa.
Posts: 15,177
|
|
![]() |
![]() |
![]() |
#15 |
"TRF" Member
Join Date: Sep 2020
Location: USA
Posts: 58
|
|
![]() |
![]() |
![]() |
#16 |
"TRF" Member
Join Date: Apr 2012
Location: USA
Posts: 1,526
|
Yes! From what the watchmakers have told us, this issue could impact any of the range which is why I specified 32xx in the title.
|
![]() |
![]() |
![]() |
#17 |
"TRF" Member
Join Date: Sep 2020
Location: USA
Posts: 58
|
Understood! I haven't researched the issue too much so wasn't sure if it has impacted some variants more than others. Cast my vote accordingly.
|
![]() |
![]() |
![]() |
#18 |
"TRF" Member
Join Date: Dec 2020
Location: .
Posts: 2,819
|
I had started at the same time a thread "Rolex 3200 Series Movement Data Collection", which I deleted and join here.
The baseline of my approach is a collection of movement measurement data, taken with a timegrapher or other methods, e.g. a smartphone App. Let us collect data since the introduction of the 3200 series at Baselworld 2015. Especially, data taken with recently purchased watches (2020, 2021) are very interesting to see if problems on rates, amplitudes, beat errors still exist or have been solved. I start adding data for my beautiful looking GMT-Master II, Ref. 126711 CHNR (caliber 3285), bought in August 2018 and worn for only about 10 days (max.) until today. ![]() Conclusions Table 1: First measurements 13 months after purchase. After full watch winding all rates are negative, depending on position between -1 s/d and -7 s/d, with amplitudes between 199 and 247 degrees. 7 days later: again full winding, then the calibre performance significantly decreased after 13:50 hours and 25:30 hours; between all measurements the watch remained at rest in position DU (dial up) and was not wound again. ![]() Conclusions Table 2: One year later. After full watch winding, rates in all positions became worse, i.e. from -4 s/d to -12 s/d, amplitudes vary from 191 to 240 degrees. After 11 days, the situation further degraded again, even after full watch winding. Waiting 24 hours (at rest) in DU position reduced the measured amplitudes to only 153 -204 degrees with rates of -10 s/d to -26 s/d. This watch was bought in August 2018, was rarely worn (10 days max.) until today, and its present performance is as listed at the end of Table 2. A clear data-based proof that something is wrong with this 3285 movement. I will give it to Rolex within the 5 years guarantee period. What are your data for the 3200 series movements? Please, always indicate when you bought your watch and the movement number (32xx). An overview in a simple table is probably easier to read than very long text. Photos of your watch are very welcome too. |
![]() |
![]() |
![]() |
#19 |
Banned
Join Date: Mar 2021
Location: Maryland
Watch: Daytona
Posts: 160
|
Quite Educating!!
|
![]() |
![]() |
![]() |
#20 |
2024 ROLEX DATEJUST41 Pledge Member
Join Date: Jan 2010
Real Name: Ed
Location: FL Keys
Watch: my avatar move...
Posts: 2,055
|
I can’t comment on amplitude info as I have no info in that regard.
126600 timing slow by 12+ s/d with first couple of months owning. It was fine originally. I sent it to Dallas RSC for repairs early 2020 and was returned about 3 months later (COVID delays), and worked fine. But within several months it was back at it loosing about the same amount of time as before. It will be going back again unfortunately. ![]() Regards,
__________________
116518-MDL ♛ 126600 SD43 Mark I |
![]() |
![]() |
![]() |
#21 | |
"TRF" Member
Join Date: Feb 2013
Real Name: Flavio
Location: N/A
Posts: 14,654
|
Quote:
|
|
![]() |
![]() |
![]() |
#22 |
"TRF" Member
Join Date: Mar 2012
Location: Brisbane
Watch: DSSD
Posts: 7,963
|
|
![]() |
![]() |
![]() |
#23 | |
2024 Pledge Member
Join Date: Dec 2009
Real Name: The Mystro ;)
Location: Central Pa.
Posts: 15,177
|
Quote:
![]() No one should expect you to believe this is a normal/acceptable part of the ownership experience of a $10k automatic with a accuracy standard. |
|
![]() |
![]() |
![]() |
#24 | |
2024 ROLEX DATEJUST41 Pledge Member
Join Date: Jan 2010
Real Name: Ed
Location: FL Keys
Watch: my avatar move...
Posts: 2,055
|
It is a bit frustrating for sure.
Quote:
When I look at the time on my wrist, I’m not looking at it as an exact time. But when it’s running slow by 2-3+ minutes after 2 weeks (even winding it twice a week while wearing it to rule out that issue), that’s a bit annoying given the cost of the watch. Regards,
__________________
116518-MDL ♛ 126600 SD43 Mark I |
|
![]() |
![]() |
![]() |
#25 |
"TRF" Member
Join Date: Dec 2018
Location: New York
Posts: 75
|
I’m not sure about amplitude but 11 months in to owning my Datejust 126200 it went from gaining 2 second a week to losing 4 seconds a week. Granted it was around the same time that I knocked it pretty hard. Not super happy with a watch losing any time at all but it’s very minor amount and has been stable for the last few months.
Here it is: |
![]() |
![]() |
![]() |
#26 | |
"TRF" Member
Join Date: Mar 2012
Location: Brisbane
Watch: DSSD
Posts: 7,963
|
Quote:
Of course we can't gauge how hard it was knocked and by nature, the results of a knock are a lottery. |
|
![]() |
![]() |
![]() |
#27 |
2024 Pledge Member
Join Date: Jun 2008
Real Name: David
Location: Gardnerville, NV
Watch: 16710
Posts: 2,662
|
I just put my watch on my wrist. If I think about it, every couple of weeks, I check it against my iPhone.
As for the rest of all this? IDGAF, there are many other issues that I'm concerned about.
__________________
Current: 16710 Previous: 16760 Fat Lady, 16613 Bluesy, 16800, 14060, 16710 Pepsi, 216570 Polar, 116710LN, 16610, 216570 Polar (again), 16713, 216570 Polar (yet again), 16710 Black w/ Pepsi Insert Hope is not a strategy. |
![]() |
![]() |
![]() |
#28 | |
"TRF" Member
Join Date: Feb 2020
Real Name: Chris
Location: USA
Watch: Sub Bluesy, DJ41
Posts: 110
|
Quote:
I did have to return it to my AD's authorized Rolex service center to be regulated (Beverly Hills) about 2 months after purchase due to sudden, inconsistent accuracy (+/- 30 to 40 sec per day). It was fixed and runs great now. |
|
![]() |
![]() |
![]() |
#29 | |
"TRF" Member
Join Date: Apr 2012
Location: USA
Posts: 1,526
|
Quote:
|
|
![]() |
![]() |
![]() |
#30 | |
"TRF" Member
Join Date: Dec 2020
Location: .
Posts: 2,819
|
32xx movement problem poll and data thread
Quote:
|
|
![]() |
![]() |
![]() |
Currently Active Users Viewing This Thread: 22 (1 members and 21 guests) | |
sleepydoc |
|
|
*Banners
Of The Month*
This space is provided to horological resources.