:00Thu 24 Sep

Label formats

About label formats

How supplier labels are read: one reader, one applicable format, for every scan at every station.

Exactly one enabled format may read a label. The order of the list is where a format is listed, not which one wins.

5 formats · 4 labels unread

New format from a label

4 labels no format reads · since 09:02

Operators saw “This label can’t be read here.” and typed the reel ID.
See them

Registry revision 41

One format per label

Every enabled format is checked on every scan, and exactly one may read a label. Two that both read it overlap, even when they read it the same way: the list’s order never decides. Narrow one, or retire it.

Vendor pipe label

Active v3used for every scan since Tue 23 Sep 18:02

Shape v3 reads

Exactly 5 fields separated by “|”; field 1 is “VND”; field 4 is digits; field 5 is “VR-” + 6 digits.

Fields it records

Part number
field 2
Lot
field 3
Quantity
field 4
Reel ID
field 5

Unmapped fields are kept with every scan as raw evidence.

Working copy · v4

Gábor Szabó · since 09:40

Without the VND marker, so labels printed without it read too.

Fields and shapes

Save after changing the kind or the number of fields to refresh the rows. A shape is literal text, digit runs (\d, \d{8}, \d+) and letter runs ([A-Z]). A field with no role is read but not kept.

Field 1
Field 2
Field 3
Field 4
Field 5

Samples

What the samples must show

At least one sample that reads and one that must not. Every mapped field is shown by a sample that reads.

Samples
#CodeExpectResultActions
1VND|PN-420|LOT-8|250|VR-000871Reads · reel VR-000871Passes
2VND|PN-420|LOT-8Must not read · 3 fieldsPasses

Check

A dry run of the registry this would publish · nothing changes

2 of 2 samples pass 2 labels of other formats read differently 6 stored labels read the same 0 read differently 3 unread labels now readable 0 ambiguous

It would read another format’s labels

  • Würth Elektronik reel label: WE|885012206095|Q:4000|L:W2614-7731|DC:2614 → reel DC:2614
  • Würth Elektronik reel label: WE|885012206095|Q:2000|L:W2615-0102|DC:2615 → reel DC:2615
  • It changes how 2 labels of other formats read: refused in every preset.

What a registry change does

Every change runs the check on the registry it publishes. Moving a format changes only where it is listed. Stored reels keep their recorded identity. Retiring a format that stored reels were read with is refused, except under the Relaxed preset with a named reason.

Publishing changes how every station reads labels, so it asks who you are again.

Versions · 2Immutable once published; going back publishes the old one again
  1. v3ActiveEszter Szabó · Tue 23 Sep 18:02 · lot read from field 3In use
  2. v2SupersededEszter Szabó · Mon 1 Sep 10:15 · quantity field added

Try a code

Read exactly as a station reads it · nothing is saved

Try VideotonRenesasWürthEIGP 114No reel IDUnreadable

This label can’t be read here.

Formats checked · 0 matched
  1. 1
    Vendor pipe label v3
    No VND marker
    No match
  2. 2
    Renesas DI label v2
    1 fields, the format has 8
    No match
  3. 3
    Videoton two-field v1
    1 fields, the format has 2
    No match
  4. 4
    GS1 application identifiers v1
    No application identifiers
    No match
  5. 5
    EIGP 114 · MH10 (Format 06) v1
    No Format 06 envelope
    No match

Labels no format reads

How these close

Each is a review item. A published version that reads it closes it.

  • WE|885012206095|Q:4000|L:W2614-7731|DC:2614
    Station SMT-2 · 11:20 · Márta Kovács
    Not read
  • WE|885012206095|Q:2000|L:W2615-0102|DC:2615
    Station SMT-2 · 11:24 · Márta Kovács
    Not read
  • WE|744031100|Q:1500|L:W2609-4410|DC:2609
    Station SMT-2 · 11:31 · Márta Kovács
    Not read
  • ZX-77781/unknown
    PDA-04 · 09:02 · Katalin Horváth
    Not read

Publish Vendor pipe label v4?

It replaces v3 for every new scan. Stored reels keep their recorded identity.

2 of 2 samples pass 2 labels of other formats read differently 6 stored labels read the same 0 read differently 3 unread labels now readable 0 ambiguous

Publishing changes how every station reads labels, so it asks who you are again.

Then: Janus runs the check again on the registry as it is, stores version 4 and registry revision 42, and every station reads with it from its next scan. If anything changed meanwhile, nothing is stored.

Go back to v2 of Vendor pipe label?

It is published again as v4, after the same check against the labels it read before. v3 is kept.

Publishing changes how every station reads labels, so it asks who you are again.

Discard working copy v4?

Its samples go with it. Nothing a station reads changes.

Alerts

Faults and blocked work stay here until fixed. Notices can be cleared.

SR-02 is limited

Bence Tóth is on itsince 09:41 · 4 h 51 min14:30 installation map v4 drafted by Dávid Horváth under permit · waiting to be applied

Tier 3, bays 1–16 are Unknown. Blocks 2 take-outs for WO-260714-09 and hides 310 pcs of PN-QFN32-MCU7. The rest of SR-02 works.

Troubleshoot SR-02Stays until fixed

Label not recognised

A Würth Elektronik label matched no code rule.

Add label rule

Put-in not finished

Reel R-2026-0109 is waiting for the sensor at SR-01-T4-L31: finish putting it in, or cancel.

Continue put-in

Counter ReelSave is failing

Owner: line counter vendorsince 13:48

12 messages waiting. SMT Line 2 counters don't know about reels taken out since 13:48.

Open Integrations

Snapshot taken · 14:30

Verified · off-host copy 14:30. Snapshots every 15 min while Janus is busy.

Choose working rack

Scans and bay lights on this station use the working rack. Opening another rack never switches it.

Racks

Help

What the words mean

Language

Applies to this station only. Records keep the words they were written in.

Prototype

Label formats

Preview stateLabel formats

Later · not in R1

View as

This page

Purpose
Label formats: active and working copies, tried on a reader, published with step-up.
Release
R1
First viewport
1 primary · 1 notice · 3 blocks