[Wiring Input #1 to the MS-Connect 210]

This describes how to wire in a momentary contact switch to the Input of the scanner for such things as unlatching output's.

kA23800000008KHCAY_en_US_1.pdf

[Wiring in 5V TTL signals to the MS-4/MS-Mini Family of products.]

Simple wiring diagram for wiring outputs to the 5V TTL signals in the MS-4/Quadrus Mini Family of products. The Mini's can Sink up to 10mA and source up to 10mA.

kA23800000008IvCAI_en_US_1.pdf

[Wiring in 5V TTL signals to the MS-3.]

Simple wiring diagram for wiring outputs to the 5V TTL signals in the MS-3. The MS-3 can Sink up to 10mA and source up to 2mA.

[Wiring Discreet Outputs to IB-131]

Simple wire for wire drawing of both the NPN (3 outputs) and the PNP (1).

kA23800000008IGCAY_en_US_1.pdf

[Will MicroHAWK Still Communicate When a PC is in Low Power Mode?]

The MicroHAWK requires a minimum of 4.7 volts DC to function. When a PC goes into sleep/low power mode, the USB ports essentially turn off or run at a lower than 4 volt range. When this happens there is not enough voltage/power for the ID-30 to function so there will be no communication/functionality from the unit.

[Why does the LVS-95XX 4.3.0.3006 and later software no longer show an overall letter grade?]

Due to changes made to the ISO 15416 verification standard in December 2017, letter grades are no longer displayed for overall symbol grades in LVS-95XX software version 4.3.0.3006 and later. Attached is a technical note outlining the changes to the standard and the LVS-95XX software.

Software Version

4.3.0.3006

Operating System

Any

kA23800000008RYCAY_en_US_1.pdf

[When updating Visionscape I-PAK on a multiple camera system, only one camera is visible after update]

Visionscape I-Pak uses job files that are loaded onto the Visionscape boards when I-Pak is put into run mode. When the new software is installed, the previous job was likely not copied to the new I-Pak\Jobs directory so I-Pak created a default 1 camera job. To resolve this: a) build a new job and add the missing cameras b)save a previous back-up into the I-Pak\jobs directory.

[When launching LVS-95XX software, I am receiving an error message with an 8-digit number beginning with "-214." What does that mean?]

This error message indicates that the .mdb file has reached or surpassed the 2GB
size limit (dictated by the MS Access size limit). The resolution for this is to first run
C:\Program Files (x86)\\Microscan\LVS-95XX\CompactLvsDb.exe to compact the .mdb file
below the size limit, then create a backup database using the Archive tab in LVS-95XX and then
deleting a sufficient number of reports to get well under the size limit. See page 92
of the operator manual for further details on database backup.

[What verification specifications does the HawkEye 1500 series with verification license conform with?]

Reference the HawkEye 1500 Verification Manual for a list of parameters that are measured for each verification type. The verification manual is part of the manual set downloaded and installed with the ReadRunner 2.4.1 and is accessible from the Start menu. The manual is also available in the download center: http://files.microscan.com/elqNow/elqRedir.htm?ref=http://files.microscan.com/_att/68d53eb8-fac9-4061-8382-9d14ec80534c/hawkeye1500manuals.zip

[What to do if your Smart Camera can ping but is invisible to AutoVISION/Visionscape.]

Possible Cause 1 - PC antivirus/firewall software blocking the camera's UDP broadcast:
The sole mechanism used by AutoVISION/Visionscape (a.k.a. AV/VS) to discover OMRON Microscan Smart Cameras is by detecting the UDP message broadcast every ~5-10 seconds. Many PC antivirus/firewall software can mistakenly block this broadcast as a potential threat.

Fix: Check your security software logs for blocked UDP broadcasts from the camera or software. If they are being blocked, disable the software to confirm this is the issue, then have your IT dept. "whitelist" the item (likely avpsvr.exe) so that it is no longer blocked in the future.

Possible Cause 2 - Camera is in Diagnostic Boot Mode:
Your camera may be in this mode if it exhibits indicator LED behaviors similar to the following:
TRIG, FAIL, TEACH, OUTPUT 1 & 2: All solid.
MODE, POWER: All solid
In normal operation when idle (not running a vision job), cameras should typically only exhibit a solid POWER LED and potentially an intermittent LINK or ACT LED:

Fix: Ensure all cable/wiring connections are undamaged and then power cycle the camera.

Possible Cause 3 - UDP Broadcast is disabled (MicroHAWK MV ONLY):
The MicroHAWK MV Smart Cameras accept a command allowing the disabling of the UDP message broadcast.

Fix: Telnet into the camera, issue the command BP_UpdateUDPAnnounce(1), then issue the command reset and allow the camera to reboot.

Possible Cause 4 - Incorrect software license (FrontRunner ONLY):
For a Smart Camera to be visible in Visionscape FrontRunner software, the camera must, at a minimum, have a Visionscape license.

Fix: Purchase the Visionscape smart camera license through your local OMRON Microscan sales contact.

[What size OCR character is valid for Quadrus MINI decoding?]

What size OCR character is valid for Quadrus MINI decoding? The font size on the surface to be read is not as important as the size of the imaged OCR character in memory. OCR will work with imaged characters ranging in height from 10 to 50 pixels, with 20 pixels being the optimal size based on read rate, accuracy and performance.

[What should I know about using a mirror with my laser scanner?]

Use a mirror that reflects off the first surface, not the back. This will reduce distortion of the image. use a material that will reflect as much light as possible to maximize the light signal of the symbol. Glass shoudl be defect-free to prevent distortion.

[What revisions of Quadrus MINI and MS-4 firmware support Pharmacode?]

This information is for all versions of MS-4, Quadrus MINI and MINI Hawk. Models with Standard IP mode only Firmware #35-634001-24 and older has Pharmacode. Firmware #35-634001-25 and later, no Pharmacode installed. To add Pharmacode, downgrade firmware to -24 using the attached file. Models with Standard and Q-mode Image Processing modes Firmware #35-634001-24 or older has Pharmacode in Q-mode and Standard Image Processing modes. Firmware #35-634001- 25 and later has pharmacode in Q-mode. X-mode Pharmacode works in all revisions.

kA23800000008GDCAY_en_US_1.mot

[What products will provide In-line Verification?]

In-line verification of all supported standards (1D and 2D) can be performed using Visionscape products, as well as the HE15xx series verifiers. Refer to product documentation for more information about Verification.

[What is X-Mode?]

This document describes X-Mode functionality in relation to the MINI Hawk Imager.

kA23800000008IOCAY_en_US_1.pdf

[What is the rule for marking Data Matrix codes on Cylinders]

The printing rule that I mention is from the NASA spec, NASA-STD-6002 (Applying Data Matrix Identification Symbols on Aerospace Parts).  This document can be retrieved from https://standards.nasa.gov/file/517/download?token=yuQmgz3V

 

Section 4.2.1.2 is the relevant section.  Per the document…

4.2.1.2 Part Geometry

Flat surfaces are preferred over curved surfaces for marking. A rectangular symbol shall be

applied to cylindrical parts, either concave or convex. The rectangle is sized to fit either within the

reflective band of light that emanates from the spine of the curve or on 5 percent of the

circumference. This band of light typically occupies 16 percent of the diameter of the curve under

normal room light and can increase in size under bright light conditions. Figure 3 illustrates the

proper method for marking curved surfaces.

[What is the pin assignment for the QX trigger connector (Connector T)?]

This document describes the revised pin assignment for Connector T on the QX-870 and QX-1. It also provides a list of new part numbers for the affected devices.

[What is the GAMP (Good Automated Manufacturing Practice) Category for LVS-95xx verifiers]

LVS-95XX software most closely aligns with a GAMP 4 (Configurable Software Packages) category.

[What is Symbol Reconstruction?]

This document describes symbol reconstruction methodologies in the QX-830 and QX-870.

kA23800000008I9CAI_en_US_1.pdf

[What is correct version of firmware for the VS-1 to use with Visionscape I-PAK HE 3.7.4?]

Visionscape version 3.7.2 build 28 is the correct version to use with Visionscape I-PAK 3.7.4. To update the firmware please go to the Start menu and select Programs > Microscan Visionscape > Tools > HawkEye 1600(T) Firmware Update. Once the program is started select the desired camera to update in the top dropdown selection and verify that 3.7.2 Build 28 is the selected Firmware Version. Click Update Firmware button to update the VS-1 firmware.

[What does the "scan sync not present" message on my laser barcode scanner mean?]

If a data string message of "scan sync not present" is output by your laser barcode scanner, this indicates a developing mirror motor hardware failure and the unit should be returned to OMRON Microscan Systems for repair.

[WebLink for MicroHAWK ID works ONLY with Ethernet-over-USB or native Ethernet]

Because WebLink for MicroHAWK ID-series barcode readers is web-based and is accessed via the reader's IP address, it only works over Ethernet connections. This may be an emulated Ethernet connection over USB (ID-20 or ID-30 with USB adapter cable) or over a native Ethernet connection (ID-40). It CANNOT be accessed over RS-232. If RS-232 communication is required for the application, configuration must be done using our ESP software.

[VS-1 has incorrect TCP/IP address and cannot communicate]

In this case, the network overview showed that the camera was being controlled by "@" or something close to that. This occurs when the camera has a space character in the camera name. Spaces are not allowed in VS-1 camera names!!! To fix the problem without a serial connection, set the PC to the IP subnet of the camera, open a web browser to the following address, "http://" + camera ip address (found from network overview) + "/setup.htm". At that web page you can reset the camera name to remove the space. You can also set the camera static IP address but the octets are backwards, so that to enter the address A.B.C.D you need to put in the address as D.C.B.A and the same for the subnet mask.

[Vissionscape error: Configuration file couldn't be read]

I had a customer with a problem loading Visionscape. The debug window showed a message from CAvpBackplane stating that the configuration file couldn't be read. Frontrunner would then show up with no GigE systems available. Darren and Tom helped me out. The fix was to do the following: Shutdown all the Visionscape stuff (including the backplane) From start menu select Run Cmd Navigate to C:\Vscape\412_16\dll (or whatever version you are using) Type in Regasm visionscape.configuration.dll /tlb That fixed it! Not exactly sure what it does but I found the following REGASM: This utility makes registry entries to make your .NET object look like a COM object

[Visionscape Smart Camera connectivity issues with 3.7 SP1]

Solution is to upgrade customer to 3.7.2 or later - this contains code that fixes the problem. In more detail, the problem was that the camdef file stored with the job in flash on the HE1600T camera gets corrupted or lost. When the job loads it can't find the camdef and the camera then crashes. In 3.7.2 the camdefs are all stored in the firmware and then moved into memory at boot time before the job loads. This prevents the problem from crashing the camera.