FAQs: Inspection features

Perceptor IoT can inspect and verify the following 1D symbologies:

  • EAN128
  • EAN13
  • EAN8
  • UPCA
  • UPCE
  • Interleaved 2of5
  • Code 93
  • Code 39 (+Extended)
  • Codabar
  • Databar
  • DatabarLimited
  • Pharmacode

Yes, the user can choose to set a minimum pass grade for barcodes of 0.0 to 4.0.

Yes - both options are available in Perceptor IoT i.e barcode reading and barcode verification.

Please check what your licence allows as each option is licensed separately. Barcode verification also requires barcode reading. This process will happen without any input from the operator.

The duplicate field checker must be enabled for every field in your label vision template that needs to be checked for duplication across any of your labels.

Follow these steps to ensure duplicates are checked for accurately:

1. Enable the duplicate field checker feature for every field that must be unique.

2. Select a product reference.

- A product reference could be your identity number, an internal part number, your customer’s part number etc.

- Whatever product reference is chosen, Perceptor will check for duplicates against that reference.

- Additional product references can be applied so for checking at multiple levels.

3. Save these settings to your label vision template.

With this feature enabled and a product reference applied for every field to be checked, Perceptor will be able to check for, identify and overstrike any duplicates. 

All fonts can be used in your label templates and inspected by Perceptor IoT.

Current inspection speed is approximately 6 inches per second, however speed can be affected by the number of areas of interest being inspected. A simple barcode inspection will not have an impact on speed but if multiple, complex inspections are required, the speed may be compromised.

Perceptor IoT can check for a numerical sequence - e.g. 0001, 00002, 00003 - in an ascending order.
Two consecutive numbers are needed to build the sequence e.g.10001, 10002. If the next number in this sequence is 10004 then it will fail 10004 and also 10005.
However, it will continue with 10006 because that follows a sequence after 10005 and the preceding 10004.
The user also has the facility to put in an incremental step of 1,2,3,4,5 or say 10.

As OCR does not have any error correction - e.g with a DataMatrix code - there is no guarantee that the OCR is 100% correct every time.

If the application is dependent on the OCR being 100% correct then the OCR should be linked to a machine-readable code that does have error correction and so can be relied upon to be 100% correct.

The purpose of the linked field function is to check that two fields are identical so if, for example, a 3 is read as an 8 using the OCR then the difference will be detected in the linked field.

Yes.

Browse Solution Categories