Approve the expected message
Record the authorised date, batch or format source, recipe selection and permissions. Define the response to absent or stale expected data before normal production.
Optical character verification
Verify printed characters against the value you expect
Use OCV to confirm a known date, batch, lot or product string is present and acceptably formed on every product.
Practical answer
Job and trial evidence
How should an OCV check be challenged against the active job?
OCV compares a printed message with an expected value. Define who approves that value and how the active job reaches inspection, then test readable wrong content separately from missing or unreadable print. A match to the same incorrect value sent to the printer does not independently check the production rule.
Challenge the actual print range
Use representative acceptable, marginal and failed characters. Agree controlled position and appearance tolerances rather than treating the OCV method name as evidence of suitability.
Test the changeover and removal
Include the final old-job pack, first new-job pack, a pause and printer restart. Define the job for packs already between printing, inspection and rejection, and retain the agreed decision and reject outcome.
For the next step, compare OCR and OCV tasks and plan tracking and reject confirmation.
Fast known-string verification
Purpose-built vision inspection
When the correct message is known, verify it directly
OCV checks that each printed character resembles the expected character in the expected position. It is a strong choice for recipe-controlled messages where the system already knows exactly what the printer should produce.
Known-string comparison
Verify the physical print against a value supplied by the recipe or line controls.
Character-by-character check
Identify substituted, missing, merged or malformed characters within the string.
Position tolerance
Allow controlled movement while rejecting a message printed outside its approved zone.
Print-quality threshold
Apply a consistent similarity or feature threshold to every inspected code.
System outcomes
Robust verification for controlled variable messages
Because the expected content is known, OCV can concentrate on confirming the printed appearance rather than recognising an unrestricted character set.
Strong recipe control
Tie the expected printed value directly to the active product or production order.
Detailed failure location
Show which character or region failed to match the approved expectation.
Efficient processing
Verify known content quickly within a tightly controlled code window.
Application engineering
Control how the expected string reaches the vision system
The expected value can be entered in a protected recipe, selected with a production barcode or exchanged with a PLC or database. We define the handshaking and error states so an absent or stale value cannot silently authorise production.
- Expected-string source and validation
- Recipe selection and permissions
- Character similarity tolerance
- Fault handling when data is unavailable
Related inspection systems
Build a complete code-control point
Combine the inspection with complementary print, data or reject checks where they reduce the risk of a non-conforming pack reaching the customer.
Frequently asked questions
OCV verification questions
Every inspection begins with real samples, representative print and the operating conditions found on your production line.
When should OCV be used instead of OCR?
OCV is often preferred when the correct content is already known and the task is to confirm its printed appearance. OCR is needed when the system must determine an unknown string.
Can OCV verify a date that changes every day?
Yes. The expected date can be updated through a controlled recipe or data interface, after which each physical print is compared with that current value.
Does OCV allow natural print variation?
Yes. Matching tolerance is established around representative acceptable print while known defects are used to ensure the setting rejects meaningful failures.
Oxford Vision Systems
Create a controlled link between recipe and printed code
Show us the expected-message source, all printed formats and normal process variation. We will define the OCV approach.
Continue planning