Programming & support

Work through software, SDKs, connectivity, and commissioning.

Start a discussion

2,347discussions

Which trim-plate image belongs with our confirmed scratch reference?

BrunoBell0626 · 7 points · Programming & support · 8 May 2026

5replies A

A planned enclosed machining cell: Our interface drawing agrees with itself until you read the notes

AnikaAli0247 · 10 points · Programming & support · 8 May 2026

11replies B

The scratch labels look less certain than the images suggest

BethChan1107 · 26 points · Programming & support · 8 May 2026

1replies C

Fairino FR5: Sorting restart state before running 198

ClaraBell0611 · 8 points · Programming & support · 8 May 2026

15replies H

My offline robot mock says yes to everything (Fairino FR10, fixture status interpretation)

HanaBrooks0796 · 24 points · Programming & support · 8 May 2026

15replies G

Fairino FR5: Reproducing delayed events without random sleeps

GraceBrown0929 · 32 points · Programming & support · 8 May 2026

2replies A

Should startup resubmit a job with no saved result? (inspection-cycle execution)

AmyBennett0728 · 17 points · Programming & support · 8 May 2026

6replies R

How do I build a trustworthy reference set for a brushed stainless trim plate? (Universal Robots UR5e)

RaviChan1085 · 9 points · Programming & support · 8 May 2026

8replies C

A reused job name has tangled our incident history (Fairino FR10)

CalebBarnes0580 · 27 points · Programming & support · 8 May 2026

10replies R

The scratch labels look less certain than the images suggest (checking cosmetic metal surfaces with a fixed camera)

RaviArcher0389 · 6 points · Programming & support · 7 May 2026

0replies O

A small finished-parts production cell: Getting consistent inspection evidence before commissioning

OscarAdams0097 · 31 points · Programming & support · 7 May 2026

17replies C

Programming & support

Which trim-plate image belongs with our confirmed scratch reference?

A planned enclosed machining cell: Our interface drawing agrees with itself until you read the notes

The scratch labels look less certain than the images suggest

Fairino FR5: Sorting restart state before running 198

My offline robot mock says yes to everything (Fairino FR10, fixture status interpretation)

Fairino FR5: Reproducing delayed events without random sleeps

Should startup resubmit a job with no saved result? (inspection-cycle execution)

How do I build a trustworthy reference set for a brushed stainless trim plate? (Universal Robots UR5e)

A reused job name has tangled our incident history (Fairino FR10)

The scratch labels look less certain than the images suggest (checking cosmetic metal surfaces with a fixed camera)

A small finished-parts production cell: Getting consistent inspection evidence before commissioning

A missing result isn't proof the job never started (part inspection)

our fr10 trim plate has one scratch and three arrows

I cannot trust our FR10 fixture display test with a permanently true mock

FR5 faceplate labels attached to a moving streak

Why did better logging make our UR5e monitor less believable?

How do I time the UR5e monitor without trusting its frozen screen?

Did logging stall our UR5e display, or just happen at the same time?

Can't choose bezel references from those travelling bright stripes

How do I stop our FR5 cover lesson treating reflections as known scratches?