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

编程与技术支持

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

发起讨论

2,347个讨论

Keeping the new UR5e cover references separate from the image-condition comparison

MiaArcher0383 · 15 分 · 编程与技术支持 · 2026年7月31日

0条回复 A

An old UR5e plate completion finishes the wrong attempt in my offline test

AnilChan1071 · 32 分 · 编程与技术支持 · 2026年7月31日

0条回复 N

Why does our FR5 mock accept every fixture-status mistake?

NathanChan1069 · 22 分 · 编程与技术支持 · 2026年7月31日

15条回复 M

Everyone can start my FR10 job; only I know what to do when it waits

MiaBrooks0818 · 8 分 · 编程与技术支持 · 2026年7月31日

0条回复 J

Another faceplate image meeting, and the streak labels are ahead of the evidence

JamieAli0208 · 7 分 · 编程与技术支持 · 2026年7月31日

20条回复 C

Our FR10 bezel labels call a travelling highlight a scratch

ChenChan1051 · 29 分 · 编程与技术支持 · 2026年7月31日

10条回复 R

Who can settle the faceplate labels before our UR5e camera is tuned?

RaviChan1085 · 4 分 · 编程与技术支持 · 2026年7月31日

0条回复 S

Our FR5 cover comparison needs more than withdrawing the guessed labels

SarahBell0676 · 16 分 · 编程与技术支持 · 2026年7月30日

16条回复 M

Detailed FR10 logs are busy while our display sits on an old reading

MiaBarnes0557 · 31 分 · 编程与技术支持 · 2026年7月30日

5条回复 R

The saved pocket cannot tell me where our FR5 sleeve actually is

RobinAdams0164 · 20 分 · 编程与技术支持 · 2026年7月30日

5条回复 N

The FR10 report mock never checks the response my parser expects

NoahCarter0977 · 5 分 · 编程与技术支持 · 2026年7月30日

19条回复 H

Our UR5e restart helper treats an uncertain verification as never sent

HazelBaker0484 · 32 分 · 编程与技术支持 · 2026年7月30日

5条回复 Q

I cannot choose bezel thresholds while the bright streaks keep changing

QuinnCasey · 22 分 · 编程与技术支持 · 2026年7月30日

20条回复 L

Our FR10 parser never complains because the mock always says true

LeahBrooks0843 · 24 分 · 编程与技术支持 · 2026年7月30日

7条回复 R

our offline FR5 report stays cheerful even with an interface mistake

RebeccaArcher0430 · 29 分 · 编程与技术支持 · 2026年7月30日

0条回复 R

Received is not available in our FR10 lathe notes

RobinCarter1034 · 27 分 · 编程与技术支持 · 2026年7月30日

11条回复

编程与技术支持

A clean FR5 tray run works, but restart can point at the wrong pocket

The FR5 sampling screen slows down when I ask it to tell me more

My offline inspection mock agrees with calls it should reject

Why are our FR10 bezel reference labels more certain than the surface review?

Keeping the new UR5e cover references separate from the image-condition comparison

An old UR5e plate completion finishes the wrong attempt in my offline test

Why does our FR5 mock accept every fixture-status mistake?

Everyone can start my FR10 job; only I know what to do when it waits

Another faceplate image meeting, and the streak labels are ahead of the evidence

Our FR10 bezel labels call a travelling highlight a scratch

Who can settle the faceplate labels before our UR5e camera is tuned?

Our FR5 cover comparison needs more than withdrawing the guessed labels

Detailed FR10 logs are busy while our display sits on an old reading

The saved pocket cannot tell me where our FR5 sleeve actually is

The FR10 report mock never checks the response my parser expects

Our UR5e restart helper treats an uncertain verification as never sent

I cannot choose bezel thresholds while the bright streaks keep changing

Our FR10 parser never complains because the mock always says true

our offline FR5 report stays cheerful even with an interface mistake

Received is not available in our FR10 lathe notes