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

编程与技术支持

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

发起讨论

2,347个讨论

Universal Robots UR5e: How do I build a trustworthy reference set for a bright-finished enclosure faceplate?

OliverAli0189 · 17 分 · 编程与技术支持 · 2026年4月2日

4条回复 J

Bright streaks move when we present the part differently

JackChan1124 · 22 分 · 编程与技术支持 · 2026年4月2日

7条回复 C

The offline test passes until an old completion arrives - fixture-check completion reporting

ChenAllen0268 · 8 分 · 编程与技术支持 · 2026年4月2日

14条回复 K

our ur5e startup retries a bracket whose result was never saved

KaiAbbott0019 · 11 分 · 编程与技术支持 · 2026年4月1日

1条回复 C

Why does our old UR5e result finish the new test only when the sleep feels like it?

CallumBennett0708 · 34 分 · 编程与技术支持 · 2026年4月1日

0条回复 N

How do I measure where status processing gets stuck? - controller availability logging

NaomiBennett0767 · 24 分 · 编程与技术支持 · 2026年4月1日

11条回复 L

The screen looks fine even when the request fails (Fairino FR5)

LucaChan1048 · 15 分 · 编程与技术支持 · 2026年4月1日

2条回复 N

Our old FR5 result ticks off the new inspection attempt

NinaAbbott0066 · 16 分 · 编程与技术支持 · 2026年3月31日

19条回复 L

FR10 status mock accepts a call our real interface rejects

LuisBennett0782 · 32 分 · 编程与技术支持 · 2026年3月31日

7条回复 G

How should our FR10 restart treat a block placed before its pocket was saved?

GabrielArcher0366 · 23 分 · 编程与技术支持 · 2026年3月31日

16条回复 O

Our cover gains a second labelled scratch when it is reseated

OscarCarter0967 · 25 分 · 编程与技术支持 · 2026年3月31日

1条回复 A

How do I keep our FR5 uncertain coupon out of the startup retry list?

AdaChen1173 · 14 分 · 编程与技术支持 · 2026年3月31日

7条回复 L

Our FR5 report gives two plate attempts the same friendly name

LauraBriggs · 12 分 · 编程与技术支持 · 2026年3月30日

17条回复 O

Trim-plate scratch labels without a physical location

OscarBennett0706 · 31 分 · 编程与技术支持 · 2026年3月30日

4条回复 H

fr10 receipt has a sequence our python export forgot

HenryBarnes0525 · 31 分 · 编程与技术支持 · 2026年3月30日

8条回复

编程与技术支持

Universal Robots UR5e: How do I build a trustworthy reference set for a bright-finished enclosure faceplate?

Bright streaks move when we present the part differently

The offline test passes until an old completion arrives - fixture-check completion reporting

our ur5e startup retries a bracket whose result was never saved

Why does our old UR5e result finish the new test only when the sleep feels like it?

Which part of our bezel are the FR5 scratch labels judging?

I cannot test our FR10 parser with a mock that agrees to everything

Cannot assign the FR5 acknowledgement after our bracket job name was reused

The FR5 test completes the current coupon with yesterday's event

our old ur5e completion keeps stealing the new attempt

How do I measure where status processing gets stuck? - controller availability logging

The screen looks fine even when the request fails (Fairino FR5)

Our old FR5 result ticks off the new inspection attempt

FR10 status mock accepts a call our real interface rejects

How should our FR10 restart treat a block placed before its pocket was saved?

Our cover gains a second labelled scratch when it is reseated

How do I keep our FR5 uncertain coupon out of the startup retry list?

Our FR5 report gives two plate attempts the same friendly name

Trim-plate scratch labels without a physical location

fr10 receipt has a sequence our python export forgot