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

编程与技术支持

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

发起讨论

2,346个讨论

Which presentation variation should our UR5e faceplate references actually cover?

CarlaBell0662 · 27 分 · 编程与技术支持 · 2026年8月20日

4条回复 C

I need the stainless-trim reference set to survive more than its nicest UR5e camera view

CarlaBarnes0575 · 15 分 · 编程与技术支持 · 2026年8月19日

8条回复 E

Why is our UR5e bezel folder repeating the scratch-label problem?

EmmaAbbott0028 · 21 分 · 编程与技术支持 · 2026年8月19日

15条回复 S

random sleeps keep hiding my old-result bug in the FR5 test

SofiaCarter0978 · 28 分 · 编程与技术支持 · 2026年8月19日

3条回复 L

Why does my FR5 startup treat an uncertain sent request as work that never left?

LuisBell0695 · 25 分 · 编程与技术支持 · 2026年8月19日

20条回复 L

I cannot approve scratch thresholds from faceplate streaks that move with presentation

LeahAllen0321 · 15 分 · 编程与技术支持 · 2026年8月19日

21条回复 I

I need the real faceplate scratch kept visible when we reduce the FR5 glare

IsabelBell0648 · 22 分 · 编程与技术支持 · 2026年8月19日

4条回复 B

our UR5e reporting substitute says true even when the interface is wrong

BenBell0631 · 29 分 · 编程与技术支持 · 2026年8月19日

1条回复 B

Which result should cross my FR5 status adapter when the request failed?

BrunoCarter0974 · 21 分 · 编程与技术支持 · 2026年8月19日

11条回复 L

I cannot tell a failed UR5e poll from a real status on our replacement dashboard

LeahChan1104 · 32 分 · 编程与技术支持 · 2026年8月19日

21条回复 E

The UR5e maintenance display freezes when I ask it to record more detail

EllaBennett0729 · 3 分 · 编程与技术支持 · 2026年8月19日

20条回复 O

I taught the FR10 clean run and left every empty-pocket decision with me

OmarCarter1013 · 19 分 · 编程与技术支持 · 2026年8月19日

16条回复 L

Why would pending authorise another FR10 inspection after a crash?

LouisAbbott0050 · 30 分 · 编程与技术支持 · 2026年8月19日

2条回复 M

Can my UR5e bezel review keep image certainty behind the physical decisions?

MayaBennett0736 · 15 分 · 编程与技术支持 · 2026年8月18日

3条回复 Q

detailed FR10 logs coincide with a telemetry screen that stops moving

QuinnChambers · 20 分 · 编程与技术支持 · 2026年8月18日

4条回复 K

How should startup distinguish an unsent coupon from an inspection with no saved answer?

KaiChen1150 · 27 分 · 编程与技术支持 · 2026年8月18日

15条回复 O

Why are our UR5e polished-cover scratch labels ahead of the physical evidence?

OscarAdams0097 · 25 分 · 编程与技术支持 · 2026年8月18日

3条回复

编程与技术支持

I cannot tell whether our FR10 screen has a value or merely a reply

Which housing jobs can startup still submit after this crash?

What should our offline FR5 reporting substitute refuse?

Which presentation variation should our UR5e faceplate references actually cover?

I need the stainless-trim reference set to survive more than its nicest UR5e camera view

Why is our UR5e bezel folder repeating the scratch-label problem?

random sleeps keep hiding my old-result bug in the FR5 test

Why does my FR5 startup treat an uncertain sent request as work that never left?

I cannot approve scratch thresholds from faceplate streaks that move with presentation

I need the real faceplate scratch kept visible when we reduce the FR5 glare

our UR5e reporting substitute says true even when the interface is wrong

Which result should cross my FR5 status adapter when the request failed?

I cannot tell a failed UR5e poll from a real status on our replacement dashboard

The UR5e maintenance display freezes when I ask it to record more detail

I taught the FR10 clean run and left every empty-pocket decision with me

Why would pending authorise another FR10 inspection after a crash?

Can my UR5e bezel review keep image certainty behind the physical decisions?

detailed FR10 logs coincide with a telemetry screen that stops moving

How should startup distinguish an unsent coupon from an inspection with no saved answer?

Why are our UR5e polished-cover scratch labels ahead of the physical evidence?