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

编程与技术支持

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

发起讨论

2,357个讨论

Which pending housing requests are safe to submit after our application crashes?

NadiaChen1161 · 22 分 · 编程与技术支持 · 2026年8月14日

20条回复 B

Our UR5e fixture-status fake approves methods it does not even define

BrunoChen1148 · 21 分 · 编程与技术支持 · 2026年8月14日

0条回复 R

One reused plate label, three clocks and an acknowledgement I cannot place

RachelAbbott0087 · 9 分 · 编程与技术支持 · 2026年8月14日

0条回复 K

I cannot judge our FR5 parser through a fake that always says true

KarenChambers · 20 分 · 编程与技术支持 · 2026年8月14日

1条回复 L

Which physical cover should our FR10 scratch label describe?

LeoBennett0710 · 30 分 · 编程与技术支持 · 2026年8月14日

18条回复 M

An empty pocket leaves our operators guessing - tray transfer

MinaCarter1033 · 27 分 · 编程与技术支持 · 2026年8月14日

9条回复 O

The scratch labels look less certain than the images suggest - planning camera inspection of reflective parts

OwenBennett0747 · 27 分 · 编程与技术支持 · 2026年8月14日

19条回复 F

My offline robot mock says yes to everything (Universal Robots UR5e, inspection result parsing)

FelixBennett0719 · 34 分 · 编程与技术支持 · 2026年8月14日

0条回复 L

Our example images keep turning shiny patches into defects - presenting reflective components for surface inspection

LinCarter0966 · 35 分 · 编程与技术支持 · 2026年8月14日

0条回复 T

When should a tray job count a transfer as complete? (tray-to-tray transfer)

TheoAdams0149 · 15 分 · 编程与技术支持 · 2026年8月14日

15条回复 C

How should read-only mode reporting show an unavailable answer? (Fairino FR5)

CalebCarter1015 · 6 分 · 编程与技术支持 · 2026年8月14日

1条回复 O

Are we teaching our camera to reject reflections? (Fairino FR5)

OmarChan1100 · 28 分 · 编程与技术支持 · 2026年8月14日

17条回复 O

Getting consistent inspection evidence before commissioning

OliverAli0189 · 16 分 · 编程与技术支持 · 2026年8月14日

3条回复 L

Our offline FR10 screen gets approval from every imaginary method

LeahBrown0930 · 5 分 · 编程与技术支持 · 2026年8月13日

18条回复 B

Polished-cover scratch labels move ahead of the FR5 evidence

BenAbbott0022 · 6 分 · 编程与技术支持 · 2026年8月13日

15条回复 I

I cannot trust the mode value our replacement SDK gives the dashboard

ImranAllen0305 · 26 分 · 编程与技术支持 · 2026年8月13日

6条回复

编程与技术支持

FR10 verification sent before crash, startup still wants to send it again

the saved pocket gets ahead of what I can prove after a stop

Busy log folder, frozen UR5e availability display

I taught the spacer job but left the recovery decisions with me

Which pending housing requests are safe to submit after our application crashes?

Our UR5e fixture-status fake approves methods it does not even define

One reused plate label, three clocks and an acknowledgement I cannot place

I cannot judge our FR5 parser through a fake that always says true

Which physical cover should our FR10 scratch label describe?

An empty pocket leaves our operators guessing - tray transfer

The scratch labels look less certain than the images suggest - planning camera inspection of reflective parts

My offline robot mock says yes to everything (Universal Robots UR5e, inspection result parsing)

Our example images keep turning shiny patches into defects - presenting reflective components for surface inspection

When should a tray job count a transfer as complete? (tray-to-tray transfer)

How should read-only mode reporting show an unavailable answer? (Fairino FR5)

Are we teaching our camera to reject reflections? (Fairino FR5)

Getting consistent inspection evidence before commissioning

Our offline FR10 screen gets approval from every imaginary method

Polished-cover scratch labels move ahead of the FR5 evidence

I cannot trust the mode value our replacement SDK gives the dashboard