Our sleeve-unloading package from an Alibaba seller has an intermittent wait. The phone clip shows the FR10 stopped, but the diagnostic page names the previous fixture. I want to send useful evidence without calling this a fault in whichever fixture happens to be on screen.
Which FR10 wait should our sleeve-unloading support clip identify?
ClaraAllen0263 · 2026年1月2日 10:10 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
6 条回复
I've had a useful sample sitting in the box while the summary showed something else, so I'd start by identifying the fitted sleeve fixture independently of that page. Then ask the program owner what the displayed name represents, and match the actual wait to its own history before support assigns it to a fixture.
10分Current fixture is identified from its label and the job record. The screen retains the last completed fixture name while it waits. I've told support that the displayed name isn't the current fixture identity.
16分Does the exported history identify the current attempt, Clara? A corrected caption on the video won't help if the log summary also carries the previous name.
12分Original events have an attempt reference; summary only shows the retained name. Developer is checking the current reference against the controller and PLC records. No cause assigned yet.
19分Keep the original clip and exports with that explanation. The mistaken name is useful evidence about the reporting problem, even though it shouldn't decide which physical fixture support investigates.
21分And put the current-identity capture step in the shift note. Otherwise the next person will quite reasonably film the same misleading page again.
19分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .