GabrielAbbott0018 · 4 Mar 2025, 03:18 UTC
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?
6 pointsApplication reads 'grip check'. Can't read the controller screen. No fault proven by the clip.
3 pointsThen 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 pointsUpdated the ticket. Included application version, equipment identification and the sequence step shown.
19 pointsAsk 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 pointsTell them what happened before the pause. Tray change, part change, restart, whatever you actually know. Leave the unknown bits unknown.
19 pointsOperator noted a fresh tray, but no tray identity. Added that limitation rather than guessing.
21 pointsThat 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 pointsDon't start adjusting the gripper because the screen mentions grip. It might be waiting on stale data. Get the evidence first.
16 pointsAgreed, 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 pointsWas the connector visibly held when it paused, or was it just between the fingers in the video?
2 pointsThis discussion is closed to new replies after six months without activity. Last activity: .