Our imported FR10 sleeve-loading package stops intermittently. Fifty-one-day ticket with the unnamed Alibaba seller, who wants more information after my clip. What should maintenance match to it before we offer a diagnosis?
Occurrence time, exact message, active step and installed program and tooling references. Then the relevant retained input and output history from that occurrence, not healthy screenshots collected after restart.
The clip starts after the stop. Shift note gives the time, and maintenance found the installed job export. Controller history shows a wait for tray availability, with no alarm recorded in that interval
It requires the identified receiving tray seated and not full. We don't have the individual conditions captured at the old stop, so the historical wait remains unexplained beyond that definition
Yes, seated and full states are now separately retained with the job step. No new occurrence captured yet. The maintainer owns that check, and the shift lead knows which message and tray identity to record