Keeping failed checks in history without counting every retry (Fairino FR5)

AmaraBrown0948 · 12 May 2026, 11:05 UTC

Reply to discussion
AM
AmaraBrown0948
I'm reconciling our batch of 205 for fixture-based dimensional inspection with Fairino FR5 in a small production cell tracking inspected items, using a molded housing. The dashboard looks nearly finished because its post-restart counter includes repeat inspections. Items can have failed checks followed by reviewed retries. I want the accepted-item count to be accurate without discarding that attempt history.

17 replies

MI
MiaArcher0383
Replying to AmaraBrown0948

Pick a traceable item and compare all of its inspection attempts with its current accepted disposition. Does your counter count the attempts rather than the item?

6points
AM
AmaraBrown0948
Replying to MiaArcher0383

@MiaArcher0383 I've traced one item in our saved history and found several successful attempts with the same identity. Our counter adds each success, inflating the apparent batch progress.

17points
MI
MiaArcher0383
Replying to AmaraBrown0948

Derive the batch view offline from item-level dispositions while retaining every inspection attempt. Counting each accepted identity once should produce the correct total.

20points
HA
HassanCarter0965
Replying to MiaArcher0383

Only if accepted means the current disposition. An item that passed and was later rejected can't stay counted just because it passed once

8points
MI
MiaArcher0383
Replying to HassanCarter0965

You're right about that missing qualification. Use each item's current authorized disposition for the batch total, retaining earlier results without treating any historic success as permanent acceptance.

18points
AM
AmaraBrown0948
Replying to MiaArcher0383

So a failed check followed by reviewed acceptance stays one item, with both attempts visible? That's the view I was trying to get.

14points
MI
MiaArcher0383
Replying to AmaraBrown0948

That's the distinction: the attempt history explains what happened to the item, while its current disposition determines its contribution to the accepted-item total.

4points
RA
RaviBell0650
Replying to MiaArcher0383

@MiaArcher0383 On my report, we put attempts and accepted items beside each other. People stopped expecting the numbers to match once the repeated inspections were visible.

8points
DI
DineshAli0212
Replying to RaviBell0650

Does a retry get a new item ID then? Or just a new attempt ID?

15points
MI
MiaArcher0383
Replying to DineshAli0212

@DineshAli0212 Preserve the identity of the physical item and assign a distinct identity to each inspection attempt, keeping the relationship between them explicit.

13points
AM
AmaraBrown0948
Replying to MiaArcher0383

@MiaArcher0383 The newer entries distinguish item and attempt identity, but some older results lack the item link needed to include them reliably in an accepted-item total.

12points
HA
HassanCarter0965
Replying to AmaraBrown0948

@AmaraBrown0948 Don't manufacture identities from event order to make them fit. Similar-looking results could be retries of the same item

4points
AM
AmaraBrown0948
Replying to HassanCarter0965

I'll leave those entries unresolved while we check our physical traceability records. Making the number prettier won't identify the items.

0points
DI
DineshAli0212
Replying to AmaraBrown0948

Do unresolved items count as rejected? Otherwise the report's got another number people have to understand.

7points
MI
MiaArcher0383
Replying to DineshAli0212

An unresolved item link or disposition doesn't establish a rejected result. Represent that uncertainty separately from both confirmed acceptance and confirmed rejection.

12points
AM
AmaraBrown0948
Replying to MiaArcher0383

Our accepted quantity remains unresolved. The counting error is understood, but the full item-level reconciliation isn't established.

6points
MI
MiaArcher0383
Replying to AmaraBrown0948

That status matches the remaining item-level gap, even though the source of inflated progress is clearer.

20points

Add to the discussion

Welcome to Application Robot

Everyone can read the forum. Sign in or create an account to start a discussion, reply, or upload photos.

Forgot your password?

By creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.