Programming & support

Work through software, SDKs, connectivity, and commissioning.

Start a discussion

2,346 discussions

How should our FR10 trim-plate reference set distinguish finish from a moving highlight?

EmmaAllen0289 · 31 points · Programming & support · 18 Aug 2026

6replies I

I cannot test fixture-status interpretation with a mock that approves everything

EmmaAli0202 · 7 points · Programming & support · 18 Aug 2026

2replies O

Our faceplate scratch captions follow whichever streak the camera sees

OmarBaker0491 · 21 points · Programming & support · 18 Aug 2026

20replies L

FR10 pending file mixes untouched coupons with inspections that may have run

LouisBarnes0572 · 9 points · Programming & support · 18 Aug 2026

11replies P

a saved pocket is not enough to restart my puck transfer

PriyaCarter1003 · 31 points · Programming & support · 17 Aug 2026

8replies R

A failed UR5e read now produces a perfectly believable mode on my screen

RebeccaBrown0952 · 10 points · Programming & support · 17 Aug 2026

20replies P

Why are moving bezel streaks being treated as established scratch references?

PriyaBennett0742 · 12 points · Programming & support · 17 Aug 2026

20replies O

The trim-plate images have travelling streaks and premature scratch labels

OscarAbbott0010 · 11 points · Programming & support · 17 Aug 2026

6replies O

Our FR5 mode wrapper finds a believable value inside a failed response

OwenCarter1008 · 32 points · Programming & support · 17 Aug 2026

1replies R

I need the faceplate reference decision, not a vote on its bright streak

RachelChan1131 · 21 points · Programming & support · 17 Aug 2026

7replies M

The timeout is clear; the acknowledgement's attempt is not

Morgan_Chambers · 21 points · Programming & support · 17 Aug 2026

14replies G

How do I hand over FR5 interruptions when I only taught the clean run?

GabrielArcher0366 · 16 points · Programming & support · 17 Aug 2026

9replies

Programming & support

How should our FR10 trim-plate reference set distinguish finish from a moving highlight?

Why does our FR5 replay display wait when detailed logging is busy?

pending does not tell me whether the FR10 verified this bracket

What should our FR5 tray-to-tray record know after a spacer transfer stops?

How do I make the UR5e reporting substitute expose a bad call?

My FR10 polished-cover question is about who can settle the scratch labels

The FR5 bezel labels need physical decisions before my repeat-image comparison

FR5 bezel thresholds cannot be based on these travelling streak captions

my sleeve transfer restarts from a pocket number that may no longer be true

I cannot test fixture-status interpretation with a mock that approves everything

Our faceplate scratch captions follow whichever streak the camera sees

FR10 pending file mixes untouched coupons with inspections that may have run

a saved pocket is not enough to restart my puck transfer

A failed UR5e read now produces a perfectly believable mode on my screen

Why are moving bezel streaks being treated as established scratch references?

The trim-plate images have travelling streaks and premature scratch labels

Our FR5 mode wrapper finds a believable value inside a failed response

I need the faceplate reference decision, not a vote on its bright streak

The timeout is clear; the acknowledgement's attempt is not

How do I hand over FR5 interruptions when I only taught the clean run?