Omron Forums Support

Go to C:\LvsData\LVS 7500 folder Backup CalHistory.csv in another location if desired. Remove all three calibration files CalHistory.csv & Calibrate.log & Calibration.bin then run calibration again.

Initially reported as a synchronization issue with re-running an existing job which had worked on previous occasions. Repeated trial of smaller & wider sync slices, as well as various positions, including slightly off web, and narrow to the point of including an area just larger than the gap between labels yielded no success. Looking at the zoom window area, horizontal lines can be seen. A Venetian blind effect. This caused enough interference in trying to sync properly, that resolving this condition resolved the sync issue. Ultimately it was found that an aging power supply was causing the light to flicker just enough for the camera to notice, but not the human eye. Replacing the power supply resolved the horizontal line issue, and a new job was created and synchronized successfully. Operating System Any

Setting the LVS7000 system to present options for Auto setup or Manual setup can be found in the INI file settings. AutoSetup tells the software when to use the LVS® 7000 automated process when creating a new job. Under the [System] A5Follows=34 AcceptReplaceInputTimer=0 AddMissingTriggers=0 AutoBreakRoll=0 AutoLogin=0 AutoMakeReady=0 AutoSetup=1? o AutoSetup=0 – Turns on manual setup when creating a new jobo AutoSetup=1 – Shows a pop-up that allows a user to choose if they want to use Auto or Manual setup when creating a new job.o AutoSetup=2 – Uses Auto-Setup when creating a new job Operating System Any

If no image is recorded by the LVS 7000 Put the software into calibration mode If an image is present in calibration mode skip to step 6If picture is still black check the camera link cables and power cable. The camera has a red light that indicates if it is powered. Shine a flashlight into the camera. This will help determine if the camera is miss aligned. If camera is misaligned, the light should be present in the image.Move the camera around in the mount until the image is visible. This may take moving the disc and the angle of the mounting plate. If image is present in calibration mode, but is still not present when running the press, check the encoder and insure it is rotating on the idler. If images are broken, make sure encoder is not slipping then clean the encoder on the idler Operating System Windows 7

If images are not being collected during normal operation, but images are updating during calibration: Use HyperTerminal to insure encoder pulses are being seen by the encoder board by sending command [l-]. A positive returned number indicates forward motion, if E0, E1 bounce is all that is seen it is running in reverse. The 7000 only collects images in forward motion. Check encoder wheel is making contact with idler. If the 7000 never captures images in operation or calibration: Test that the camera has connection/communication via manufacturer supplied GUI. If no response, test cable connections, retry.Swap Camera Link cables. Software Version All Firmware Version All Operating System Windows 7

If the camera is a Basler camera, this is a known issue resolved by replacement of the power supply with a Basler power supply. Basler 2000031201, Power Supply, 12V DC/HRS 6-pin, for all 6-pin Basler GigE cameras can be purchased through https://graftek.biz/. If this is through a camera other than Basler, it more likely to be a cabling issue, or power surge. New Camera Link cables are suggested if there is no known power surge / brown-outs. Software Version All Firmware Version All Operating System Windows 7

Look at the linelight: Are there labels stuck to the light lens?Are there dark areas along the light array as if LEDs may be out? (Using dark sunglasses or squinting will help to identify.) Has the system been moved or camera placement altered? This can also occur is a web wrap-up occurred in the camera /light location. If so a FFC (Flat Field Correction) may be required. Software Version All Firmware Version All Operating System Windows 7

Depending on the press and camera mounting positioning, there is a possibility of vibration transferring from the press into the camera mount. Check the camera lens to insure it is secure.Check all mounting hardware to insure the camera mount has not shaken loose over time. The mount may feel secure, but a bolt being slightly loose is all it take to cause movement.It is best to check all connections with a wrench.If all connections are solid, try running the press at a slower or faster speed to minimize the amount of shake in the machine. The press may have a certain speed that causes resonance, and by changing the speed of the press, this can be eliminated. ` Operating System Any

LVS7000 image is completely black Please check: Line light is ON Lens is not covered or otherwise obscuredLine light is aligned to correct focal point Software Version All Firmware Version All Operating System Windows 7

LVS7000 CPU is maxxed out, and PC is unresponsive after starting a job. "Mfe964.exe" process is at 99% in Task Manager. Indication that an inspection is hanging up, and the system is unable to complete this inspection, or process any further inspections. A. Try restarting the software. B. Try soft and hard reboots of PC. C. Check that all camera cables at both ends are secure, no glitches in image. If the above steps offer no resolution, open the currently failing job (without running any web) to see what inspections are taking place, as this could be a job specific issue. - Make note of each sector, in order, for what the inspection is, and any match conditions, etc. - Create a new job, jog the web, and recreate each of the sectors noted (one at a time) to see which is failing. Once the failing inspection condition is found, take appropriate steps to resolve. This could be any number of things, depending on the inspection. For example, an OCR/OCV inspection sector which yields no return value, could be hung up on an improper font. The font may be the incorrect type, may be corrupted, or may not be properly trained. The sector could be too large (or small), or contain other graphics irrelevant to the text to be decoded. The direction selector could be wrong. Software Version Any Operating System Windows 7

The ColorMode for most color cameras should =1 in the LVS7000.INI file. [SystemConfiguration] CameraPort=0 ColorMode=1 DistanceMethod=1 EncoderPort=4 MaxSpeed=500 LinesPerInch=341.333 PageBreaks=1 RimsBarcodePlacement=0 ShowPrintBarcode=0 The Dalsa Color 8K camera must be ColorMode=2. Within the LVS-7000 program pressing the button combination [Ctrl]+[W] will open the Bayer color control screen. This will allow changing the Pixel lookup matrix by clicking the correct matrix. COMMIT must be pressed to insure the updated data is loaded as new default values. Software Version All Firmware Version All Operating System Windows 7

Set Auto Stop = 1 in LVS7000.ini to get this feature

Problem: Starting 7000 software, the following MFE Fatal Error appears: "Opening encoder on COMx: FAILED" Problem: Starting RIMS software, the following Fatal Error appears: "Unable to access COMx" Solution: 1. Check Device Manager for proper encoder COM port: (USB Serial Port (COMx) 2. Verify that the Lvs7000.ini or Rims.ini file "EncoderPort" line matches what Device Manager reports: [SystemConfiguration] EncoderPort=5 3. If there is no "USB Serial Port (COMx)" line shown in device manager, check the back of the PC to ensure that there is a known good USB cable connecting the IO-Encoder Board to any available USB port on the PC: 4. Other items to check: a) Beige 44-pin cable is securely connected to both the IO-Encoder Board, and the Power Distribution Board. b) Power Distribution Board has power (circuit breaker on). c) Encoder is connected properly and has power. d) Fuse is not blown. e) Relay is functional. 5: When you first plug in the LVS-7000 / RIMS hardware (box or cabinet) and flip the circuit breaker on, you should see a green light on each of the two blue power supplies, as well as a single green light on the Power Distribution Board (labeled “PWR.SUPPLY”). Then, when you turn the PC on, you should hear a click from the relay on the Power Distribution Board, and two more green LED’s should light up (one next to the “PWR.SUPPLY” LED, and one at the other end of the board labeled “12V”). (Photo of example Power Distribution Board with PC on below.) If you don’t see the lights as mentioned above, check that the fuse on the Power Distribution Board is not blown. 6: Example Power Distribution Board, with PC on: Operating System Windows 7

If end user is unable to suspend or disable Trend Micro AV, it can prevent the LVS software from installing. Disable Trend Micro and install. Then please submit a 'false positive' report at https://success.trendmicro.com/solution/1115860-reporting-a-false-positive-issue-in-worry-free-business-security-wfbs

When LVS7510 is integrated to the Zebra Xi4 series printer, the tear off position should be at maximum value (+120). Software Version 20.2.x.x Operating System Windows 7

How to fix the Autoscan Run-time ‘380’ error Issue. Navigate to the following address C:\Users\LVS_7000\AppData\Roaming\Label Vision Systems\LVS 7000\Jobs\LVS 01 LVS_7000=Computer name LVS 01=Specific job folder name Rename the AutoScan.dat file to AutoScanxx.dat Start the LVS 7000 Software and execute the job like normal. Check the Autoscan box. The function should now work. Shut down the LVS 7000 software navigate to the job folder listed above. It should have created a new Autoscan.dat file. Delete the old renamed Autoscanxx.dat file. Software Version 5.6.4 Operating System Windows 7

Below are MFG Part Numbers From Microscan (5M) and TURK versions (10M, 15M, 30M) Common M12-12 pin Plug to M12-12 pin Socket Cordset: Microscan, 61-9000117-01, CORDSET, COMMON, M12 12 PIN PLUG TO M12 12 PIN SOCKET Turck, RKC 12T-10-RSC, M12 12 Pin Plug to 12 Pin Socket – 10M Turck, RKC 12T-15-RSC, M12 12 Pin Plug to 12 Pin Socket – 15M Turck, RKC 12T-30-RSC, M12 12 Pin Plug to 12 Pin Socket – 30M Ethernet M12-8 pin Plug to Standard RJ45 Jack Cordset: Microscan, 61-9000118-01, CORDSET, ETHERNET, M12 8 PIN PLUG TO RJ45, 5M Turck, RSS RJ45S 841-10M, M12 8 PIN PLUG TO RJ45 – 10M Turck, RSS RJ45S 841-15M, M12 8 PIN PLUG TO RJ45 – 15M Turck, RSS RJ45S 841-30M, M12 8 PIN PLUG TO RJ45 – 30M NOTE* Plug = Male connector Socket = Female Connector

Error Message *Windows could not install drivers". For the older Visionscape and DMx AutoID+ hardware keys: http://www3.safenet-inc.com/support/hasp/hasp4/enduser.aspx For the newer GigE Visionscape keys (4.0+), they need the HASP HL drivers: http://www3.safenet-inc.com/support/hasp/enduser.aspx

SCDI and DOAL are the same. Red, Blue, & IR = 50Reflect / 50 Transmit White = 30Reflect / 30 Transmit

The attached file gives some ideas on the differences between NL-200 Series and LC-50/LC-100. kA23800000008EyCAI_en_US_1.pdf

The Laser scanners are capable of reporting the number of decodes within a read cycle. Symbol quality can be guaged by comparing the number of decodes within the read cycle to an expected number of decodes. For true verification, you can use the Hawkeye 1500 series or Visionscape. To judge the number of decodes on a good sample, set Parameters / I/O / Quality Outputs / Number of Decodes to Enabled. Go into the Terminal view and watch the decoded output of parts moving by at normal speed; you will see a five digit number following the symbol data that represents the number of decodes during the read cycle. Next, run some samples of bad codes and monitor the number of decodes. Use the difference between the two outputs as the scale of a good code and a bad code. Once you have determined the threshold between a good code and a bad code, you can program a discrete output to fire on Trend Analysis. Set the Decodes/Trigger to the determined value, and the output will fire when the number of decodes falls below the threshold. Reference the User's Manual of any product to learn more about Reads/Trigger or Decodes/Trigger.

* check to see if it is a strobe unit. If it is, you will need to use a strobe controlled. * Be sure to use a current controller to prevent damage to the light. The pinout of this light can vary. The current pin-out should be power on pin 1, and ground on pin 3. The pin-out can also be power on pin 1, and ground on pin 2. The wire colors of the black cable with a green over-mold on the 4-pin M12 connector is: 1 = Brown 2 = White 3 = Blue 4 = Black

The OCV Fontless tool will group touching characters as a single character to be inspected. However if a OCVRuntime or a OCVFont tool is used, a library must be created for each character inspected. This allows the OCVRuntime or OCVFont tool to be able to train a code that has touching characters. Please remember to increase the "Allowed Overlap During Read" found in the LayoutStep datum (tab). For most applications I set this to 5 pixels.

During the installation if the CRC error relating to the readme file is displayed. The user can click Ignore and allow the installation to continue. The installation will complete and the I-PAK software will run properly The I-PAK VH error message is shown below Operating System Any

A sample 1 camera equipment list has been created for the I-Pak HE and I-Pak SE configurations I-Pak HE sample equipment list https://na3.salesforce.com/00P500000055XpR I-Pak SE sample equipment list https://na3.salesforce.com/00P500000055XpX