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

编程与技术支持

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

发起讨论

2,357个讨论

Fairino FR10: A fixed camera, small presentation changes, very different streaks

LeoAbbott0014 · 35 分 · 编程与技术支持 · 2026年8月1日

11条回复 R

A fixed camera, small presentation changes, very different streaks (Fairino FR5)

RobinAdams0164 · 2 分 · 编程与技术支持 · 2026年8月1日

9条回复 H

I can see a timeout but can't match the acknowledgement (Fairino FR5, fixture inspection)

HassanBennett0704 · 8 分 · 编程与技术支持 · 2026年8月1日

0条回复 H

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条回复

编程与技术支持

Fairino FR10: A fixed camera, small presentation changes, very different streaks

A fixed camera, small presentation changes, very different streaks (Fairino FR5)

I can see a timeout but can't match the acknowledgement (Fairino FR5, fixture inspection)

I cannot separate FR5 display stalls from the extra file work

Our FR5 cover folder is certain about scratches the images cannot settle

One FR5 ready entry describes two different events

Another reflective part, the same premature scratch labels

moving bezel streaks are already being used as scratch targets

I cannot specify ready while it means both receipt and available space

Extra FR10 logs have turned my availability display into a waiting screen

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