Programming & support

Work through software, SDKs, connectivity, and commissioning.

Start a discussion

2,347discussions

Which UR5e transfer state should survive when an aluminium block may already be placed?

BenBarnes0544 · 21 points · Programming & support · 3 Mar 2026

1replies R

How do I make our FR10 fake notice a missing read?

RebeccaAli0256 · 0 points · Programming & support · 2 Mar 2026

0replies A

Our cover lesson points to the brightest line instead of an identified scratch

AlexBrooks0820 · 10 points · Programming & support · 2 Mar 2026

16replies I

Cannot write our UR5e operator lesson while ready means two different things

ImranBrown0914 · 19 points · Programming & support · 2 Mar 2026

21replies C

How should our FR5 restart treat a puck whose placement was never recorded?

CarlaArcher0401 · 2 points · Programming & support · 2 Mar 2026

6replies Z

Cannot hand over our FR5 faceplate lesson with guessed scratch labels

ZaraBennett0743 · 19 points · Programming & support · 2 Mar 2026

1replies I

Why does our FR10 cover folder mix camera originals with enhanced phone pictures?

IsabelBennett0735 · 9 points · Programming & support · 2 Mar 2026

20replies H

Why does our nicer bezel picture hide the scratch?

HenryArcher0351 · 17 points · Programming & support · 1 Mar 2026

8replies L

Our trim plate changes verdict when the bright streak moves

LeoBaker0449 · 36 points · Programming & support · 1 Mar 2026

10replies J

Should request receipt and loading-area availability be separate interface events?

JaneBennett0771 · 35 points · Programming & support · 1 Mar 2026

0replies F

I handed over the UR5e start button and kept the decisions in my head

FelixArcher0371 · 30 points · Programming & support · 1 Mar 2026

1replies P

Why is our FR10 cover marked as scratched in one view and accepted in another?

PriyaBennett0742 · 10 points · Programming & support · 1 Mar 2026

5replies

Programming & support

Cannot choose an FR5 scratch threshold from covers nobody physically judged

Why does ready mean receipt to one UR5e supplier and availability to the other?

fr10 wrapper reads a failed response as availability

Our FR10 lesson ends where the empty pocket starts

Which UR5e housing attempt owns this acknowledgement after restart?

Why is our UR5e front image labelled with a scratch on the back?

Why are our labelled scratches travelling across the trim plate?

Conflicting scratch labels on the faceplate reference set

Which UR5e transfer state should survive when an aluminium block may already be placed?

How do I make our FR10 fake notice a missing read?

Our cover lesson points to the brightest line instead of an identified scratch

Cannot write our UR5e operator lesson while ready means two different things

How should our FR5 restart treat a puck whose placement was never recorded?

Cannot hand over our FR5 faceplate lesson with guessed scratch labels

Why does our FR10 cover folder mix camera originals with enhanced phone pictures?

Why does our nicer bezel picture hide the scratch?

Our trim plate changes verdict when the bright streak moves

Should request receipt and loading-area availability be separate interface events?

I handed over the UR5e start button and kept the decisions in my head

Why is our FR10 cover marked as scratched in one view and accepted in another?