0% found this document useful (0 votes)
64 views11 pages

2014RO 06514 - Manual 2D OidDecoder - EN - v2.5

The document provides a user manual for the 2D-OID DECODER. It describes how to install the decoder and configure its settings. Key settings include the module file name, folder, and field positions. It supports decoding GIMM and LJS barcode formats. The manual also outlines how to use the decoder for batch production and provides specifications and troubleshooting information.

Uploaded by

Kilobyte202005
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
64 views11 pages

2014RO 06514 - Manual 2D OidDecoder - EN - v2.5

The document provides a user manual for the 2D-OID DECODER. It describes how to install the decoder and configure its settings. Key settings include the module file name, folder, and field positions. It supports decoding GIMM and LJS barcode formats. The manual also outlines how to use the decoder for batch production and provides specifications and troubleshooting information.

Uploaded by

Kilobyte202005
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 11

2D-OID DECODER

EMDEP 2D-OID DECODER

USER MANUAL
USER MANUAL
Internal ID Commercial ID Date Version Written by
2012-PR1977 2014RO-06514 25/02/2022 2.4 Engineering Department

2D-OID DECODER

Document history and versions


Version Date Edited by Changed sections Reason for change
1.0 11/07/2012 Josep M. Rocamora All First Version
2.0 14/07/2014 Jordi Montornés 2,3,4 Support for LJS barcodes
2.4 25/02/2022 Sònia Martínez 1, 4 Installer and new script for batch
production
2.5 18/07/2022 Sònia Martínez 2.1 Whitelist parameter

Contents
1.Installation..................................................................................................................................................3
2.Settings........................................................................................................................................................3
2.1.Sample of GIMM bar code...................................................................................................................5
2.2.Sample of LJS bar code........................................................................................................................5
2.3.Sample of app.config file.....................................................................................................................5
3.Overview and applications..........................................................................................................................7
4.Batch production........................................................................................................................................7
4.1.Sample of LJS bar code for batch production......................................................................................8
5.Specifications..............................................................................................................................................8
6.Troubleshooting........................................................................................................................................10

www.emdep.com 2 / 11
2014RO-06514_Manual--2D-OidDecoder_EN_v2.5.odt - ©EMDEP 2022
USER MANUAL
Internal ID Commercial ID Date Version Written by
2012-PR1977 2014RO-06514 25/02/2022 2.4 Engineering Department

2D-OID DECODER

1. Installation
Prerequisites:

• Microsoft .Net FrameWork 2.0

• WinTestem

Installation process:

1. Run the installer 2D-OID-Decoder_SETUP_EN_vXX.exe.

2. Needed files will be copied to C:\emdep-2\Tools\AddOns\2dOidDecoder folder.

3. Check the configuration of scripts:

• load_oid_modules2D.vbs (to load the test data for electrical test)

• load_oid_modules2D_Vision.vbs (to load the test data for vision test)

• decode_oid_modules2D.vbs (to get the list of modules, delimited by comma)

and app.config and adjust them to your configuration (see section 2-Settings).

2. Settings
In order to configure the correct execution of the application, the user may set up the given scripts
(load_oid_modules2D.vbs, load_oid_modules2D_Vision.vbs, decode_oid_modules2D.vbs or
decode_oid_batch.vbs) in the package. These script creates an object called “m_eng” from the class
“Emdep.OidDecoder.Engine” that has several properties or parameters to configure. Look at the
function “setup()” where all parameters are introduced, there you can change it for matching user
necessities. These scripts can be initialized with the application Wintestem, doing a process and using
the instruction “run”. The parameters you can set up are the following:

• General settings

◦ Language: string defining the application language. By default “English” is set and this is
the only language dictionary provided in the package.

◦ AutomaticClose: it is a boolean parameter (true or false) that when set true the application
will close when all bar codes will be read correctly, and when false will show an “OK”
button in order to confirm the correct execution.

All the other parameters are set up in the “app.config” file, the parameters you can set up are:

• Module File Settings for GIMM barcodes (in section <Modules>)

www.emdep.com 3 / 11
2014RO-06514_Manual--2D-OidDecoder_EN_v2.5.odt - ©EMDEP 2022
USER MANUAL
Internal ID Commercial ID Date Version Written by
2012-PR1977 2014RO-06514 25/02/2022 2.4 Engineering Department

2D-OID DECODER

◦ File Name: name of the file which will be read by the application. If filename is
“MODULELIST.xxx” (where xxx is the index of module file specified in the first bar code),
the parameter needs to be set up as “MODULELIST”.

◦ File Folder: specifies the directory where module files can be found.

◦ Separator: a text containing the separator/delimiter of bar codes, that will indicate the
beginning and ending of a bar code. By default is “$”.

◦ OrderID: position where orderID can be found in moduleList file.

◦ Module: position where the name of the module can be found in moduleList file.

◦ LineID: position where the lineID can be found in moduleList file.

Example of line in module file:

55NALN100#AV6T-14335-LXA#A#1

In the example: Separator = #, OrderId = 4, Module = 2 and LineId = 3

• Module File Settings for LJS barcodes (in section <LJS_modules>)

◦ File Name: name of the file which will be read by the application. If filename is
“MODULELIST.xxx” (where xxx is the index of module file specified in the first bar code),
the parameter needs to be set up as “MODULELIST”.

◦ File Folder: specifies the directory where module files can be found.

◦ Separator: a text containing the separator/delimiter of bar codes, that will indicate the
beginning and ending of a bar code. By default is “;”.

◦ LineID: position where the lineID can be found in moduleList file.

◦ OrderID: position where orderID can be found in moduleList file.

◦ Value: position where the value can be found in moduleList file.

◦ Module: position where the name of the module can be found in moduleList file.

Example of line in module file:

A;1;L;55VHSB048;ACC LHD

In the example: Separator = ; , LineId = 1, OrderId = 2, Value=3 and Module = 4

• Bar code settings

◦ BarCodeSeparator: a text containing the separator of bar codes fields, that will indicate the
beginning and ending of a field inside a bar code. By default is “@”.

www.emdep.com 4 / 11
2014RO-06514_Manual--2D-OidDecoder_EN_v2.5.odt - ©EMDEP 2022
USER MANUAL
Internal ID Commercial ID Date Version Written by
2012-PR1977 2014RO-06514 25/02/2022 2.4 Engineering Department

2D-OID DECODER

◦ Gimm: position (column) in the bar code where GIMM (text to identify a GIMM barcode) is
placed.

◦ LJS: position (column) in the bar code where LJS (text to identify a LJS barcode) is placed.

◦ BarCodeVersion: position (column) in the bar code where barcode version is placed.

◦ LineId: position (column) in the bar code where LineId is placed.

◦ VersionNumberOLT: position (column) in the bar code where the database/module


version number for OLT is placed.

◦ VIN: position (column) in the bar code where the Vehicle Identification Number is placed.

◦ ReplacementParts: position (column) in the bar code where the replacement parts are
placed.

◦ ConsumptionDate: position (column) in the bar code where the consumption date is
placed.

◦ CurrentDate: position (column) in the bar code where the current date is placed.

◦ ProductionLine: position (column) in the bar code where the production line is placed.

◦ SequencingInformationCustomerID: position (column) in the bar code where the


Sequencing information (customer container id ) is placed.

◦ SequencingInformationPositionCustomer: position (column) in the bar code where the


Sequencing information (position inside customer container) is placed.

◦ ProductName:position (column) in the bar code where the product name is placed.

◦ CustomerLocation: position (column) in the bar code where the customer location is
placed.

◦ StadisticalCode: position (column) in the bar code where the Statistical code (generated
number, represents one variant) is placed.

◦ ListOfModules: position (column) in the bar code where the List of module (information
with special codification) is placed.

◦ GimmSerialNumber: position (column) in the bar code where the GIMM serial number
(unique id inside GIMM) is placed.

◦ LjsSerialNumber: position (column) in the bar code where the LJS serial number (unique id
inside LJS) is placed.

2.1. Whitelist modules list


From version 2.5.2, load_oid_modules2D.vbs and load_oid_modules2D_Vision.vbs scripts accepts a
parameter to ignore the modules that are not defined in the system. Wintestem variable @str23 should

www.emdep.com 5 / 11
2014RO-06514_Manual--2D-OidDecoder_EN_v2.5.odt - ©EMDEP 2022
USER MANUAL
Internal ID Commercial ID Date Version Written by
2012-PR1977 2014RO-06514 25/02/2022 2.4 Engineering Department

2D-OID DECODER

contain the absolute path to the file that contains the module list. In this file must be one module
defined by line.

When these scripts load a module, if module file doesn’t exists, the module name will be checked in the
whitelist file to be ignored:

• If the whitelist include that module name, the script will continue with the following modules
to be loaded.

• If that module is not included in the whitelist the script will raise an error.

2.2. Sample of GIMM bar code


GIMM@1@010@A@SAMPLE_VIN@REPLACEMENTPART@20120701000000@20120621000000@HEAD
LAMP L1@CONT_23@CELL_09@HEADLAMP@VALENCIA@STAT_1234567890@123@SN_NUMBER

2.3. Sample of LJS bar code


LJS@1@010@A@SAMPLE_VIN@REPLACEMENTPART@20120701000000@20120621000000@HEADLA
MP L1@CONT_23@CELL_09@HEADLAMP@VALENCIA@STAT_1234567890@LL1UL5551ALAA@111

2.4. Sample of app.config file


<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<modules>
<!-- Information for GIMM barcodes -->
<file> <!-- name and folder of the ModuleList file -->
<Name>MODULELIST</Name>
<Folder>C:\Emdep-2\MyProject\20140711_OID-
Decorder_with_LJS\GIMM_Modules</Folder>
</file>
<!-- definition of the fields in the ModuleList file -->
<separator>#</separator>
<orderId>4</orderId>
<module>1</module>
<lineId>3</lineId>
</modules>

<LJS_modules>
<!-- Information for LJS barcodes -->
<file> <!-- Information for GIMM barcodes -->
<Name>MODULELIST</Name>
<Folder>C:\Emdep-2\MyProject\20140711_OID-
Decorder_with_LJS\LJS_Modules</Folder>
</file>
<!-- definition of the fields in the ModuleList file -->
<separator>;</separator>
<lineId>1</lineId>
<orderId>2</orderId>
<value>3</value>

www.emdep.com 6 / 11
2014RO-06514_Manual--2D-OidDecoder_EN_v2.5.odt - ©EMDEP 2022
USER MANUAL
Internal ID Commercial ID Date Version Written by
2012-PR1977 2014RO-06514 25/02/2022 2.4 Engineering Department

2D-OID DECODER

<module>4</module>
</LJS_modules>
<barcode>
<separator>@</separator> <!-- separator of fields in barcode -->
<gimm>1</gimm> <!-- field for GIMM barcodes -->
<barCodeVersion>2</barCodeVersion> <!-- common field -->
<versionNumberOLT>3</versionNumberOLT> <!-- common field -->
<lineId>4</lineId> <!-- common field -->
<vin>5</vin> <!-- common field -->
<replacementParts>6</replacementParts> <!-- common field -->
<consumptionDate>7</consumptionDate> <!-- common field -->
<currentDate>8</currentDate> <!-- common field -->
<productionLine>9</productionLine> <!-- common field -->
<sequencingInformationCustomerID>10</sequencingInformationCustomerID> <!--
common field -->
<sequencingInformationPositionCustomer>11</sequencingInformationPositionCustomer>
<!-- common field -->
<productName>12</productName> <!-- common field -->
<customerLocation>13</customerLocation> <!-- common field -->
<stadisticalCode>14</stadisticalCode> <!-- common field -->
<listOfModules>15</listOfModules> <!-- common field -->
<gimmSerialNumber>16</gimmSerialNumber> <!-- field for GIMM barcodes -->

<ljs>1</ljs> <!-- field for LJS barcodes -->


<ljsSerialNumber>16</ljsSerialNumber> <!-- field for LJS barcodes -->
</barcode>
</configuration>

3. Overview and applications


This application is useful for decode OID 2D bar codes read by an operator with a scanner. When the
application starts, it shows a window like the one in the figure 1.

www.emdep.com 7 / 11
2014RO-06514_Manual--2D-OidDecoder_EN_v2.5.odt - ©EMDEP 2022
USER MANUAL
Internal ID Commercial ID Date Version Written by
2012-PR1977 2014RO-06514 25/02/2022 2.4 Engineering Department

2D-OID DECODER

Figure 1: Initial Screen

In this window there are three parts:

• OID Bar codes: is where the operator will introduces the scanned code in text format.

• OID Information: will show all the Fields extracted form the first bar code.

• Module List: will show the list of selected modules when decoding the bar code values.

When the bar code is properly decoded, the application will return a string containing the list of selected
modules by the decoding function.

4. Batch production
For batch production the process should run script decode_oid_batch.vbs. This script opens a window
where the operator can scan the OID card and translate the parameters to wintestem variables.

Data block description:

www.emdep.com 8 / 11
2014RO-06514_Manual--2D-OidDecoder_EN_v2.5.odt - ©EMDEP 2022
USER MANUAL
Internal ID Commercial ID Date Version Written by
2012-PR1977 2014RO-06514 25/02/2022 2.4 Engineering Department

2D-OID DECODER

4.1. Sample of LJS bar code for batch production


LJS@000000031@003@IP@5A2E87420@.@.@20211020@1@0@.@[email protected]@73301599-
10@Bxxxx@*000000031*=

5. Specifications
1. The bar code must contain 16 fields, separated by a separator, by default the separator is @
2. Depending of the first field (GIMM or LJS), the software will look for the MODULELIST.xxx
specified in section <modules> (GIMM) or <LJS_modules> (LJS) of app.config file
3. The application shows the modules on the screen allowing the user or supervisor to verify the
module composition before the test.

Figure 2: Screen with a decoded BarCode

www.emdep.com 9 / 11
2014RO-06514_Manual--2D-OidDecoder_EN_v2.5.odt - ©EMDEP 2022
USER MANUAL
Internal ID Commercial ID Date Version Written by
2012-PR1977 2014RO-06514 25/02/2022 2.4 Engineering Department

2D-OID DECODER

4. If the operator introduces a wrong bar code, the text field will turn red and will allow the
operator to reintroduce the bar code again. When the bar code introduced is correctly
decoded, automatically the application will lock the text field.

Figure 3: Error in the field

5. After introducing and validating all required bar codes, the application will return a string with
the list of required modules separated by commas.

www.emdep.com 10 / 11
2014RO-06514_Manual--2D-OidDecoder_EN_v2.5.odt - ©EMDEP 2022
USER MANUAL
Internal ID Commercial ID Date Version Written by
2012-PR1977 2014RO-06514 25/02/2022 2.4 Engineering Department

2D-OID DECODER

6. Troubleshooting
Problem Cause Recommended actions

Error message: The application execution has been -


“Canceled”. canceled by clicking the “Cancel”
button.

Error message: “No Application window closed with X Close always with cancel button.
OID bar codes read”. button. The application has been
interrupted while correct execution.

Error message: “OID Application window closed with X Close always with cancel button. Check
bar code wrong: button. The application has been wrong codes when text fields turn red.
XXXXXX”. interrupted when an error appeared
after decoding a bar code.

Error message: “File The file specified in app.config is Check the app.config file and modify
not found or unable to wrong. the fields “fileName” and “fileFolder” if
load: <filename>” convenient.

Error message: “Error The file hasn't the standard structure Check the app.config file and modify
parsing line X in file the fields “fileName”, “fileFolder”,
<filename>”. Or index specified already exist “separator” and orderID if convenient.
(duplicated)
If file does not match the structure,
please correct it or change to other
file.

Error message: “Index The LineID in bar code does not Check that the first bar code
for the specified LineID appear in file specified, so it is introduced is correct and has de
X not found” impossible to add any module. proper LineID character.

If these recommended actions do not help to solve the problem, please see section 2. Setting and check
if your configuration is correct.

www.emdep.com 11 / 11
2014RO-06514_Manual--2D-OidDecoder_EN_v2.5.odt - ©EMDEP 2022

You might also like