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

Cannot narrow our FR5 unloading stop from the video I sent

JessCarr · 2026年7月1日 09:17 UTC

回复讨论
JE
JessCarr
My phone video got a request for more information, not a diagnosis, and after 45 days on this imported FR5 housing-unloading ticket I'd like the unnamed Alibaba seller to explain which evidence would distinguish the intermittent stops.

8 条回复

SA
SarahBaker0502
回复 JessCarr

Start with one identifiable stop. What does the screen actually say?

9
WI
WillBrooks0835
回复 JessCarr

Does your recording include the period before the stop? A stationary arm alone won't distinguish a program wait from the event that led to it.

16
JE
JessCarr
回复 JessCarr

Sarah, the screen says waiting for destination; Will, my recording starts afterward, but I have a saved sequence record for that occurrence.

21
SA
SarahBaker0502
回复 JessCarr

Send that pair and ask which destination condition the installed routine expects.

15
JE
JessCarr

Support has identified the wait as destination space unavailable, and our production note says the receiving tray was full on that occurrence; that accounts for this stop, not the others I lumped into the ticket.

7
WI
WillBrooks0835
回复 JessCarr

Was waiting with a full tray expected by the handover? The operator may still need a clearer explanation even where the routine behaved as designed.

11
JE
JessCarr

Yes, the sequence document describes it, but our quick-start sheet doesn't mention a full receiving tray; I've linked the relevant handover section and separated the remaining unexplained occurrences for support.

20
SA
SarahBaker0502
回复 JessCarr

Useful separation. Keep the unexplained ones open even if this answer closes the full-tray question.

22

参与讨论

欢迎来到 Application Robot

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

忘记密码?

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