Omron Forums Support
-
Posts
0 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Downloads
Posts posted by Omron Forums Support
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
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 window
- Navigate 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 following
allow-hotplug eth1
iface eth1 inet static
address 192.168.188.1netmask 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 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
Due to camera drivers used on older (2013 and earlier) models of LVS-9510 and LVS-9570, version 4.3 software released in December 2017 is not supported for these older units. LVS-9570 with a serial # that is lower than 14140 (December 2013 and older) cannot be upgraded. LVS-9510 with serial #s 12906 and lower (prior to June 15, 2012) also are not compatible with version 4.3 and later software.
Software Version
4.3 and newer
Operating System
Windows 10;Windows 7;Windows XP
Most mid and high range label design software allows for re-scaling of print templates for different dpi of printers. In that case a customer who has designed print templates for a 203 dpi printer and would like to purchase a LVS-7510 with 300 dpi printer can easily adjust their print templates for use with the LVS-7510 system. For customers using label design software that does not provide this easy re-scaling, it would be required to create new print templates. A 203 dpi version of the ZT600 series will be supported by LVS-7510 in 2018. However, it is recommended that only barcodes with x-dimensions of 15 mil or larger be used with that resolution printer to help minimize the likelihood of a defect in the print head leading to a barcode fault.
The use of the "Import image from file" function via the Archive tab of LVS-95XX software is not possible with DPM standards such as ISO/IEC TR29158. The process of grading a DPM symbol requires using a live image. Only with this live image can TR29158 rules can be applied.
Software Version
All
Operating System
Windows 10;Windows 7;Windows XP
In some cases, the USB license dongle will lose the Visionscape licensed features (Standard GigE, Intellifind, TPC, DIVS). The reason for this is that each time Visionscape reads the license key, information is written back to the dongle. Non-volatile EEPROM memory eventually fails after some finite number of writes, effectively corrupting the key. This has been fixed in a run-time update to the USB key that allows the key to save license information on the computer instead of the dongle.
This runtime has been include in newer versions of the software.
Dongles that have lost their licenses will need to be replaced. Contact Microscan for replacement options.
To prevent dongle failure, update the software to the latest versions. This software can be found on the Microscan website. Contact Microscan for updates to specific solutions.
Software Version
AutoVision 3.0.
Operating System
Windows 7
USB ports go completely dead in sleep mode which disconnects camera.
There is a way to keep the USB ports active during sleep mode.
- Go into Device Manager, navigate down to Universal Serial Bus controllers.
- On each USB Root Hub item, right-click and choose Properties.
- Click on the Power Management tab and un-check the box for Allow the computer to turn off this device to save power.
Operating System
Windows 7
Q: Can the original floor stand be used? A: Yes with adapter 98-209441 Q: Do the wires run through the center hole? A: Yes Q: What processor is used in the I-Pak SE system? A: Intel Core 2 Duo Q: Is the UPS mounted externally? A: Yes
How to update the QX-hawk firmware when the unit does not respond to the normal auto connect. 1. Start the QX-Hawk in Safe mode. To do this , power the unit while keeping the Default pin (3) connected to the ground pin (7). In the standard QX cables, these are the green and blue wires. Keep the connection until the red cross comes on or for about 15 seconds. 2. Start ESP and force connect with communication settings 115,N,8,1. 3. Go to the ESP terminal. 4. Type and see if there is an answer. The unit should respond with the firmware versions and the text SAFE MODE. 5. Try to update the APP code which has been working before. The update can take more than 10 minutes. After the update, re-power the QX-Hawk. * If the update has succeeded, try to connect via Ethernet and update to the new Kernel, App code and the DSP code. In this order. * If the update has not succeeded, Force connect via RS-232 and update to the new Kernel, App code and the DSP code.
Before executing the attached WSF File (Windows Script File), you must:
- Certify that Telnet Client is enabled on Windows. For more information, please check the article "Enabling Telnet Client on Windows."
- Copy the upgrade licenses for the unit to: C:\Microscan\Vscape\Licensing. (You may only have the license for one unit at a time.)
- Certify that you have a fresh AutoVISION 4 installation, i.e., just one VSF file available on C:\Microscan\Vscape\Firmware.
- Certify that you have correct boot version on the unit.
Operating System
Any
Download and install the current QX Hawk firmware to add the improved Ethernet IP interface. http://files.microscan.com/elqNow/elqRedir.htm?ref=http://files.microscan.com/_att/d46296e3-3002-4189-9839-e7516e4e6fbb/QX_Hawk_FW_APP-15_DSP-11.zip
When this warning is shown at the bottom of the MICROSCAN LVS© Grading tab, yet the code is receiving an A grade, it is notifying the User that there is an unprintable character in the embedded data string. While not a failure, we do notify that the unprintable character is present.
Review Unprintable Characters on Structure Tab
In this example, when directed to the Structure tab, the data structure analysis is viewable. In this string of data, there is a <Space>. A space cannot be printed, but is present in the data.
Software Version
LVS-95XX
Firmware Version
LVS-95XX
Operating System
Any
The attached universal mounting spec sheet is for the following products: MS-880/MS-890 (for MS-890, reference MS-880) MS-3 Laser/CCD MS-2 (reference MS-3) MS-820 MS-860 MS-9 QX-830 (reference MS-820) QX-870 (reference MS-860) MS-850 (reference MS-860) MS-4/Quadrus MINI series
Over the years, operational requirements of GS1 System users have influenced the dimensional specifications of GS1 System symbols, and these dimensional specifications have in turn influenced the development of scanning system optics and printing processes. The dimensional requirements for each application area defined in Section 2 of General Specifications are set out in the GS1 System Symbol Specification Tables (SSTs).
In the previous version of software, there was greater symmetry in the chosen aperture. With version 15, there have been changes to the required aperture for EAN/UPC-A (Table 2 now requires a 10 mil aperture where previously it was 6 mil), GS1 Data Matrix (previously the aperture was 80% of the cell size whereas now there are fixed apertures depending on the table), as well as others.
Each SST provides the following barcode specification detail:
- The barcode(s) specified by the GS1 System for each application area.
- The minimum, target, and maximum X-dimension (narrow element width) for the symbol, based on the scanning environment.
- The minimum and target barcode height, based on the scanning environment.
- The Quiet Zone width and, for primary and secondary symbols, the minimum and maximum separation between the two symbols (these measurements are expressed as multiples of the X-dimension in the form nX).
- The minimum ISO quality specification expressed as g.g/aa/www, where g.g is the minimum overall symbol grade to one decimal place (on a 4.0 scale), aa is the effective measuring aperture in thousandths of an inch, and www is the wavelength of the light source in nanometers.
The benefit of having to choose the SST means the verifier can now check X-dimension and symbol height to the specified application where before choosing a SST was required we could not.
Table Selections are determined by Customer selection based upon the product that is being labeled.
If the labeler selects a table, the symbology being used should follow the specifications in the table selected. EX: If Table 6 is selected for Regulated Healthcare Non-Retail not used in General Distribution, and the labeler has selected to use a 2D GS1 Data Matrix symbol, the symbol should follow the specifications in the table for minimum and maximum X-dimension requirements, symbol height requirements, quiet zone requirements and minimum quality specifications.
Operating System
Any
The NL200 series lighting controllers are not UL listed.
Operating System
Windows 7
Beyond Trust software will prevent the proper installation of AutoVISION (Visionscape) on a PC. To install the software the following steps must be followed. 1. Logon as an admin account 2. Disable the Beyond Trust services. 3. Reboot 4. Install AutoVISION and reboot. 5. Login as a the same admin and let the installer finish 6. Re-enable the Beyond Trust services 7. Reboot
The recommend torque for the front panel accessory screws is 2 in-lbs; and 8 in-lbs for the mounting plate screws.
This setup is very Generic and assumes you are in early setup stages with control of placement of a trigger and if possible line speed. The note shows examples and uses of some parameters to help in most moving based issues. This best case scenario has the barcode directly under the Imager, in Field Of View, when the trigger goes active.
Every symbol decoded will run through the database. - If the symbol is in the database, it is a Match. - If the symbol is not in the database, it is a Mismatch. At the end of the read cycle, there is only ONE result, which will be (in the order of priority): - If ANY symbols are not decoded (the number of symbols required is set in the Multisymbol option, under Read Cycle), the read cycle result is Noread. - If ANY symbols do not match the database, the result is Mismatch. - If ALL symbols are decoded, and they are in the database, the result is Match. Each of the three outputs can be programmed for one of these events, and in some cases, a combination of these events. Also note that in most readers, when Matchcode is enabled, there is no more ‘good read’. Settings that say ‘Good Read’ now mean ‘Match’.
This instruction explains how to remove the filter. WARNING: Removing the IR filter will expose the sensor to environmental conditions. 1. Remove Lens. 2. Remove the two screws, metal plate, and the clear IR filter located inside the lens housing. 3. Re-install the plate and two screws without the IR filter.
The attached document provides instructions for the user to switch to different firmware on the MicroHAWK camera. This functionality will require the dual boot license on the camera, in addition to the ID and machine vision licenses.
Using the PDF Comparator in LVS-75XX software
in Code Verification
Posted
p by step procedure demonstrating how to use the PDF comparator in the LVS75xx application.
Overview
Operation
From the Blemish setup screen of the LVS-75XX software, the Correlate Artwork button launches the ScanProof application.
• 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….
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