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

编程与技术支持

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

发起讨论

2,346个讨论

Which UR5e reply fields should our diagnostic screen trust after a failed request?

NadiaCarter0987 · 40 分 · 编程与技术支持 · 2025年10月4日

10条回复 E

How do I test our FR5 report when the mock accepts a misspelled method?

EmmaBarnes0550 · 5 分 · 编程与技术支持 · 2025年10月4日

5条回复 C

our cover scratch examples disagree with each other

CalebBrown0928 · 16 分 · 编程与技术支持 · 2025年10月4日

5条回复 A

Which FR10 request owns the acknowledgement after our restart?

AlexAdams0124 · 37 分 · 编程与技术支持 · 2025年10月2日

6条回复 D

Why are we ordering another light before identifying the scratched faceplate?

DineshBennett0734 · 13 分 · 编程与技术支持 · 2025年10月2日

1条回复 D

our polished cover gains a scratch when someone turns it

DanielAbbott0043 · 21 分 · 编程与技术支持 · 2025年10月2日

1条回复 H

How should our FR10 fixture-status mock reject a bad call?

HazelAli0223 · 31 分 · 编程与技术支持 · 2025年10月1日

21条回复 N

One polished cover has a different scratch in every view

NaomiBaker0506 · 31 分 · 编程与技术支持 · 2025年10月1日

0条回复

编程与技术支持

ready still means two things in our FR10 handover

How do we tune an FR10 inspection around a cover nobody kept?

The faceplate scratch changes shape in the training slides

Our startup helper wants to repeat a plate check it may already have sent

same bezel, two scratch labels

How should I stop startup repeating a possibly completed fixture check?

Which FR5 attempt owns the acknowledgement after our laptop restarted?

UR5e lathe plan with two meanings of ready

Faceplate reject folder without a confirmed defect

Why did our accepted cover become three scratch examples?

Cannot choose a restart pocket from our UR5e helper's saved index

The trim-plate scratch moves when we reseat the plate

Which UR5e reply fields should our diagnostic screen trust after a failed request?

How do I test our FR5 report when the mock accepts a misspelled method?

our cover scratch examples disagree with each other

Which FR10 request owns the acknowledgement after our restart?

Why are we ordering another light before identifying the scratched faceplate?

our polished cover gains a scratch when someone turns it

How should our FR10 fixture-status mock reject a bad call?

One polished cover has a different scratch in every view