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

编程与技术支持

交流软件、SDK、连接通信及调试问题。

发起讨论

2,347个讨论

Which UR5e transfer state should survive when an aluminium block may already be placed?

BenBarnes0544 · 21 分 · 编程与技术支持 · 2026年3月3日

1条回复 R

How do I make our FR10 fake notice a missing read?

RebeccaAli0256 · 0 分 · 编程与技术支持 · 2026年3月2日

0条回复 A

Our cover lesson points to the brightest line instead of an identified scratch

AlexBrooks0820 · 10 分 · 编程与技术支持 · 2026年3月2日

16条回复 I

Cannot write our UR5e operator lesson while ready means two different things

ImranBrown0914 · 19 分 · 编程与技术支持 · 2026年3月2日

21条回复 C

How should our FR5 restart treat a puck whose placement was never recorded?

CarlaArcher0401 · 2 分 · 编程与技术支持 · 2026年3月2日

6条回复 Z

Cannot hand over our FR5 faceplate lesson with guessed scratch labels

ZaraBennett0743 · 19 分 · 编程与技术支持 · 2026年3月2日

1条回复 I

Why does our FR10 cover folder mix camera originals with enhanced phone pictures?

IsabelBennett0735 · 9 分 · 编程与技术支持 · 2026年3月2日

20条回复 H

Why does our nicer bezel picture hide the scratch?

HenryArcher0351 · 17 分 · 编程与技术支持 · 2026年3月1日

8条回复 L

Our trim plate changes verdict when the bright streak moves

LeoBaker0449 · 36 分 · 编程与技术支持 · 2026年3月1日

10条回复 J

Should request receipt and loading-area availability be separate interface events?

JaneBennett0771 · 35 分 · 编程与技术支持 · 2026年3月1日

0条回复 F

I handed over the UR5e start button and kept the decisions in my head

FelixArcher0371 · 30 分 · 编程与技术支持 · 2026年3月1日

1条回复 P

Why is our FR10 cover marked as scratched in one view and accepted in another?

PriyaBennett0742 · 10 分 · 编程与技术支持 · 2026年3月1日

5条回复

编程与技术支持

Cannot choose an FR5 scratch threshold from covers nobody physically judged

Why does ready mean receipt to one UR5e supplier and availability to the other?

fr10 wrapper reads a failed response as availability

Our FR10 lesson ends where the empty pocket starts

Which UR5e housing attempt owns this acknowledgement after restart?

Why is our UR5e front image labelled with a scratch on the back?

Why are our labelled scratches travelling across the trim plate?

Conflicting scratch labels on the faceplate reference set

Which UR5e transfer state should survive when an aluminium block may already be placed?

How do I make our FR10 fake notice a missing read?

Our cover lesson points to the brightest line instead of an identified scratch

Cannot write our UR5e operator lesson while ready means two different things

How should our FR5 restart treat a puck whose placement was never recorded?

Cannot hand over our FR5 faceplate lesson with guessed scratch labels

Why does our FR10 cover folder mix camera originals with enhanced phone pictures?

Why does our nicer bezel picture hide the scratch?

Our trim plate changes verdict when the bright streak moves

Should request receipt and loading-area availability be separate interface events?

I handed over the UR5e start button and kept the decisions in my head

Why is our FR10 cover marked as scratched in one view and accepted in another?