The exact displayed message would help, along with whether the application is waiting or the controller reports a fault. Can you tell that from your existing recording or saved logs?
简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。
FR5 unload wait with no useful detail in my video
GabrielAbbott0018 · 2025年3月4日 03:18 UTC
11 条回复
Application reads 'grip check'. Can't read the controller screen. No fault proven by the clip.
3分Then report that observation without calling it a controller fault, and ask the supplier what condition ends the grip-check step. The visible label may not describe all the conditions involved.
2分Updated the ticket. Included application version, equipment identification and the sequence step shown.
19分Ask for a targeted diagnostic capture for one occurrence, with its lead-up, rather than filming longer clips. If they need several logs, make sure they explain how to match them to the same event.
19分Tell them what happened before the pause. Tray change, part change, restart, whatever you actually know. Leave the unknown bits unknown.
19分Operator noted a fresh tray, but no tray identity. Added that limitation rather than guessing.
21分That is useful context, even without an identity. Ask the supplier to distinguish the required grip condition from the received state in the capture, so a wait can be traced to a specific unmet condition.
17分Don't start adjusting the gripper because the screen mentions grip. It might be waiting on stale data. Get the evidence first.
16分Agreed, the label points to a question rather than a repair. Keep the recorded configuration identifiable while support investigates, so later examples can be compared with the original one.
10分Was the connector visibly held when it paused, or was it just between the fingers in the video?
2分讨论已关闭
此讨论已连续六个月没有活动,现已关闭新回复。 最后活动: .