Can I send support something better than another stop video?

MeiAdams0168 · 24 May 2025, 04:27 UTC

Closed
ME
MeiAdams0168
Our FR5 connector-loading trial stops intermittently. Seller support has watched my phone video and wants more information. I watched it again. You get a lovely view of the arm, half a view of the tool and absolutely no readable message. I used to tell students to write down exactly what happened before asking for help. Apparently that advice was for other people. We bought the package through Alibaba, and the seller is handling the ticket. What should I pull together around the next observed stop so we can get a useful answer without deliberately provoking it?

12 replies

RA
RaviBarnes0563
Replying to MeiAdams0168

Capture the exact message, job step and setup version with one matching log occurrence; the operator's description of what happened just before the stop can be useful too.

4 points
ME
MeiAdams0168
Replying to RaviBarnes0563

Operator had already written it down. 'Fixture ready lost'. I should have asked her before making my little documentary. Controls is finding the matching trace.

18 points
RA
RaviBarnes0563
Replying to MeiAdams0168

Did she see anything change at the fixture when that message appeared?

23 points
ME
MeiAdams0168
Replying to RaviBarnes0563

She says no. Part was waiting in the tool. Trace shows the input dropped, but we haven't checked where along the signal path that happened.

16 points
RA
RaviBarnes0563
Replying to MeiAdams0168

Include that observation as hers in the ticket, and ask controls to identify the source of the ready signal before anyone starts changing settings.

13 points
CA
CallumBell0621
Replying to MeiAdams0168

Check which device writes that state. Our training bench once had two writers clearing the same bit, though I would not assume your lost input has the same cause.

25 points
ME
MeiAdams0168
Replying to CallumBell0621

One writer confirmed in our PLC. The physical input dropped too. Maintenance is checking the fixture switch and its target. We've kept all of this under the original ticket.

15 points
RA
RaviBarnes0563
Replying to MeiAdams0168

Who is keeping the seller and maintenance updated? It's easy for them to investigate different versions of the story once several people start replying.

5 points
HA
HarishAllen0315
Replying to MeiAdams0168

Was the physical input drop captured in the same occurrence as the screen message? I would include a shared event reference before presenting those as one sequence.

-8 points
ME
MeiAdams0168
Replying to HarishAllen0315

Same occurrence, yes. Controls linked them. I'm coordinating the ticket, with the operator's note and matched trace attached together.

17 points
ME
MeiAdams0168
Replying to RaviBarnes0563

Maintenance found a loose target on that fixture. Repaired and checked. The supervised trial hasn't repeated the message so far. I've sent that result with the run scope, and asked support whether they need anything else to close this occurrence.

9 points
RA
RaviBarnes0563
Replying to MeiAdams0168

Keep the fixture identifier in the handover; another similar-looking fixture could otherwise make the next stop look like the repair failed.

15 points

Discussion closed

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