Programming & support

Work through software, SDKs, connectivity, and commissioning.

Start a discussion

2,347discussions

Keeping the new UR5e cover references separate from the image-condition comparison

MiaArcher0383 · 15 points · Programming & support · 31 Jul 2026

0replies A

An old UR5e plate completion finishes the wrong attempt in my offline test

AnilChan1071 · 32 points · Programming & support · 31 Jul 2026

0replies N

Why does our FR5 mock accept every fixture-status mistake?

NathanChan1069 · 22 points · Programming & support · 31 Jul 2026

15replies M

Everyone can start my FR10 job; only I know what to do when it waits

MiaBrooks0818 · 8 points · Programming & support · 31 Jul 2026

0replies J

Another faceplate image meeting, and the streak labels are ahead of the evidence

JamieAli0208 · 7 points · Programming & support · 31 Jul 2026

20replies C

Our FR10 bezel labels call a travelling highlight a scratch

ChenChan1051 · 29 points · Programming & support · 31 Jul 2026

10replies R

Who can settle the faceplate labels before our UR5e camera is tuned?

RaviChan1085 · 4 points · Programming & support · 31 Jul 2026

0replies S

Our FR5 cover comparison needs more than withdrawing the guessed labels

SarahBell0676 · 16 points · Programming & support · 30 Jul 2026

16replies M

Detailed FR10 logs are busy while our display sits on an old reading

MiaBarnes0557 · 31 points · Programming & support · 30 Jul 2026

5replies R

The saved pocket cannot tell me where our FR5 sleeve actually is

RobinAdams0164 · 20 points · Programming & support · 30 Jul 2026

5replies N

The FR10 report mock never checks the response my parser expects

NoahCarter0977 · 5 points · Programming & support · 30 Jul 2026

19replies H

Our UR5e restart helper treats an uncertain verification as never sent

HazelBaker0484 · 32 points · Programming & support · 30 Jul 2026

5replies Q

I cannot choose bezel thresholds while the bright streaks keep changing

QuinnCasey · 22 points · Programming & support · 30 Jul 2026

20replies L

Our FR10 parser never complains because the mock always says true

LeahBrooks0843 · 24 points · Programming & support · 30 Jul 2026

7replies R

our offline FR5 report stays cheerful even with an interface mistake

RebeccaArcher0430 · 29 points · Programming & support · 30 Jul 2026

0replies R

Received is not available in our FR10 lathe notes

RobinCarter1034 · 27 points · Programming & support · 30 Jul 2026

11replies

Programming & support

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

Who can settle the faceplate labels before our UR5e camera is tuned?

Our FR5 cover comparison needs more than withdrawing the guessed labels

Detailed FR10 logs are busy while our display sits on an old reading

The saved pocket cannot tell me where our FR5 sleeve actually is

The FR10 report mock never checks the response my parser expects

Our UR5e restart helper treats an uncertain verification as never sent

I cannot choose bezel thresholds while the bright streaks keep changing

Our FR10 parser never complains because the mock always says true

our offline FR5 report stays cheerful even with an interface mistake

Received is not available in our FR10 lathe notes