Skip to content
RepWatchForumSign in

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 21 total)
TimeLog 02449Participant

Case 42 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me? · source wording exercise

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.

Review focus: source wording. Retain the source wording beside any paraphrase. Use the original answer fragment “Without those fields, the rate, amplitude and beat-error values lack…” as the discussion anchor; no new event or result is supplied.

Exercise RWF-26818/42: address this question within its stated limits.

TimeLog 02449Participant

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

Describe visible bridge shapes and markings separately from the proposed identification. Ask a qualified watchmaker to inspect it if identification matters for servicing; do not open the case merely for a forum answer.

TimeLog 02449Participant

Case 4 — Packing photographs: document condition without exposing an address

Summary draft for “Packing photographs: document condition without exposing an address”: the answer addresses “Photograph the item and protective packing…”; the related point is “Remove names, addresses, barcodes and tracking tokens from public…”. 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 02449Participant

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

Correction note for “Seller review template: facts, dates and unresolved questions”: retain the wording beginning “Use fields for order date, promised terms, dated…” 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 02449Participant

Method note for “Crown operation: when a forum cannot diagnose the resistance”: use “Describe whether resistance occurs during winding or setting 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 02449Participant

Clarification for “What a water-resistance claim does and does not establish”: the point beginning “Ask a qualified watchmaker about a suitable test for that individual…” 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 02449Participant

State whether thickness includes the highest point of a domed crystal. Different measurement methods can produce different figures, so keep both the source and method beside each dimension.

TimeLog 02449Participant

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.

TimeLog 02449Participant

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.

TimeLog 02449Participant

Case 24 — Packing photographs: document condition without exposing an address

A condition record is useful but a shipping label contains personal information. How can the record be shared safely?

Exercise RWF-15814/24: address this question within its stated limits.

TimeLog 02449Participant

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

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.

TimeLog 02449Participant

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.

TimeLog 02449Participant

Case 30 — Strap compatibility: width is only the first measurement

Two straps share the same nominal width but differ in thickness and spring-bar clearance. Which dimensions need checking?

Exercise RWF-10720/30: address this question within its stated limits.

TimeLog 02449Participant

Case 7 — Reading a timegrapher recording without losing the context

Summary draft for “Reading a timegrapher recording without losing the context”: the answer addresses “Keep the complete recording and ask for the…”; the related point is “A single number cannot establish service condition, movement identity…”. 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 02449Participant

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

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