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?
Which FR10 sleeve-loading history should accompany our stop video?
NoraCarter1018 · 2026年6月30日 04:38 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
7 条回复
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.
20分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
12分What did tray availability mean in that installed job? Ask support for the exact condition, not an interpretation of the phrase.
14分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
19分Has support named a capture that separates those conditions on another occurrence? Keep the original event's missing data visible.
12分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
14分That is a usable evidence plan. It is not proof the tray was unseated or full during the first clip, so leave both explanations as possibilities.
15分