Skip to content
RepWatchForumSign in

Forum Replies Created

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

Case 14 — QC checklist: prioritise observable faults over pixel hunting

Clarification for “QC checklist: prioritise observable faults over pixel hunting”: the point beginning “Start with function, legibility, assembly and…” 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.

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

Common advice says service every five years, but service is expensive and some people run watches much longer. What observable signs actually indicate a mechanical watch needs attention, as opposed to just being due on a calendar?

Exercise RWF-29432/22: address this question within its stated limits.

Case 20 — Crystal reflections: why a dark patch is not a coating test

Method note for “Crystal reflections: why a dark patch is not a coating test”: use “No single lighting setup settles…” 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 17 — First QC request: the minimum useful information

Clarification for “First QC request: the minimum useful information”: the point beginning “State the model configuration, the specific concern and…” 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.

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

The lift angle must match the movement specification for the amplitude reading to be meaningful. If it is unknown, label amplitude as provisional instead of accepting the instrument default.

Case 27 — QC checklist: prioritise observable faults over pixel hunting

Summary draft for “QC checklist: prioritise observable faults over pixel hunting”: the answer addresses “Start with function, legibility, assembly and…”; the related point is “Explain what the full-size image shows, what the crop adds and…”. 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.

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

Amplitude depends on the movement and measurement setup. Compare it with appropriate specifications and a qualified watchmaker’s assessment; a universal pass/fail threshold would be misleading.

Case 30 — Service enquiry: information a watchmaker can use

Method note for “Service enquiry: information a watchmaker can use”: use “Document when it stops, winding behaviour, recent impacts and…” 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.

If the manufacturer provides a suitable procedure, a running-time log can support a service enquiry. State the winding method and stop time. A shortened run does not identify the cause by itself.

Clarification for “Comparing dial colour under different lighting”: the point beginning “State the lighting and…” 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.

Can the same settings and winding state be used for several positions? Record each position separately rather than combining measurements taken under different conditions.

Document spring-bar diameter, end-tip fit and the strap’s clearance using appropriate measuring tools. If dimensions or compatibility are uncertain, ask a watchmaker rather than forcing a bar or substituting an unsuitable part.

Lug width is the essential one: the inside distance between the lugs where the strap fits. Measure with a ruler marked in millimetres, ideally reading it under magnification. Most watches use even numbers (18, 20, 22mm), but odd widths exist. If you measure 19 or 21, measure again and check the manufacturer spec before ordering.

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

Common advice says service every five years, but service is expensive and some people run watches much longer. What observable signs actually indicate a mechanical watch needs attention, as opposed to just being due on a calendar?

Exercise RWF-11716/26: address this question within its stated limits.

Case 32 — First QC request: the minimum useful information

Correction note for “First QC request: the minimum useful information”: retain the wording beginning “State the model configuration, the specific concern and…” in the record. If later material changes it, add the date, the changed wording and the source for that change; do not invent a completed correction here. Keep the stated question separate from any broader claim.

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