Programming & support

Work through software, SDKs, connectivity, and commissioning.

Start a discussion
Started in

2,357discussions

F

One FR10 job label across two attempts and three clocks

FionaChan1108 · 6 points · Programming & support · 29 Nov 2025
0replies
J

FR5 cover references with a holder nobody can seat twice

JasperChan1073 · 23 points · Programming & support · 29 Nov 2025
10replies
N

I can't trust the FR5 status while the wrapper accepts every nonempty reply

NoahBarnes0542 · 28 points · Programming & support · 29 Nov 2025
17replies
N

Why does our FR10 dashboard turn an error field into a mode?

NoraAli0235 · 15 points · Programming & support · 29 Nov 2025
8replies
F

Which ready signal acknowledges our FR5 loading request?

FelixBaker0458 · 33 points · Programming & support · 28 Nov 2025
14replies
L

fr5 status freezes when the log saves

LiamArcher0403 · 11 points · Programming & support · 28 Nov 2025
6replies
T

Our trim plate has a scratch in one image and a bright edge in another

ThomasAli0190 · 9 points · Programming & support · 26 Nov 2025
14replies
A

How do I reproduce the old FR5 completion without another random sleep?

AnikaArcher0421 · 20 points · Programming & support · 26 Nov 2025
7replies
D

our polished-cover labels name a scratch nobody has located

DineshChan1082 · 9 points · Programming & support · 25 Nov 2025
0replies
S

Why does our FR5 test double accept a status query I misspelled?

SamBrooks0855 · 16 points · Programming & support · 24 Nov 2025
6replies
E

Cannot assign this FR10 receipt even with the restart boundary marked

EllaChen1164 · 25 points · Programming & support · 24 Nov 2025
12replies
R

The FR5 bezel's bright line moves while its scratch caption stays put

RobBlair · 8 points · Programming & support · 24 Nov 2025
1replies
N

Our FR10 trim-plate comparison quietly mixes two finishes

NaomiBaker0506 · 19 points · Programming & support · 24 Nov 2025
12replies
N

Cannot use our accepted UR5e bezel as a scratch example because somebody drew an arrow

NadiaBrown0900 · 32 points · Programming & support · 24 Nov 2025
11replies
A

Cannot give the FR10 operator a next step from transfer incomplete

AnilAbbott0027 · 22 points · Programming & support · 23 Nov 2025
7replies
D

Why are we still calling two different FR5 handover states ready?

DavidChan1128 · 15 points · Programming & support · 23 Nov 2025
13replies
L

our cover comparison has plenty of rejects and hardly any ordinary parts

LucaBaker0439 · 15 points · Programming & support · 23 Nov 2025
20replies
T

Our FR10 report passes tests even when I remove the parser

TheoBell0671 · 7 points · Programming & support · 23 Nov 2025
3replies
J

Pending request with no trustworthy restart decision

John_Blair · 27 points · Programming & support · 23 Nov 2025
1replies
G

Why does our FR10 handover turn an empty pocket into a call to me?

GeorgiaBlair · 17 points · Programming & support · 21 Nov 2025
3replies