Omron Forums Support
-
Posts
0 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Downloads
Posts posted by Omron Forums Support
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.
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.
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.
the attached document Discusses modification of the dm.config file, and also explains what will happen if a camera is swapped.
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.
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.
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.
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
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.
- Press the AutoVISION button and connect power to the VisionMINI / VisionHAWK
- Wait approximately 30 seconds
- Open a command prompt window
- For a VisionMINI type in the following command
- Telnet 192.168.188.10
- For a VisionMINI Xi type in the following command
- Telnet 192.168.0.100
- For a VisionHAWK type in the following command
- Telnet 192.168.0.10
- For a VisionMINI type in the following command
- Press the Enter key and you should see the prompt, [SAFE-KERNEL]
- Enter the following commands, Followed by the enter key: (case sensitive)
- BP_Dump
- cd “/tffs0/Config/Focus”
- xdelete “*.acq”
- reset
Operating System
Any
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)
| Inspection | Max Trig/Sec | Max PPM |
| OCVFontless – 10 character, No AutoFind locator | 13.2 | 792 |
| OCVFontless – 20 character, No AutoFind locator | 10.3 | 618 |
| OCVFontless – 10 character, +/- 1 character AutoFind locator | 10.3 | 618 |
| OCVFontless – 20 character, +/- 1 character AutoFind locator | 8 | 480 |
| OCVFontless – 10 character, +/- 2 character AutoFind locator | 8.7 | 522 |
| OCVFontless – 20 character, +/- 2 character AutoFind locator | 6.9 | 414 |
| Barcode - Code 128, 0 degree rotation, trained | 17 | 1020 |
| OCR tool - 10 character | 8.2 | 492 |
| OCR tool - 20 character | 5.1 | 306 |
| +/-2 character Intellilifind Locate (Outline only, +/-10 degree rotation, scale off) and OCR tool - 10 characters | 6.1 | 366 |
| +/-2 character Intellilifind Locate (Outline only, +/-20 degree rotation, scale off) and OCR tool - 10 characters | 4.2 | 252 |
| Intellifind with +/- 2 character search (Outline only, +/-10 degree rotation, scale off) | 11 | 660 |
Software Version
VS 7.0.1.6
The following procedure will change the appropriate settings in the VisionHAWK to allow the camera to focus properly after the lens has been changed.
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.
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
| Job | OCR tool | Segmentation | Library | Max Rate (ppm) | Process time (ms) |
| OCR_ArialTest00.avz | OCR tool | AutoSize | AlphaNumeric | 230 | 170 |
| OCR_ArialTest01.avz | OCR tool | AutoSize | Numeric | 270 | 125 |
| OCR_ArialTest02.avz | IntelliText OCR | Default | AlphaNumeric | 180 | 234 |
| OCR_ArialTest03.avz | IntelliText OCR | Default | Numeric | 205 | 190 |
| 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
Follow these instructions to attempt to correct the problem:
- Boot the camera to [SAFE-KERNEL] mode
- BP_Dump
- cd “/tffs0/Config/Focus”
- xdelete “*.acq”
- reset
Operating System
Any
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.
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").
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.
To view the licenses enabled the system, make sure the dongle is connected to the PC and start the 7XXX software. Before logging into the software press CTRL-A and a window will be displayed showing the current licenses. The attached files shows how this looks with 7000 software.
This Link is to a YouTube video showing the addition of the QX-800 series to an EIP Network. http://www.youtube.com/watch?v=7TJIcevRIjo
Using a DELL laptop with Nvidia Quadro 880M, locate and capture/decode buttons cause the video driver to crash, occasionally causing a blue screen. Updating drivers to 260.99 resolved the problem.
This is usually caused by the customer changing settings in the INI file under [Camera]. They put Flip=1. This tried to reverse the pixel readout, but flip only ever worked for a specific camera: Dalsa P2-4x-04K40. When this setting was changed in the INI file it reversed the tap readout. This caused vertical blank lines in the image. The symptoms looked exactly like another issue that was related to a known Basler Power Supply issue. Once Flip=0 was reset, the image was fine, however the image was now mirrored. This explains why Flip= was changed to try to deal with the mirrored image. The actual fix is to rotate the camera 180.
In this particular case, the entire 7000 system was relocated by the customer from one press to another, and the web run in the opposite direction from the original installation.
Operating System
Any
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
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.
Visionscape I-PAK HE doesn't start
in Machine Vision
Posted
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.