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

编程与技术支持

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

发起讨论

2,346个讨论

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

Universal Robots UR5e: How do I build a trustworthy reference set for a brushed stainless trim plate?

ImranBarnes0566 · 12 分 · 编程与技术支持 · 2026年8月13日

1条回复 C

Matching Python and PLC events for Universal Robots UR5e (part acceptance recording)

CalebAdams0145 · 34 分 · 编程与技术支持 · 2026年8月13日

12条回复 Z

The SDK changed shape and my parser didn't (controller status polling)

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

17条回复 I

Where should a software mock stop? (Fairino FR10, read-only controller reporting)

IsaacChan1129 · 23 分 · 编程与技术支持 · 2026年8月13日

3条回复 N

A plausible status from a failed request (Fairino FR10, read-only mode reporting)

NadiaBell0639 · 20 分 · 编程与技术支持 · 2026年8月12日

7条回复 M

A workshop fixture inspection cell: How do I keep an uncertain attempt out of automatic resubmission?

MiaBrooks0818 · 32 分 · 编程与技术支持 · 2026年8月12日

10条回复 O

My Universal Robots UR5e dashboard believes an error response

OmarArcher0404 · 39 分 · 编程与技术支持 · 2026年8月12日

21条回复 N

Our retry bookkeeping needs a tougher offline test (Fairino FR5)

NoahBrown0890 · 6 分 · 编程与技术支持 · 2026年8月12日

6条回复 A

Same job label, wrong attempt marked complete (inspection-cycle tracking)

AlexChan1081 · 30 分 · 编程与技术支持 · 2026年8月12日

8条回复 C

The fake SDK keeps the screen happy and misses mistakes (Fairino FR5, read-only controller reporting)

CarlaCarter1010 · 20 分 · 编程与技术支持 · 2026年8月12日

8条回复

编程与技术支持

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

What belongs in a useful robot recovery handover? (parts tray sorting)

Universal Robots UR5e: How do I build a trustworthy reference set for a brushed stainless trim plate?

Matching Python and PLC events for Universal Robots UR5e (part acceptance recording)

The SDK changed shape and my parser didn't (controller status polling)

Where should a software mock stop? (Fairino FR10, read-only controller reporting)

A plausible status from a failed request (Fairino FR10, read-only mode reporting)

A workshop fixture inspection cell: How do I keep an uncertain attempt out of automatic resubmission?

My Universal Robots UR5e dashboard believes an error response

Our retry bookkeeping needs a tougher offline test (Fairino FR5)

Same job label, wrong attempt marked complete (inspection-cycle tracking)

The fake SDK keeps the screen happy and misses mistakes (Fairino FR5, read-only controller reporting)