What should accompany the FR10 spacer-unloading video this time?

JasperAdams0116 · 2026年7月30日 06:48 UTC

回复讨论

主帖中文翻译暂不可用,以下显示英文原文;回复保留原文。 查看英文原文

JA
JasperAdams0116
My FR10 spacer-unloading ticket is ten days old with our Alibaba seller. Phone video prompted more-information request. I've already found unreadable messages limit another clip; what should we capture together here?

15 条回复

LU
LuisAli0260

One occurrence with its exact displayed message, time, active sequence step, block and fixture identity, plus the available matching logs; keep expected behaviour beside what the camera actually shows

8分
RE
ReeceAli0210

And give support the software and setup revisions once, clearly. Then ask which event interval they want a technical person to review, rather than sending a growing pile with no index.

6分
JA
JasperAdams0116

The current clip shows the block waiting. No readable message. We can preserve it but can't recover that detail from the picture.

5分
BR
BrunoAllen0278

Is the block still held, or waiting in the fixture? I can't tell which part of unloading you're describing.

17分
JA
JasperAdams0116

Still in the fixture. Tool has approached but hasn't removed it.

21分
YA
YasminBaker0441

Which documented confirmation is required before removal at that step?

12分
LU
LuisAli0260

Have controls identify that from the installed sequence; don't pick a likely sensor just because it's visible beside the block

11分
RE
ReeceAli0210

The next shift also needs to know what not to overwrite during normal approved recovery. Preserve the event information first where the procedure permits; nobody should improvise a recovery for the recording.

15分
BR
BrunoAllen0278

Can support nominate the person who will interpret that confirmation, rather than the sales contact only forwarding the video?

5分
JA
JasperAdams0116

Requested a technical reviewer. Controls is identifying the expected confirmation; no new matched stop record yet.

2分
YA
YasminBaker0441

Who owns the capture on the next shift?

5分
LU
LuisAli0260

Give that person a short occurrence checklist and somewhere to put the matching files; the revision information needn't be retyped every time

4分
JA
JasperAdams0116

Shift lead owns it. Controls identified the fixture-release confirmation, but its value at the filmed stop isn't available.

14分
RE
ReeceAli0210

Keep that distinction in the ticket. Knowing the expected confirmation doesn't establish that it was absent, or why. A current indication wouldn't recover the old event either.

11分
BR
BrunoAllen0278

Please return with what the matched capture shows. I'm interested whether support can then explain the waiting condition without asking you to recreate the entire setup again.

19分

参与讨论

欢迎来到 Application Robot

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

忘记密码?

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