Skip to content
RepWatchForumSign in

Forum Replies Created

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

Case 23 — Reading a timegrapher recording without losing the context

Method note for “Reading a timegrapher recording without losing the context”: use “Keep the complete recording and ask for the…” 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 1 — Maintenance question: how do I tell if an automatic actually needs service?

A sudden rate change has several possible causes. Ask a watchmaker to test suspected magnetism rather than diagnosing it from a compass or attempting an adjustment based on forum replies.

Clarification for “QC photography: what photos actually help verify a pre-owned listing?”: the point beginning “Ask for a straight-on dial photo with diffuse light and no…” 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 2 — Crystal types: sapphire, mineral and acrylic trade-offs for daily wear

Spec sheets list sapphire, mineral or acrylic crystals, and opinions in threads are very strong. For a daily-wear watch, what are the real trade-offs, and is an anti-reflective coating worth paying for?

Exercise RWF-23699/2: address this question within its stated limits.

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

Clarification for “Movement identification: the limits of a rotor photograph”: the point beginning “Describe visible bridge shapes and markings separately…” 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 5 — Clasp photographs: what to request before judging alignment

Request open and closed views from both sides, with the watch supported safely. Separate cosmetic alignment from whether the clasp engages reliably; functional concerns need hands-on inspection.

Keep the date, work performed, provider invoice reference and test results where available. Redact addresses and payment information; do not invent service events to fill an empty history.

Case 40 — Bracelet fit: half-links, micro-adjust holes and the 'between sizes' problem · source wording exercise

Summary draft for “Bracelet fit: half-links, micro-adjust holes and the 'between sizes' problem”: the answer addresses “Fit often improves by moving one link from the 6 o'clock…”; the related point is “That doesn't change length, but it shifts where the clasp sits…”. Keep both connected to the opening question, and mark any conclusion needing further records as unresolved. Review focus: source wording. Retain the source wording beside any paraphrase.

Case 16 — 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-16224/16: address this question within its stated limits.

Case 25 — Clasp photographs: what to request before judging alignment

Limit of the answer in “Clasp photographs: what to request before judging alignment”: “Request open and closed views from both sides,…” 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.

Case 5 — 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.

A dated note in the frame can support a claim that photographs are recent, but it is not conclusive proof of ownership, authenticity or an honest transaction. Treat it as one limited check alongside independent verification.

Before the table goes live, a question: are you comparing current production only, or older references too? Dial printing, lume colour and crown signing often changed between batches. If older pieces are in scope, add a production-period column, or every disagreement will look like an error when it's really a running change.

Case 33 — Beginner glossary Q&A: complication, caliber, jewel count, power reserve

A complication is any function beyond hours, minutes and seconds. A date window counts, technically, and so do a chronograph, GMT hand or moon phase. More complications usually mean more parts, more thickness and more service cost. For a first everyday watch, decide which functions you'd really use before treating them as value.

Case 29 — Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?

Start with how you measured it. Comparing against a phone clock once a day for a week, at the same time, and noting the offset is reliable enough. One 24-hour reading isn't, because rate depends on wrist time, position overnight and state of wind. Average across several days before deciding anything.

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