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

编程与技术支持

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

发起讨论

2,346个讨论

How do I test our FR10 fixture display when the last good value stays on screen?

PavelAdams0092 · 8 分 · 编程与技术支持 · 2025年8月19日

7条回复 N

How do I release an old completion at the same point in every test?

NaomiArcher0419 · 13 分 · 编程与技术支持 · 2025年8月19日

10条回复 T

Our offline FR10 display likes every response it has ever been given

TobyAli0231 · 37 分 · 编程与技术支持 · 2025年8月19日

12条回复 N

Cannot sign off our FR10 handover with recovery left to my phone

NoahBarnes0542 · 3 分 · 编程与技术支持 · 2025年8月18日

3条回复 S

Faceplate scratches that change with the picture settings

SamBennett0768 · 30 分 · 编程与技术支持 · 2025年8月18日

11条回复 C

Bezel reject cards with no rejected feature marked

ChloeBaker0483 · 2 分 · 编程与技术支持 · 2025年8月18日

10条回复 F

Two faceplates share one scratch label

FarahAdams0156 · 29 分 · 编程与技术支持 · 2025年8月18日

20条回复 O

Our read-only screen stays cheerful through a failed request

OliverChen1146 · 38 分 · 编程与技术支持 · 2025年8月18日

4条回复 R

Can't hand over a dashboard that invents a healthy FR10 status

RobinBennett0773 · 8 分 · 编程与技术支持 · 2025年8月17日

4条回复 P

How do I assign this UR5e acknowledgement when the job label was reused?

PriyaBell0655 · 26 分 · 编程与技术支持 · 2025年8月17日

0条回复 H

How do I make our FR10 parsing mock capable of disappointing me?

Harriet_Bailey · 24 分 · 编程与技术支持 · 2025年8月16日

4条回复 N

Pending on our screen can mean the FR10 already got it

NadiaChan1074 · 21 分 · 编程与技术支持 · 2025年8月16日

9条回复 A

How should I label two views of the same accepted bezel?

AlexAdams0124 · 14 分 · 编程与技术支持 · 2025年8月15日

4条回复

编程与技术支持

What should our FR5 status mock return when the request fails?

our FR10 ready signal has two owners and two meanings

our FR5 handover assumes every tray pocket is full

Delayed completion crossing into the next coupon attempt

Pocket saved as empty while the sleeve may still be held

Bezel images taken with two different camera crops

How do I make our FR10 status mock return an awkward answer?

How do I test our FR10 fixture display when the last good value stays on screen?

How do I release an old completion at the same point in every test?

Our offline FR10 display likes every response it has ever been given

Cannot sign off our FR10 handover with recovery left to my phone

Faceplate scratches that change with the picture settings

Bezel reject cards with no rejected feature marked

Two faceplates share one scratch label

Our read-only screen stays cheerful through a failed request

Can't hand over a dashboard that invents a healthy FR10 status

How do I assign this UR5e acknowledgement when the job label was reused?

How do I make our FR10 parsing mock capable of disappointing me?

Pending on our screen can mean the FR10 already got it

How should I label two views of the same accepted bezel?