Programming & support

Work through software, SDKs, connectivity, and commissioning.

Start a discussion

2,347discussions

How should our FR10 cover comparison preserve defect visibility as glare changes?

BethAllen0324 · 37 points · Programming & support · 30 Jun 2026

14replies I

Cannot choose FR5 trim-plate thresholds before the reference set covers real defects

ImranBrooks0827 · 4 points · Programming & support · 30 Jun 2026

8replies N

Our UR5e acknowledgement sits between two reused coupon-job labels

NathanBennett0721 · 8 points · Programming & support · 30 Jun 2026

1replies P

Why does our saved UR5e pocket survive when the transfer state does not?

PriyaBennett0742 · 28 points · Programming & support · 30 Jun 2026

21replies F

How should startup treat a UR5e request sent before the result was saved?

FionaAbbott0064 · 14 points · Programming & support · 30 Jun 2026

0replies M

Cannot assign our FR5 acknowledgement between two reused plate-job labels

MeiAli0255 · 17 points · Programming & support · 30 Jun 2026

0replies A

Did detailed UR5e logging stall acquisition or only my screen?

AdamCarr · 22 points · Programming & support · 30 Jun 2026

1replies A

Late FR10 coupon completion lands on the replacement attempt

AnilBennett0723 · 20 points · Programming & support · 30 Jun 2026

12replies A

Cannot interpret FR10 mode from the old scalar and new response container alike

AnikaBrooks0856 · 2 points · Programming & support · 29 Jun 2026

0replies A

FR5 diagnostic screen freezes when detailed logging is enabled

AnnaArcher0416 · 31 points · Programming & support · 28 Jun 2026

21replies I

Bright faceplate streaks with scratch labels attached

ImranBarnes0566 · 25 points · Programming & support · 28 Jun 2026

10replies G

Cannot tune the FR5 trim-plate check from unconfirmed bright streaks

GabrielCarter0975 · 4 points · Programming & support · 28 Jun 2026

11replies I

My UR5e handover works until the first empty pocket

Ian_Carr · 29 points · Programming & support · 28 Jun 2026

8replies I

How can I expose parser failures when our FR5 mock always returns true?

ImranCarter1001 · 19 points · Programming & support · 28 Jun 2026

12replies

Programming & support

Why does my UR5e dashboard find a status inside a failed reply?

our fr10 tray lesson taught start and left me as recovery

Our polished-cover scratch labels follow the light

Which physical trim-plate decisions should our FR5 image labels follow?

FR10 trim-plate reference captions still follow the bright streak

fr5 bezel images have scratch names without scratch evidence

How should our FR10 cover comparison preserve defect visibility as glare changes?

Cannot choose FR5 trim-plate thresholds before the reference set covers real defects

Our UR5e acknowledgement sits between two reused coupon-job labels

Why does our saved UR5e pocket survive when the transfer state does not?

How should startup treat a UR5e request sent before the result was saved?

Cannot assign our FR5 acknowledgement between two reused plate-job labels

Did detailed UR5e logging stall acquisition or only my screen?

Late FR10 coupon completion lands on the replacement attempt

Cannot interpret FR10 mode from the old scalar and new response container alike

FR5 diagnostic screen freezes when detailed logging is enabled

Bright faceplate streaks with scratch labels attached

Cannot tune the FR5 trim-plate check from unconfirmed bright streaks

My UR5e handover works until the first empty pocket

How can I expose parser failures when our FR5 mock always returns true?