Stopped connector job, questionable message screenshot

MayaChen1171 · 15 Jul 2025, 18:32 UTC

Closed
MA
MayaChen1171
Our imported UR5e connector loader pauses after the fixture closes. The screenshot in my seller support ticket says clamp open timeout, which does not match what I watched. They want another video. How do I establish which message actually belongs to the stop?

18 replies

LU
LuisAbbott0086
Replying to MayaChen1171

I once sent a screenshot of the last alarm while the station was waiting on something else entirely. Check whether your screen is showing an active condition or a historical entry before trying to explain the mismatch.

8 points
MA
MayaChen1171
Replying to LuisAbbott0086

The operator opened the alarm page for the photo. I assumed the top line was current. I will check how the page is sorted.

18 points
LU
LuisAbbott0086
Replying to MayaChen1171

Could be as simple as that.

25 points
MA
MayaChen1171
Replying to LuisAbbott0086

Top line was the oldest retained entry. The photo belongs to the right stop, but the selected alarm does not. Corrected the ticket and asked maintenance for the active sequence state.

14 points
LU
LuisAbbott0086
Replying to MayaChen1171

Thanks for posting that distinction. It is easy to have a genuine photo tell the wrong story when the page needs explaining.

21 points
AD
AdaAdams0129
Replying to MayaChen1171

What was physically in the fixture during the pause, Maya? I would include whether the connector had already been placed, as well as which message the screen selected.

15 points
MA
MayaChen1171
Replying to AdaAdams0129

Connector placed, fingers withdrawn. Fixture closed around it. I described the pause as after fixture closes, but left the completed placement out of the report.

15 points
LU
LuisAbbott0086
Replying to MayaChen1171

That should help whoever reads the sequence. Have they told you which state they want captured if it happens again?

6 points
CH
ChenAdams0094
Replying to MayaChen1171

I would add how long the station was unavailable on each occurrence. Not a diagnosis, I know, but our planner could not arrange cover when every report just said intermittent. We needed the interruptions separated rather than one growing total.

16 points
AD
AdaAdams0129
Replying to ChenAdams0094

Chen, would you count the time waiting for support separately from the actual stopped-cycle time? Those have been very different on our lab jobs.

24 points
NO
NoahArcher0368
Replying to AdaAdams0129

They were different on a teaching cell I covered too. A short interruption ate a whole class because nobody authorised to deal with it was available. The event itself and the loss of use both mattered. I would avoid squeezing either into one neat downtime number.

21 points
CH
ChenAdams0094
Replying to AdaAdams0129

Yes, Ada, separate entries. I meant the time the station could not be used for the planned work, with the reason for waiting alongside it. Otherwise it sounds as though the equipment spent the whole interval producing the fault.

12 points
MA
MayaChen1171
Replying to LuisAbbott0086

Support has asked for the active step and two named ordinary fixture inputs. Maintenance can capture them together. I've also added the stopped time and the wait for assistance as separate fields.

10 points
LU
LuisAbbott0086
Replying to MayaChen1171

Who gets the capture when you're not there? You have done the hard work of narrowing the request; it would be a shame for it to sit in one person's phone.

22 points
AD
AdaAdams0129
Replying to MayaChen1171

Does support want those inputs before or after the fixture closes? Their requested window should be clear to the person collecting it.

15 points
MA
MayaChen1171
Replying to AdaAdams0129

They asked for the sequence around closure, including the lead-in. Maintenance set that capture up. It goes to the shared ticket mailbox, Luis, with the occurrence identified.

13 points
MA
MayaChen1171
Replying to MayaChen1171

A repeat is captured now. Support says the station is waiting for a clearance input that has not changed. Maintenance is checking the relevant target arrangement. No repair confirmed yet.

13 points
NO
NoahArcher0368
Replying to MayaChen1171

Maya, can the next shift see that specific investigation on the handover? Otherwise someone will reopen your old clamp-open screenshot and send the whole thing backwards.

17 points

Discussion closed

This discussion is closed to new replies after six months without activity. Last activity: .