Why does another video need to show another silent FR10?

AnnaBell0677 · 20 Jun 2025, 22:46 UTC

Closed
AN
AnnaBell0677
Our seller on Alibaba wants more footage of the FR10 pausing before sleeve pickup, but I need a useful maintenance handover rather than a film collection; what should accompany one occurrence so somebody can identify the waiting condition?

17 replies

RA
RaviAdams0128
Replying to AnnaBell0677

Exact displayed wait message, occurrence time, active program step and the matching application or controller log. Include which fixture and sleeve were present, so support isn't comparing different setups.

24 points
AN
AnnaBell0677
Replying to RaviAdams0128

The application says fixture occupied while the sleeve is still in it, which sounds reasonable to me; maintenance says the unload step is waiting for another indication.

11 points
NO
NoraAli0235
Replying to AnnaBell0677

Which indication? 'Another' leaves us guessing again.

24 points
AN
AnnaBell0677
Replying to NoraAli0235

Fixture released. That stays false on the captured screen. I have asked maintenance to match the PLC state to that occurrence, not to infer it from the label.

23 points
RA
RaviAdams0128
Replying to AnnaBell0677

Get the normal sequence description from the integrator too; fixture occupied may be expected at this stage while released is still required before pickup.

11 points
OM
OmarChan1100
Replying to AnnaBell0677

Can the operator read that difference on the screen?

16 points
AN
AnnaBell0677
Replying to OmarChan1100

No, they thought occupied meant the fixture had detected a problem; the message gives them no next contact or explanation.

7 points
WI
WillBennett0748
Replying to AnnaBell0677

I would have read it that way too. Our tooling support gets photographs of parts when the actual wait is for a fixture condition. Useful photos, wrong question. Is there a mechanical release indicator maintenance can compare with the ordinary input during the same event?

6 points
AN
AnnaBell0677
Replying to WillBennett0748

There is; maintenance can inspect it and capture the indication with the input trace, with the cell secured for their checks.

2 points
NO
NoraAli0235
Replying to AnnaBell0677

Keep the captured mismatch specific. Don't rename this 'bad sensor' before they check the mapping.

12 points
RA
RaviAdams0128
Replying to AnnaBell0677

Anna, ask who owns that comparison. Seller support and your integrator both need the same incident, but one person should be assembling the answer.

18 points
AN
AnnaBell0677
Replying to RaviAdams0128

Our maintenance lead owns it; seller and integrator are copied in. I have removed my earlier email subject 'release sensor fault' because nobody established that.

22 points
OM
OmarChan1100
Replying to AnnaBell0677

Thanks for spelling out the two states. That would help with the operator wording too.

23 points
RA
RaviAdams0128
Replying to AnnaBell0677

Once they identify the cause, include how it was checked and which setup was returned to use. The next shift needs more than an email saying support replied.

13 points
WI
WillBennett0748
Replying to AnnaBell0677

Did maintenance see the release indicator change, Anna? Curious about that comparison, not assuming the fixture itself is stuck.

14 points
AN
AnnaBell0677
Replying to WillBennett0748

The physical indication changed during the captured check, but the application's released state did not; maintenance and controls are tracing the signal path. No confirmed repair yet.

18 points
NO
NoraAli0235
Replying to AnnaBell0677

Useful finding. Still need the PLC input between those two observations.

25 points

Discussion closed

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