Validate the barcode.
Verify the MES decision.

Reviewed 15 October 2026 · Raju Bros Softech Pvt ltd · Based on documented application behavior; validate your station.

• Use an authorised ADMIN account with Model Setting and MES editing permissions. Confirm the licence package and any separate Data Link entitlement required by your design.
• Agree the barcode count, capture order, required length/text, within-DUT duplicate policy and interlocking conditions with production engineering.
• Obtain an approved MES test endpoint and non-production barcode set. Agree the request format, accepted/rejected response, timeout handling and result-reconciliation procedure with the MES owner.

1. Save the model

   Open Model Setting, add or select the model, set Barcode Count and the validation option, and review Allow duplicate barcode within same DUT. Click SAVE MODEL.

2. Define each required slot

   Choose Barcode No and Barcode display name. Select Validation type: Length + Must contain, Length only, Must contain only, or No Validation. Use Scan sample barcode and review Calculated length; set Must contain string when required.

3. Choose capture and MES timing

   Select Manual or Serial Trigger as Capture mode. Serial Trigger slots need a matching Scan Barcode or Assign Barcode From Variable sequence step with SLOT=n. Review the slot’s MES validation setting: Default, On Capture or Disabled.

4. Save and challenge the rule

   Click SAVE BARCODE RULE. Use RULE TEST and TEST RULE with an approved valid sample and deliberately invalid samples. Check incorrect length and required-text cases separately. Repeat for every slot.

In Model Setting > INTERLOCKING, select the Barcode No and enabled rule. Set Search folder, File name pattern and Check mode. Available checks include File Exists Only, Read File Contains Text, Specific Line Contains Text and CSV Barcode Result Lookup.

1. Define the evidence required

   Choose the PASS text or CSV columns/result rule appropriate to the upstream process. Review case sensitivity, timeout, Network fail behaviour and any maximum file age requirement.

2. Test with a known barcode

   Enter Test barcode and click TEST. Check the result against a known valid upstream record, then a missing or rejected record. For CSV lookup, also test a duplicate barcode and a barcode with no matching row.

3. Save the reviewed rule

   Use SAVE INTERLOCK. The network and missing-record policies affect whether testing blocks, warns or proceeds. Approve those policies deliberately; an enabled file-age check rejects old files even when Warn/Allow is selected.

1. Configure the request contract

   Open Admin / Testing > MES > IP Based MES. Review Before Testing and After Testing separately. Configure Protocol, HTTP URL/method/content type or MES server IP/port, Payload TX format, Accepted responses and Response timeout ms.

2. Review the generated payload

   Inspect Preview body and confirm the barcode, model and station tokens resolve as intended. Save with SAVE MES SETTING. Use only the fields and token names agreed with your MES owner.

3. Run an approved before-test trial

   In MES Manual Trial, enter Trial machine ID, Trial product ID and Trial barcode. USE SAVED loads the current before-test payload into the trial editor; REFRESH PREVIEW updates its preview. Check Manual trial TX preview, then SEND MES TRIAL to your approved test endpoint and inspect RX response.

4. Compare acceptance with the business rule

   The manual trial uses the before-testing settings. Confirm that the response meets the intended acceptance rule. The ANY option accepts any non-empty response, so it cannot distinguish a business rejection from approval.

5. Validate the production lifecycle

   Use a controlled run with the selected model and test plan to verify capture timing, start blocking, saved results and the separate after-test exchange. Record the server acknowledgement and reconcile it against the station record.

MES configuration Inside the software

Enlarge

The following are test cases to perform, not claimed results from a customer station. Record actual outcomes and approve the configuration before production.