Skip to content
RepWatchForumSign in

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 25 total)
TimeLog 00289Participant

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

Correction note for “Lug-to-lug and end-link overhang in wrist photographs”: retain the wording beginning “Record lug-to-lug and the effective span…” 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.

TimeLog 00289Participant

Distinguish label creation from physical acceptance and retain dated event text with personal details removed. Ask the sender or carrier for clarification; missing scans alone do not establish loss or seizure.

TimeLog 00289Participant

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

Log the rate over several comparable days, identify the correct specification and state the conditions. Stable and changing patterns raise different questions; a watchmaker can assess whether regulation, inspection or no action is appropriate.

TimeLog 00289Participant

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

Reader check for “Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log”: distinguish the discussion point “Two cases 2mm apart in diameter can be within 1mm of…” 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: comparison. Make the basis of a comparison explicit before interpreting it.

TimeLog 00289Participant

Reader check for “First QC request: the minimum useful information”: distinguish the discussion point “State the model configuration, the specific concern 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.

TimeLog 00289Participant

Method note for “QC checklist: prioritise observable faults over pixel hunting”: use “Start with function, legibility, assembly 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.

TimeLog 00289Participant

Correction note for “Disputed observation: is this dial colour shift real or just lighting?”: retain the wording beginning “The difficulty is that phone cameras adjust white balance automatically,…” 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.

TimeLog 00289Participant

Case 24 — Crystal types: sapphire, mineral and acrylic trade-offs for daily wear

The core trade-off is scratch resistance versus shatter resistance. Sapphire is very hard to scratch but can chip or crack from a sharp impact on an edge. Acrylic scratches easily but flexes, rarely shatters, and light scratches can be polished out at home. Mineral glass sits in between and is often the cheapest to replace.

TimeLog 00289Participant

Clarifying question first: do you have a baseline? If you've never recorded the watch's rate or power reserve, 'drifting' is hard to judge. Start a simple log now with daily offset against a reference time for a week, and the hours it runs from full wind. Once you have that, later changes mean something.

TimeLog 00289Participant

Case 3 — Crown operation: when a forum cannot diagnose the resistance

Summary draft for “Crown operation: when a forum cannot diagnose the resistance”: the answer addresses “Describe whether resistance occurs during winding or setting and…”; the related point is “Stop forcing it and arrange inspection rather than trying…”. 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.

TimeLog 00289Participant

Case 13 — Crown operation: when a forum cannot diagnose the resistance

Correction note for “Crown operation: when a forum cannot diagnose the resistance”: retain the wording beginning “Describe whether resistance occurs during winding or setting 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.

TimeLog 00289Participant

Clarification for “Forum comparison archive: link the evidence and the correction”: the point beginning “Preserve the reasoning trail instead of silently replacing an…” 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.

TimeLog 00289Participant

Summary. Pick sapphire for scratch resistance in low-impact use, acrylic for impact tolerance and easy polishing, and mineral as a low-cost middle option. Prefer inner-surface AR if you're worried about wear. Look at crystal profile when comparing thickness. Choose by how you'll use the watch, not by the material label.

TimeLog 00289Participant

One method that often helps without any service is using overnight resting position to cancel daily drift. Many watches gain in some positions and lose in others. If yours loses on the wrist, try leaving it crown up or dial up overnight and log the result for a few nights. Some people get close to zero this way.

TimeLog 00289Participant

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

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