Omron Forums Support

INTERNAL ONLY. DO NOT PUBLISH. License files are located here: O:\Public_Read\Mfg_Eng\MobileHawkLicenseFiles The data sent by the Mobile Hawk is: License Key Failed!! To restore the Microscan files after a 'Delete all files' or 'U' command - Start the Mobile Hawk - Start ESP - ESP will not see the Mobile Hawk because it is in USB Keyboard mode. Use the button in ESP to set the Mobile Hawk in ESP USB mode. - Load the license file from the Utilities / Firmware / Batch File Upload. The license files can be found at: \\10.10.2.20\vol1\Mfg\Public_Read\Mfg_Eng\MobileHawkLicenseFiles - Power the Mobile Hawk with the trigger button pressed. Repress the button until you hear a beep. - Scan the ‘Reset to USB Factory defaults’ and the ‘Save Settings symbol’. - Repower the Mobile Hawk. To see the files present on the Mobile Hawk, send ‘Command type L’ from the MS-Q command encoder ( + and select the View menu in ESP.) To see the hidden files, send ‘Command type L, Data 1 from the ESP command encoder.

This is caused by a missing Mobile Hawk License. To fix this, contact Microscan support 425-203-4841 (helpdesk@microscan.com) with the reader serial number. Provide the serial number, and you will be provided with instructions to continue.

Out of the box, the MINI Hawk and X-mode algorithm will decode 1D and stacked symbologies at a slow rate. This is because when using X-mode, the reader will attempt to decode Data Matrix, AND THEN attempt to decode 1D symbologies. To fix this problem, Disable Data Matrix when reading 1D symbols. If you need to read both Data Matrix and 1D symbols, use the configuration database in the Setup view. Set the number of indexes to 2, and then 'load current to index' for both database entries; they should now both be the same. Locate the Symbology column, and then select only Data Matrix for the first entry (de-select the rest), and select 1D symbologies for the second entry (de-select Data Matrix).

Microscan has encountered a situation resulting from a revision level change in a key component of the VS-1 smart camera.The new revision cameras cannot be “downgraded” to operate with older firmware or Visionscape GUIs. For Full Details on The VS-1 Camera Versions and Visionscape Versions please review the attached PDF. kA23800000008EJCAY_en_US_1.pdf

The UDP broadcast that the MicroHAWK sends to facilitate its discovery on an Ethernet network uses port 30717. Please ensure that this port stays free on any network where a MicroHAWK might be connected. Operating System Any

MicroHAWK 20 Series Focus displacement from front of window to top of unit is 28.4mm MicroHAWK 30 and 40 Series Focus displacement from front of window to top of unit is 27.9mm Software Version All Firmware Version All Operating System Windows 10

To discuss the MicroHAWK PoE implementation and recommended equipment when integrating the device. kA238000000087QCAQ_en_US_1.pdf

If after updating the App code some features do not work or it behaves oddly, you need to update the boot code. This is usually only seen if updating an old Microhawk.

Below is a table referencing the differences from Hardware Pinout to Parameter naming convention in software. MicroHAWK MV-40 (I/O)PINDescriptionIN/OUTAutoVISIONVisionScape1TriggerINSensorSensor Point12New MasterINDigitalPhysical Input 0001 5Output 1OUTOutput 1Physical Output 000211Output 2OUTOutput 2Physical Output 00036Output 3OUTOutput 3Physical Output 0004 Operating System Any

Operating System Any

Please note that we have had a rash of users complaining that MicroHAWK MV will stop receiving a sensor trigger after a certain period of time. We have traced this to the Debounce time in the camdef. The current solution for this is the give them a modified camdef that sets the Debounce time to 0. Leave the Filter time as is. If you are using AutoVISION only, you will have to edit the original camdef file. In FrontRunner, you can create a copy of the camdef with a modified name and debounce time.

Process for Making a MicroHAWK ID reader Dual Boot to MV Update Unit to Latest MicroHAWK ID Version of ID Software 1. Make sure you have the latest version of ESP downloaded and installed on your computer. Unzip to a utility folder for easy access. 2. Make sure you have the latest version of WebLink downloaded to your computer. Unzip to same utility folder for easy access. 3. Upgrade the camera to the latest version of WebLink via ESP. See MicroHAWK Firmware Update Guide in the WebLink file folder for directions. The required files will be in your utility folder. a. Upgrade the App first b. Upgrade WebLink second 4. Reset the unit. Verify that it is running the latest software with no issues. 5. Query the level of the Boot Loader. If you do not have at least boot loader 35-9000033-1.1.0.3024.bin then you should upgrade this as well. a. The newest Boot Loader is held at Microscan on \\Moonshotn. Request it if you do not have it. (The boot loader was also attached to the email accompanying this process sheet.) b. Copy this file to a utility directory along with WebLink and ESP for easy access. 6. To upgrade the Boot Loader, hit CTRL-B when you are in the Firmware update dialog and then navigate to the boot loader in your utility directory. Upgrade the Boot Loader on the camera. 7. CRITICAL – POWER CYCLE CAMERA AFTER UPDATING BOOTLOADER. Reset will not work. 8. Verify that the camera is still functioning normally as a reader. Update Camera to Run Machine Vision – Load Licenses, Setup CloudLink Directory, Load Vision Software, Enable Power Strobe Load software on PC, Generate and Load Licenses to Camera. 1. Verify that you have the latest version of AutoVISION installed on your computer. 2. Generate MV licenses for camera based on the camera Mac Address a. From Bank 0, create and save AutoVISION, Verification, Visionscape b. From Bank 3, create and save Machine Vision and Dual Boot. 3. Download and start FileZilla Client from Filezilla.org. 4. Connect Filezilla to the camera with IP address, “target” and “password”. 5. In the Remote Site directory pane (upper right), click on the sd0:0 folder, and then click on all the other subfolders to update them. 6. Drag the new Machine Vision licenses into the /sd:0/Config/Licensing folder. Create Web Directory and Install CloudLink Files 1. Under sd:0, create a new directory called “http_mv” if one does not already exist. 2. There may already be a http_MV directory. If so, use that here and throughout the rest of the procedure. 3. Under c:\microscan\vscape\firmware\http, locate the corresponding 08000030XX_HMI.zip file. 4. Unzip it to a subfolder in this same directory on the pc. 5. Drag entire unzipped contents of this directory to the new /sd0:0/http_mv directory (_MV). Install Vision Firmware 1. Navigate to /sd0:0/Firmware/Launch directory. 2. Drag reader .vsf file to the /sd0:0/Firmware/BootPackages/AutoID directory 3. Go to lower left hand Filename pane in Filezilla. Drag the current 08000030XX.SM5KER.vsf file from the PC to the camera Launch folder. Make sure it is the SM5KER file, and not the SM5BOOT file. 4. Also drag a copy of this file to the /sd0:0/Firmware/BootPackages/MachineVision directory. 5. Telnet to the camera using its IP Address. Login is “target”, password is “password”. 6. Type in “reset” to reboot the camera. 7. It should now come up as a Machine Vision unit. Update Boot Parameters So That Vision Uses CloudLink Web Directory 1. Telnet again to the camera using its IP Address, “target” and “password”. 2. Note that you are up running vision, enter the following command typing it exactly as you see it below. This will tell MV to use the http_mv directory for loading CloudLink. BP_UpdateWebRootDirectory “/sd0:0/http_mv” (or _MV). 3. Do a BP_DumpAll command in Telnet. 4. Near the bottom, verify that the Web Server Root entry is set to /sd0:0/http_mv (or _MV). Enable Power Strobe 1. If unit is a MV-30 or an MV-40, you must also enable Power Strobe. 2. When you are booted to Machine Vision, type in the following command. BP_UpdateDevCapsPowerStrobe 1, “MSCANFACTUNLK” Test CloudLink and Power Strobe 1. Reset camera again. 2. Connect to camera using browser. 3. Test Power strobe functionality. Setting up and Testing Dual Boot 1. In Telnet, type in sbp to show the boot packages. 2. Type in lbp # to load a specific boot package. his should reset the device which will then boot up using the new package. 3. Pick the Reader one. Verify that it comes up as reader. 4. Repeat Step 3. Pick machine vision. Make sure it comes up as machine vision. 5. If changes do not work then you have not repowered system after updating boot loader. You must repower, not reset.

Customer wants to know the maximum number of codes that can be checked for Duplicates The 7000, 75xx software uses an access database when performing duplicate checking. The maximum size of this database is 2 GB. Record size = Data Length + 10 chars (approx) Max # records (approx) = 2,000,000,000 / Record Size INTERNAL NOTE Duplicate checking is performed by attempting to add a record for the current read string to the database. If an error occurs, then the string must already exist and this is a duplicate error.

In Visionscape FrontRunner Editor, Select the desired Blob tool Click the Show Advanced Datums button Change the Process Every Nth line to 1 The Maximum Blob Size will operate as expected.

The solution to this issue is that the end user needs to Re-Install and Launch the software for the first time with Full Administrator rights to the PC. It then creates a everyone group so any user can run the software with a User Account Login. Note: Please temporarily turn off all anti-virus software to prevent interference with the LVS-95XX software installation. Error Screenshot: Follow the steps below to reinstall the software. Purpose: Completely uninstall and re-install the LVS-95XX software. Explanation: In certain situations, it may be necessary to thoroughly and completely uninstall the LVS-95XX software and any residual settings in order to resolve a given error or issue. This facilitates the re- installation of the software onto the PC from a completely fresh state, as if it was the first time the software had ever been installed. 1. Begin by uninstalling the LVS-95XX software itself. You can do this by going to Control Panel > Programs and Features, as shown below. Then simply follow the prompts to uninstall. 2. Uninstall the accompanying drivers, as shown in the screen below. The process will mirror Step 1. 3. You will need to delete the existing registry key. Start the Registry Editor by typing “regedit.exe” into the Windows search box, as shown below. Next, delete the registry key highlighted in the second screenshot at one of the following paths: HKEY_LOCAL_MACHINE > SOFTWARE > Wow6432Node > Microscan > LVS-95XX > Database or HKEY_LOCAL_MACHINE > SOFTWARE > Label Vision Systems > Database. 4. All Integra 95XX components should now be uninstalled and the PC should be ready for a new installation. If you have the original CD or USB installation media that came with your verifier, you may now insert it and reinstall the software according to the guidelines specified in the LVS-95XX Series Software Installation Guide.If you have been provided a download link for the software, extract the files, then continue to follow the installation guidelines mentioned previously. 5. Once the software has been successfully reinstalled, copy your .mdb file for you verifier to the new folder location. On your original installation media, in the “LVS-95XX” folder, is a file named “I95xx_yyyyy.mdb”, with “xx” being the rest of the model number of your verifier and “yyyyy” being its serial number. This file should be copied and placed in the appropriate folder listed below and renamed appropriately: If you installed 3.0.9qq or earlier: Move to “C:\Users\Public\I9500”; rename to “I9500.mdb”. If you installed 4.0.0h or later: Move to “C:\Users\Public\LVS-95XX”; rename to “LVS-95XX.mdb”. 6. Once installation is complete, plug in the verifier and attempt to login to the software with the below credentials to confirm that the install was successful: Operator ID: admin Password: admin Software Version 4.X.Xx Operating System Any

Make sure that you have administrator privileges to the computer prior to install. 1. Close the LVS-95XX software. 2. Unplug the USB cable of the Microscan system from the computer. 3. Go to Installation Flash Drive > “Other setup” folder > click “Keysetup.exe.” 4. Select “Keylok 2 (USB w/ Driver)” and “Standalone.” 5. Click the “Begin Install” button. A message appears indicating that all files have been copied. Close the dialog box. 6. Plug in the USB cable. 7. Windows should report a "New hardware found” message. Select “No, not this time.” 8. On the next screen, select “Install software automatically.” 9. Click “Finish.” 10. Run the LVS-95XX software. You should be able to correctly log on to your system and the “The machine is not authorized to perform this function” message should not appear. If the message appears, follow the next step. 11. If the “The machine is not authorized to perform this function” appears again, and this is a new installation, click on the Windows search bar and search for %temp%. 12. Open the temp folder and scroll down to locate the Keylok icon. 13. If the icon is present, go to the address bar and copy the file path. 14. Open your Device Manager and click on the USB that has the warning icon. 15. Right-click and select “Update Driver Software.” 16. Select “Browse my computer for driver software” and paste in the link copied from the address bar from the temp file into the browse bar. 17. Click “Next.” The drivers will be automatically installed. 18. If the issue persists, please make sure that firewalls are allowing for installation Operating System Windows 10;Windows 7;Windows XP kA23800000008MJCAY_en_US_1.pdf

See attached .pdf Operating System Windows 10 kA23800000007tACAQ_en_US_1.pdf

LVS-95xx Error message "Propeller device using COMxx which is too large" This error can happen when a PC has been connected to many different USB devices and those devices are assigned COM port #s with a higher # than 16. Therefore, the port that the 9570 is plugged into should be reassigned (in Device Manager) to a lower port # than 16, provided it does not conflict with another serial or USB device that is attached to your laptop, such as an external mouse or keyboard.

Each LVS-95xx verifier is factory calibrated and tested to the ISO 15422 specification. As part of the initial on-site installation and ongoing use it is recommended that the verifier be field calibrated at least every 30 days using the calibration card that is shipped with the unit. The calibration card is a NIST traceable card which has multiple barcodes on it as well as the values for contrast and other barcode parameters which are entered into the LVS-95xx software during the calibration process. Either the UPC-A or EAN barcode can be used during the calibration process. The card should be kept clean and in its dark sleeve, and replaced after 2 years with a new card that can be ordered from Omron Microscan.

Legacy LVS-9500, LVS-9505, and certain older LVS-9510 models (which used a 1.3MP camera sensor vs. the current 5MP) are not supported on versions of the LVS-95XX software newer than 4.1.0j, which is the last version to support these products. Operating System Any

If labels are running without being verified, and the LVS-75XX system is not stopping the printer, then most likely synchronization is lost To correct the synchronization, follow these steps: 1. Select "Edit this Template" 2. Move the red sync slice to an area of the label that contains static data. It may be necessary to make the “sync width” more narrow. 3. Click the “synchronize” button and the template should now be synchronized. Software Version 5.6.x.x/ 20.2.x Operating System Any

The factory default password to be used for all 7 of the LVS-75XX IQ/OQ test accounts is: password123 Operating System Any

Omron Microscan uses a process in manufacturing whereby Microscan software with a “7500 Master Verifier” checks the grading parameters for the 3 symbols which are printed on the calibration card. The software then computes the values of the parameters that are listed on the card which the operator writes onto the card along with the reference number and the 7500 Master Verifier serial number.

There are a few causes for this. The USB connections to the read head and the light tower have been switched.Both USB connections should be reset by removing them from the computer, and the +5V DC should be removed from the read head so that the "sensor control board" can reset. Reconnect the +5V DC back to the read head before connecting the USB from the read head to the original position it was in when the software was first installed on the computer. The USB connections to the read head or light tower was interrupted while the software was running.a. Both USB connections should be reset by removing them from the computer, and the +5V DC should be removed from the read head so that the "sensor control board" can reset. Reconnect the +5V DC back to the read head before connecting the USB from the read head to the computer. Then reconnect the light tower USB to the computer. b. After following the instructions in step 2a above, restart the 7500/7510 software. Software Version 5.6.x.x and 20.

OCR and OCV can only be performed on upper case characters in the LVS-7500/7510 software--unless the OCR-BMT fonts are being used. When a special character or lower case character is put in the "match this text" field in step 5: Setup matching, then a run time error 6 may be generated during runtime. Software Version 20.2.x.x Operating System Windows 7