Can't call this an FR5 gripper fault from a silent clip

RuthBailey · 12 Sept 2025, 09:53 UTC

Closed
RU
RuthBailey
Our FR5 housing-unload report says gripper fault because the arm waits with the housing still held, but I never captured the pendant message and the clip ends before anything changes; what should I ask the next shift to collect without sending the seller another diagnosis we made up?

15 replies

CA
CalebBrown0928
Replying to RuthBailey

Ask for the exact message, active step and time from the same pause, with the fixture identity. Then describe where the housing is without naming a failed component yet.

6 points
RU
RuthBailey
Replying to CalebBrown0928

I can supply unit and program identifiers now, but the old message is lost; the operator remembers destination waiting, which I am leaving as a recollection rather than putting it in quotation marks.

9 points
AA
AaronAllen0262
Replying to RuthBailey

Keep that recollection beside the old clip, but do not turn it into the exact message for a new event just because the stopped pose looks similar.

21 points
LU
LuisChan1130
Replying to RuthBailey

Who can collect the next occurrence when you're not there?

11 points
JO
JonasBell0633
Replying to CalebBrown0928

We once captured the right message and the wrong fixture name. Put a photo of the actual fixture identifier in the report if there is one, rather than using whichever name the shift happens to call it.

8 points
NA
NathanBarnes0547
Replying to LuisChan1130

And who has the seller's answer afterwards, the shift lead or just your inbox?

16 points
RU
RuthBailey
Replying to NathanBarnes0547

Luis and Nathan, shift lead owns capture and the shared ticket; Jonas, the new occurrence includes fixture D6's label, with a waiting for destination positioned message at unload-place and the same-occurrence time.

2 points
DI
DineshCarter0995
Replying to RuthBailey

Ask controls what destination positioned means in this program, since the name may combine several conditions rather than point to one detector.

15 points
CA
CalebBrown0928
Replying to DineshCarter0995

That is the question I'd put to support too, with D6 and the program version. The new capture gives them a specific sequence condition to explain.

6 points
AA
AaronAllen0262
Replying to RuthBailey

Do you have the input state from that same occurrence, or only a screenshot taken after someone moved the destination back?

12 points
RU
RuthBailey
Replying to AaronAllen0262

Same occurrence, Aaron; controls says one destination-location input is missing, and maintenance is checking the D6 target arrangement before we change any sequence handling.

1 points
JO
JonasBell0633
Replying to RuthBailey

Keep the supplied drawing revision with that inspection. On ours a target looked displaced until we found the drawing described an older fixture, so the visible difference alone had sent us towards the wrong repair.

18 points
RU
RuthBailey
Replying to JonasBell0633

Maintenance has D6 revision C, matching its identification, and found a loose target mounting; repair is proposed but not completed, with the original gripper-fault title corrected in the shared ticket.

12 points
NA
NathanBarnes0547
Replying to RuthBailey

Will the shift lead get the repair and trial result before the ticket gets closed?

21 points
DI
DineshCarter0995
Replying to RuthBailey

And keep the old clip unmatched in that final explanation; a useful finding on D6 should not silently become the cause of every previous pause.

18 points

Discussion closed

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