Dear PickMaster User,
The new release of PickMaster 3.13 is now available. The new functions, error corrections as well as known issues are listed in the release notes below.
Release Notes PickMaster 3.13
This version of the PickMaster application is compatible with:
-
S4Cplus M2000
-
RobotWare 4.0.113 or later
-
IRC5 M2004
-
RobotWare 5.10 or later
- GENERAL NOTES
1.1 - Tested on English Windows XP Professional and Windows 2000
The application is tested on a US English Windows XP Professional SP 2 and
Windows 2000 SP 4.
The recommended operating system is US English Windows XP Professional SP 2.
1.2 - Requirements
PickMaster requires .NET 1.1 and .NET 2.0. The required versions of .NET are
automatically installed when installing PickMaster.
The Windows Installer 3.0 is required for the installation and must be installed
before installing PickMaster. The Windows Installer 3.0 is included in Windows
XP SP2.
- FUNCTION RELATED NOTES
2.1 - Multiple robots
This release was not tested with 8 single robot systems. It has been tested with
a maximum of three robots. The software is designed to handle eight robots. This
release does also support multimove on the IRC5.
2.2 - Windows XP Service Pack 2
The firewall installed with Windows XP Service Pack 2 will prevent the
PickMaster Time Synchronization Service to function. This will cause any IRC5 to
function improperly. Please refer to the System Setup chapter in the User’s
Guide for further information.
2.3 - Upgrading RobotWare on IRC5
An upgrade of RobotWare to a new version may require an upgrade of the ABB
Industrial Robot Communication Runtime on the PC. The installation can be found
in the Utility folder on the RobotWare CD.
The ABB Industrial Robot Communication Runtime can also be updated by installing
the latest Robot Studio Online (RSO). It is hoever not recomended to run RSO on
the same computer as PickMaster. The separate ABB Industrial Robot Communication
Runtime installation is the recomended way to update.
Please note that when upgrading the baseware on the IRC5, the robot controller
will change its system identification. The robot controller must therefore be
reselected in the PickMaster line file. Please refer to The Line chapter in the
User’s Guide for further information.
2.4 - Encoder software version
The encoder board must have Qtracker version 1.9 or later. This version corresponds
to material number 3HNE01586-1/XX, where XX should be 11 or higher.
Instructions on how to check and change the software can be found on the PickMaster
support forum (http://www.robotstudio.com/).
2.5 - Upgrading from PickMaster 2.XX
Uninstall any previous versions of PickMaster before installing PickMaster 3.13.
The frame grabber drivers must be reinstalled.
Lines and projects from PickMaster 2.XX are compatible with PickMaster 3.13.
2.6 - Upgrading from PickMaster 2.23, or earlier, to 3.13 and frame grabber drivers
When upgrading from PickMaster 2.23, or earlier, to PickMaster 3.13 the frame
grabber drivers for Cognex MVS 8120 and MVS 8100 might not work. The drivers
must be manually uninstalled and reinstalled.
Windows renames the Cognex-provided cognexhw.inf file to a name of the form
oemnn.inf, where nn is an integer. To locate the correct oemnn.inf file to
delete, search for the string “Cognex” in all oemnn.inf files.
There may be more than one match if CVL or other Cognex software has been
installed several times on the PC. Delete all Cognex-derived oemnn.inf files.
Each such file will have a matching file with .pnf extension; delete those files
as well. For example, if oem23.inf contains the string “Cognex,” then delete
both oem23.inf and oem23.pnf.
Uninstalling Windows NT Drivers
After uninstalling CVL from a Windows NT system, make sure that the relevant
driver files were removed.
Check whether the following driver files were removed by the uninstallation. If
not, manually delete the appropriate files from Windows Explorer, as follows:
- MVS-8100 driver
(all versions): winntsystem32driversv8100.sys
Note The MVS-8100 driver applies to all MVS-8100C, MVS-8100C/CPCI,
MVS-8100M, and MVS-8100M+ frame grabbers. - MVS-8100L driver
(CVL 5.5.1): winntsystem32driversvp8100l.sys
(CVL 5.5.3 and later): winntsystem32driversfg8100l.sys - MVS-8100D driver
(CVL 6.0 and later): winntsystem32driversfg8100d.sys - MVS-8120 driver
(CVL 5.5 and later): winntsystem32driversfg8120.sys
Use the program “PickMasterFrame grabber driversSetup Cognex driver.exe” on
the PickMaster CD to reinstall the drivers.
2.7 - PickMaster RIS plug-ins must be reconfigured when upgrading to 3.13
The RIS configurations (Tcp, Serial, DigitalIO, Fieldbus) in PickMaster must be
reconfigured when upgrading to PickMaster 3.13 from PickMaster 2.xx due to
internal changes.
2.8 - New default signal names in PickMaster 2.10
New default signal names where introduced in the PickMaster 2.10. The new signal
names are adapted to suit the default signal names in the RobotWare 4.0.70 and
later. When upgrading a system to this version, the RobotWare must be upgraded to
4.0.113.
There are two different ways to handle the incompatibility:
-
Use the saved robot EIO parameters from the old RobotWare version. This will fit
the signal names in the projects created in PickMaster versions before
PickMaster 2.10. If new lines are created in PickMaster 3.13, the default signal
names must be changed. -
Change the saved EIO parameters and the signal names in the PickMaster lines
created in previous versions to the names shown below. Load the changed EIO file
to the controller.
Changes:
diSensor1 → di1_1
diSensor2 → di2_1
diSensor3 → di3_1
diSensor4 → di4_1
diSensor5 → di1_2
diSensor6 → di2_2
diSensor7 → di3_2
diSensor8 → di4_2
doPickStart1 → doStartCnv1
doPickStart2 → doStartCnv2
doPickStart3 → doStartCnv3
doPickStart4 → doStartCnv4
doPickStart5 → doStartCnv5
doPickStart6 → doStartCnv6
doPickStart7 → doStartCnv7
doPickStart8 → doStartCnv8
2.9 - Stop/Pause robot from RIS clients
In PickMaster 2.20 it is possible to stop a robot (see 4.3) and this command is
also added to the RIS plug-ins. Previous versions of the RIS plug-ins only had
the option to pause a robot even if the command might have been called stop. To
verify that the Pause and Stop commands are configured as expected and to add a
command value for the new Stop command open the configuration dialog for each
project accessed through a RIS plug-in and accept the changes.
2.10 - Dragging the Detailed vision info dialog box
The computer can hang