LECTOR®620 LECTOR 620 Image-Based Code Reader Lector 620 Operati… · LECTOR®620 ONLINE HELP...

LECTOR®620

ONLINE HELP SOPAS ETO N L I N E H E L P S O PA S E T

LECTOR�620Image-Based Code Reader

Clever, simple, industrial

ONLINE HELP SOPAS ET

LECTOR®620

2 © SICK AG · Germany · All rights reserved · Subject to change without notice 8013778/0000/2010-

Software Versions

Copyright

Copyright © 2010

SICK AG Waldkirch

Auto Ident, Reute Plant

Nimburger Strasse 11

79276 Reute

Germany

Trademark

Windows 2000™, XP™, Vista™ and Internet Explorer™ are trademarks or registered trade-marks of Microsoft Corporation in the USA and in other countries.

Acrobat™ Reader™ is a trademark of Adobe Systems Incorporated.

Software Function Version

Device description (LECTOR620.sdd) Operation and configuration of the LECTOR®620

V 1.0

SOPAS-ET / SOPAS SingleDevice Operation and configuration software

V 2.32


LECTOR®620

Contents

8013778/0000/2010-11-18 © SICK AG · Germany · All rights reserved · Subject to change without notice 3

Table of contents1 Notes on this document................................................................................................... 52 Operation and configuration with SOPAS-ET ................................................................ 7

2.1 Software interface............................................................................................. 72.2 Online images.................................................................................................... 7

2.2.1 Online images ............................................................................................... 82.2.1.1 Image history..........................................................................................102.2.1.2 Code infobox...........................................................................................102.2.1.3 Statistics .................................................................................................11

2.3 Stored images .................................................................................................122.3.1 Stored images.............................................................................................13

2.3.1.1 Image history..........................................................................................142.3.1.2 Code infobox...........................................................................................14

2.4 Project tree ......................................................................................................152.4.1 Parameter ...................................................................................................15

2.4.1.1 Reading configuration ...........................................................................152.4.1.1.1Image acquisition ..............................................................................152.4.1.1.25Object trigger control.......................................................................21

2.4.1.2 Increment configuration ........................................................................272.4.1.2.1Increment ...........................................................................................27

2.4.1.3 Code config.............................................................................................282.4.1.3.11D Symbologies .................................................................................282.4.1.3.102D symbologies ...............................................................................312.4.1.3.14Stacked codes .................................................................................322.4.1.3.16General code settings .....................................................................332.4.1.3.20Codabar............................................................................................332.4.1.3.30Code 39 ...........................................................................................352.4.1.3.41UPC/EAN..........................................................................................372.4.1.3.522/5 interleaved ...............................................................................402.4.1.3.65Code 93 ...........................................................................................412.4.1.3.72Code 128 Family .............................................................................422.4.1.3.84Pharmacode ....................................................................................452.4.1.3.91Data matrix ......................................................................................462.4.1.3.109PDF 417.........................................................................................49

2.4.1.4 Data processing .....................................................................................492.4.1.4.1Collection of data...............................................................................492.4.1.4.3Code summarization .........................................................................492.4.1.4.7Output control ....................................................................................502.4.1.4.20Evaluation conditions......................................................................522.4.1.4.25Match-code ......................................................................................542.4.1.4.48Filter/Sorter for output....................................................................582.4.1.4.51Output format ..................................................................................692.4.1.4.55Diagnosis settings ...........................................................................80

2.4.1.5 Application counters ..............................................................................842.4.1.5.1Application counters..........................................................................84

2.4.1.6 Network / Interface / IOs ......................................................................852.4.1.6.1Network options.................................................................................852.4.1.6.4Master / slave....................................................................................852.4.1.6.7Multiplexer / server ...........................................................................852.4.1.6.10Monitoring........................................................................................852.4.1.6.14Serial ................................................................................................862.4.1.6.32Ethernet ...........................................................................................882.4.1.6.54CAN...................................................................................................922.4.1.6.61Digital inputs....................................................................................922.4.1.6.82Digital outputs/beeper....................................................................962.4.1.6.128Function buttons ........................................................................ 109


LECTOR®620


Contents

2.4.2 Service ......................................................................................................1112.4.2.1 Operating data .....................................................................................111

2.4.2.1.1Device information..........................................................................1112.4.2.1.7Operating data.................................................................................1112.4.2.1.11Service information.......................................................................112

2.4.2.2 System status ......................................................................................1122.4.2.2.1System information.........................................................................112

2.4.3 Analysis .....................................................................................................1122.4.3.1 Event monitor.......................................................................................112

2.4.3.1.1Event monitor ..................................................................................1123 Used Open Source programms and its license texts...............................................113

3.1 NCURSES – 5.7 - License.............................................................................1133.2 Z-Lib 1.2.3 .....................................................................................................1133.3 e2fsprogs-1.41.11 (UUID-license based on BSD 3-clause license)..........1143.4 Dropbear – 0.52.tar.bz2 ..............................................................................114

3.4.1 Portions of the client-mode work are (c) 2004 Mihnea Stoenescu, under the same license: ..........................................................................115

3.4.2 Import code in keyimport.c is modified from PuTTY's import.c, licensed as follows: ..................................................................................115

3.5 OpenSSH – 5.1p1.........................................................................................1163.5.1 Cryptographic attack detector for ssh - source code.............................1163.5.2 ...................................................................................................................1163.5.3 ...................................................................................................................1163.5.4 ...................................................................................................................1173.5.5 Portable OpenSSH contains the following additional licenses: ............118

3.6 GNU GENERAL PUBLIC LICENSE .................................................................1203.7 Libstdc++-v3 .................................................................................................1203.8 Glibc 2.8 ........................................................................................................121

3.8.1 GNU LESSER GENERAL PUBLIC LICENSE ..............................................1213.8.2 GNU GENERAL PUBLIC LICENSE.............................................................123

ONLINE HELP SOPAS ET Chapter 1

LECTOR®620

Notes on this document


1 Notes on this document

This document contains the online help of device description LECTOR620.sdd (for operati-on and configuration with SOPAS Single Device or SOPAS-ET).

Used symbols To gain easier access, some information in this documentation is emphasized as follows:

Intended use The camera-based LECTOR®620 is an intelligent sensor for the automatic, stationary deco-ding of codes on moving or still-standing objects. It reads all common 1D codes (barcodes)/2D codes (stacked codes/matrix codes). Via its host interface, the LECTOR®620 transmits the reading data to a higher-level computer for further processing.

Safety information Read the LECTOR®620 operating instructions and familiarize yourself with the device and its functions.

To avoid the dazzle caused by integrated illumination, do not look into the reading win-dow when switching the LECTOR®620 on and off.

Hint

This symbol points out specific features.

Note

This symbol indicates additional settings in the SOPAS-ET configuration software.

Important

This symbol indicates supplementary technical documentation.

The accessible radiation of the laser LEDs poses no risk.

Temporary, irritating, optical effects on the human eye (e.g. dazzle, blindness from flash, after-images, impairment of color vision) cannot be completely ruled out, particularly with low ambient brightness. Precautionary measures are not required. Caution - incorrect use may result in the user being exposed to hazardous radiation.

Do not intentionally look directly into the light sources for long periods of times.

Observe the currently applicable regulations on photobiological safety of lamps and lamp systems as well as laser protection.

Hint

No maintenance is required in order to ensure compliance with risk group RG 1/laser pro-tection class 1.

Chapter 1 ONLINE HELP SOPAS ET

LECTOR®620


Notes on this document

Further informationImportant

For information on startup, operation, and maintenance, see the operating instructions for the LECTOR®620.

For more information on the LECTOR®620, see the LECTOR®620 product page on the inter-net at the SICK Partner Portal, www.mysick.com:

• Detailed technical data in the online data sheet• Scale drawing and 3D CAD scale models in various electronic formats• EC Declaration of Conformity• Integration of the Lector™620 in field bus systems• Overview of the command strings• Updates of the SOPAS ET configuration software• Other useful software

You can also obtain assistance from your sales partner (www.sick.com).


LECTOR®620

Operation and configuration with SOPAS-ET


2 Operation and configuration with SOPAS-ET

2.1 Software interface

Wizards Pressing the AUTO-SETUP button on the WIZARDS tab on the left-hand side of the software interface automatically calls up the Auto Setup wizard for automatic setting of the following parameters:

• READING DISTANCE

• IMAGE SETTINGS

– BRIGHTNESS

– CONTRAST

• CODE SETTINGS

Context help The CONTEXT HELP tab on the left-hand side of the software interface provides you with infor-mation on the currently selected parameters.

2.2 Online images

The recorded images are displayed on the Online images tab.

The display enables you to look at the images in detail and assess the recording quality. By modifying the configuration and comparing the recorded images, you can optimize the rea-ding properties and the position of the LECTOR®620.

The reading results are displayed in Code infobox.

For an evaluation of the current setting for the contrast, the identified codes are displayed with different colors:

• Green (excellent): Contrast between 55 % and 100 %

• Yellow (good): Contrast between 20 % and 55 %

• Red (poor): Contrast less than 20 %

Note

The automatic setting of these parameters can also be called up individually (chapter 2.4.1.6.131 Auto-Setup, page 110).


LECTOR®620



2.2.1 Online images

The most recently recorded image is displayed in the main view of the Online images group.

The display enables you to look at the images in detail and assess the recording quality. By modifying the configuration and comparing the recorded images, you can optimize the rea-ding properties and the position of the LECTOR®620.

The reading results are displayed in Code infobox.





Operation If you press the Operation button, the mode for setting up the LECTOR®620 is stopped, and the operating mode of the LECTOR®620 is activated in accordance with the current configu-ration.

In Image history, the recorded images are displayed one after the other. The reading results are displayed in Code infobox. The display fields of the Statistics group contain the reading results of the most recent readings.





Edit If you press the Edit button, the reading process for testing the configuration is started. Ima-ges are recorded in a free-running manner in this process and displayed in the main view.

Changes to the configuration (e.g. image settings or code configuration) and to the position of the LECTOR®620 (e.g. reading distance or reading angle) are immediately visible in the main view. As a result, you can carry out test readings and check/optimize the current po-sition and configuration of the LECTOR®620.






LECTOR®620



Behavior of the LECTOR®620 during setup:

• Each second, one image is transferred to the image history in order to log changes.

• For an evaluation of the current setting for the contrast, the identified codes are displayed with different colors.

• The code contents and other relevant data for all identified codes are displayed in the code info box to enable you to assess the reading stability.

• The reading results are transferred to the AUX interface in the configured output format.

• The reading results are not transferred to the host interface.

• External triggers at the digital inputs are ignored.

• Trigger distribution on the CAN interface is deactivated.

• Digital outputs are not set.

Pause You can use the button to pause the continuous display of recorded images during setup and in operating mode.

In the case of paused continuous display, reading continues; however, the currently dis-played image can be looked at in more detail without being overwritten with a new image.

The image region of interest can be moved with the mouse ( ).

You can use the button to continue with the continuous display of recorded images.

Store You use the button to store the currently displayed image on the PC. For each stored image, an xml file containing additional information is stored.

You can choose any image name and storage location.

Enlarge You use the button to enlarge the image by degrees.


To look at the code structure in more detail and thus find errors in the code, you can also enlarge the image using the mouse scroll wheel.

Reduce You use the button to reduce the image by degrees.

You can also reduce the image using the mouse scroll wheel.

Standard size You use the button to display the image in its standard size.


LECTOR®620



2.2.1.1 Image history

In Image history, the recorded images are displayed one after the other. The images recor-ded most recently are added on the left.

By comparing and assessing the recorded images, you can analyze, for example,

• whether the trigger is set correctly and the appropriate region of the reading area was recorded

• whether the codes for moving objects were represented in focus and whether the shutter time was set correctly

• how often a code was recorded per reading gate.

To find out the reason for unsuccessful readings, you may find it useful to analyze the images without identified codes (NO READ).

The images displayed in reduced form in Image history are displayed by clicking in the main view. The file name and storage location of the images are displayed as a tooltip (mouseo-ver).

You can use the and buttons to switch between several sequences.

The number of displayed images depends on the operating mode and the configuration:

• Depending on the configuration of the Image selection parameter, either the last 200 in-dividual images are displayed (one individual image per trigger) or 60 images per second are displayed in individual sequences.

• During reading to test the configuration (operating mode Edit), the last 30 images recor-ded are displayed.

2.2.1.2 Code infobox

The reading results are displayed in Code infobox. So that the readability and reading quality can be evaluated, the code contents and other relevant data of all detected codes are dis-played. Codes that were detected multiple times on an image are listed one below the other.

You can use drag and drop to enlarge the columns and change the column sequence.

Code content The contents of the codes are displayed in the Code content column.

By assigning the code contents to the code, you can compare the read contents with the actual contents of the code.

Code ID The code type of the code are displayed in the Code ID column. By assigning the code type to the code contents, you can activate/deactivate certain code types in the code configura-tion in order to limit multiple contents to one code type, for example.


LECTOR®620



Contrast PCS. The contrast of the codes in % is displayed in the Contrast PCS. column.

A high contrast simplifies identification of a code. By comparing different configurations, you can find the setting for the highest possible contrast.

• From 55 % - 100 %: Contrast EXCELLENT

• From 20 % - 55 %: Contrast GOOD

• Less than 20 %: Contrast POOR

Module width/height inpx

The module width and height of the codes is displayed in pixels in the Module width/height in px column.

The value can be used to evaluate the reading reliability (reserve) in relation to the image resolution. The higher the value, the more reliable the reading. A value of at least 2/2, is recommended, i.e. every code element is represented by at least 2/2 pixels.

By comparing the two values, you may be able to detect a distortion of the image or of the code.

• The module width is the dimension of the smallest code element (bar of a barcode or cell in a DataMatrix code) in pixels.

• The module height is the length of a bar of a barcode or the height of a cell in the Data Matrix code.

2.2.1.3 Statistics

The display fields of the Statistics group are used to evaluate the reading results across all triggers since the device was started or since the last reset.

The reading results during setup of the LECTOR®620 are not taken into consideration in the statistics.

Reading gates The number of all triggers since the device was started or since the last reset are displayed in the Reading gates display field.

The triggers during setup of the LECTOR®620 are not taken into consideration in the stati-stics.

Good Reads The number of triggers for which the condition for Good Read was met is displayed in the Good Reads display field.



LECTOR®620



No Reads The number of triggers for which the condition for Good Read was NOT met is displayed in the No Reads display field.


Read rate The proportion of triggers for which the condition for Good Read compared to all triggers is displayed as a % in the Read rate display field.


Reset The Reset button is used to delete the values of the Reading gates, Good Reads, No Reads, and Read rate display fields.

2.3 Stored images

Stored images can be displayed on the Stored images tab.

The images stored in the LECTOR®620 or on the MicroSD memory card can be transferred to the PC. The data (images, xml files, etc.) stored in the LECTOR®620 or on the MicroSD memory card can also be deleted.

By comparing and assessing the recorded images, you can, for example, analyze which codes were not identified and whether faulty code structures have prevented a reading. For this, the images displayed in reduced form in Image history are displayed by clicking in the main view. The relevant code data is listed in Code infobox. To classify the recorded images more effectively, you can use the right mouse button to display the date and time of recor-ding.






LECTOR®620



2.3.1 Stored images

Stored images can be displayed in the main view of the Stored images group.

The images stored in the LECTOR®620 or on the MicroSD memory card can be transferred to the PC and can, for example, be stored in a database and called up as required. The data (images, xml files, etc.) stored in the LECTOR®620 or on the MicroSD memory card can also be deleted.

By comparing and assessing the recorded images, you can, for example, analyze which codes were not identified and whether faulty code structures have prevented a reading. For this, the images displayed in reduced form in Image history are displayed by clicking in the main view. The relevant code data is listed in Code infobox. To classify the recorded images more effectively, you can use the right mouse button to display the date and time of recor-ding.





Copy images You can use the Copy images button to transfer the images stored in the LECTOR®620 or on the MicroSD memory card to the PC.

You can choose any storage location on the PC.

Delete images You can use the Delete images button to remove the images stored in the LECTOR®620 or on the MicroSD memory card (images, xml files, etc.).

Load image(s) You use the Load image(s) button to display the previously transferred images.

Store You use the button to store the currently displayed image on the PC. For each stored image, an xml file containing additional information is stored.

You can choose any image name and storage location.

Enlarge You use the button to enlarge the image by degrees.


To look at the code structure in more detail and thus find errors in the code, you can also enlarge the image using the mouse scroll wheel.


LECTOR®620



Reduce You use the button to reduce the image by degrees.

You can also reduce the image using the mouse scroll wheel.

Standard size You use the button to display the image in its standard size.

2.3.1.1 Image history

In Image history, the recorded images are displayed one after the other. The images recor-ded most recently are added on the left.

By comparing and assessing the recorded images, you can analyze, for example,

• how often a code was recorded in total

• how often a code was recorded per reading gate

• whether the codes for moving objects were represented in focus and whether the shutter time was set correctly

To find out the reason for unsuccessful readings, you may find it useful to analyze the images without identified codes (NO READ).

The images displayed in reduced form in Image history are displayed by clicking in the main view. The file name and storage location of the images are displayed as a tooltip (mouseo-ver).

You can use the and buttons to switch between several sequences.

The number of displayed images depends on the operating mode and the configuration:

• Depending on the configuration of the Image selection parameter, either the last 200 in-dividual images are displayed (one individual image per trigger) or 60 images per second are displayed in individual sequences.

• During reading to test the configuration (operating mode Edit), the last 30 images recor-ded are displayed.

2.3.1.2 Code infobox

The reading results are displayed in Code infobox. So that the readability and reading quality can be evaluated, the code contents and other relevant data of all detected codes are dis-played. Codes that were detected multiple times on an image are listed one below the other.

You can use drag and drop to enlarge the columns and change the column sequence.

Code content The contents of the codes are displayed in the Code content column.

By assigning the code contents to the code, you can compare the read contents with the actual contents of the code.


LECTOR®620



Code ID The code type of the code are displayed in the Code ID column. By assigning the code type to the code contents, you can activate/deactivate certain code types in the code configura-tion in order to limit multiple contents to one code type, for example.

Contrast PCS. The contrast of the codes in % is displayed in the Contrast PCS. column.

A high contrast simplifies identification of a code. By comparing different configurations, you can find the setting for the highest possible contrast.

• From 55 % - 100 %: Contrast EXCELLENT

• From 20 % - 55 %: Contrast GOOD

• Less than 20 %: Contrast POOR

Module width/height inpx

The module width and height of the codes is displayed in pixels in the Module width/height in px column.

The value can be used to evaluate the reading reliability (reserve) in relation to the image resolution. The higher the value, the more reliable the reading. A value of at least 2/2, is recommended, i.e. every code element is represented by at least 2/2 pixels.

By comparing the two values, you may be able to detect a distortion of the image or of the code.

• The module width is the dimension of the smallest code element (bar of a barcode or cell in a DataMatrix code) in pixels.

• The module height is the length of a bar of a barcode or the height of a cell in the Data Matrix code.

2.4 Project tree

2.4.1 Parameter

Parameter

2.4.1.1 Reading configuration

Reading configuration

2.4.1.1.1Image acquisition

Image acquisition

2.4.1.1.2Reading distance

Reading distance


LECTOR®620



2.4.1.1.3Reading distance

The Reading distance parameter is used to set the distance between the LECTOR®620 and the object. The reading distance is used to modify the depth of field of the LECTOR®620 at the installation location.

The value can be entered manually in mm or set automatically using the Auto button.

To avoid disruptive reflections on the object surface, the LECTOR®620 should be in-stalled at a suitable fixing bracket (see installation information).

The reading distance influences the minimum code resolution and the size of the reading area:

• If the reading distance is small, smaller codes can be read.

• A larger reading distance increases the reading area. The reduction in image brightness caused by this is compensated for by the brightness control and, if necessary, by increasing the shutter time.

2.4.1.1.4Auto

Pressing the Auto button calls up the Auto Setup wizard for automatic configuration of the reading distance.

For the reading distance to be adjusted automatically, a suitable object with contrast chan-ges or edges (e.g. code, text, or other structures) must be placed in the reading area.

A prerequisite for automatic configuration of the reading distance is a certain basic brightness at which the structures in the image are visible.

2.4.1.1.5Shutter time

Shutter time


The Shutter time parameter is used to define the timeframe in μs for recording an image.

• A short shutter time permits high object speeds. As the image brightness is reduced as a result, the signal gain (Brightness) may need to be adjusted. However, this increases the image noise.

• A long shutter time leads to higher brightness and thus lower image noise. This setting is ideal for objects at a standstill or for slow movements.


Shutter time

2.4.1.1.8Image

Image


LECTOR®620



2.4.1.1.9Brightness

The Brightness parameter is used to set the gain of the signal. This enables the image brightness to be adjusted so that the code can be seen and decoded well.

Note here that too high a gain leads to a high image noise, making the reading of codes more difficult.

To avoid this, the value should be increased step by step until the code can be read suc-cessfully.

2.4.1.1.10Brightness

Brightness

2.4.1.1.11Contrast

The Contrast parameter is used to set the gamma adjustment in % and to modify it to the contrast of the code.

If the optical difference between white and black code elements is small, the parameter should be set to a high value, until you can clearly differentiate between the code elements.

You can use the information in Code infobox (Contrast PCS.) to check the contrast:

• 100 %: Max. contrast

• 10 %: Code can already be identified

2.4.1.1.12Contrast

Contrast

2.4.1.1.13Auto

Pressing the Auto button calls up the Auto Setup wizard for automatic configuration of the brightness and contrast.

For the settings to be adjusted automatically, a suitable object with contrast changes or edges (e.g. code, text, or other structures) must be placed in the reading area.

2.4.1.1.14Illumination

The parameters of the Illumination group are used to deactivate and configure the illumina-tion elements.

Optimizing the settings leads to an optimum, high-contrast, and consistently illuminated reading area. External influences caused by sun, darkness, room lighting, etc. can therefore be minimized.


LECTOR®620



2.4.1.1.15Internal

The Internal parameter is used to modify the internal illumination of the LECTOR®620 in line with the application's in situ lighting situation.

• OFF: If external illumination is used, the internal illumination can be deactivated.

• RED: The red illumination permits the maximum contrast for codes in the wavelength spectrum between blue and green.

• BLUE: The blue illumination offers the maximum contrast for codes in the wavelength spectrum between green and red and can improve the reflection properties for codes on metal surfaces.

• RED+BLUE: The illumination in both colors offers the maximum contrast for black codes. The illumination of the reading area is homogeneous with increased light output. This set-ting is recommended in the case of a high reading distance and if the background color is unknown or could change.

2.4.1.1.16Aiming laser

For various operating statuses, you can use the Aiming laser parameter to mark the opti-mum position for the codes in the center of the reading area directly on the object using the integrated laser pointer.

As a result, you can easily position the codes manually and achieve optimum alignment.

• OFF: Aiming laser is deactivated.

• LIVE IMAGE, AUTO-SETUP: Aiming laser is only activated to set up the LECTOR®620.

• TRIGGER, LIVE IMAGE, AUTO-SETUP: Aiming laser remains activated as long as the reading gate is open.

To avoid malfunctions caused by the aiming laser, deactivate it (OFF). For manual rea-ding or if the position changes frequently, the TRIGGER, LIVE IMAGE, AUTO-SETUP setting is re-commended.

To activate/deactivate the aiming laser using keys on the LECTOR®620, the Function parameter must have value TRIGGER AND AIMING LASER.


LECTOR®620



2.4.1.1.17Green feedback spot

The Green feedback spot parameter is used to select the condition causing a green LED spot to be illuminated in the reading area. As a result, an optical notification can be set up for a specific event.

The timeframe for illumination is defined using the Duration parameter.

• OFF: The LED spot never illuminates.

• GOOD READ: The green LED spot illuminates if reading was successful.

• NO READ: The green LED spot illuminates if reading was unsuccessful.

• TEACH-IN 1 OK: The green LED spot illuminates if the MATCHCODE TEACH-IN 1 was read in suc-cessfully.

• TEACH-IN 1 NOK: The green LED spot illuminates if the MATCHCODE TEACH-IN 1 was not read in successfully.

• TEACH-IN 2 OK: The green LED spot illuminates if the MATCHCODE TEACH-IN 2 was read in suc-cessfully.

• TEACH-IN 2 NOK: The green LED spot illuminates if the MATCHCODE TEACH-IN 2 was not read in successfully.

• CONDITION MATCH1: The green LED spot illuminates if the read code corresponds to the matchcode of CONDITION MATCH1.

• CONDITION MULTCODES1: The green LED spot illuminates if the number of read codes cor-responds to the required number from CONDITION MULTCODES1.

• CONDITION TEACHIN1: The green LED spot illuminates if the read code corresponds to the matchcode from CONDITION TEACHIN1.

• CONDITION TEACHIN2: The green LED spot illuminates if the read code corresponds to the matchcode from CONDITION TEACHIN2.

2.4.1.1.18Duration

The Duration parameter is used to define the timeframe for the optical notification (Green feedback spot).

2.4.1.1.19Image filter

Image filter


LECTOR®620



2.4.1.1.20Noise reduction

The Noise reduction parameter is used to activate/deactivate the smoothing of the image in order to clearly distinguish the code from the background.

Smoothing improves the reading properties particularly if the image is noisy as a result of a high gain (Brightness) or the code background is very restless.

2.4.1.1.21Dot size

You can use the Dot size parameter to optically enlarge the code elements in order to adapt the LECTOR®620 to hard-to-read codes (e.g. codes with gaps between the points of the L-pattern).

: difficult to read

: ideal to read

In the case of codes that were created e.g. with inkjet printers, dot peeners, or lasers, the code elements may not be connected in some cases. In this case, the readability of the co-des can be improved by enlarging the code elements.

The value should be increased step by step until the code can be read successfully.

2.4.1.1.22Increase Performance

The parameters in the Increase Performance group can be used to eliminate disruptive in-fluences and therefore increase the performance of the LECTOR®620.

By modifying the settings on the application, you can reduce the decoding time, increase reading reliability, or increase the readability of low-contrast codes.

2.4.1.1.23Image rotation 180°

If the Image rotation 180° parameter is activated, the image is recorded rotated around 180°.

As the image is processed from the top down, codes in the top part of the image are identi-fied earlier. By rotating the image around 180°, you can therefore reduce the evaluation time for codes that are not positioned centrally. This is particularly true for readings at a standstill.


LECTOR®620



2.4.1.1.24Image region of interest

You can use the Image region of interest parameter to concentrate the reading area on the required region.

A reduction in the reading area reduces the evaluation time and increases the frame rate. This enables you to achieve higher object speeds.

To change the size of the reading area, you drag and drop the red marking or enter the four percentage values.

2.4.1.1.25Object trigger control

Object trigger control

2.4.1.1.26Start/Stop of object trigger

Start/Stop of object trigger

2.4.1.1.27Trigger delay

The Trigger delay parameter is used to choose between configuration with units of length or configuration with units of time.

• TRACK CONTROLLED: The values of the Pause, Reading gate length, Start delay, and Stop de-lay parameters are entered in mm. In the event of a track-controlled delay, the reading gate is not opened until the object has continued to move a predefined distance after the trigger signal.

• TIME CONTROLLED: The values of the Pause, Reading gate length, Start delay, and Stop de-lay parameters are entered in ms. In the event of a time-controlled delay, the reading gate is not opened until a predefined time has elapsed after the trigger signal.

2.4.1.1.28Start delay

You can use the Start delay parameter to influence the time for opening the reading gate. The unit can be selected in the Trigger delay parameter.

A positive value causes the reading gate to be opened later, e.g. in order to only enter codes that are at the rear of an object to therefore reduce the decoding time.

By modifying the trigger, you can adjust the image recording more accurately to the code position.

• A. START DELAY (additional time/distance in which the reading gate remains closed after event A)


LECTOR®620



2.4.1.1.29Start by

The Start by parameter is used to select the signal source for opening the reading gate.

• A START BY (signal for opening reading gate)

If the reading gate is open, the LECTOR®620 records images with a frequency of 60 Hz and evaluates these by codes. Ideally, at least one code will have been completely recorded and identified on an image. If the reading gate is closed, no images are recorded.

Signal sources for opening the reading gate:

• SENSOR / RESULT 1: A signal at digital input 1 (e.g. via a light barrier) opens the reading gate.

• SENSOR / RESULT 2: A signal at digital input 2 (e.g. via a light barrier) opens the reading gate.

• EXTERNAL INPUT 1: A signal at external digital input 1 (e.g. via a light barrier) opens the rea-ding gate.

• EXTERNAL INPUT 2: A signal at external digital input 2 (e.g. via a light barrier) opens the rea-ding gate.

• SOPAS COMMAND: A command to open the reading gate is expected e.g. from an external controller (PLC). (A detailed list of the command language is available from SICK on re-quest.)

• AUTO CYCLE: The reading gate is opened and closed automatically after a defined cycle (using the Pulse and Pause parameters) (e.g. if the feed speed stays the same and the code position is constant or for manual code reading)

• CAN: The signal for opening and closing the reading gate is expected via the CAN inter-face. In a network of devices that communicate with each other via the CAN network, the signal for opening the reading gate can be distributed. For this, a suitable trigger signal is received by a device (usually the master) and distributed to the other CAN network.

• USER DEFINED COMMAND: You can freely define a command for opening the reading gate, which is e.g. generated by an external controller (PLC) and transmitted to the LECTOR®620.

• FREE RUNNING: The reading gate is permanently open. As a result, manual code reading is possible without an external trigger signal (e.g. from a light barrier). Signals for opening/clo-sing the reading gate are ignored. As it is therefore not possible to define a specific point in time for data output, a signal for NO READ cannot be output. The time of output and the rea-ding speed depend on the degree of utilization of the LECTOR®620.


LECTOR®620



2.4.1.1.30Stop delay

You can use the Stop delay parameter to influence the time for closing the reading gate. The unit can be selected in the Trigger delay parameter.

A positive value enables the reading gate to be closed later, e.g. to extend the evaluation period for codes at the rear of an object.

• B. STOP DELAY (additional time/distance for which the reading gate remains open after event B)

2.4.1.1.31Stop by

The Stop by parameter is used to select the signal source/condition for closing the reading gate.

• B STOP BY (signal for closing reading gate)

If the reading gate is open, the LECTOR®620 records images with a frequency of 60 Hz and evaluates these by codes. Ideally, at least one code will have been completely recorded and identified on an image. If the reading gate is closed, no images are recorded.

Signal sources for closing the reading gate:

• NOT DEFINED: No function for closing the reading gate defined

• TRIGGER SOURCE: The reading gate is closed by the same signal source that opened it. (For example, opening of reading gate as soon as an object breaks a light barrier and closing of reading gate as soon as the object is no longer in front of the light barrier.)

• SENSOR / RESULT 1: A signal at digital input 1 (e.g. via a light barrier) closes the reading gate.


• EXTERNAL INPUT 1: A signal at external digital input 1 (e.g. via a light barrier) closes the rea-ding gate.


• SOPAS COMMAND: A standard command to close the reading gate is expected e.g. from an external controller (PLC). (A detailed list of the command language is available from SICK on request.)


LECTOR®620



• TIMER/TRACKING: The reading gate remains open for a defined time/distance (Reading gate length). If the speed of the objects remains the same, and increment pulse is not re-quired (Increment source). If the speed changes, the signals of an incremental encoder, for example, can be used to calculate the current speed. As a result, the reading gate can be closed independently of the speed of the object as soon as the object has covered a certain distance.

• GOOD READ: The reading gate is closed as soon as the GOOD READ condition has been met (e.g. the required number of codes was read). As a result, the reading gate is only open for as long as required (direct notification of whether a code was identified).

• USER DEFINED COMMAND: You can freely define a command for closing the reading gate, which is e.g. generated by an external controller (PLC) and transmitted to the LECTOR®620.

• CONDITION MATCH 1: The reading gate is closed as soon as the condition is met.

• CONDITION MULTCODES1: The reading gate is closed as soon as the number of identified co-des matches the required number.

• CONDITION TEACHIN1: The reading gate is closed as soon as the Matchcode Teach-in 1 con-dition is met.

• CONDITION TEACHIN2: The reading gate is closed as soon as the Match-code Teach-in 2 (Ad-ditional) condition is met.

2.4.1.1.32Reading gate length

If the TIMER/TRACKING signal source is selected under the Stop by parameter, the Reading gate length parameter is used to enter the duration for which the reading gate stays open. The unit can be selected in the Trigger delay parameter.

2.4.1.1.33Or

You can use the Or parameter to choose a second signal source/condition for closing the reading gate.

For the reading gate to be closed, one of the signal sources/conditions must be met.








• TIMER/TRACKING: The reading gate remains open for a defined time/distance (Reading gate length).


LECTOR®620



• GOOD READ: The reading gate is closed as soon as the GOOD READ condition has been met (e.g. the required number of codes was read). As a result, the reading gate is only open for as long as necessary (direct notification).






2.4.1.1.34Or

You can use the Or parameter to choose a third signal source/condition for closing the rea-ding gate.

For the reading gate to be closed, one of the signal sources/conditions must be met.








• TIMER/TRACKING: The reading gate remains open for a defined time/distance (Reading gate length).

• GOOD READ: The reading gate is closed as soon as the GOOD READ condition has been met (e.g. the required number of codes was read). As a result, the reading gate is only open for as long as necessary (direct notification).





LECTOR®620





2.4.1.1.35Pulse

If the AUTO CYCLE signal source is selected under the Start by parameter, the Pulse parame-ter is used to enter the duration for which the reading gate stays open. The unit can be selec-ted in the Trigger delay parameter.

2.4.1.1.36Pause

If the AUTO CYCLE signal source is selected under the Start by parameter, the Pause parame-ter is used to enter the duration for which the reading gate is closed. The unit can be selec-ted in the Trigger delay parameter.

2.4.1.1.37Of

If the CAN signal source is selected under the Start by parameter, the Of parameter can be used to enter the CAN address of a device from the CAN network. This device receives a sui-table trigger signal and distributes it to the other devices in the CAN network.

2.4.1.1.38Trigger echo on

If the COMMAND signal source is selected under the Start by parameter, the command is sent from the LECTOR®620 as a response to the controller if the Trigger echo on parameter is activated.

As a result, the controller can check transmitted SOPAS commands.

2.4.1.1.39Reading gate on

Pressing the Reading gate on button manually opens the reading gate.

So that you can test the current settings, all outputs, output strings and image transmission function in accordance with the configuration. The reading gate is closed in accordance with the configuration.

This function is ideally suited to testing operating mode and simulating a machine trig-ger with a mouse click.

2.4.1.1.40Reading gate off

Pressing the Reading gate off button manually closes the reading gate.

This enables you to conclude the reading operation even if the configured condition for au-tomatically closing the reading gate does not occur.

This function is ideally suited to testing operating mode and simulating a machine trig-ger with a mouse click.


LECTOR®620



2.4.1.1.41Trigger distribution

Trigger distribution

2.4.1.1.42Distribute on

Distribute on

2.4.1.2 Increment configuration

Increment configuration

2.4.1.2.1Increment

The Increment group contains parameters for converting signals for distances and speeds.

The signals are either generated by the configuration software (SOPAS) or via the CAN inter-faces or are generated via an incremental encoder on the digital input. Incremental enco-ders refer to sensors for capturing positional changes (linear) or angle changes (rotating) that can capture the distance and direction or angle change and direction or rotation. They are also known as relative encoders.

2.4.1.2.2Increment source

The Increment source parameter is used to select the source for the increment signals:

• FIXED SPEED: You can use the Fixed speed parameter to enter a constant value for the feed speed of the conveyer belt.

• SENSOR 1: The increment signals are expected from an incremental encoder connected at digital input 1. You configure the digital input using the parameters of the Sensor / Result 1 group.

• SENSOR 2: The increment signals are expected from an incremental encoder connected at digital input 2. You configure the digital input using the parameters of the Sensor / Result 2 group.

• CAN: The incremental signals are expected via the CAN interface.

• SOPAS COMMAND: Commands are expected as increment signals. The commands can be generated e.g. by an external controller (PLC) and transmitted to the LECTOR®620 at defi-ned intervals.

2.4.1.2.3Fixed speed

The Fixed speed parameter is used to enter a constant value for the feed speed of the con-veyer belt in m/sec.

This speed is automatically converted to time/distance.


LECTOR®620



2.4.1.2.4System increment resolution

You use the System increment resolution parameter to define the conversion factor for the increment signal.

The value corresponds to the distance covered per increment in mm. For the concrete cal-culation of speeds and distances, the value must be adapted to the incremental encoder used.

2.4.1.3 Code config.

Code config.

2.4.1.3.11D Symbologies

The 1D Symbologies group contains all parameters for configuration of the 1D symbologies (barcodes).

2.4.1.3.2Codabar

If the Codabar parameter is activated, decoding is activated for the code type.

As only activated code types are processed, you can increase the processing speed by specifically activating/deactivating the required code types.

• Code name: Codabar (two-value)

• Character set: 16 alphanumeric characters (10 digits, 6 special characters)

• Structure: 7 code elements (4 bars, 3 gaps); start character (A, B, C or D), code contents, stop character (A, B, C or D)

• Intrinsic reliability: Low

• Space required: Variable

• Area of application: Packet and postal service

• Standard: EN 798 bar-coding


LECTOR®620



2.4.1.3.3Code 39

If the Code 39 parameter is activated, decoding is activated for the code type.


• Code name: Code 39 (two-value)

• Character set: 43 alphanumeric characters (10 digits, 26 letters, 7 special characters)

• Structure: 9 code elements (5 bars, 4 gaps), 3 of which wide and 6 narrow

• Intrinsic reliability: Medium

• Space required: High

• Standard: ISO/IEC 16388


2.4.1.3.4UPC/EAN

If the UPC/EAN parameter is activated, decoding is activated jointly for code types UPC A, UPC E, EAN 8 and EAN 13.


2.4.1.3.52/5 Interleaved

If the 2/5 Interleaved parameter is activated, decoding is activated for the code type.


• Code name: 2/5 Interleaved or ITF (2-value)

• Character set: Numeric characters

• Structure: 5 code elements per character, 2 of which wide and 3 narrow (characters at uneven positions are represented by bars. Characters at even positions are represented by gaps.)

• Intrinsic reliability: Low

• Space required: Low (with up to 18 characters)




LECTOR®620



2.4.1.3.6Code 93

If the Code 93 parameter is activated, decoding is activated for the code type.


• Code name: Code 93 (4-value)

• Character set: 43 alphanumeric characters (10 digits, 26 upper-case letters, 7 special characters: Blanks, -, ., $, /, + and %)

• Intrinsic reliability: Medium

• Space required: Low



2.4.1.3.7Code 128 Family

If the Code 128 Family parameter is activated, decoding is activated jointly for code types Code 128 and EAN 128. (Code type Pharmacode must be deactivated.)


2.4.1.3.8Pharmacode

If the Pharmacode parameter is activated, decoding is activated for the code type.

All other code types are deactivated.

• Code name: Pharmacode (binary)

• Character set: Numeric characters (integers between 3 and 131070)

• Structure: Wide bars: 1, narrow bars: 0 (main code and additional code can have different colors)

• Intrinsic reliability: High


• Standard: Barcode standard of the company Laetus

• Area of application: Packaging check in the pharmaceutical industry (agreement with re-ference code from a code list)


LECTOR®620



2.4.1.3.9Minimum module width

You use the Minimum module width parameter to specify in mm the smallest structure for decoding a code.

To optimize decoding, the value should be tailored as accurately as possible to the smallest code element (module width) that actually occurs in the code. To be able to reliably read codes with different module widths, the value for the absolutely smallest module width must be entered.

2.4.1.3.102D symbologies

The 2D symbologies group contains all parameters for configuration of the 2D codes (two-dimensional codes).

2.4.1.3.11Automatic code configuration

Pressing the AUTO (Automatic code configuration) button calls the Auto Setup wizard for the automatic configuration of code types.

To perform code configuration automatically, a suitable code must be placed in the reading area.

At the moment (up until 2011), the function only supports the Data Matrix symbology.

2.4.1.3.12Minimum cell size

You use the Minimum cell size parameter to specify in mm the smallest structure of cells for decoding a code.

To optimize decoding, the value should be tailored as accurately as possible to the smallest code element (cell size) that actually occurs in the code. The cell size should be between 60 % and 105 % of the ideal cell size.

To be able to reliably read codes with different cell sizes, the value for the absolutely smal-lest cell size must be entered


LECTOR®620



2.4.1.3.13Data Matrix

If the Data Matrix parameter is activated, decoding is activated for the code type.

As only activated code types are processed, you can increase the processing speed by spe-cifically activating/deactivating the required code types.

• Code name: Data Matrix

• Max. number of numeric characters: 3116

• Max. number of alphanumeric characters: 2335

• Max. number of ASCII characters: 1982

• Max. number of ISO characters: 1556

• Structure: Symbol with L-pattern, rectangular symbols also possible


• Area of application: Electronics, automotive, aviation, pharmaceutical and food pak-kaging

2.4.1.3.14Stacked codes

The Stacked codes group contains all the parameters for configuring the stacked codes (se-veral barcodes stacked in rows one above the other, with the same start and stop charac-ter).

2.4.1.3.15PDF417

If the PDF417 parameter is activated, decoding is activated for the code type.


• Code name: PDF417

• Character set: 2710 numeric, 1850 alphanumeric, 1400 ASCII or 1108 ISO characters

• Symbol size: 3 - 90

• Intrinsic reliability: Very high (error correction)

• Space required: Very low




LECTOR®620



2.4.1.3.16General code settings

Settings for all activated code types are made via the parameters of the General code set-tings group.

2.4.1.3.17Code Contrast

To find the codes in the reading area, the system searches the recorded image for structu-res with sufficiently large jumps in contrast. A code pattern is only expected in these struc-tures.

The Code Contrast parameter can be used to define a minimum value for these jumps in contrast in %. Areas in which the contrast is below the defined values are not searched for code patterns.

• A low value (e.g. 10 %) must be defined to ensure that codes with low contrast can still be read reliably. However, this increases the decoding time, as a larger image area has to be searched.

• For codes with higher contrast, the value can be increased accordingly. In each case, a smaller image area has to be searched, which leads to a reduction in the decoding time.

2.4.1.3.18Code background

You can use the Code background parameter to restrict decoding to codes with a light back-ground color or to codes with a dark background color; this can reduce the decoding time.

• WHITE: Only dark codes on a light background are read.

• BLACK: Only light codes on a dark background (inverted codes) are read.

• BOTH: Both dark codes on a light background and light codes on a dark background (in-verted codes) are read.

2.4.1.3.19Code appearance

The Code appearance parameter is used to restrict the decoding to mirrored or non-mirro-red codes, which can reduce the decoding time.

• NORMAL: Only non-mirrored codes can be decoded correctly.

• MIRRORED: Only mirrored codes, which are recorded from the bottom through a glass pane, can be decoded correctly. For this, the recorded images are mirrored again before decoding.

• BOTH: Both mirrored and non-mirrored codes are read.

2.4.1.3.20Codabar

Codabar

2.4.1.3.21General

General (CBAR)


LECTOR®620



2.4.1.3.22Multiread

You use the Multiread parameter to define a minimum number of GOOD READ required for a reading to be output as a GOOD READ.

By defining a minimum number of readings, you reduce the likelihood of misinterpretations for codes with poor printing quality or a low contrast, and increase reading reliability.

2.4.1.3.23Start/Stop identical

If the Start/Stop identical parameter is activated, only codes whose start character is the same as the stop character are read.

A code of code type Codabar can have one of the four characters (A, B, C or D) as the start/stop character. If only identical start and stop characters are permitted, the reading reliabi-lity is increased, and misinterpretations are avoided.

2.4.1.3.24Transmit start/stop

If the Transmit start/stop parameter is activated, the start and stop characters are trans-mitted together with the code contents.

As a result, the characters are available for evaluation of the reading results.

2.4.1.3.25Check digit test

This Check digit test parameter is used to define the calculation method for the plausibility check on the code contents. A check digit is calculated from the code contents and compa-red with the check digit in the code. The selected method must match the method used du-ring creation of the code. If the calculated check digit matches the check digit in the code, the reading is regarded as a GOOD READ).

Check digits prevent misinterpretations and increase reading reliability.

2.4.1.3.26Not calibratable

Not calibratable (CBAR)


LECTOR®620



2.4.1.3.27Code length

You can use the Code length parameter to restrict the permitted number of characters in a code.

• FREE: Codes of any code length are read.

• INTERVAL: The Interval parameter can be used to define the minimum and maximum code length. Only codes with a code length between these two values are read.

• FIXED: The Fixed length parameter is used to define several fixed code lengths. Only codes with one of these defined code lengths are read.

2.4.1.3.28Interval

The Interval parameter can be used to define the minimum and maximum code length. Only codes with a code length between these two values are read.

By defining a minimum and maximum code length, you restrict the range of codes to be read. This can lead to a reduction in the decoding time.

2.4.1.3.29Fixed length

The Fixed length parameter is used to define several fixed code lengths. Only codes with one of these defined code lengths are read.

By defining certain permitted code lengths, you restrict the range of codes to be read. This can lead to a reduction in the decoding time.

2.4.1.3.30Code 39

Code 39

2.4.1.3.31General

General (C39)

2.4.1.3.32Multiread




LECTOR®620



2.4.1.3.33Transmit start/stop

If the Transmit start/stop parameter is activated, the start and stop characters are trans-mitted together with the code contents.

As a result, the characters are available for evaluation of the reading results.

2.4.1.3.34Full ASCII

The Full ASCII parameter must be activated if the code contains both digits and other cha-racters.



Check digits prevent misinterpretations and increase reading reliability.

2.4.1.3.36C32 conversion

If the C32 conversion parameter is activated, decoding is activated for the code type.


• Code name: C32 conversion (two-value)

• Character set: 32 alphanumeric characters (upper case letters A - Z, digits 0 - 9, no special characters)

• Structure: Leading light zone, start character, message characters, check digit, stop cha-racter, closing light zone (13 - 16 modules per character)


• Space required: Variable symbol length

• Standard: ISO/IEC 16388, ANSI/AIM BC5 1995

• Area of application: Article number for pharmaceutical products (Italian pharmaceutical code), drug packaging for human medicine


Not calibratable (C39)


LECTOR®620








2.4.1.3.39Interval






2.4.1.3.41UPC/EAN

UPC/EAN

2.4.1.3.42General

General (UPC_EAN)

2.4.1.3.43Multiread




LECTOR®620



2.4.1.3.44Add-on

The Add-on parameter is used to configure how the extended code structure is used (addi-tional information usually on magazines).

• NONE: No extended code structure for the code

• ACTIVE: Extended code structure for the code

• REQUIRED: Only codes with an extended code structure are read.

Add-on length The Add-on length parameter is used to define the length of the extended code structure.

• 2 DIGITS: A 1

• 5 DIGITS: A 1 B 2 C

• 2 OR 5 DIGITS: A 1 or A 1 B 2 C

2.4.1.3.45UPC

UPC

2.4.1.3.46UPC A

If the UPC A parameter is activated, decoding is activated for the code type.


• Code name: UPC A (Universal Product Code) (4-value)

• Character set: 12 numeric characters (check digit: last character)

• Structure: 2 characters for country prefix, 9 characters for manufacturer and article, 1 character as check digit



• Standard: DIN/EN 797

• Area of application: Food and consumer goods in the USA and Canada


LECTOR®620



2.4.1.3.47UPC E

If the UPC E parameter is activated, decoding is activated for the code type.


• Code name: UPC E (Universal Product Code) (4-value)

• Character set: 8 numeric characters

• Structure: System ID (always 0), 2 characters for country prefix, 4 characters for manuf-acturer and article, 1 character as check digit




• Area of application: Food and consumer goods in the USA and Canada

2.4.1.3.48UPC E extended

If the UPC E extended parameter is activated, 8-character codes of code type UPC E are au-tomatically converted to 12-character codes. (Code type Pharmacode must be deactivated.)

2.4.1.3.49EAN

EAN

2.4.1.3.50EAN 8

If the EAN 8 parameter is activated, decoding is activated for the code type.


• Code name: EAN 8 (European Article Numbering) (4-value)

• Character set: 8 numeric characters (check digit: last two characters)

• Structure: 2 characters for the country prefix (in accordance with CCG, in Germany GS1 Germany), 4 characters for the manufacturer and article (in accordance with CCG), 2 cha-racters as check digit




• Area of application: Food and consumer goods in Europe


LECTOR®620



2.4.1.3.51EAN 13

If the EAN 13 parameter is activated, decoding is activated for the code type.


• Code name: EAN 13 (European Article Numbering) (4-value)

• Character set: 13 numeric characters (check digit: last two characters)

• Structure: 2 characters for the country prefix (in accordance with CCG, in Germany GS1 Germany), 8 characters for the manufacturer and article (in accordance with CCG), 2 cha-racters as check digit




• Area of application: Food and consumer goods in Europe

2.4.1.3.522/5 interleaved

2/5 interleaved

2.4.1.3.53General

General (25IL)

2.4.1.3.54Multiread





Check digits prevent misinterpretations and increase reading reliability. The use of a check digit is recommended for this code type.


LECTOR®620



2.4.1.3.56Check-Digit-Test #2

Check-Digit-Test #2


Check-Digit-Test #3


Check-Digit-Test #4


Check-Digit-Test #5

2.4.1.3.60Classification restriction

Classification restriction


Not calibratable (25IL)






2.4.1.3.63Interval






2.4.1.3.65Code 93

Code 93


LECTOR®620



2.4.1.3.66General

General (C93)

2.4.1.3.67Multiread










2.4.1.3.70Interval






2.4.1.3.72Code 128 Family

Code 128 Family

2.4.1.3.73General

General (C128)


LECTOR®620



2.4.1.3.74Code 128

If the Code 128 parameter is activated, decoding is activated for the code type. (Code type Pharmacode must be deactivated.)


• Code name: Code 128 (4-value)

• Character set: Alphanumeric (ASCII) with three switchable character sets and a check di-git

Character set A: Digits, upper case letters, special characters, and ASCII control characters

Character set B: Digits, upper and lower case letters, special characters, and escape cha-racters

Character set C: 100 digit pairs (00 - 99) and FNC1 special characters

• Structure: Start symbol, usage information, check digit, stop symbol (11 modules per sym-bol; 3 bars and 3 gaps each)

• Intrinsic reliability: Very high (self-verifying: number of bars even, number of gaps uneven)

• Space required: Maximum possible number of characters per centimeter


• Area of application: All areas, as UCC 128 / EAN 128 in retail

2.4.1.3.75EAN 128

If the EAN 128 parameter is activated, decoding is activated for the code type. (Code type Pharmacode must be deactivated.)


• Code name: EAN 128 (4-value)

• Character set: Alphanumeric (ASCII) with three switchable character sets

Character set A: Digits, upper case letters, and special characters

Character set B: Digits, upper and lower case letters

Character set C: Digits with double density

• Structure: FNC1, characters, check digit




• Area of application: Marking of commodities


LECTOR®620



2.4.1.3.76Multiread










2.4.1.3.79Interval






2.4.1.3.81EAN 128

EAN 128

2.4.1.3.82FC1-Value within code

With the parameter FC1-Value within code an alternative character for the FC1-character (control character at the beginning of the code) can be defined for the EAN 128 code.

Up to three characters can be defined. Enter data as a decimal character.


LECTOR®620



2.4.1.3.83FC1-Value on first position

With the parameter FC1-Value on first position an alternative character for the FC1-charac-ter (control character at the beginning of the code) can be defined for the EAN 128 code.

Up to three characters can be defined. Enter data as a decimal character.

2.4.1.3.84Pharmacode

Pharmacode

2.4.1.3.85General

General (PHARMA)

2.4.1.3.86Multiread



2.4.1.3.87Module width

You can use the Module width parameter to choose between the automatic and user-defi-ned module width.

User-defined modulewidth

You use the User-defined module width parameter to specify in mm the smallest structure for decoding a code.

Missing start and stop characters for codes of code type Pharmacode mean that incorrect readings could occur for structures with a similar code. To increase reading reliability, the value should be tailored as accurately as possible to the smallest code element (module width) that actually occurs in the code.

2.4.1.3.88Reverse

If the Reverse parameter is activated, the code is read in reverse direction.

As the codes of code type Pharmacode do not have a start or stop character and do not have a check digit at the end, the code contents differ depending on the reading direction. The reading direction must therefore be defined in the configuration.


Not calibratable (PHARMA)


The Fixed length parameter can be used to define a required code length. Only codes with this length are read.


LECTOR®620



2.4.1.3.91Data matrix

Data matrix

2.4.1.3.92General

General (DM)

2.4.1.3.93Code format

You can use the Code format parameter to select the format (Data Matrix Code symbology) for data output:

• ECC200: The data is output with the standard data formatting.

• GS1: The data is output with the special GS 1 data formatting. User-specific characters can be defined for the FNC1 character (control character at the start of the code) and for the separator (control character within the code). As a result, after every APPLICATION IDENTI-FIER for example, a line break (CR, LF) can be inserted in the data string.

2.4.1.3.94Max. allowed error correction

Max. allowed error correction

2.4.1.3.95Activate ISO15415 verification

If the Activate ISO15415 verification parameter is activated, the codes are verified for com-pliance with the ISO/IEC 15415 standard. For this, the code contents are used to calculate values that can be output in the data strings via configuration of the output formats.

As the calculation of the values increases the decoding time, the function should only be activated if required.


Not calibratable (DM)

2.4.1.3.97Symbol size

You can use the Symbol size parameter to restrict the permitted number of lines and co-lumns of the codes.

The code dimensions are calculated from the symbol size and module size. For this, the symbol size is multiplied by the module size.


LECTOR®620



To reduce the decoding time, it may make sense to set the actual symbol size of the code and thus exactly specify the expected code size.

• FREE: All AIM/ISO/IEC-specified Data Matrix ECC200 sizes are decoded.

• FIXED: The Fixed length 1, Fixed length 2 and Fixed length 3 parameters can be used to select fixed symbol sizes. Only codes with one of these defined symbol sizes are read.

2.4.1.3.98Fixed length 1

The Fixed length 1 parameter can be used to select a fixed symbol size. Only codes with this symbol size are read.

By defining certain permitted symbol sizes, you restrict the range of codes to be read. This can lead to a reduction in the decoding time.








Fixed length 4


Fixed length 5

2.4.1.3.103Allow rectangular data fields

If the Symbol size parameter has value FREE , square (e.g. 16 x 16) and rectangular (e.g. 8 x 18) symbols are identified if the Allow rectangular data fields parameter is activated.

2.4.1.3.104Increase Performance

The parameters of the Increase Performance group can be used to ensure the readability of the codes at high object speeds and/or reduce the evaluation type.


LECTOR®620



2.4.1.3.105Errors in L-pattern

According to the ISO/IEC 16022 standard, the code structure (L-pattern) must be marked without gaps and must extend across the complete code height and width. If the Errors in L-pattern parameter is active, however, codes with an incorrect code structure are also read.

During decoding, any gaps in the code structure are ignored. For the code to still be read, there must be a quiet zone of at least 5 times the cell size around the code. This may increa-se the decoding time.

2.4.1.3.106Code surrounded by patterns

If the Code surrounded by patterns parameter is activated, patterns/lines (e.g. strip conduc-tors on printed circuit board) in the code environment are ignored during evaluation.

As a result, the reading concentrates on the code elements and the decoding time is redu-ced.

Codes with poor quality are generally ignored if the function is activated.

2.4.1.3.107Code surrounded by text

If the Code surrounded by text parameter is activated, text (e.g. on packaging) in the code environment are ignored during evaluation.

As a result, the reading concentrates on the code elements and the decoding time is redu-ced.

Codes with poor quality are generally ignored if the function is activated.


LECTOR®620



2.4.1.3.108Decoding

The parameter Decoding defines if the reading is optimized on time or on aggressive deco-ding.

• FAST: Fast decoding is recommanded when the code quality is good and the decoding time must be very short.

• AGGRESSIVE: Aggressive is usefull when decoding time is not that relevant, e.g. stationary applications, but the code is of poor quality, e.g. low contrast, errors in the codes.

• BALANCED: Balanced meets the needs of applications in between.

2.4.1.3.109PDF 417

PDF 417

2.4.1.3.110General

General (PDF)

2.4.1.4 Data processing

Data processing

2.4.1.4.1Collection of data

Collection of data

2.4.1.4.2Timeout

Timeout

2.4.1.4.3Code summarization

Code summarization

2.4.1.4.4Separate codes depending on position

If the Separate codes depending on position parameter is activated, the system differenti-ates between codes of the same code type and with identical code contents depending on their position on the object.

The identical codes on the object must have a definable minimum distance (Code distance).


LECTOR®620



2.4.1.4.5Code distance

The Code distance parameter is used to define the minimum distance for differentiating between identical codes.

The system only differentiates between codes with the same symbology and identical code contents if their distance on the object is at least the defined Code distance.

2.4.1.4.6Separate codes dependent on sensor

Separate codes dependent on sensor

2.4.1.4.7Output control

Output control

2.4.1.4.8Output control

The Output control group contains the parameters used to define the timeline for data out-put for Output format 1 and Output format 2.

2.4.1.4.9Control

Control

2.4.1.4.10Data transmission point

You can use the Data transmission point parameter to define when the reading results are to be output.

• END OF TRIGGER: The reading results of all codes are output as soon as the reading gate is closed. As a result, the data is output at a definable point in time.

• AS SOON AS POSSIBLE: The reading results of a code are output immediately after code iden-tification (even if the reading gate is still open). As a result, data can immediately be pro-cessed further.

• NEW LABEL: The reading results of a code are output directly after identification of a code. However, before the same code can be output again, another code must be identified. As a result (e.g. during manual reading), you can avoid a code being identified multiple times and the data output again.

• END OF LABEL: The reading results of a code are output as soon as the code leaves the rea-ding area of the LECTOR®620.


LECTOR®620



2.4.1.4.11Output condition

If the AS SOON AS POSSIBLE value is selected for the Data transmission point parameter, you can use the Output condition parameter to select the condition for data output.

• GOOD READ: The reading results are output if the reading was successful.

• CONDITION MATCH1: The reading results are output if the read code corresponds to the matchcode from CONDITION MATCH1.

• CONDITION MULTCODES1: The reading results are output if the number of read codes corre-sponds to the required number from CONDITION MULTCODES1.

• CONDITION TEACHIN1: The reading results are output if the read code corresponds to the matchcode from CONDITION TEACHIN1.

• CONDITION TEACHIN2: The reading results are output if the read code corresponds to the matchcode from CONDITION TEACHIN2.

2.4.1.4.12Data output mode

The Data output mode parameter is used to define the frequency of data output.

• SINGLE: The reading results are output once.

• MULTIPLE: The reading results are initially output once. After a certain period of time (Label timeout or Condition timeout), the data is output again. With a suitable setting, you can dif-ferentiate between different objects with identical codes.

Label timeout If the AS SOON AS POSSIBLE value is selected for the Data transmission point parameter, you can use the Label timeout parameter to define the duration up to renewed output of the da-ta. During this period, the data is output again as long as the code is in the reading area.

The unit can be selected in the Output delay parameter.

Condition timeout If the AS SOON AS POSSIBLE value is selected for the Data transmission point parameter, you can use the Condition timeout parameter to define the duration up to renewed output of the data. During this period, the data is output again as long as the condition for data output (Output condition) is met.


2.4.1.4.13Label timeout

Label timeout

2.4.1.4.14Condition timeout

Condition timeout


LECTOR®620



2.4.1.4.15Delay

If the END OF TRIGGER value is selected for the Data transmission point parameter, the Delay parameter can be used to hold back the data for a certain period after the reading gate has been closed. You can therefore change the timeline on the controller (PLC).


2.4.1.4.16Output delay

The Output delay parameter is used to choose between configuration with units of length or configuration with units of time for the Delay, Label timeout, Condition timeout, and Timeout parameters

• TRACK CONTROLLED: The entries for the parameters are made in mm.

• TIME CONTROLLED: The entries for the parameters are made in ms.

2.4.1.4.17Certain numb. of new labels

If the NEW LABEL value is selected for the Data transmission point parameter, the Certain numb. of new labels parameter can be used to define the minimum number of codes (la-bels) that have to be read before a code is output again. This can be used to ensure that the same object is not read multiple times.

2.4.1.4.18Label timeout active

If the Label timeout active parameter is activated, you can define the time period after which an identical code (label) may be output again.

2.4.1.4.19Timeout

If the END OF LABEL value is selected for the Data transmission point parameter, you can use the Timeout parameter to define the period after which a code is output again.


2.4.1.4.20Evaluation conditions

Evaluation conditions


LECTOR®620



2.4.1.4.21Conditions for Good Read

The Conditions for Good Read selection list is used to define the condition for which a rea-ding is classed as a GOOD READ.

• USE MIN./MAX. NUMBER OF CODES: Depending on the configuration of parameters Check min. number of valid codes and Check max. number of valid codes a reading is classed as a GOOD READif the number of read codes lies between the specified minimum value and the speci-fied maximum value.

• CONDITION MATCH1: Reading is rated as a GOOD READ if the read code corresponds to MATCHCODE MATCH 1.

• CONDITION MULTCODES1: Reading is rated as a GOOD READ if the number of read codes cor-responds to the required number.

• CONDITION TEACHIN1: Reading is rated as a GOOD READ if the read code corresponds to MATCHCODE TEACH-IN 1.

• CONDITION TEACHIN2: Reading is rated as a GOOD READ if the read code corresponds to MATCHCODE TEACH-IN 2.

2.4.1.4.22Check min. number of valid codes

If the Check min. number of valid codes parameter is activated, the number of different co-des is determined and compared with a specified minimum value (Minimum).

This enables you to check, for example, whether all required codes for an object are avai-lable.

Minimum The Minimum parameter is used to define the minimum number of different codes that must be identified so that a reading is classed as a GOOD READ. If the specified value is not reached, the reading is classed as invalid (NO READ).

All codes that differ from the other codes in terms of the symbology, code length, code con-tents, or code positions are counted.

2.4.1.4.23Check max. number of valid codes

If the Check max. number of valid codes parameter is activated, the number of different co-des is determined and compared with a specified maximum value (Maximum).

This enables you to ensure, for example, that only the required codes for an object are avai-lable.

Maximum The Maximum parameter is used to define the maximum number of different codes that can be identified so that a reading is classed as a GOOD READ. If the specified value is exceeded, the reading is classed as invalid (NO READ).

All codes that differ from the other codes in terms of the symbology, code length, code con-tents, or code positions are counted.


LECTOR®620



2.4.1.4.24Evaluation conditions

Evaluation conditions

2.4.1.4.25Match-code

Match-code

2.4.1.4.26Matchcode Teach-in 1

The Matchcode Teach-in 1 group contains the parameters for teaching in matchcode 1.

To activate a taught-in matchcode, the corresponding condition is selected e.g. for the Conditions for Good Read parameter.

2.4.1.4.27Activate teach-in mode

Depending on the setting for the Start teach-in parameter, the Activate teach-in mode pa-rameter is used to define which signal prepares or starts teach-in of the matchcode.

The signal can come e.g. from a key switch at one of the digital inputs or can be triggered by a command.

• NOT DEFINED: No matchcode teach-in.

• SENSOR 1: Matchcode teach-in is prepared or started by a signal at digital input 1 (e.g. a key switch).

• SENSOR 2: Matchcode teach-in is prepared or started by a signal at digital input 2.

• EXT. INPUT 1 (see note): Matchcode teach-in is prepared or started by a signal at digital ex-ternal input 1.


• SOPAS COMMAND: Matchcode teach-in is prepared or started by a command.

The connection module CDB620 or CDM420 in conjunction with the parameter memory module CMC600 can be used to extend the number of available digital inputs. The parame-ter memory module CMC is used for input extension and converts a digital signal into a com-mand. External digital input react more slowly than the internal digital inputs of the LECTOR®620.

2.4.1.4.28Or teach-in via function buttons

If the Or teach-in via function buttons parameter is activated, the matchcode can also be taught in via the buttons on the LECTOR®620. No signal is required in order to prepare teach-in (Activate teach-in mode).


LECTOR®620



2.4.1.4.29Teach-in stop by

Depending on the setting for the Start teach-in parameter, the Teach-in stop by parameter is used to define which signal or condition stops teach-in of the matchcode.

• TEACH-IN TRIGGER SOURCE: Teach-in is stopped by a signal (e.g. a key switch) at one of the digital inputs of the LECTOR®620.

• OBJECT TRIGGER: Teach-in stops as soon as the reading gate is closed.

• TAUGHT VALID CODE: Teach-in stops as soon as a matchcode was read successfully.

2.4.1.4.30Teach-in condition

Teach-in condition

2.4.1.4.31Invert condition

Invert condition

2.4.1.4.32Teach-in code content

If the Teach-in code content parameter is activated, the code content of the matchcode is taught in and included as a condition.

This reduces the likelihood of the code being confused with other codes.

2.4.1.4.33Teach-in code ID (type)

If the Teach-in code ID (type) parameter is activated, the code type of the matchcode is taught in.


2.4.1.4.34Teach-in code length

If the Teach-in code length parameter is activated, the code length of the matchcode is taught in.


2.4.1.4.35Match-code Teach-in 2 (Additional)

The Match-code Teach-in 2 (Additional) group contains the parameters for teaching in matchcode 2.

To activate a taught-in matchcode, the corresponding condition is selected e.g. for the Conditions for Good Read parameter.


LECTOR®620



2.4.1.4.36Activate teach-in mode

Depending on the setting for the Start teach-in parameter, the Activate teach-in mode pa-rameter is used to define which signal prepares or starts teach-in of the matchcode.

The signal can come e.g. from a key switch at one of the digital inputs or can be triggered by a command.

• NOT DEFINED: No matchcode teach-in.

• SENSOR 1: Matchcode teach-in is prepared or started by a signal at digital input 1 (e.g. a key switch).

• SENSOR 2: Matchcode teach-in is prepared or started by a signal at digital input 2.



• SOPAS COMMAND: Matchcode teach-in is prepared or started by a command.


2.4.1.4.37Teach-in stop by

Depending on the setting for the Start teach-in parameter, the Teach-in stop by parameter is used to define which signal or condition stops teach-in of the matchcode.

• TEACH-IN TRIGGER SOURCE: Teach-in is stopped by a signal (e.g. a key switch) at one of the digital inputs of the LECTOR®620.

• OBJECT TRIGGER: Teach-in stops as soon as the reading gate is closed.

• TAUGHT VALID CODE: Teach-in stops as soon as a matchcode was read successfully.

2.4.1.4.38Teach-in condition

Teach-in condition

2.4.1.4.39Invert condition

Invert condition

2.4.1.4.40Teach-in code content

If the Teach-in code content parameter is activated, the code content of the matchcode is taught in and included as a condition.



LECTOR®620



2.4.1.4.41Teach-in code ID (type)

If the Teach-in code ID (type) parameter is activated, the code type of the matchcode is taught in.


2.4.1.4.42Teach-in code length

If the Teach-in code length parameter is activated, the code length of the matchcode is taught in.


2.4.1.4.43General Match code teach-in - settings

The General Match code teach-in - settings group contains the parameters for teaching in matchcodes.

The two matchcodes are stored in the Matchcode Teach-in 1 and Match-code Teach-in 2 (Additional) group respectively and can be subsequently modified individually.

2.4.1.4.44Start teach-in

The Start teach-in parameter is used to select the signal that triggers automatic teach-in of a matchcode.

• AUTOMATIC/STATIC: The reading gate is automatically opened by a signal (e.g. a key switch). The next read code is taught in as a matchcode.

• MACHINE TRIGGER / DYNAMIC: Matchcode teach-in is prepared by a signal (e.g. a key switch) at one of the digital inputs of the LECTOR®620. After the reading gate has been opened (usually by a light barrier), the next read code is taught in as a matchcode.

2.4.1.4.45Allowed code types

You use the Allowed code types parameter to define which code types are to be taught in as the matchcode.

As every code of a different code type could also be interpreted as a pharmacode, the Phar-macode code type must be selected exclusively.

• ACTIVATED CODE TYPES: In accordance with the code configuration, all activated code types are accepted for matchcode teach-in. To ensure that the desired code type can be read, the code configuration must first be checked.

• ALL TYPES (EXCEPT PHARMACODE): All code types except Pharmacode are accepted for match-code teach-in.

• ONLY PHARMACODE: Only codes of code type Pharmacode are accepted for matchcode teach-in.


LECTOR®620



2.4.1.4.46Code configuration

You use the Code configuration parameter to define whether and how the teaching in of a matchcode should affect the current code configuration.

• DON'T CHANGE: The current code configuration is not changed by a matchcode teach-in. All configured code types can continue to be read.

• LIMIT TO LAST TAUGHT CODE: The code configuration is adapted to the taught-in matchcode. The parameters for code type, code length, and code content are limited to the properties of the matchcode. As a result, only codes that match the matchcode can be read.

• EXPAND BY LAST TAUGHT CODE: The code configuration is adapted to the taught-in matchcode by also activating the parameters for the taught matchcode. As all other code settings re-main unchanged, all configured code types can continue to be read.

2.4.1.4.47Save permanent

If the Save permanent parameter is activated, the taught-in match code are kept even after the LECTOR®620 is switched off.

As the information is stored in the device's internal memory, on the Micro-SD memory card and/or parameter memory module CMC600, the save operation may be delayed.

2.4.1.4.48Filter/Sorter for output

Filter/Sorter for output

2.4.1.4.49Filters/Sorters for Output Format1

You can use the graphical interface of the Filters/Sorters for Output Format1 group to re-strict (filter) data for output of the reading results and define the sequence in which the data is output (sort). By combining filters and sorters, you can therefore individually influence data output.

Any number of filters and sorters can be graphically arranged for this between the device and PC. The filters can also be arranged in parallel.

You can add further filters and sorters by pulling down the corresponding symbols. If you move the symbols while holding down the Ctrl key, you can copy filters or sorters. You can delete the symbols by moving them to the trash. Selected symbols can also be removed by pressing the DEL. key.

During filtering, you can use the button to define the variable and condition for filtering.

Example: (CL) CODE LENGTH = 10: Only codes with a code length of exactly 10 characters are output.

During sorting, you use the button to select the variable used to sort the reading results. You can also choose between sorting in ascending and descending order.


LECTOR®620



Example: (CL) CODE LENGTH - ASCENDING: The codes with the shortest code length are output first.

For more information, see the F1 help.

Items Description

BC - Code content Code content of read code

CL - Code length Code length of read code

X - X pos. absolute Code distance to trigger position X in mm

Y - Y pos. absolute Code distance to trigger position Y in mm

Z - Z pos. absolute Code distance to trigger position Z in mm

CS - Code security Indicates how 1D codes was read

VAL - Code valid (1 or 0) Output whether read code is valid/ whether the set condition is fulfilled (e.g. whether number of multireads was fulfilled)

ID - Code type Code type of read code

ON - Internal object number Number of actual object (summed up number of scanned objectes)

CC - Code count Number of read codes within reading gate

VCC - Number of valid codes Number of valid codes within reading gate

More code-realted items… Description

IWA - Code ID Code type according to allignment number (ASCII position of code ID which is a alphabetical number of the respective code type)

IN - Increment Increment value at start of reading gate

FC - Focus position Reading distance which is set in mm

RSD1DV - Ratio scans/decoded scans value Ratio between "S1D - Scans auf 1D Codes" to "S1D1 - Decoded scans on 1D codes". Grading to verify the reading stability on 1D codes

VTH - Threshold of CS for code to become valid Valid if CS>=VTH which means that number of scans = VTH*2 (for 1D codes only)

S1D - Scans on 1D codes Number of scans on 1D codes

SD1D - Decoded scans on 1D codes Number of decoded scans on 1D codes

FCT - Code type full description Code type, elaborated description

DI - Dimension Indicates wheter it is a 1D code or a 2D code

X1 - Code corner 1 X Pixel position of code corner 1X

Y1 - Code corner 1 Y Pixel position of code corner 1Y







CPX - X position relative to image origin Code center X in pixels

CPY - Y position relative to image origin Code center Y in pixels

AN2 - Tilt angle Tilt angle for 1D codes and 2D codes relative to the horizontal (angular degree)


LECTOR®620



MCR - Ratio between image and multicount [in %]

Ratio between images and successful multi-reads

X2D - X 2D Symbol size (number of modules) in X direction; for 2D codes only

Y2D - Y 2D Symbol size (number of modules) in Y direction; for 2D codes only

MX2 - Modul X size Average modul size in X direction in mm; for 2D codes only

MY2 - Modul Y size Average modul size in Y direction in mm; for 2D codes only

IV2 - Inverse (boolean) Code was read inverted

MD2 - Mirrored (boolean) Code was read mirrored

CTG - ISO16022/ISO15415 Symbol contrast grade

Grading for symbol contrast according to ISO/IEC16022 and ISO/IEC15415. Checks the con-trast between brigth and dark dots in the code.

CTG - ISO16022/ISO15415 Symbol contrast value

Value for symbol contrast according to ISO/IEC16022 and ISO/IEC15415. Checks the con-trast between brigth and dark dots in the code.

More… Description

PGV - ISO16022/ISO15415 Print growth value Grading for print growth according to ISO/IEC16022 and ISO/IEC15415. Checks the diffe-rence between the ideal and the actual dot size.

PGG - ISO16022/ISO15415 Print growth grade Value for print growth according to ISO/IEC16022 and ISO/IEC15415. Checks the diffe-rence between the ideal and the actual dot size.

ANUV - ISO16022/ISO15415 Axial non-unifor-mity value

Value for axial non-uniformity according to ISO/IEC16022 and ISO/IEC15415. Checks the ration between length and width of the code. If the code is streched or compressed in length or width, it is given a poor rating for its axial non-linearity.

ANUG - ISO16022/ISO15415 Axial non-unifor-mity grade

Grading for axial non-uniformity according to ISO/IEC16022 and ISO/IEC15415. Checks the ration between length and width of the code. If the code is streched or compressed in length or width, it is given a poor rating for its axial non-linearity.

UECV - ISO16022/ISO15415 Unused error cor-rection value

Value for unused error correction according to ISO/IEC16022 and ISO/IEC15415. Checks how much redundant data had to be used during rea-ding to decode the data content. The best grade is achieved if redundancy was not required at all.

UECG - ISO16022/ISO15415 Unused error cor-rection grade

Grading for unused error correction according to ISO/IEC16022 and ISO/IEC15415. Checks how much redundant data had to be used during rea-ding to decode the data content. The best grade is achieved if redundancy was not required at all.

OSG - Overall symbol grade Overall symbol grade according to ISO/IEC16022 and ISO/IEC15415. This grading can be considered as a summary of the criteria. The poorest af all the criteria used is always output.



LECTOR®620



GNUV - ISO15415 Grid non-uniformity value Grading for grid non-uniformity according to ISO/IEC15415. A grid is placed over the code using the alternating pattern to locate the scan points for decoding. Grid non-uniformity checks the extent to which the grid deviates from the ideal grid.

GNUG - ISO15415 Grid non-uniformity grade Value for grid non-uniformity according to ISO/IEC15415. A grid is placed over the code using the alternating pattern to locate the scan points for decoding. Grid non-uniformity checks the extent to which the grid deviates from the ideal grid.

MODV - ISO15415 Modulation value Value for modulation according to ISO/IEC15415. Checks uniformity of the reflectance of dark and light dots.

MODG - ISO15415 Modulation grade Grading for modulation according to ISO/IEC15415. Checks uniformity of the reflectance of dark and light dots.

FPDV - ISO15415 Fixed pattern damage value Value for fixed pattern damage according to ISO/IEC15415. Checks the fundamental characteri-stics of the code (quiet zone, finder, alternating patterns and reference dots) for defects and cal-culates an average.

FPDG - ISO15415 Fixed pattern damage grade Grading for fixed pattern damage according to ISO/IEC15415. Checks the fundamental charac-teristics of the code (quiet zone, finder, alterna-ting patterns and reference dots) for defects and calculates an average.

EC - ECC level Specific DMX quality value

ECCW - ECC code words Number of read code modules for Reed-Solo-mon-Error correction

DCW - Data code words Number of code data modules

NEC - Num. ECC correctables Number of correctable code modules in case of damage

NEE - Num. of ECC errors Number of incorrect code modules

NES - Num. of ECC erasures Number of incorrect code modules with known position

MC - Multi Count. Indicates how often a code was read within a reading gate (Codes are not displayed separa-tely!)

DLSZ - Number of devices Number of connected devices

DLCS - Device list separated by comma List of connected devices separated by comma

DLBS - Device list separated by blank List of connected devices separated by blank

DN - Device number Device number alternatively parameteruzed in field bus; default: number is identical to "Device ID"

DIN - Increment read from device Increment read by device

SID - Symbol ID Symbol ID

More obj. related items… Description

FIX1 - Fix defined string 1 User defined string 1


More… Description


LECTOR®620




TT - Reading gate duration in ms Reading gate duration in ms

OTL - Trigger length in mm Trigger length in mm

NZ - Nr. of mismatches Number of mismatches (codes which do not fulfil the matchcode condition)

NY - Nr. of no matches Number of objects without any match

GNC - Global nr. of codes Number of codes

NVRB - Global nr. valid released codes Number of valid released codes

NC - Number of reading gates Number of reading gates

DID - Device ID Device ID

SCGR - Superordinate counter Good Read Superordinate Good Read counter; remains in case of a new parameterization (reset via power cycle)

SCNR - Superordinate counter No Read Superordinate No Read counter; remains in case of a new parameterization (reset via power cycle)

DEVN - Device name Device name

APC01 - Application counter 1 Definable counter 1










TS - Time stamp Time stamp of reading gate (start reading gate)

RR - Read rate Ration between Good Reads (SCGR) and num-ber of reading gates

OGA - Distance between two objects Object to previous object in mm

Match counter… Description

Match1 Counter how often condition Match1 was ful-filled (object related)

TeachIn1 Counter how often condition TeachIn1 was ful-filled (object related)


Superordinate counter…. Description

Match1 Counter how often condition Match1 was ful-filled

TeachIn1 Counter how often condition TeachIn1 was ful-filled




LECTOR®620



2.4.1.4.50Filters/Sorters for Output Format2

You can use the graphical interface of the Filters/Sorters for Output Format2 group to re-strict (filter) data for output of the reading results and define the sequence in which the data is output (sort). By combining filters and sorters, you can therefore individually influence data output.

Special character… Description

NUL 00H Null

SOH 01H Start of heading

STX 02H Start of text

ETX 03H End of text

EOT 04H End of transmission

ENQ 05H Enquiry

ACK 06H Acknowledge

BEL 07H Bell

BS 08H Backspace

HT 09H Horizontal tab

LF 0AH NL line feed, new line

VT 0BH Verticval tab

FF 0CH NP from feed, new page

CR 0DH Carriage return

SO 0EH Shift out

SI 0FH Shift in

DLE 10H Data link escape

DC1 11H Device control 1




NAK 15H Negative acknowledge

SYN 16H Synchronous idle

ETB 17H End of transmission block

CAN 18H Cancel

EM 19H End of medium

SUB 1AH Substitute

ESC 1BH Escape

FSP1CH File separator

GSP 1DH Group separator

RSP 1 EH Record separator

USP 1FH Unit separator

SPC 20H Space

DEL 7FH Delete

User defined User defined [HEX]

Nothing Nothing


LECTOR®620



Any number of filters and sorters can be graphically arranged for this between the device and PC. The filters can also be arranged in parallel.

You can add further filters and sorters by pulling down the corresponding symbols. If you move the symbols while holding down the Ctrl key, you can copy filters or sorters. You can delete the symbols by moving them to the trash. Selected symbols can also be removed by pressing the DEL. key.

During filtering, you can use the button to define the variable and condition for filtering.

Example: (CL) CODE LENGTH = 10: Only codes with a code length of exactly 10 characters are output.

During sorting, you use the button to select the variable used to sort the reading results. You can also choose between sorting in ascending and descending order.

Example: (CL) CODE LENGTH - ASCENDING: The codes with the shortest code length are output first.


Items Description


















LECTOR®620































More… Description







LECTOR®620





















More… Description


LECTOR®620







































More… Description


LECTOR®620












NUL 00H Null



ETX 03H End of text


ENQ 05H Enquiry

ACK 06H Acknowledge

BEL 07H Bell

BS 08H Backspace






SO 0EH Shift out

SI 0FH Shift in









CAN 18H Cancel


SUB 1AH Substitute

ESC 1BH Escape




LECTOR®620



2.4.1.4.51Output format

Output format

2.4.1.4.52Output format 1

The format of the data string for output of the reading results is defined on the graphical interface of the Output format 1 group. A total of 2 different formats (Output format 1 and Output format 2) can be defined. During configuration of the interfaces, one of the two out-put formats can be assigned.

The output format is graphically displayed and can contain conditions, special characters (orange), variables (blue), or free text. To individually modify the output format, you select the required insertion position with the mouse. Entry takes place using the keyboard or spe-cial buttons:

You can use the button or the context menu (right mouse button) to insert e.g. conditi-ons, special characters (e.g. start and stop), or variables for the reading results.


You can use the button to modify the properties of a condition. For each condition, you can define which data should be output if the condition is met. You can also define data for the case in which the condition is not met. Conditions can be nested.

To check the output format, you can display the reading results on the terminal. To do this, you open the terminal using the button in the toolbar and establish a connection with the device (CONNECTION menu on the terminal). For each trigger (reading gate), a data string is transmitted and displayed on the terminal.



SPC 20H Space

DEL 7FH Delete


Nothing Nothing

Items Description










LECTOR®620






































Items Description


LECTOR®620





More… Description


















LECTOR®620

































More… Description


LECTOR®620

























NUL 00H Null



ETX 03H End of text


ENQ 05H Enquiry

ACK 06H Acknowledge

BEL 07H Bell

BS 08H Backspace








LECTOR®620



Wizard If you press the Wizard button, a dialog box is displayed in which you can select frequently used standard output formats. The output format selected in the wizard is transferred to the graphical interface of the Output format 1 group and graphically displayed. The output for-mat can subsequently be individually modified.

2.4.1.4.53Output format 2

The format of the data string for output of the reading results is defined on the graphical interface of the Output format 2 group. A total of 2 different formats (Output format 1 and Output format 2) can be defined. During configuration of the interfaces, one of the two out-put formats can be assigned.

The output format is graphically displayed and can contain conditions, special characters (orange), variables (blue), or free text. To individually modify the output format, you select the required insertion position with the mouse. Entry takes place using the keyboard or spe-cial buttons:

You can use the button or the context menu (right mouse button) to insert e.g. conditi-ons, special characters (e.g. start and stop), or variables for the reading results.


SO 0EH Shift out

SI 0FH Shift in









CAN 18H Cancel


SUB 1AH Substitute

ESC 1BH Escape





SPC 20H Space

DEL 7FH Delete


Nothing Nothing



LECTOR®620



You can use the button to modify the properties of a condition. For each condition, you can define which data should be output if the condition is met. You can also define data for the case in which the condition is not met. Conditions can be nested.

To check the output format, you can display the reading results on the terminal. To do this, you open the terminal using the button in the toolbar and establish a connection with the device (CONNECTION menu on the terminal). For each trigger (reading gate), a data string is transmitted and displayed on the terminal.

Items Description































LECTOR®620


















More… Description













LECTOR®620























More… Description


LECTOR®620







































LECTOR®620



Wizard If you press the Wizard button, a dialog box is displayed in which you can select frequently used standard output formats. The output format selected in the wizard is transferred to the graphical interface of the Output format 2 group and graphically displayed. The output for-mat can subsequently be individually modified.



NUL 00H Null



ETX 03H End of text


ENQ 05H Enquiry

ACK 06H Acknowledge

BEL 07H Bell

BS 08H Backspace






SO 0EH Shift out

SI 0FH Shift in









CAN 18H Cancel


SUB 1AH Substitute

ESC 1BH Escape





SPC 20H Space

DEL 7FH Delete


Nothing Nothing



LECTOR®620



2.4.1.4.54Heartbeat format

Heartbeat format

2.4.1.4.55Diagnosis settings

Diagnosis settings

2.4.1.4.56Image diagnostic

The Image diagnostic group contains the parameters for image output.

Depending on your requirements, the selection of images to be stored can be restricted. For example, you can store only images from unsuccessful readings in order to investigate pos-sible causes of failed/incorrect readings.

2.4.1.4.57Conditions for image storing

The Conditions for image storing parameter is used to select the condition on which images are stored for diagnosis.

• GOOD READ: Only images of a successful code reading are stored.

• NO READ: Only images of an unsuccessful code reading are stored.

• ALL: All recorded images are stored.

• CONDITION MATCH 1: The recorded images are only stored if the read code corresponds to the matchcode from CONDITION MATCH 1.

• CONDITION MULTCODES1: The recorded images are only stored if the number of read codes corresponds to the required number from CONDITION MULTCODES1.

• CONDITION TEACHIN1: The recorded images are only stored if condition Matchcode Teach-in 1 is met.

• CONDITION TEACHIN2: The recorded images are only stored if condition Match-code Teach-in 2 (Additional) is met.

2.4.1.4.58Image selection

You use the Image selection parameter to select the images to be stored for each reading gate.

• LAST GOOD READ / LAST IMAGE: If the code reading was successful, the last image on which one or more codes were read is stored. If the code reading was not successful, the most recently recorded image is stored. (Recommended for applications for which the code does not move out of the reading gate during reading.)

• FIRST IMAGE: The first recorded image is stored. (Recommended for applications for which the code is in motion during reading and for which triggering takes place to the code, i.e. the first image already contains a code.)

• IMAGE SEQUENCE: All recorded images are stored as a sequence. (Recommended for appli-cations for which the reading gate is opened by an object and the position of the code on the object is not known exactly.) The recording of image sequences is used to check trigge-ring and recording quality for moving objects. The images are numbered top left. If image numbers are missing, not all recordings can be decoded and the settings (e.g. code set-tings) must be modified accordingly.


LECTOR®620



2.4.1.4.59Image quality

You use the Image quality parameter to modify the file size or quality (resolution) of the stored image files. The setting has no effect on the reading speed of the LECTOR®620.

For each image, an xml file containing the data of the Code infobox is stored.

• Quality level 6 (max. resolution): File size with full image region of interest 354 kB

• Quality level 5: File size with full image region of interest 90 KB





2.4.1.4.60Destination for images

The Destination for images group contains the parameters for storing the image files. The destination for images defines the medium on which the images are stored.

2.4.1.4.61Internal memory (permanent)

If the Internal memory (permanent) parameter is activated, the recorded images are perma-nently stored in the internal memory of the LECTOR®620. The images are retained even af-ter the device has been switched off.

The available internal memory size is 120 MB. The stored images can be transferred to the PC and can be manually deleted.

2.4.1.4.62Counter

The Counter parameter has the fixed value TRIGGER NO. and cannot be changed.

The stored images are sequentially numbered. The number is increased by 1 each time the reading gate is opened. After the device is restarted, numbering starts again at 1. If the me-mory is full, no further images are stored.

2.4.1.4.63Modulo

2.4.1.4.64Internal memory (temporary)

If the Internal memory (temporary) parameter is activated, the recorded images are stored in the internal memory of the LECTOR®620. When the LECTOR®620 is switched off, the stored images are deleted.

The available internal memory size is 15 MB. Therefore around 40 images can be stored. The stored images can be transferred to the PC and can be manually deleted.


LECTOR®620



2.4.1.4.65Counter

The Counter parameter is used to define the numbering for the stored images.

• CYCLIC NO: The stored images are sequentially numbered up to a definable value (Modulo). As soon as this value has been reached, numbering starts again from 1, thereby overwriting existing images. After the device is restarted or parameters are changed, numbering also starts again from 1. In the case of cyclic numbering, the most recently recorded images are stored.

• TRIGGER NO: The stored images are sequentially numbered. The number is increased in each case by 1 as soon as the reading gate is opened. After the device is restarted, numbe-ring starts again at 1. If the memory is full, no further images are stored. In the case of num-bering via the trigger, the images recorded first are stored.

2.4.1.4.66Modulo

The Modulo parameter is used to define the maximum value for the counter.

As soon as this value has been reached, numbering starts again from 1, thereby overwriting existing images. This enables you to restrict the maximum memory required for the stored images.

2.4.1.4.67MicroSD card

If the MicroSD card parameter is activated, the recorded images are permanently stored on the memory card of the LECTOR®620.

For this, a suitable memory card (MicroSD up to 32 GB, file system FAT) must be available in the LECTOR®620.

You can use memory cards to easily increase the storage space. The stored image files can be analyzed/processed further on any PC.

For many MicroSD cards, the maximum number of files per folder is restricted to 10000.

2.4.1.4.68Counter





LECTOR®620



2.4.1.4.69Modulo



2.4.1.4.70Remove SD card

If you press the Remove SD card button, any write or read operations are concluded and the memory card is de-energized. As a result, the memory card can be removed safely and you do not need to worry about losing data or destroying the card.

2.4.1.4.71Check SD card

You can press the Check SD card button to check the functioning of the memory card.

2.4.1.4.72SOPAS (PC)

If the SOPAS (PC) parameter is activated, the recorded images are stored on the connected PC.

For this, the SOPAS configuration software must be running during recording. The recorded images are shown in the main view of the Online images tab.

2.4.1.4.73Counter




2.4.1.4.74Modulo



2.4.1.4.75Select directory

You can use the Select directory button to define the storage location for the recorded ima-ges on the connected PC.


LECTOR®620



2.4.1.4.76Image file path

The Image file path group contains the parameters for the storage location and naming of the image files.

2.4.1.4.77Folder name

The Folder name parameter is used to select the standard name for the image folder.

• SERIAL NUMBER: The image files are stored in a folder that has the same name as the LEC-TOR®620 serial number.

• DEVICE NAME: The image files are stored in a folder that has the same name as the value of the Name parameter. If you assign suitable device names, you can easily differentiate between the image files of several similar devices (e.g. in a network).

Name You can use the Name parameter to define the device name for the LECTOR®620. The image files of the LECTOR®620 are stored in a folder of the same name. If you assign sui-table device names, you can easily differentiate between the image files of several similar devices (e.g. in a network).

2.4.1.4.78Subfolder Good Read / No Read

If the Subfolder Good Read / No Read parameter is activated, the images are stored in two different subfolders depending on the read result (GOODREAD or NOREAD) to enable easier analysis.

2.4.1.4.79Good Read / No Read file prefix

If the Good Read / No Read file prefix parameter is activated, the images are only given a name supplement depending on the read result (GOODREAD or NOREAD) to enable easier ana-lysis.

2.4.1.4.80Image file name

You can use the Image file name parameter to define the file name for the image files. The image files are also given a sequential number, and if the Good Read / No Read file prefix parameter is activated, a name supplement (GOODREAD or NOREAD).

By assigning suitable file names, you can clearly assign the image files (e.g. to a project or device).

2.4.1.5 Application counters

Application counters

2.4.1.5.1Application counters

Application counters

2.4.1.5.2Reset counter values

Reset counter values


LECTOR®620



2.4.1.5.3Store current counter values now

Store current counter values now

2.4.1.5.4Value

Value

2.4.1.5.5Store value permanent

Store value permanent

2.4.1.6 Network / Interface / IOs

Network / Interface / IOs

2.4.1.6.1Network options

Network options

2.4.1.6.2Device ID

Device ID

2.4.1.6.3Device name

Device name

2.4.1.6.4Master / slave

Master / slave

2.4.1.6.5Function

Function

2.4.1.6.6Slave list

Slave list

2.4.1.6.7Multiplexer / server

Multiplexer / server

2.4.1.6.8Function

Function

2.4.1.6.9Server list

Server list

2.4.1.6.10Monitoring

Monitoring

2.4.1.6.11Assign to

Assign to


LECTOR®620



2.4.1.6.12Monitored devices

Monitored devices

2.4.1.6.13Max. bootup time of monitored devices

Max. bootup time of monitored devices

2.4.1.6.14Serial

Serial

2.4.1.6.15Serial Host

The Serial Host group contains the parameters for configuring the serial Host interface. The serial Host interface is typically used for communication with the controller (PLC).

2.4.1.6.16Output Format

You use the Output Format parameter to select the output format for the interface.

• NO OUTPUT: There is no data output via this interface.

• OUTPUT FORMAT 1: In the event of output via this interface, the data is formatted in line with the configuration in the Output format 1 group.


• CUSTOMER OUTPUT FORMAT: Via this interface, the data is output based on customer-specific formatting. The formatting is defined via the With number parameter.

2.4.1.6.17With number

The With number parameter is used to specify the number of the customer-specific output format.

2.4.1.6.18Multiplexer output

Multiplexer output

2.4.1.6.19Baud rate

You can use the Baud rate parameter to adapt the maximum transmission speed of the LECTOR®620 to the host.

The value is specified in Baud/s. This value is used to define the number of signal changes per second that can take place via the interface. Depending on the protocol, up to four bits per signal change can be transmitted (e.g. at 2400 Bauds up to 9600 bit/second).

2.4.1.6.20Stop bits

The Stop bits parameter is used to define whether 1 (typical) or 2 characters are used at the end of a transmitted character as the pause (stop bits). The setting must match the setting on the host.


LECTOR®620



2.4.1.6.21Data bits / parity

You use the Data bits / parity parameter to define the number of data bits (8 or 7) and the corresponding parity. The setting must match the setting on the host.

2.4.1.6.22Hardware

The Hardware parameter is used to select the protocol (RS232 or RS244) for the serial in-terface.

2.4.1.6.23Enable heartbeat

If the Enable heartbeat parameter is activated, a signal is output via the interface at regular intervals (Heartbeat interval). The availability of the LECTOR®620 can therefore be checked via the interface.

2.4.1.6.24Heartbeat interval

The Heartbeat interval parameter is used to define the time between the heartbeat signals in s.

2.4.1.6.25Restart interval on sending

If the Restart interval on sending parameter is activated, the time between the heartbeat signals starts again after output of the reading results.

2.4.1.6.26Serial Aux

The Serial Aux group contains the parameters for configuring the serial Aux interface. The serial Aux interface is typically used to parameterize and analyze the LECTOR®620.

As the configuration of the interface on the LECTOR®620 cannot be changed, the settings must be modified on the connected device (e.g. PC or controller).




• READING DIAGNOSIS: This interface is used to output a diagnosis string for each reading gate.

• MONITOR SERIAL HOST INTERFACE: The Aux interface is used to output the same data that is output via the Host interface. As a result, the data traffic of the host interface can be chek-ked.

• RDT400 PROTOCOL: A predefined data string is output via this interface. As a result, the rea-ding results of several devices can be combined and evaluated using a remote diagnostic tool (RDT).




LECTOR®620



For the reading diagnosis, the following information is combined in a diagnosis string for each reading gate:

• TT: Length of the reading gate in ms

• OTL: Trigger length in mm

• CC: Number of codes per reading gate

• FC: Focus length in mm

• Code content

• Code type

for 1D symbologies

• CL: Code length

• RSD1DV: Proportion of scans to decoded scans in (reading reliability) in %

for 2D symbologies

• SZ: Symbol size

• RES: Resolution of a cell in pixels

• CTV: Symbol contrast in %

• UECV: Decodability (unused error correction) in %

• MC: Number of multireads per code

2.4.1.6.28RDT ID

RDT ID







2.4.1.6.32Ethernet

Ethernet

2.4.1.6.33Ethernet General

The Ethernet General group contains general parameters for configuring the Ethernet inter-faces (Host and Aux).


LECTOR®620



2.4.1.6.34Addressing Mode

You use the Addressing Mode parameter to define whether the IP address for the LEC-TOR®620 is to be defined manually (STATIC) or by a server (DHCP).

2.4.1.6.35IP address

The IP address parameter is used to manually define the Ethernet address for the LEC-TOR®620. A prerequisite for this is a connection with the LECTOR®620 in the SERVICE user level.

It is possible to use the connection wizard to change the IP address and Subnet-Mask parameters in the AUTHORIZED CLIENT user level.

The Ethernet address must match the setting for the Subnet-Mask parameter and must be adapted in line with the network.

2.4.1.6.36Subnet-Mask

The Subnet-Mask parameter is used to define the bit mask or prefix mask for network pro-tocol IPv4 and IPv6. A prerequisite for this is a connection with the LECTOR®620 in the SERVICE user level.


The setting must be adapted to the network.

2.4.1.6.37Default gateway

The Default gateway parameter can be used to specify the IP address of a gateway for im-plementation of the network protocol. A prerequisite for this is a connection with the LEC-TOR®620 in the SERVICE user level.


2.4.1.6.38Speed

The Speed can be used to adapt the maximum transmission speed of the LECTOR®620 to the speed of the network.

To ensure a reliable connection, you are advised to automatically determine the speed of a directly connected PC (AUTO).

2.4.1.6.39Negotiated

The current speed is displayed in the Negotiated display field.

For this, there must be a connection between the LECTOR®620 and the PC.


LECTOR®620



2.4.1.6.40MAC-Address

The MAC-Address display field shows a unique number for devices with an Ethernet inter-face. This number can be used to uniquely identify the LECTOR®620.

2.4.1.6.41Ethernet Host Port

The Ethernet Host Port group contains the parameters for configuring the Ethernet Host in-terface. The Ethernet Host interface is typically used for communication with the controller






2.4.1.6.43Multiplexer output

Multiplexer output

2.4.1.6.44Server/Client

The Server/Client parameter is used to select the function of the LECTOR®620 within a net-work.

• SERVER: The LECTOR®620 performs the function of the server within a network.

• CLIENT: Within a network, the LECTOR®620 is subordinate to a server. The server is defi-ned via the Server Address parameter.

2.4.1.6.45IP port

The IP port parameter is used to adapt the port number for the Ethernet Host interface (de-fault value: 2112) to the connected PC or the controller (PLC).

2.4.1.6.46Server Address

The Server Address parameter is used to define the IP address of the server to which the LECTOR®620 is assigned within a network.






LECTOR®620





2.4.1.6.50Ethernet Aux Port

The Ethernet Aux Port group contains the parameters for configuring the Ethernet Aux inter-face. The Ethernet Aux interface is typically used to parameterize and analyze the LEC-TOR®620.




• READING DIAGNOSIS: This interface is used to output a diagnosis string for each reading gate.



For the reading diagnosis, the following information is combined in a diagnosis string for each reading gate:

• TT: Length of the reading gate in ms

• OTL: Trigger length in mm

• CC: Number of codes per reading gate

• FC: Focus length in mm

• Code content

• Code type

for 1D symbologies

• CL: Code length

• RSD1DV: Proportion of scans to decoded scans in (reading reliability) in %

for 2D symbologies

• SZ: Symbol size

• RES: Resolution of a cell in pixels

• CTV: Symbol contrast in %

• UECV: Decodability (unused error correction) in %

• MC: Number of multireads per code

2.4.1.6.52Server/Client

The Server/Client parameter has the fixed value CLIENT and cannot be changed.


LECTOR®620



2.4.1.6.53IP port

The IP port parameter is used to adapt the port number for the Ethernet Aux interface (de-fault value: 2111) to the connected PC or the controller (PLC).

2.4.1.6.54CAN

CAN

2.4.1.6.55CAN

CAN

2.4.1.6.56Mode

Mode

2.4.1.6.57Use device-ID as node-ID

Use device-ID as node-ID

2.4.1.6.58Device ID

Device ID

2.4.1.6.59Baudrate

Baudrate

2.4.1.6.60Output format

Output format

2.4.1.6.61Digital inputs

Digital inputs

2.4.1.6.62Sensor / Result 1

The Sensor / Result 1 group contains the parameters for modifying digital input 1.

2.4.1.6.63Control

The Control parameter is used to choose between configuration with units of length or con-figuration with units of time.

• TRACK CONTROLLED: The configuration is based on track increments in mm that are either generated by the configuration software (SOPAS) or via the CAN interfaces or are generated via an incremental encoder on the digital input.

• TIME CONTROLLED: Configuration is based on time information in ms.


LECTOR®620



2.4.1.6.64Sensitivity

The Sensitivity parameter is used to choose between edge control and level control.

• EDGE: Depending on the configuration of the Logic parameter, the digital input reacts to the change between Low (0) and High (1). A permanently present signal is ignored.

• LEVEL: Depending on the configuration of the Logic parameter, the digital input reacts to a permanently present signal.

2.4.1.6.65Logic

The Logic parameter is used to select the polarity for the Sensitivity parameter.

• NOT INVERTED: The digital input reacts to a rising edge, i.e. to the change from Low (0) to High (1) or a permanent High signal (1).

• INVERTED: The digital input reacts to a falling edge, i.e. to the change from High (1) to Low (0) or a permanent Low signal (0).

2.4.1.6.66Debouncing

Depending on the configuration of the Control parameter, the Debouncing parameter is used to specify the distance in mm or time in ms for which the signal must at least be pre-sent at the external input. If the value is not achieved, the signal is not identified.

Depending on the application, this value must be modified in accordance with the required reading pulse rate.

2.4.1.6.67Sensor / Result 2

The Sensor / Result 2 group contains the parameters for modifying digital input 2.

2.4.1.6.68Control









LECTOR®620



2.4.1.6.70Logic







2.4.1.6.72External Input 1


The External Input 1 group contains the parameters for modifying external digital input 1.

2.4.1.6.73Control









LECTOR®620



2.4.1.6.75Logic







2.4.1.6.77External Input 2


The External Input 2 group contains the parameters for modifying external digital input 1.

2.4.1.6.78Control









LECTOR®620



2.4.1.6.80Logic







2.4.1.6.82Digital outputs/beeper

Digital outputs/beeper

2.4.1.6.83Output / Result 1

The Output / Result 1 group contains the parameters for modifying digital output 1.

2.4.1.6.84Active

The Active parameter is used to select the event for which the digital output is activated.

• SOPAS COMMAND: The output is activated by a command. As a result, the defined statuses can be displayed via a connected control lamp as a result of a controller (PLC) command.

• DEVICE READY: The output is activated as soon as the LECTOR®620 is operational.

• GOOD READ: The output is activated in the event of a successful reading.

• NO READ: The output is activated in the event of an unsuccessful reading.

• TEACH-IN 1 OK: The output is activated if the MATCHCODE TEACH-IN 1 was taught in suc-cessfully.

• TEACH-IN 1 NOK: The output is activated if the MATCHCODE TEACH-IN 1 was not taught in suc-cessfully.



• CONDITION MATCH 1: The output is activated if the read code corresponds to the matchcode from CONDITION MATCH 1.

• CONDITION MULTCODES1: The output is activated if the number of read codes corresponds to the required number from CONDITION MULTCODES1.


LECTOR®620



• CONDITION TEACHIN1: The output is activated if the read code corresponds to the match-code from CONDITION TEACHIN1.


2.4.1.6.85Function (Off)

The Function (Off) parameter is used to select the event for which the digital output is deac-tivated.

• TIMER/TRACKING: The output is deactivated after a certain period of time (Length).

• NEXT OBJECT TRIGGER: The output is deactivated as soon as the next reading gate is opened.

• SOPAS COMMAND: The output is deactivated by a command. As a result, the defined sta-tuses can be displayed via a connected control lamp as a result of a controller (PLC) com-mand.

• GOOD READ: The output is deactivated in the event of a successful reading.

• NO READ: The output is deactivated in the event of an unsuccessful reading.

• TEACH-IN 1 START: The output is deactivated as soon as the processing for teaching in the MATCHCODE TEACH-IN 1 starts.


• CONDITION MATCH 1: The output is deactivated if the read code corresponds to the match-code from CONDITION MATCH 1.

• CONDITION MULTCODES1: The output is deactivated if the number of read codes corre-sponds to the required number from CONDITION MULTCODES1.

• CONDITION TEACHIN1: The output is deactivated if the read code corresponds to the match-code from CONDITION TEACHIN1.


2.4.1.6.86Or

You can use the Or parameter to choose a second condition for deactivating the digital out-put.

One of the conditions must be met for the digital output to be deactivated.

• ---: Second condition not selected.






LECTOR®620



2.4.1.6.87Logic

The Logic parameter is used to select the polarity of the digital output.

• NOT INVERTED: On activation, the digital output switches from Low (0) to High (1).

• INVERTED: On activation, the digital output switches from High (1) to Low (0).

2.4.1.6.88Control


• TRACK CONTROLLED: The entries for the Length parameter are made in mm.

• TIME CONTROLLED: The entries for the Length parameter are made in ms.

2.4.1.6.89Length

If the TIMER/TRACKING condition is selected under the Function (Off) parameter, you can use the Length parameter to enter the duration for which the digital output remains activated. The unit can be selected in the Control parameter.



2.4.1.6.91Active















LECTOR®620
















2.4.1.6.93Or








2.4.1.6.94Logic





LECTOR®620



2.4.1.6.95Control




2.4.1.6.96Length




Digital outputs 3 and 4 are not available via the 15-pin D-Sub connection on connection modules CDB620 and CDM420 and can only be used in conjunction with a 17-pole line with open ends.

2.4.1.6.98Active















LECTOR®620
















2.4.1.6.100Or








2.4.1.6.101Logic





LECTOR®620



2.4.1.6.102Control




2.4.1.6.103Length




Digital outputs 3 and 4 are not available via the 15-pin D-Sub connection on connection modules CDB620 and CDM420 and can only be used in conjunction with a 17-pole line with open ends.

2.4.1.6.105Active















LECTOR®620
















2.4.1.6.107Or








2.4.1.6.108Logic





LECTOR®620



2.4.1.6.109Control




2.4.1.6.110Length


2.4.1.6.111External Output 1

The connection module CDB620 or CDM420 in conjunction with the parameter memory module CMC600 can be used to extend the number of available digital outputs. The para-meter memory module CMC is used for output extension and converts a digital signal into a command. External digital outputs react more slowly than the internal digital outputs of the LECTOR®620.

The External Output 1 group contains the parameters for modifying external digital output 1.

2.4.1.6.112Active















LECTOR®620
















2.4.1.6.114Or








2.4.1.6.115Logic





LECTOR®620



2.4.1.6.116Control




2.4.1.6.117Length


2.4.1.6.118External Output 2

The connection module CDB620 or CDM420 in conjunction with the parameter memory module CMC600 can be used to extend the number of available digital outputs. The para-meter memory module CMC is used for output extension and converts a digital signal into a command. External digital outputs react more slowly than the internal digital outputs of the LECTOR®620.

The External Output 2 group contains the parameters for modifying external digital output 2

2.4.1.6.119Active















LECTOR®620
















2.4.1.6.121Or








2.4.1.6.122Logic





LECTOR®620



2.4.1.6.123Control




2.4.1.6.124Length


2.4.1.6.125Beeper

The Beeper group contains the parameters for modifying the acoustic signal.

As with the digital outputs, you can select an event for which the beeper is activated. As soon as the event occurs, the beeper reports this acoustically.

2.4.1.6.126Beeper

The Beeper parameter is used to select the event for which the beeper is activated.

• GOOD READ: The beeper sounds if the reading was successful.

• NO READ: The beeper sounds if the reading was unsuccessful.

• TEACH-IN 1 OK: The beeper sounds if the MATCHCODE TEACH-IN 1 was taught in successfully.

• TEACH-IN 1 NOK: The beeper sounds if the MATCHCODE TEACH-IN 1 was not taught in suc-cessfully.

• TEACH-IN 2 OK: The beeper sounds if the MATCHCODE TEACH-IN 2 was taught in successfully.

• TEACH-IN 2 NOK: The beeper sounds if the MATCHCODE TEACH-IN 2 was not taught in suc-cessfully.

• CONDITION MATCH 1 : The beeper sounds if the read code corresponds to the matchcode from CONDITION MATCH 1.

• CONDITION MULTCODES1: The beeper sounds if the number of read codes corresponds to the required number from CONDITION MULTCODES1.

• CONDITION TEACHIN1: The beeper sounds if the read code corresponds to the matchcode from CONDITION TEACHIN1.

• CONDITION TEACHIN2: The beeper sounds if the read code corresponds to the matchcode from CONDITION TEACHIN2.

2.4.1.6.127Volume

The Volume parameter can be used to deactivate the beeper (OFF) or set the volume of the beeper (LOUD or SOFT).

As a result, the beeper can be adapted to background noise.


LECTOR®620



2.4.1.6.128Function buttons

Function buttons

2.4.1.6.129Function buttons

The Function buttons contains the parameters for defining the functions of the buttons on the LECTOR®620.

2.4.1.6.130Function

You use the Function parameter to define the function and behavior of the buttons on the LECTOR®620.

• NO FUNCTION: The function buttons on the LECTOR®620 are deactivated. As a result, you can avoid malfunctions during operation caused by pressing the buttons by accident.

• TRIGGER AND AIMING LASER: You can use the buttons on the LECTOR®620 to carry out a rea-ding without the LECTOR®620 having to be connected to the PC.

- You use the left button to open the reading gate. The reading gate remains open until the button is released again or until the condition for closing the reading gate has been met.

- You use the right button to turn the aiming laser on/off. The aiming laser is automatically turned off after 5 minutes.

• MENU (SAVE PERMANENT): The buttons on the LECTOR®620 have a menu function and can be used for parameterization. The changed parameter values are permanently stored in the device. Existing values are overwritten.

• MENU (SAVE TEMPORARY): The buttons on the LECTOR®620 have a menu function and can be used for parameterization. Existing values are initially overwritten. The changed parame-ter values are retained and stored in the device until the device is restarted. As the old pa-rameter values are restored after the restart, this setting is useful for testing parameter changes. The function can also be used to temporarily read another code and reset the set-tings by restarting the device.


LECTOR®620



If the menu function is activated, the following functions can be accessed using the buttons on the LECTOR®620:

• READ DIAGN: A suitable code in the reading area is read with the current configuration. The reading rate of the last 10 readings is displayed in % via the bar chart on the housing of the LECTOR®620.

• TEACHIN MATCHCODE: A suitable code in the reading area is read and stored as a match-code.

• AUTO-SETUP (initially only available for DATA MATRIX): Depending on the configuration of the parameters in the Auto-Setup group, the reading distance, image settings (brightness and contrast), and code settings are modified automatically. For this, a suitable object with con-trast changes or edges (e.g. code, text, or other structures) must be placed in the reading area.

• AUTOFOCUS: The focus position (reading distance) is modified automatically. For this, a sui-table object with contrast changes or edges (e.g. code, text, or other structures) must be placed in the reading area.

• USERDEFINED: (currently not implemented)

2.4.1.6.131Auto-Setup

The Auto-Setup group contains the parameters for modifying the Auto Setup wizard.

The AUTO-SETUP function is split into three individual modules:

• READING DISTANCE

• IMAGE SETTINGS (brightness and contrast)

• CODE SETTINGS (initially only available for DATA MATRIX)

The AUTO-SETUP function can be called up in different ways:

• via the wizard

• via the buttons on the LECTOR®620

• by pressing the AUTO button

• via a command (Sopas command)

Commands for calling the AUTO-SETUP function:

• SMN MASSTART: The Auto Setup process is started.

• SMN MASFINISH: The Auto Setup process is stopped and the result is transmitted. To return to reading mode, you must end the Auto Setup process with a stop command.

• SMN MASCANCEL: The Auto Setup process is stopped. However, the result is discarded. To return to reading mode, you must end the Auto Setup process with a stop command.

Even if you call up the AUTO-SETUP function via a command, the settings for the wizard (standard or extended) are taken into consideration. The settings can also be configured using commands. A detailed list of commands can be obtained from SICK on request.


LECTOR®620



2.4.1.6.132Change reading distance

If the Change reading distance parameter is activated, the reading distance is modified using the AUTO-SETUP function. The function is called up using the buttons on the LEC-TOR®620.

2.4.1.6.133Change camera settings

If the Change camera settings parameter is activated, the brightness and contrast are mo-dified using the AUTO-SETUP function. The function is called up using the buttons on the LEC-TOR®620.

2.4.1.6.134Change code settings

If the Change code settings parameter is activated, the code settings for the DATAMATRIX symbology are modified using the AUTO-SETUP function. The function is called up using the buttons on the LECTOR®620.

2.4.2 Service

Service

2.4.2.1 Operating data

Operating data

2.4.2.1.1Device information

The identification data of the LECTOR®620 is indicated via the parameters of the Device in-formation group.

This data is important for service work.

2.4.2.1.2Manufacturer

The manufacturer of the LECTOR®620 is indicated in the Manufacturer display field.

2.4.2.1.3Device type

The device type of the LECTOR®620 is indicated in the Device type display field.

2.4.2.1.4Software version

The version of the installed firmware is indicated in the Software version display field.

2.4.2.1.5Order number

The order number of the LECTOR®620 is indicated in the Order number display field.

2.4.2.1.6Serial number

The serial number of the LECTOR®620 is indicated in the Serial number display field.

2.4.2.1.7Operating data

Operating data


LECTOR®620



2.4.2.1.8Power-On counter

Power-On counter

2.4.2.1.9Operating hours

Operating hours

2.4.2.1.10Power-On hours

Power-On hours

2.4.2.1.11Service information

Service information

2.4.2.1.12Last username

Last username

2.4.2.1.13Last parametrization

Last parametrization

2.4.2.1.14um

um

2.4.2.1.15Last maintenance

Last maintenance

2.4.2.1.16Next maintenance

Next maintenance

2.4.2.2 System status

System status

2.4.2.2.1System information

System information

2.4.3 Analysis

Analysis

2.4.3.1 Event monitor

Event monitor

2.4.3.1.1Event monitor

Event monitor


LECTOR®620

Used Open Source programms and its license texts


3 Used Open Source programms and its license texts

3.1 NCURSES – 5.7 - License

Copyright (c) 2006 Free Software Foundation, Inc.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restric-tion, including without limitation the rights to use, copy, modify, merge, publish, distribute, distribute with modifications, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or sub-stantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IM-PLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE ABOVE COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHE-THER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Except as contained in this notice, the name(s) of the above copyright holders shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization.

These are the principal authors/contributors of ncurses since 1.9.9e, in decreasing order of their contribution:

• TD Thomas E. Dickey

• JPF Juergen Pfeifer

• ESR Eric S Raymond

• AVL Alexander V Lukyanov

• PB Philippe Blain

• SV Sven Verdoolaege

3.2 Z-Lib 1.2.3

Copyright (C) 1995-2004 Jean-loup Gailly and Mark Adler

This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software.


LECTOR®620



3.3 e2fsprogs-1.41.11 (UUID-license based on BSD 3-clause license)

Copyright (C) 1996, 1997 Theodore Ts'o.

Redistribution and use in source and binary forms, with or without modification, are permit-ted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, and the entire permission notice in its entirety, including the disclaimer of warranties.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, IN-CLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FIT-NESS FOR A PARTICULAR PURPOSE, ALL OF WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCURE-MENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSI-NESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF NOT ADVISED OF THE POSSIBI-LITY OF SUCH DAMAGE.

3.4 Dropbear – 0.52.tar.bz2

Licenser:

• Matt Johnston

• Mihnea Stoenescu

• Tom StDenis

• Tatu Ylonen

• Andre Luca

• odd C. Miller

• Simon Tatham

Dropbear contains a number of components from different sources, hence there are a few licenses and authors involved. All licenses are fairly non-restrictive.

The majority of code is written by Matt Johnston, under the license below.


LECTOR®620



3.4.1 Portions of the client-mode work are (c) 2004 Mihnea Stoenescu, under the same license:

Copyright (c) 2002-2008 Matt Johnston

Portions copyright (c) 2004 Mihnea Stoenescu

All rights reserved.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restric-tion, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:


THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IM-PLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WH-ETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

3.4.2 Import code in keyimport.c is modified from PuTTY's import.c, licensed as follows:

PuTTY is copyright 1997-2003 Simon Tatham.

Portions copyright Robert de Bath, Joris van Rantwijk, Delian Delchev, Andreas Schultz, Jeroen Massar, Wez Furlong, Nicolas Barry, Justin Bradford, and CORE SDI S.A.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restric-tion, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:


THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IM-PLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE COPY-RIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNEC-TION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.


LECTOR®620



3.5 OpenSSH – 5.1p1

3.5.1 Cryptographic attack detector for ssh - source code

Copyright (c) 1998 CORE SDI S.A., Buenos Aires, Argentina.

All rights reserved. Redistribution and use in source and binary forms, with or without modi-fication, are permitted provided that this copyright notice is retained.

THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES ARE DISCLAIMED. IN NO EVENT SHALL CORE SDI S.A. BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY OR CONSEQUENTIAL DAMAGES RESULTING FROM THE USE OR MISUSE OF THIS SOFTWARE.

Ariel Futoransky <[email protected]>

<http://www.core-sdi.com>

3.5.2

Copyright 1995, 1996 by David Mazieres <[email protected]>.

Modification and redistribution in source and binary forms is permitted provided that due credit is given to the author and the OpenBSD project by leaving this copyright notice intact.

3.5.3

Copyright (c) 1983, 1990, 1992, 1993, 1995 The Regents of the University of California.

All rights reserved.


1. Redistributions of source code must retain the above copyright notice, this list of con-ditions and the following disclaimer.


3. Neither the name of the University nor the names of its contributors may be used to en-dorse or promote products derived from this software without specific prior written per-mission.

THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ̀ `AS IS'' AND ANY EX-PRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WAR-RANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (IN-CLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLU-DING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFT-WARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.


LECTOR®620



3.5.4

Remaining components of the software are provided under a standard 2-term BSD licence with the following names as copyright holders:

• Markus Friedl

• Theo de Raadt

• Niels Provos

• Dug Song

• Aaron Campbell

• Damien Miller

• Kevin Steves

• Daniel Kouril

• Wesley Griffin

• Per Allansson

• Nils Nordman

• Simon Wilkinson

Portable OpenSSH additionally includes code from the following copyright holders, also un-der the 2-term BSD license:

• Ben Lindstrom

• Tim Rice

• Andre Lucas

• Chris Adams

• Corinna Vinschen

• Cray Inc.

• Denis Parker

• Gert Doering

• Jakob Schlyter

• Jason Downs

• Juha Yrjölä

• Michael Stone

• Networks Associates Technology, Inc.

• Solar Designer

• Todd C. Miller

• Wayne Schroeder

• William Jones

• Darren Tucker

• Sun Microsystems

• The SCO Group

• Daniel Walsh

Copyright < year > <copyright holders >. All rights reserved.


LECTOR®620






THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHAN-TABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEM-PLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS IN-TERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CON-TRACT, STRICT LIABILITY, OR TOR (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

3.5.5 Portable OpenSSH contains the following additional licenses:

a) md5crypt.c, md5crypt.h

"THE BEER-WARE LICENSE" (Revision 42):

<[email protected]> wrote this file. As long as you retain this notice you can do whatever you want with this stuff. If we meet some day, and you think this stuff is worth it, you can buy me a beer in return. Poul-Henning Kamp

b) snprintf replacement

Copyright Patrick Powell 1995

This code is based on code written by Patrick Powell ([email protected]) It may be used for any purpose as long as this notice remains intact on all source code distributions

c) Compatibility code (openbsd-compat)

Apart from the previously mentioned licenses, various pieces of code in the openbsd-com-pat/ subdirectory are licensed as follows:

Some code is licensed under a 3-term BSD license, to the following copyright holders:

• Todd C. Miller

• Theo de Raadt

• Damien Miller

• Eric P. Allman

• The Regents of the University of California

• Constantin S. Svintsoff


LECTOR®620






3. Neither the name of the University nor the names of its contributors may be used to en-dorse or promote products derived from this software without specific prior written per-mission.

THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ̀ `AS IS'' AND ANY EX-PRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WAR-RANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (IN-CLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLU-DING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFT-WARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

d) Some code is licensed under an ISC-style license, to the following copyright holders:

• Internet Software Consortium.

• Todd C. Miller

• Reyk Floeter

• Chad Mynhier

Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND TODD C. MILLER DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTA-BILITY AND FITNESS. IN NO EVENT SHALL TODD C. MILLER BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RE-SULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

e) Some code is licensed under a MIT-style license to the following copyright holders:

- Free Software Foundation, Inc.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restric-tion, including without limitation the rights to use, copy, modify, merge, publish, distribute, distribute with modifications, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:



LECTOR®620



THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IM-PLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE ABOVE COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHE-THER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Except as contained in this notice, the name(s) of the above copyright holders shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization.

3.6 GNU GENERAL PUBLIC LICENSE

Version 2, June 1991

Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA- Everyone is permitted to copy and distribute verbatim co-pies of this license document, but changing it is not allowed.

NO WARRANTY

11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHER-WISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IM-PLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILI-TY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTI-VE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBU-TE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PAR-TIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMA-GES.

3.7 Libstdc++-v3

The source code of libstdc++-v3 is distributed under version 2 of the GNU General Public License, with the so-called "runtime exception," as follows (or see any header or implemen-tation file):

As a special exception, you may use this file as part of a free software library without restric-tion. Specifically, if other files instantiate templates or use macros or inline functions from this file, or you compile this file and link it with other files to produce an executable, this file does not by itself cause the resulting executable to be covered by the GNU General Public License. This exception does not however invalidate any other reasons why the executable file might be covered by the GNU General Public License.


LECTOR®620



3.8 Glibc 2.8

3.8.1 GNU LESSER GENERAL PUBLIC LICENSE

Version 3, 29 June 2007

Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

This version of the GNU Lesser General Public License incorporates the terms and conditi-ons of version 3 of the GNU General Public License, supplemented by the additional permis-sions listed below.

0. Additional Definitions.

As used herein, "this License" refers to version 3 of the GNU Lesser General Public License, and the "GNU GPL" refers to version 3 of the GNU General Public License.

"The Library" refers to a covered work governed by this License, other than an Application or a Combined Work as defined below.

An "Application" is any work that makes use of an interface provided by the Library, but which is not otherwise based on the Library. Defining a subclass of a class defined by the Library is deemed a mode of using an interface provided by the Library.

A "Combined Work" is a work produced by combining or linking an Application with the Li-brary. The particular version of the Library with which the Combined Work was made is also called the "Linked Version".

The "Minimal Corresponding Source" for a Combined Work means the Corresponding Sour-ce for the Combined Work, excluding any source code for portions of the Combined Work that, considered in isolation, are based on the Application, and not on the Linked Version.

The "Corresponding Application Code" for a Combined Work means the object code and/or source code for the Application, including any data and utility programs needed for repro-ducing the Combined Work from the Application, but excluding the System Libraries of the Combined Work.

1. Exception to Section 3 of the GNU GPL.

You may convey a covered work under sections 3 and 4 of this License without being bound by section 3 of the GNU GPL.

2. Conveying Modified Versions.

If you modify a copy of the Library, and, in your modifications, a facility refers to a function or data to be supplied by an Application that uses the facility (other than as an argument passed when the facility is invoked), then you may convey a copy of the modified version:

a) under this License, provided that you make a good faith effort to ensure that, in the event an Application does not supply the function or data, the facility still operates, and performs whatever part of its purpose remains meaningful, or

b) under the GNU GPL, with none of the additional permissions of this License applicable to that copy.


LECTOR®620



3. Object Code Incorporating Material from Library Header Files.

The object code form of an Application may incorporate material from a header file that is part of the Library. You may convey such object code under terms of your choice, provided that, if the incorporated material is not limited to numerical parameters, data structure lay-outs and accessors, or small macros, inline functions and templates (ten or fewer lines in length), you do both of the following:

a) Give prominent notice with each copy of the object code that the Library is used in it and that the Library and its use are covered by this License.

b) Accompany the object code with a copy of the GNU GPL and this license document.

4. Combined Works.

You may convey a Combined Work under terms of your choice that, taken together, effec-tively do not restrict modification of the portions of the Library contained in the Combined Work and reverse engineering for debugging such modifications, if you also do each of the following:

a) Give prominent notice with each copy of the Combined Work that the Library is used in it and that the Library and its use are covered by this License.

b) Accompany the Combined Work with a copy of the GNU GPL and this license document.

c) For a Combined Work that displays copyright notices during execution, include the copy-right notice for the Library among these notices, as well as a reference directing the user to the copies of the GNU GPL and this license document.

d) Do one of the following:

0) Convey the Minimal Corresponding Source under the terms of this License, and the Cor-responding Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version to pro-duce a modified Combined Work, in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.

1) Use a suitable shared library mechanism for linking with theLibrary. A suitable mecha-nism is one that (a) uses at run time a copy of the Library already present on the user's com-puter system, and (b) will operate properly with a modified version of the Library that is interface-compatible with the Linked Version.

e) Provide Installation Information, but only if you would otherwise be required to provide such information under section 6 of the GNU GPL, and only to the extent that such informa-tion is necessary to install and execute a modified version of the Combined Work produced by recombining or relinking the Application with a modified version of the Linked Version. (If you use option 4d0, the Installation Information must accompany the Minimal Correspon-ding Source and Corresponding Application Code. If you use option 4d1, you must provide the Installation Information in the manner specified by section 6 of the GNU GPL for convey-ing Corresponding Source.)

5. Combined Libraries.

You may place library facilities that are a work based on the Library side by side in a single library together with other library facilities that are not Applications and are not covered by this License, and convey such a combined library under terms of your choice, if you do both of the following:

a) Accompany the combined library with a copy of the same work based on the Library, un-combined with any other library facilities, conveyed under the terms of this License.

b) Give prominent notice with the combined library that part of it is a work based on the Li-brary, and explaining where to find the accompanying uncombined form of the same work.


LECTOR®620



6. Revised Versions of the GNU Lesser General Public License.

The Free Software Foundation may publish revised and/or new versions of the GNU Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Library as you received it spe-cifies that a certain numbered version of the GNU Lesser General Public License "or any la-ter version" applies to it, you have the option of following the terms and conditions either of that published version or of any later version published by the Free Software Foundation. If the Library as you received it does not specify a version number of the GNU Lesser General Public License, you may choose any version of the GNU Lesser General Public License ever published by the Free Software Foundation.

If the Library as you received it specifies that a proxy can decide whether future versions of the GNU Lesser General Public License shall apply, that proxy's public statement of accep-tance of any version is permanent authorization for you to choose that version for the Libra-ry.

3.8.2 GNU GENERAL PUBLIC LICENSE

Version 3, 29 June 2007

Copyright © 2007 Free Software Foundation, Inc. <http://fsf.org/> Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not al-lowed.

TERMS AND CONDITIONS

0. Definitions.

“This License” refers to version 3 of the GNU General Public License. “Copyright” also means copyright-like laws that apply to other kinds of works, such as semiconductor masks.

“The Program” refers to any copyrightable work licensed under this License. Each licensee is addressed as “you”. “Licensees” and “recipients” may be individuals or organizations.

To “modify” a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a “modified version” of the earlier work or a work “based on” the earlier work.

A “covered work” means either the unmodified Program or a work based on the Program.

To “propagate” a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except exe-cuting it on a computer or modifying a private copy. Propagation includes copying, distribu-tion (with or without modification), making available to the public, and in some countries other activities as well.

To “convey” a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying. An interactive user interface displays “Appropriate Legal Noti-ces” to the extent that it includes a convenient and prominently visible feature that (1) dis-plays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion.


LECTOR®620



1. Source Code.

The “source code” for a work means the preferred form of the work for making modificati-ons to it. “Object code” means any non-source form of a work.

A “Standard Interface” means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular program-ming language, one that is widely used among developers working in that language.

The “System Libraries” of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A “Major Component”, in this context, means a major essential component (kernel, window system, and so on) of the specific operating sy-stem (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.

The “Corresponding Source” for a work in object code form means all the source code nee-ded to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's Sy-stem Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For ex-ample, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work.

The Corresponding Source need not include anything that users can regenerate automati-cally from other parts of the Corresponding Source.

The Corresponding Source for a work in source code form is that same work.

2. Basic Permissions.

All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a cove-red work is covered by this License only if the output, given its content, constitutes a cove-red work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law.

You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this Licen-se in conveying all material for which you do not control copyright. Those thus making or run-ning the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted mate-rial outside their relationship with you.

Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary.


LECTOR®620



3. Protecting Users' Legal Rights From Anti-Circumvention Law.

No covered work shall be deemed part of an effective technological measure under any ap-plicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measu-res.

When you convey a covered work, you waive any legal power to forbid circumvention of tech-nological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit opera-tion or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.

4. Conveying Verbatim Copies.

You may convey verbatim copies of the Program's source code as you receive it, in any me-dium, provided that you conspicuously and appropriately publish on each copy an appropri-ate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the ab-sence of any warranty; and give all recipients a copy of this License along with the Program.

You may charge any price or no price for each copy that you convey, and you may offer sup-port or warranty protection for a fee.

5. Conveying Modified Source Versions.

You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:

• a) The work must carry prominent notices stating that you modified it, and giving a rele-vant date.

• b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to “keep intact all notices”.

• c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable sec-tion 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it.

• d) If the work has interactive user interfaces, each must display Appropriate Legal Noti-ces; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so.

A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an “aggregate” if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.


LECTOR®620



6. Conveying Non-Source Forms.

You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:

• a) Convey the object code in, or embodied in, a physical product (including a physical dis-tribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange.

• b) Convey the object code in, or embodied in, a physical product (including a physical dis-tribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyo-ne who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium cu-stomarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge.

• c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercial-ly, and only if you received the object code with such an offer, in accord with subsection 6b.

• d) Convey the object code by offering access from a designated place (gratis or for a char-ge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements.

• e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d.

A separable portion of the object code, whose source code is excluded from the Correspon-ding Source as a System Library, need not be included in conveying the object code work.

A “User Product” is either (1) a “consumer product”, which means any tangible personal pro-perty which is normally used for personal, family, or household purposes, or (2) anything de-signed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, “normally used” refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, indu-strial or non-consumer uses, unless such uses represent the only significant mode of use of the product. “Installation Information” for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.


LECTOR®620



If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of posses-sion and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source con-veyed under this section must be accompanied by the Installation Information. But this re-quirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).

The requirement to provide Installation Information does not include a requirement to con-tinue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network. Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an im-plementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.

7. Additional Terms.

“Additional permissions” are terms that supplement the terms of this License by making ex-ceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the ex-tent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Pro-gram remains governed by this License without regard to the additional permissions.

When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place addi-tional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.

Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:

• a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or

• b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or

• c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or

• d) Limiting the use for publicity purposes of names of licensors or authors of the mate-rial; or

• e) Declining to grant rights under trademark law for use of some trade names, trade-marks, or service marks; or

• f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liabi-lity to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors.


LECTOR®620



All other non-permissive additional terms are considered “further restrictions” within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits reli-censing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.

If you add terms to a covered work in accord with this section, you must place, in the rele-vant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.

Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way.

8. Termination.

You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically ter-minate your rights under this License (including any patent licenses granted under the third paragraph of section 11).

However, if you cease all violation of this License, then your license from a particular copy-right holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.

Moreover, your license from a particular copyright holder is reinstated permanently if the co-pyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright hol-der, and you cure the violation prior to 30 days after your receipt of the notice.

Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been termi-nated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10.

9. Acceptance Not Required for Having Copies.

You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.


LECTOR®620



10. Automatic Licensing of Downstream Recipients.

Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License.

You are not responsible for enforcing compliance by third parties with this License. An “en-tity transaction” is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts.

You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (inclu-ding a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.

11. Patents.

A “contributor” is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's “contributor version”. A contributor's “essential patent claims” are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its con-tributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, “control” in-cludes the right to grant patent sublicenses in a manner consistent with the requirements of this License.

Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and other-wise run, modify and propagate the contents of its contributor version.

In the following three paragraphs, a “patent license” is any express agreement or commit-ment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To “grant” such a patent license to a party means to make such an agreement or commitment not to enforce a pa-tent against the party.

If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. “Knowingly relying” means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your reci-pient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid.

If, pursuant to or in connection with a single transaction or arrangement, you convey, or pro-pagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically ex-tended to all recipients of the covered work and works based on it.


LECTOR®620



A patent license is “discriminatory” if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing soft-ware, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the cove-red work, unless you entered into that arrangement, or that patent license was granted, pri-or to 28 March 2007. Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you un-der applicable patent law.

12. No Surrender of Others' Freedom.

If conditions are imposed on you (whether by court order, agreement or otherwise) that con-tradict the conditions of this License, they do not excuse you from the conditions of this Li-cense. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could sa-tisfy both those terms and this License would be to refrain entirely from conveying the Pro-gram.

13. Use with the GNU Affero General Public License.

Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public Li-cense into a single combined work, and to convey the resulting work. The terms of this Li-cense will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such.

14. Revised Versions of this License.

The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Program specifies that a cer-tain numbered version of the GNU General Public License “or any later version” applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation.

If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy's public statement of acceptance of a version per-manently authorizes you to choose that version for the Program.

Later license versions may give you additional or different permissions. However, no addi-tional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version.


LECTOR®620



15. Disclaimer of Warranty.

THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EIT-HER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRAN-TIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, RE-PAIR OR CORRECTION.

16. Limitation of Liability.

IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PRO-GRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENE-RAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

17. Interpretation of Sections 15 and 16.

If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.

END OF TERMS AND CONDITIONS


LECTOR®620



SICK AG | Waldkirch | Germany | www.sick.com

��

��

��

��

18��

��

��

��

��

��

��

��

� �

Australia��

�� E-Mail [email protected]

Belgium/Luxembourg�� !"��#$%&'�

Brasil�� !"��$"#$%&�(&'�

Ceská Republika��E-Mail [email protected]

China�� E-Mail [email protected]

Danmark��E-Mail [email protected]

Deutschland�� E-Mail [email protected]

España�� !"��#$%&�$

France�� !"��#$%&��

Great Britain�� !"��#$%&�&)%

India�� !"��#$%��*"&�(

Israel��!"��#$%�$��$��$&�(

Italia�� !"��#$%&�

Japan�� !"��$)++��#$%&,+

Nederlands�� !"��#$%&��

Norge ��!"��")$��,��*#$%&��

Österreich�� !"��#$%&"�

Polska�� !"��#$%&+�

Republic of Korea�� /��!"��#$%%��"&��

Republika Slovenija�� !"��#$%&$

România�� !"�� #$%&��

Russia�� !"��#$%�")��("��&�)

Schweiz�� !"��"�#$%&�

Singapore�� E-Mail [email protected]

Suomi�� !"��$%#$%&�

Sverige��!"��#$%&$�

Taiwan�� !"��$"��$#$%&�(&�0

Türkiye��!"��#$%&�(&��

United Arab Emirates��!"��#$%&"�

USA/Canada/México�� !"��#$%)$"&�(

!��+��$��"�1�$�"�*�"2��$��"��(",��*)$��"��"��$�"��www.sick.com

LECTOR®620 LECTOR 620 Image-Based Code Reader Lector 620 Operati… · LECTOR®620 ONLINE HELP...

Documents

Transcript of LECTOR®620 LECTOR 620 Image-Based Code Reader Lector 620 Operati… · LECTOR®620 ONLINE HELP...