VisionView Maintenance Utility Release Notes

Transcription

1 VisionView Maintenance Utility Release Notes Copyright , Cognex Corporation. All rights reserved. Overview This document describes Release of the Cognex VisionView Maintenance Utility. For updated release notes and documentation, including localized versions, visit the VisionView Online Support Center. System Requirements New Features Changes & Fixes Known Issues

2 System Requirements Hardware Requirements Intel Pentium 4 processor running at 2 GHz (or equivalent). 256MB of available RAM. 500MB of available hard-disk space. Video card capable of displaying 1024x768 resolution at 16-bit color depth. The DPI Display setting must be set to 96 DPI. Network Interface Card (at least 100Mbps) for connecting to VisionView devices. Operating System Requirements The VisionView Maintenance Utility has been tested on the following 32-bit operating systems: Microsoft Windows Server 2003, Service Pack 2 Microsoft Windows XP Professional, Service Pack 3 Microsoft Windows Vista Business, Service Pack 1 NOTES: Although the VisionView Maintenance Utility application may function on other operating systems, systems not meeting the preceding requirements are not supported. You must have administrative privileges to the PC to install the VisionView software. Software Requirements The Microsoft.NET Framework 3.5 SP1 must be installed before installing the VisionView Maintenance Utility. Microsoft.NET Framework 3.5 SP1 is included with the Maintenance Utility; if not detected on the PC, it is automatically installed. Supported Languages English Japanese Chinese (Simplified) Korean French German Spanish (European) Italian

3 New Features Added support for the VisionView PC software. The Maintenance Utility can detect any active instances of the VisionView PC software running on a networked PC. You can perform file operations including backup, restore and duplicate. You can also restore VisionView to the default settings and reset the VisionView Administrator Password. NOTE: The Configure and Firmware Update application steps and the Restart button are not supported with the VisionView PC software.

4 Changes & Fixes NOTE: Change Request numbers (CR#) have been included (where applicable) to improve tracking of Known Issues reported via Cognex Technical Support. If a VisionView s firmware files have become corrupt and it is the only VisionView device detected on the network, the Update Firmware button is disabled and the device's status now properly states Invalid Firmware Update Key. (CR# 57463) If there is high network traffic, the firmware update process no longer fails, causing the VisionView settings to be reset to their firmware defaults. Previously, the firmware update process could fail, causing an error message to appear and the VisionView settings to be reset to their firmware defaults. (CR# 52943, CR# 56834) The Alternate DNS field has been renamed to DNS Domain. (CR# 56172) If VisionView is assigned a link-local IP address, operations such as firmware update, restart, identify or resetting the Administrator password, will now function properly. (CR# 56804, CR# 56805, CR# 56806)

5 Known Issues NOTE: Change Request numbers ( CR# ) have been included to improve tracking of Known Issues reported via Cognex Technical Support. Issue: If attempting to restore or duplicate a VisionView Operator Interface Panel when the operator is performing touch screen operations or when the device is actively performing user interface functions (for example, detecting sensors in Setup Mode), may result in two instances of the VisionView application running on the device. This could result in poor performance and a reduction of available memory. (CR# 63720) Workaround: After performing a restore or duplicate operation, power-cycle the device again; this will remove any additional instances of the application and VisionView will resume normal operation. Issue: If using the Maintenance Utility and an active instance of the VisionView PC software is detected on the network, the Maintenance Utility application will be terminated. (CR# 62303) Workaround: It is recommended that you install the Maintenance Utility or later. Issue: If repairing a VisionView by updating the firmware files, the Maintenance Utility does not prompt the user to powercycle the device and the firmware update process may timeout. (CR# 63513) Workaround: During the firmware update process, the Updating Firmware dialog will state, "Warning: Continuing will cause the device to restart. Please confirm this action." Click the OK button, then manually power-cycle the device to complete the firmware update. Issue: If a VisionView device is highlighted and the user navigates to the Duplicate application step, the list of Available Backups may not properly display all backup files that are stored in the specified Backup and Restore folder on the PC. (CR# 63158) Workaround: Refresh the list of Available Backups by selecting a different VisionView device in the list of discovered devices. Issue: In the Duplicate application step, when attempting to sort the list of Duplicate Devices by Backup Date, the list does not sort correctly (from oldest to newest, or vice-versa). (CR# 63112) Issue: If duplicating from a VisionView Operator Interface Panel to the VisionView PC software, or vice-versa, the Administrator Password is not duplicated and is reset to the default (blank) password. (CR# 63506) Issue: If VisionView is assigned a link-local IP address, the password cannot be reset. (CR# 56806) Issue: The VisionView Maintenance Utility does not support changing the Device Names to contain the following characters: / \ [ ] " : ; < > + =,? * _. If a VisionView Device Name contains these characters, and the user attempts to change the Device Name from the Maintenance Utility, any changes made to the Network Settings may not take effect. (CR# 57116) Workaround: It is recommended that these characters not be used in the VisionView Device Name, as they are not compatible with most standard network naming conventions. If the Device Name must contain one of these characters, change the Device Name from the VisionView application. Issue: If a laptop is docked and the Maintenance Utility is running, then the laptop is safely undocked and automatically switches to a wireless connection, the Maintenance Utility may fail. (CR# 57422) Issue: If a VisionView device with a valid backup file is detected while the Maintenance Utility is running, the Restore button may be disabled and the device's status may improperly state No backup. (CR# 63756) Workaround: Restart the Maintenance Utility application.