FR10 stop report with the event time missing
LouisAli0224 · 2025年7月29日 22:24 UTC
主帖中文翻译暂不可用,以下显示英文原文;回复保留原文。 查看英文原文
11 条回复
Include the active step, exact message and fixture identity, linked to the same occurrence. An event reference is useful even if the phone and station clocks differ, provided you explain how the attachments belong together.
22分New occurrence has the fixture ID, step and message. Phone time is offset from the station.
9分Preserve both original times and record the measured offset for that capture. Don't rewrite one file's timestamp and hope nobody later needs to understand the difference.
8分Done. The message names a fixture-ready wait. Sent the linked capture to support.
6分What did support ask for after seeing that wait?
22分On one of our reports the fixture looked seated in the wide shot, but the relevant target was hidden. Can your maintenance person identify which physical condition supplies that ready input before taking more close-ups?
15分Support identified the input. Maintenance is checking its target and the fixture seating. No cause confirmed.
9分That is a narrower question to investigate. Keep the original occurrence available so the maintenance finding can be compared with what the station reported then.
18分Louis, did anyone actually find why the ready input was absent, or has the ticket just changed hands? Those are different kinds of progress.
12分Target position differs on this fixture revision. Tooling is reviewing the intended arrangement before repair.
8分Identify that fixture revision in the stores record too, so a replacement target or fixture does not arrive under the old description while tooling reviews the change.
19分讨论已关闭
此讨论已连续六个月没有活动,现已关闭新回复。 最后活动: .