Omron Forums Support

The problem could be that the Visionscape I-PAK HE software cannot communicate to the camera. 1. Shut down I-PAK user interface. 2. Cycle power for each camera by removing the cable from the X1 connector. (9 o'clock position if the camera is oriented so that the small connector is the 12 o'clock posiion.) 3. Wait 1 minute. 4. Restart PC with I-PAK. When I-PAK starts it might ask user to select a camera. 5. Once started, click the setup button and use change product to select the desired job.

When a Visionscape job file is moved from one PC to another, auxiliary files are often not moved or the location of the auxiliary files may be different. This is also a problem when the scripts are moved from different versions of Visionscape. The key to understanding this situation is the "perlscr" file typically found in the "C:\Vscape\Jobs\perlmod" folder. This file is itself a Perl script and is run when a script file is added to the job. If the perlscr file has an error then the error will be displayed in the Visionscape debug window. If a script called out by the perlscr is not available then a warning message "Can't locate xxxx.pm" describing the script than cannot be found and the location where the script is expected to be will show in the debug window. There will also be an error message "Error parsing or unable to open script file C:\vscape\jobs\perlmod\perlscr". One solution to this would be to comment out the line in the perlscr file that contains the script that is missing and causing the perlscr to fail to load. The "#" symbol should be used as a comment. One other situation that may happen is that the VisionSystemStep datum "Support File Root Directory" may be incorrectly set to a path that includes the MAC of the Visionscape Smart Camera rather than the default "C:\vscape\jobs\" and should be reset to this default. So the key is to use the Visionscape debug window and ensure the perlscr file is able to be parsed correctly.

This is not an issue in VS 7.0.3 (AV 3.0.3), but in VS 8.0.1 (AV 4.0.1) if you are using a Emulator or GigE system, you should set you Dwell time to 0. This is necessary for modern multicore pcs to function properly with any sort or wait or pulsed IO step. If this is not set, you may see inspections suspend and the job hang. This Dwell Percentage datum is found in the Vision System step as highlighted in the attachment. Software Version VS 8.0, AV 4.0

Reference the ReadMe.wri file for the Visionscape 4.0 release where it states that “LogicTech Setpoint program is known to make Visionscape 4.0.0 software inoperable. Please uninstall the LogicTech Setpoint software prior to installing Visionscape 4.0.0." Similar problems have been reported with other mouse drivers as well. Work-around: Uninstall mouse driver software before installing Visionscape.

Install latest Visionscape software 3.7.1.13 or later. Update firmware in Visionscape Smart Camera To correct the runtime display issues, create a new job.

A common issue with some older laptops, including Dell Latitudes, is that FrontRunner will lock up part way through the loading process. This is caused by the 'Real Time Priority' setting. Older laptops can't handle the Real Time operation, and so the priority will need to be adjusted. This document will help resolve a lock-up issue for laptops running Visionscape 4.x with a GigE Camera attached. kA23800000008IxCAI_en_US_1.pdf

the attached document Discusses modification of the dm.config file, and also explains what will happen if a camera is swapped. kA23800000008JSCAY_en_US_1.pdf

1. Shut down Visionscape Backplane. 2. Move USB license key to different port. After connection should see the end of the key light up . 3. If key doesn't light up, try Downloading the latest HASP HL drivers from: ftp://ftp.aladdin.com/pub/hasp/Sentinel_HASP/Runtime_%28Drivers%29/Sentinel_HASP_Run-time_setup.zip Reinstall these drivers on your PC. 4. Start the Visionscape Backplane at the local PC. Note *The GigE license is NOT detected if the user is logged into the PC via a Remote PC.

Visionscape uses 8 bit gray scale tif images or 24 bit color tif images. when loading images from file, you also have the option to load bitmap files.

In Setup go to Advanced Settings > System Settings > General tab. Enable the Always on Top option. Shutdown Visionscape I-Pak and restart the computer. After the computer has rebooted and Visionscape I-Pak starts all of the camera windows will be displayed at runtime.

Vignetting is seen when using the Tamron 25mm #lens (P/N: 98-92800574) with the 5 mp #gige camera - CMG50 (P/N: 98-000120-01). This is a lens issue, not a camera issue. Also tried the Tamron 50mm #lens (P/N: 98-92800576) and there is very little vignetting.

The Vision HAWK and Vision MINI will refuse to boot with many of the LED indicator lights remaining on if the following conditions are met: 1) The serial port is set to VxWorks (via the "BP_UpdateConsoleTTY 2" command and 2) The serial port is floating (not connected to anything). The workarounds currently are to either connect the serial port (grounding the Rx and Tx are sufficient or to set the serial port connection to none or VsApp ("BP_UpdateConsoleTTY 0" or "BP_UpdateConsoleTTY 1").

Can the Vision Hawk lens be changed in the Field? In it's current state, there is no documented procedure on how to swap the lens, so swapping lenses is not supported.

Follow these instructions to attempt to correct the problem: Boot the camera to [SAFE-KERNEL] modeBP_Dumpcd “/tffs0/Config/Focus”xdelete “*.acq”reset Operating System Any

JobOCR toolSegmentationLibraryMax Rate (ppm)Process time (ms)OCR_ArialTest00.avzOCR toolAutoSizeAlphaNumeric230170OCR_ArialTest01.avzOCR toolAutoSizeNumeric270125OCR_ArialTest02.avzIntelliText OCRDefaultAlphaNumeric180234OCR_ArialTest03.avzIntelliText OCRDefaultNumeric205190 Image: SXGA (1280x960) ROI: 450 x 120 Char: 36 pixel height OCR tool only - No locator, no data valid Visionscape 7.0.2.17 Software Version VS 7.0.2.17

VisionHAWK Ethernet/IP Explicit Messaging Example VisionHAWK does support explicit messages and this is going to be the easiest way to communicate as you will be able to pull the data from the Micrologix controller. You will need to do a few things to get the job to output the data to the Ethernet/IP assembly and this is an easy process. The steps are outlined below; 1. Set the output data in the Ethernet/IP Assemblies in AutoVision. a. Open Autovision. b. Connect to your VisionHAWK. c. Add the OCR Tool. d. Link the OCR Tool data to the Ethernet/IP Assembly. Each link represents the available data that one can link to the Ethernet/IP assemblies and I’ve highlighted what the OCR tool has to offer. 1. Pass/Fail Status: Status bit for the OCR Tool a. 1 = OCR Inspection Passed b. 0 = OCR Inspection Failed 2. ASCII String Data a. This will be a STRING in the PLC, so the first 4 bytes will be the length of the string (size DINT) followed by an SINT array of 2044 bytes. 3. Number of Characters Found: The total number of characters found in the inspection by the OCR Tool. This will be same value as the LEN in the STRING above. e. Click the Link button in the OCR Tool Example 1. Linking the OCR Tool Inspection Status bit The link chain will highlight green after you set the link 2. Linking the OCR Tool Inspection ASCII Data The link chain will highlight green after you set the link 3. Linking the OCR Tool’s total number of characters found The link chain will highlight green after you set the link f. Verify that the data link is correct by running the job once as a test by click in the Run Once button. g. Click the Data Navigator to see the data. h. Download the Job to the reader. 2. Configure the MSG instruction to read the Ethernet/IP Input Assembly explicitly. a. Reference Page 2-14 through 2-17 on the Assembly, class and instances to read the data that was linked above. b. Example i. Read the OCR Inspection Status bit set above which was assigned to BOOL1. In page 2-15: Service Code: 0xE (Get Attribute) Class: 0x68 (Class 104) Instance: 0x1 (Always 1) Attribute: 0x1 (Refer to page 2-15 for the attribute value) ii. Read the OCR ASCII Data that was set above which was STRING1. Service Code: 0xE (Get Attribute) Class: 0x6c (Class 107) Instance: 0x1 (Always 1) Attribute: 0x1 (Refer to page 2-15 for the attribute value) iii. Read the total number of characters found in the OCR Inspection Tool that was set above which was INT1. Service Code: 0xE (Get Attribute) Class: 0x69 (Class 107) Instance: 0x1 (Always 1) Attribute: 0x1 (Refer to page 2-15 for the attribute value) You’ll need to set the MSG instruction in the RSLogix500 program to make sure communication is established and that the controller can read the data from the unit. I’m not 100% sure on how to do this as I’ve not personally done it before. You’ll need to find a way to read the data using CIP (Common Industrial Protocol) and in the 1766-rm001 manual states that this can be done when creating the Message File and setting the sub element 2 to 1 (CIP) and making your Target Device = CIP Generic in sub elements 12 to 15. Chapter 22 has an example on configuring an Ethernet/IP Message so you should be able to get things to work from this point on. Operating System Any

The following procedure will change the appropriate settings in the VisionHAWK to allow the camera to focus properly after the lens has been changed. kA238000000086HCAQ_en_US_1.pdf

VisionHAWK C-Mount WVGA processing times using AutoVISION 3.0.1.6 Max Trigger rate is the same if FrontRunner, AutoVISION or I-PAK is used as the UI Character size = 20x28 (high contrast thermal print on white label) InspectionMax Trig/SecMax PPMOCVFontless – 10 character, No AutoFind locator13.2792OCVFontless – 20 character, No AutoFind locator10.3618OCVFontless – 10 character, +/- 1 character AutoFind locator10.3618OCVFontless – 20 character, +/- 1 character AutoFind locator8480OCVFontless – 10 character, +/- 2 character AutoFind locator8.7522OCVFontless – 20 character, +/- 2 character AutoFind locator6.9414Barcode - Code 128, 0 degree rotation, trained171020OCR tool - 10 character8.2492OCR tool - 20 character5.1306+/-2 character Intellilifind Locate (Outline only, +/-10 degree rotation, scale off) and OCR tool - 10 characters6.1366+/-2 character Intellilifind Locate (Outline only, +/-20 degree rotation, scale off) and OCR tool - 10 characters4.2252Intellifind with +/- 2 character search (Outline only, +/-10 degree rotation, scale off)11660 Software Version VS 7.0.1.6

Press the AutoVISION button and connect power to the VisionMINI / VisionHAWKWait approximately 30 secondsOpen a command prompt window For a VisionMINI type in the following command Telnet 192.168.188.10For a VisionMINI Xi type in the following command Telnet 192.168.0.100For a VisionHAWK type in the following command Telnet 192.168.0.10Press the Enter key and you should see the prompt, [SAFE-KERNEL]Enter the following commands, Followed by the enter key: (case sensitive) BP_Dumpcd “/tffs0/Config/Focus”xdelete “*.acq”reset Operating System Any

The Telnet Client needs to be enabled on Windows for simple "Terminal-style" Ethernet communication with Readers, Imagers or Smart Cameras.Execute the attached WSF File (Windows Script File) and the Telnet Client will be automatically enabled on Windows.You need to perform this operation only once. Operating System Windows 7

Summary Tests were run using an ID-20 and a Raspberry Pi3 SBC running Raspbian to determine to what extent the ID-20 is compatible with this hardware / software combination. It was found that, if the ID-20 has a static IP address, then WebLink and Telnet can both be used to talk to the reader. However, the virtual com port cannot be accessed from Linux Initial Network Configuration 1. Starting with a clean Raspbian operating system. Set up your wifi or wired network for internet access if required. 2. Go to network icon in top-right of menu bar and right-click on it. 3. You'll see two network adapters listed if you click on the interface drop-down – wlan0 and eth0 Now plug in your ID-20 (configured for static IP address) ifconfig from terminal will show additional adaptor eth1. There is no graphical tool for configuration ethernet interfaces. Instead, you have to edit /etc/network/interfaces. You can do this as follows: Open a terminal windowNavigate to the correct directory ( cd /etc/network )make a copy of the interfaces file ( sudo cp interfaces oldinterfaces ) Open interfaces file with nano ( sudo nano interfaces )scroll down to end of file and type in the followingallow-hotplug eth1 iface eth1 inet static address 192.168.188.1 netmask 255.255.255.248 gateway 0.0.0.0 Once you've typed that in, Control-O and Enter to save and Control-X to exit. To check that it worked you can type in “more interfaces” to see the contents of the interfaces file. Now unplug the camera and plug it in again. You can see the network settings by using the ifconfig command in the terminal window. At this point you can open Chromium (web browser) and navigate to the address of your camera to bring up WebLink just as you can on a Windows PC. Testing with WebLink through browser. WebLink works exactly the same on Linux as it does on Windows. Testing with Telnet from command line Note that telnet is not installed by default on Raspbian. sudo apt-get install telnet to do this. Problems were encountred accessing mirror servers for packages, unplugging the MicroHAWK from Raspberry Pi appeared to help solve these issues. This suggests that the software was trying to use the wrong network adapter to access the servers. Once telnet was installed it worked just as it does on Windows. Remote triggering from another PC. Set up SSH on Raspberry Pi. You enable this by going to the Pi menu - Preferences - Raspberry Pi Configuration - Interfaces. You should probably change the default password for security here and the Pi will nag you if you don't. Connect to Raspberry Pi SSH from PC using program like PuTTY. Port number for SSH is 22. You can then enter commands just as you would if you were running on the Pi directly. Adding Additional Cameras Adding additional cameras requires adding additional information to the /etc/network/interfaces file. Here's a screenshot showing two ID-20 MicroHAWK cameras connected to Raspberry Pi. Tests have not yet been run to ensure that multiple cameras enumerate in the same order every time the Pi is powered up. Using Dynamic IP Addressing At this point in time it has not been proved possible to connect Raspbian to an ID-20 set to DHCP. Tests were run with both static and DHCP (APIPA) on the Pi. Using VCOM to communicate with ID-20 VCOM does not work on the Pi3 / Raspbian (or any other version of Linux tested). The cause for this is believed to be the lack of support for composite USB devices in Linux. Looking on the web, it appears that there are a number of devices that have the same problem on Linux and that these have been hard-coded into one of the linux driver files (/drivers/usb/class/cdc-acm.c). This is unlikely to happen for the MicroHAWK. Apparently the workaround is to mark the device (in the file above) with "NO_UNION_NORMAL" which means that the device has no union descriptor. Appendix A : Configuring the ID-20 to use a static IP address The ID-20 needs to be configured to use a static IP address before using it with Raspbian. The easiest way to do this is to connect the reader to a PC and then open a web browser to connect using WebLink. Once you have WebLink open (default address is 192.168.188.2), go to the gear wheel icon in the upper right, click on it and then click on the Advanced icon. This will open the configuration pages as shown below. Select Communications. Click on DHCP and change it to Static. If the camera address also needs changing then do that here too. Close the Advanced Settings box and save the camera settings to flash memory using the icon in the upper right indicating a reader on top of a floppy disk. The ID-20 is now ready to connect to Linux. Operating System Any

The HyperTerminal files (hypertrm.dll, hypertrm.exe) can be copied to a Windows 7 PC to allow use of this software. Saving a HyperTerminal session (*.ht) does not start properly when double clicked in windows 7. To allow a HyperTerminal session to start in Windows requires the following changes. Navigate to Start/All Programs/Accessories/Communications, left-click on the last HyperTerminal icon, right-click on the *.ht file that you just created and click send to Desktop.Right Click on the new desktop shortcut and select properties- under target, delete the quotation marks from the path.At the beginning of the path, add the following text: "C:\Program Files(x86)\HyperTerminal\hypertrm.exe"Make sure there is a space between the two paths.Click OK to save the changes Operating System Windows 7

p by step procedure demonstrating how to use the PDF comparator in the LVS75xx application. Overview The comparison of the LVS-7510 golden to the Master PDF file happens only at setup.ScanProof compares the .BMP version of the LVS-75XX golden image created from the label during the AutoSetup process to a PDF Master artwork file selected by the user.This comparison happens on only one image; the golden image taken during setup. After the comparison in ScanProof, the LVS golden image is compared to the image of every label printed. Operation From the Blemish setup screen of the LVS-75XX software, the Correlate Artwork button launches the ScanProof application. The LVS-7510 application goes dormant while ScanProof is performing the comparison. The ScanProof application produces a comparison report and passes it back to the LVS-7510.When the ScanProof application terminates, the LVS-7510 returns to the Blemish Setup screen. A report from the ScanProof application is passed to the LVS-7510.• If the report is marked Fail, the LVS-7510 software notifies the user of a failed report. • If the report is marked Pass, the LVS-7510 allows the user to complete the Blemish setup. Before you start…. Depending on the hardware configuration, please make sure you have the following versions installed in your LVS-75XX PC. LVS-75XX Internal ??? LVS-75XX External 5.6.7.415 & aboveCopy the Microscan.ini to the following path:C:\Users\Public\ScanProof\Setups Follow the steps below to use the PDF Comparator. 1. Launch the LVS-75XX application. 2. Click Log In. 3. Click Create a NEW job. 4. Print 5 – 10 labels. 5. Click Show More to see at least 1 label with half a label on top & half a label below. 6. Draw Sector to setup label & click >>>. 7. Use Arrowkeys to move sector. Use Control - Arrowkeys to resize sector. 8. Click >>> to save job. 9. Click Yes to proceed. 10. Close warning dialog box. 11. Click Edit job. 12. Click on Blemish sector & click >>>. 13. Click Correlate artwork. 14. Select & open the desired pdf file. 15. ScanProof launches & LVS-75XX application hides. 16. Use the Rotate buttons (if necessary) to orientate the PDF image. 17. Click TICK to confirm Master Label. 18. Select File menu > Setup > Microscan. 19. Click Run Inspection. 20. Go through the list of Differences. Classify them. 21. Click Generate Report. 22. Select the Status & enter the necessary information. 23. Save report. • The report should be saved in the job folder • C:\LvsData\LVS-7500\Jobs\LVS000007A\ArtworkComparison Keep the report with the inspection job to ensure the LVS-7510 software is able to locate the Pass report. 24. Exit ScanProof. 25. ScanProof closes & returns to LVS-75XX application. 26. If the ScanProof report status was Fail, redo…. Sample Report 1 Sample Report 2 Sample Report 3 Software Version 5.6.7.416 and a

This example application will use one MS-3 to scan a carton, then teach the product code to the product scanner. If the product is incorrect, the output will fire. The Ms-Connect 210 is used as the intermediate device to control the two scanners. The carton scanner will strip off the first two and last one digits from the carton (ITF) code, and load it into the product scanner, which will then scan the UPC codes. kA23800000008E7CAI_en_US_1.zip

Shown at the bottom of this note is a picture showing of a 7000 system that uses a Basler spL8096-70km camera that occasionally has vertical lines in the image. This problem can be corrected for a short while, by rebooting the system. The long term fix is to purchase a Basler power supply. Below is a link to a vendor that sells the Basler power supply. This has shown to get rid of the vertical lines that show up in that model of camera from time to time. http://www.graftek.com/pages/spL8192-70km.htm The part number for the power supply is under accessories: 2000031201 Power Supply, 12V DC/HRS 6-pin Operating System Any