Programming & support

Work through software, SDKs, connectivity, and commissioning.

Start a discussion

2,347discussions

Where should a software mock stop? - fixture status interpretation

MinaBrooks0859 · 31 points · Programming & support · 4 Jun 2026

11replies A

Fairino FR5: Our status wrapper reads too much into a container

AmyBrooks0815 · 3 points · Programming & support · 4 Jun 2026

9replies B

A fixed camera, small presentation changes, very different streaks - inspecting reflective surfaces for scratches

BethBell0672 · 36 points · Programming & support · 3 Jun 2026

1replies S

A subcontract lathe department: documenting a machine-tending interface: one status, conflicting definitions

SamArcher0420 · 4 points · Programming & support · 3 Jun 2026

3replies O

A cosmetic components workshop: What counts as a confirmed defect on a reflective surface?

OscarAbbott0010 · 8 points · Programming & support · 3 Jun 2026

15replies H

Our job label survived a restart a little too well (fixture inspection)

HanaBrown0883 · 26 points · Programming & support · 3 Jun 2026

0replies R

Fairino FR10: Working on inspection result parsing while our cell is unavailable

ReeceBaker0471 · 19 points · Programming & support · 3 Jun 2026

0replies J

The scratch labels look less certain than the images suggest (planning camera inspection of reflective parts)

JackBell0689 · 5 points · Programming & support · 3 Jun 2026

11replies W

An old completion finishes my new attempt (fixture-check completion reporting)

WillAbbott0052 · 7 points · Programming & support · 3 Jun 2026

0replies A

Recovering inspection-cycle execution bookkeeping across a crash (Universal Robots UR5e)

AdaBennett0738 · 22 points · Programming & support · 2 Jun 2026

2replies B

Are we teaching our camera to reject reflections? (Fairino FR5, inspecting reflective surfaces for scratches)

BrunoBell0626 · 9 points · Programming & support · 2 Jun 2026

6replies J

A cosmetic components workshop: Getting consistent inspection evidence before commissioning

RaviBennett0737 · 35 points · Programming & support · 1 Jun 2026

15replies B

The scratch labels look less certain than the images suggest (Universal Robots UR5e)

BrunoBell0626 · 23 points · Programming & support · 1 Jun 2026

20replies K

The fake SDK keeps the screen happy and misses mistakes - sample status display

KaiAbbott0019 · 32 points · Programming & support · 1 Jun 2026

11replies R

A bench integration setup: Our status wrapper reads too much into a container

RobinBrown0947 · 31 points · Programming & support · 1 Jun 2026

0replies R

A cosmetic components workshop: How do I build a trustworthy reference set for a reflective aluminium bezel?

RaviBennett0737 · 8 points · Programming & support · 1 Jun 2026

1replies

Programming & support

Where should a software mock stop? - fixture status interpretation

Fairino FR5: Our status wrapper reads too much into a container

A fixed camera, small presentation changes, very different streaks - inspecting reflective surfaces for scratches

A subcontract lathe department: documenting a machine-tending interface: one status, conflicting definitions

A cosmetic components workshop: What counts as a confirmed defect on a reflective surface?

Our job label survived a restart a little too well (fixture inspection)

Fairino FR10: Working on inspection result parsing while our cell is unavailable

The scratch labels look less certain than the images suggest (planning camera inspection of reflective parts)

An old completion finishes my new attempt (fixture-check completion reporting)

Recovering inspection-cycle execution bookkeeping across a crash (Universal Robots UR5e)

Are we teaching our camera to reject reflections? (Fairino FR5, inspecting reflective surfaces for scratches)

How do I make event-order bugs repeatable? (Fairino FR10)

Fairino FR10: Our handover taught startup and skipped recovery

Fairino FR10: Bright streaks move when we present the part differently

A saved pocket number isn't telling me what happened (Fairino FR5)

A cosmetic components workshop: Getting consistent inspection evidence before commissioning

The scratch labels look less certain than the images suggest (Universal Robots UR5e)

The fake SDK keeps the screen happy and misses mistakes - sample status display

A bench integration setup: Our status wrapper reads too much into a container

A cosmetic components workshop: How do I build a trustworthy reference set for a reflective aluminium bezel?