Skip to content
RepWatchForumSign in

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 15 total)

Case 35 — Model comparison: dive bezel action and alignment, how to compare fairly

Back-play is the most objective feel measurement. Set the bezel on a click and gently push it the other way without forcing it. Noticeable wobble before it engages means play. A little is common and within normal production, but if one model has visible movement and the other doesn't, that's a real difference you can describe.

Case 13 — Movement identification: the limits of a rotor photograph

Method note for “Movement identification: the limits of a rotor photograph”: use “Describe visible bridge shapes and markings separately…” as a row heading in a proposed working record. Put the statement, its supporting source or measurement, and any unresolved detail in separate fields. This proposes a format; it supplies no additional evidence. Keep the stated question separate from any broader claim.

Case 25 — Maintenance question: how do I tell if an automatic actually needs service?

Sealing and movement performance are separate questions. Ask a qualified watchmaker about inspection and testing appropriate to the particular watch and its intended use; a healthy rate does not establish water resistance.

Limit of the answer in “Movement identification: the limits of a rotor photograph”: “Describe visible bridge shapes and markings separately…” is an excerpt from the discussion, not an independent verification. A reader needs the relevant original material before treating an interpretation as established. Review focus: scope. Keep the stated question separate from any broader claim.

Resolution checklist. 1) Rebalance links around the clasp. 2) Test every micro-adjust hole with each link count. 3) Check fit morning and afternoon. 4) Look for half-links by bracelet reference. 5) Accept slightly loose if the head is light. If none of that works, a strap with finer hole spacing is a reasonable conclusion, not a failure.

Method note for “Model comparison: dive bezel action and alignment, how to compare fairly”: use “Crisp vs mushy is mostly about…” as a row heading in a proposed working record. Put the statement, its supporting source or measurement, and any unresolved detail in separate fields. This proposes a format; it supplies no additional evidence. Keep the stated question separate from any broader claim.

Case 23 — Seller review template: facts, dates and unresolved questions

Summary draft for “Seller review template: facts, dates and unresolved questions”: the answer addresses “Use fields for order date, promised terms, dated…”; the related point is “Leave unsupported fields blank and separate observations from opinions; this…”. Keep both connected to the opening question, and mark any conclusion needing further records as unresolved. Review focus: scope. Keep the stated question separate from any broader claim.

The difficulty is that phone cameras adjust white balance automatically, and blue dials are especially sensitive. Two photos of the same dial under different light can easily look like a 'batch difference'. Any comparison needs both dials in the same frame, under the same light, ideally next to a neutral grey or white reference card.

Clarification for “Lug-to-lug and end-link overhang in wrist photographs”: the point beginning “Use a similar camera distance and neutral wrist position; photographs support…” belongs to the question as written. It should not be read as a report that a new check, purchase or experiment has been completed. Review focus: scope. Keep the stated question separate from any broader claim.

Use the same numeral, camera axis and approximate image scale. Keep the uncropped originals alongside the detail crops and distinguish optical balance from physical window alignment.

Case 6 — Lug-to-lug and end-link overhang in wrist photographs

Method note for “Lug-to-lug and end-link overhang in wrist photographs”: use “Record lug-to-lug and the effective span…” as a row heading in a proposed working record. Put the statement, its supporting source or measurement, and any unresolved detail in separate fields. This proposes a format; it supplies no additional evidence. Keep the stated question separate from any broader claim.

Case 32 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log

Summary so far. Rows: diameter, lug-to-lug, thickness (method stated), lug width, crystal type, water resistance (as specified), movement family, production period. Each row has a source tag. Corrections go in the dated log with old and new values. If nobody objects, that's the template, and later posts should give evidence rather than restate opinions.

Jewel count describes bearings used in a movement design; it is not a quality ranking. Compare the documented movement architecture and service support rather than assuming a higher count makes one watch better.

Reader check for “Crown operation: when a forum cannot diagnose the resistance”: distinguish the discussion point “Describe whether resistance occurs during winding or setting and…” from its proposed application. The thread offers a way to reason about the question, without adding a personal experience or a newly observed outcome. Review focus: scope. Keep the stated question separate from any broader claim.

Case 9 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?

I ran a watch on a basic timegrapher and got +6 s/d, 245 degrees amplitude and 0.8 ms beat error, dial up, about an hour after winding. Is this good, bad or normal? I don't want to send it for service on a single reading.

Exercise RWF-00859/9: address this question within its stated limits.

Viewing 15 posts - 1 through 15 (of 15 total)