Code Verification
116 topics in this forum
-
- 0 replies
- 244 views
When an operator selects "GS1 General Specification" as the Application Standard, there are really two processes going on. First, the LVS-95XX software checks the print quality based on ISO/IEC 15415/15416 (that's all the grades for contrast, defects, etc.). Simultaneously, since you have told the software to expect a GS1-formatted symbol, it checks the symbol against the requirements of the GS1 standard itself, one of which is the "x-dimension", or the width of the narrowest bar or element in the symbol in thousandths of an inch or "mils". Other criteria are also included, such as barcode height, etc., depending on your symbology. Each of the 11 GS1 Symbol Specification …
Last reply by Omron Forums Support, -
Each LVS-95xx can be identified via a “reference” name, which could be the unit serial # or factory production area for example.When the data archive is exported to a mapped network folder into a database such as Excel, using a vertical bar field separator, it will include a field that has the reference name for each record in that file.The files can then be manually combined if desired into a single file where the reference field would be used to denote which LVS-95xx that record came from.
Last reply by Omron Forums Support, -
In the LVS-95xx software setup page exists the option to the user to configure software to either warn with a message or Fail the symbol (forcing an F Grade and providing the message) if the height or X-dimension are outside the specified range of the Symbol Specification Table under consideration. This is selectable when any of the GS1 Application Standards are used. Further, LVS-95xx automatically provides the correct aperture as well as the X-dimension (maximum and minimum) for the Table being used. This helps ensure that the barcode is compliant with the full requirements of the GS1 Application Standard that is relevant for the barcode being graded.
Last reply by Omron Forums Support, -
- 0 replies
- 193 views
In the C:\Users public folder add a folder such as LVS-9510. Then open the LVS-95xx software, go to archive tab, select the Change SQL Connection button,and paste the string as an exact match (highlighted in red font below) only by changing the to the red font text below in the data source = then click OK. Then select yes on all popups and the software will copy the database over to the specified folder. The user MUST leave the end of the file path EXACTLY AS IS in the path on the data source =. C:\Users\Public\LVS-9510\LVS-95XX\LVS-95XX.mdb
Last reply by Omron Forums Support, -
- 0 replies
- 186 views
This most likely is due to the contact sensor size being changed or reverted back to it's default setting, which is 5". To fix this, go into the settings menu, search for "contact sensor" and change the value from 5 to 8. Save, close the software and restart. Software Version 20.2.xxx Operating System Any
Last reply by Omron Forums Support, -
- 0 replies
- 224 views
After the user enables the AutoScan check box an error occurs. Run-time error '380': Invalid property value Solution is to delete the AutoScan.dat file from the Jobs folder
Last reply by Omron Forums Support, -
- 0 replies
- 206 views
RIMS will access the file Operator.dat but it looks like RIMS doesn't have a utility to create the file. I don't see where it gets the file so it may be that you have to copy the file from the 7000 and paste it into the folder with the Rims.ini file.
Last reply by Omron Forums Support, -
- 0 replies
- 430 views
The issue is that the factory calibration file (.mdb) was not copied and renamed to the correct folder on the PC. There are several solutions to this issue. Please follow the instructions in the manuals - Appendix J to correct the problem. Manuals are downloaded during install or can be downloaded from the following link to our download center. http://www.microscan.com/en-us/support/download-center Please copy the .mdb file found on the original install media. The format of the name is likely Product Model #_Serial #.mdb (Example LVS-9510-16298.mdb) and place it in correct folder Then rename it to the same name as the folder. (Example for Software version 4.1.0 and forwar…
Last reply by Omron Forums Support, -
- 0 replies
- 212 views
If 7000 won't start, or has an error stating "Initialization Failure" Look for Mfe64Mil9.exe in the Task Manager and kill the process.
Last reply by Omron Forums Support, -
- 0 replies
- 243 views
When the 7510 software opens it looks for configuration files and template information in specific locations on the local drive or network drive. When this information can't be found due to folders being moved, or the network drives not being accessible the software does not open and it returns runtime error 52. Operating System Any
Last reply by Omron Forums Support, -
- 0 replies
- 214 views
This error usually occurs when there are not have enough labels present in the viewing window. When using the automatic setup feature, be sure to "zoom out" to see at least three entire labels in the viewing window. This is necessary for the software to detect a label. Operating System Any
Last reply by Omron Forums Support, -
- 0 replies
- 286 views
If the read head and light tower USB's have been switched around on the computer the operating system has trouble distinguishing them Please reference the attached Word document for the solution to 7500/7510 USB Device not recognized. Disconnect the read head USB and the light tower USB and follow the procedure in figure 1Follow the steps in figure one to remove the existing ports and drivers for the read head and light tower. When removing the USB device, check the box next to delete driver. Right click "Command Prompt" in Accessories and choose "Run as Administrator" - important!Enter "set devmgr_show_nonpresent_devices=1" (without quotes)Enter "start_devmgmt_msc"I…
Last reply by Omron Forums Support, -
- 0 replies
- 193 views
For a 7000 system, the Lvs7000.ini file can have the Power Distribution Board (PDB) outputs configured as follows to communicate with the PLC: [PLC] DataValidOutputLine=3 DataValidDwell=20 PassOutputLine=4 FailOutputLine=5 Output lines are the Power Distribution Board output ports. The DataValidOutput is set after the Pass and Fail outputs are set. Dwell time is in milliseconds that the DataValidOutput signal lasts. NOTE: - The above port numbers are the only ports known to work for these signals as of this writing. - If the Pass output is set, it will remain set until the Fail output is set. - If the Fail output is set, it will remain set until the Pass output is set…
Last reply by Omron Forums Support, -
- 0 replies
- 177 views
After completing calibration in a 7000, one of the following errors occur: - Run-time error '62': Input past end of file - The file "C:\Users\LVS7000\AppData\Roaming\Label Vision Systems\LVS 7000\CalHistory.csv" has no data available SOLUTION: Move the "Cal*" files to a backup directory and rerun calibration. Calibration should now be successful. History from the backup file may need to be added to the new file created in case keeping the backup file is not sufficient. Operating System Any
Last reply by Omron Forums Support, -
- 0 replies
- 674 views
<FNC1> is a "non-printable" special character reserved for GS1-compliant symbols when using Code 128, QR code or Data Matrix symbologies. It is what indicates that a symbol is a GS1-128 symbol, for example, rather than just a regular Code 128. If “GS1 General Specifications” is selected as the Application Standard on the “Setup” tab, and <FNC1> is not encoded in the first position of the code, the code will automatically be graded an “F” since it is not GS1 compliant (see bottom image). If the code is intended to be GS1 compliant, notify the originator that GS1 requires <FNC1> to be present at the start of the symbol. If you are not grading a GS1 barcode…
Last reply by Omron Forums Support, -
- 0 replies
- 291 views
The "Resetting camera..." message appears and the background activity occurs when there has been a loss of USB connectivity with the LVS-95XX verifier, specifically the camera (see screenshot below): When the LVS-95XX software detects it is no longer in communication with the camera, it attempts to reset the connection. Prior to adding this reset logic in version 4.3.0.3006 and later, the software would throw a "fatal error" message and crash. With this new logic, the software doesn’t throw the fatal error and crash the software, rather opting to show the "Resetting camera..." message and attempting to regain connection with the camera. If/when the camera is found onc…
Last reply by Omron Forums Support, -
- 0 replies
- 209 views
-
- 0 replies
- 198 views
-
- 0 replies
- 201 views
-
- 0 replies
- 1.1k views
Issue: When using an LVS-95XX Series barcode verifier, a user may come across labels that produce significantly lower grade scores that exhibit two specific symptoms: 1. Modulation and Reflectance Margin grades dramatically lower than most other graded criteria. 2. Modulation and Reflectance Margin grades that are exactly or nearly identical to each other. While these symptoms may still be present, a different grade may even be generated if the label is graded on another LVS-95XX model, such as an LVS-9510 vs. an LVS-9580. Labels exhibiting these symptoms are most likely using a problematic label substrate material. Explanation: The reason for this is that ISO s…
Last reply by Omron Forums Support, -
- 0 replies
- 226 views
Introduction: Purpose: This guide is a last resort process to help correct calibration failures with the UID devices. This manual exposure adjustment should only be used if the UID Normalization software fails to calibrate the UID device. Explanation: This guide assumes working knowledge of the UID products, Terminal Emulators, and setting up a connection between the two. The instructions in this guide will explain what commands need to be sent to the UID device to check/update the UID device LightingType’s Exposure value as needed to obtain a successful calibration. This process is not 100 percent guaranteed to work. Supported Devices: UID-CHK003 - UID COMPLIAN…
Last reply by Omron Forums Support, -
- 0 replies
- 965 views
Introduction: Purpose: This Guide will walk you through the process of installing the UID Checker Software on Windows 10. Explanation: The UID Checker software was not built to run on Windows 10. When initially trying to install the software on Windows 10, the installer will throw a pop-up message that states that the software can only be installed on Windows 2000, Windows XP or Windows Vista. However, Windows 10 does have a compatibility mode feature that allows you to install software built for earlier version of Windows. This guide will show you how to install the UID Checker software on Windows 10 in compatibility mode. Supported Devices: UID-CHK003 - UID CO…
Last reply by Omron Forums Support, -
On rare occasions, the error below may appear when using an LVS-95XX-series barcode verifier: This can occur with LVS-9580/9585 models made after May 2018 and all LVS-9570 models. If you encounter this error, please attempt the following steps first: 1. Ensure the verifier is plugged into a known-good USB 2.0 port prior to starting the software. 2. With the software closed, try changing USB ports. 3. Reinstall the LVS-95XX software package including all drivers using full local PC admin rights. If, after taking these steps, the error is still present, it is possible that the device may have had its internal serial number reprogrammed by the so…
Last reply by Omron Forums Support, -
This technical note intends to provide a single resolution path for those experiencing the issues discussed; it is ONLY for those users experiencing any of these issues. Previous technical notes have documented two separate but related camera issues on a limited number of installations of the LVS-95XX-series barcode verifiers and accompanying software. The first is a “Camera resetting” error message that is accompanied by the camera image alternating between pure white and pure black without input from the user. The second is the presence of varying amounts of image “artifacts” or streaks being displayed in both the live video feed (when positioning the …
Last reply by Omron Forums Support, -
- 0 replies
- 258 views
The GS1 General Specification is freely-downloadable directly from the GS1 organization. The main GS1 website is www.gs1.org, though there may also be region or country-specific GS1 websites such as GS1 US (www.gs1us.org). The GS1 General Specification can generally be found in their Resource Library in PDF format. As of GS1 Gen Spec v20, the tables can be found in Chapter 5.10 (subject to future changes).
Last reply by Omron Forums Support,