简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。

fr10 sleeve stop ticket needs something the engineer can use

BrunoBaker0452 · 2026年6月24日 19:10 UTC

回复讨论
BR
BrunoBaker0452
Nineteen days open with our Alibaba seller. Phone video sent. What should identify one intermittent sleeve-loading stop properly?

9 条回复

CH
ChenBennett0703

Can the clip be tied to an event time, exact displayed message and active step, Bruno? Include the sleeve job and fixture identity too. Support needs the matching controller and ordinary PLC interval, not a film that only establishes the arm stopped.

16
BR
BrunoBaker0452

Clip starts after the stop. Operator note gives a time window, not the exact occurrence.

1
SO
SofiaAdams0108

Ask maintenance what retained events fit that window. Keep multiple candidates if the evidence cannot distinguish them yet.

2
BR
BrunoBaker0452

Two candidates found. Different active steps. No basis to choose one from the stationary-arm picture.

0
CH
ChenBennett0703

Who will organise the next useful occurrence record on your side? I would have the covering shift try the export procedure on saved data first, so the next stop does not become another video without the information support asked for.

21
SO
SofiaAdams0108

And ask the engineer which export fits your installed version. A generic menu instruction can waste the whole shift.

8
BR
BrunoBaker0452

Maintenance cover tried the version-matched export on a saved event. Screen, step and fixture details now share one occurrence note.

16
BR
BrunoBaker0452

A later stop was captured that way. Support has identified a wait for fixture-index confirmation; why it was absent remains under investigation.

13
CH
ChenBennett0703

That's a real narrowing of the ticket. Keep the two old candidate events unassigned rather than retrospectively giving them the new stop's explanation; they may or may not have been the same condition.

2

参与讨论

欢迎来到 Application Robot

所有人都可以阅读论坛。登录或注册后即可发起讨论、回复或上传照片。

忘记密码?

注册账号即表示你同意我们的 使用条款 社区准则。请阅读我们的 隐私政策 ,了解我们如何处理你的信息。