ABB Webware Server Admin Guide 4.9
ABB Webware Server Admin Guide 4.9
The information in this manual is subject to change without notice and should not be construed as a commitment by ABB. ABB assumes no responsibility for any errors that may appear in this manual. Except as may be expressly stated anywhere in this manual, nothing herein shall be construed as any kind of guarantee or warranty by ABB for losses, damages to persons or property, fitness for a specific purpose or the like. In no event shall ABB be liable for incidental or consequential damages arising from use of this manual and products described herein.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
This manual and parts thereof must not be reproduced or copied without ABB's written permission, and contents thereof must not be imparted to a third party nor be used for any unauthorized purpose. Contravention will be prosecuted. Additional copies of this manual may be obtained from ABB at its then current charge.
Copyright 1999-2006, 2008-2009 ABB All rights reserved. ABB AB Robotics Products 721 68 Vsters Sweden
Table of Contents
1.1 What is WebWare Server? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 1.2 WebWare Server Network Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 1.3 Information Flow and Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 2 Get Started with WebWare Server 23
2.1 Get Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 2.2 WebWare Server Implementation Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 2.3 WebWare Server Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 2.4 PC Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.5 Recommended Software for Performance Enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.6.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 2.6.2 Upgrading WebWare Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 2.6.3 Complete Installation of WebWare Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 2.6.4 Custom Installation of WebWare Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 2.6.5 License Key Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 2.6.6 How to request and install a license key over the Internet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 2.6.7 How to request a license key using e-mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 2.6.8 How to install a license key received by e-mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 2.6.9 Completing the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 2.6.10 Checking Your Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 2.6.11 Medium and Large System Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 2.6.12 Configure WebWare Server Authentication - Medium & Large Systems. . . . . . . . . . . . . . . . . . 54 2.6.13 Setting Up a Data Collector - Medium & Large Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 2.6.14 Creating Additional WebWare Data Collectors - Medium & Large Systems . . . . . . . . . . . . . . . 60 2.6.15 WebWare Server Database Setup for Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
2.7 Installing ABB WebWare Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
2.7.1 User Security Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 2.7.2 Download the Installation Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 2.7.3 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
2.8 Configuring System Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
2.8.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 2.8.2 Enabling the WebWare Interface - Small Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 2.8.3 Determining the IP Address of Robots on Your Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 2.8.4 ABB Robot Configuration Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 2.8.5 Connecting a Robot to a Data Collector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 2.8.6 Creating a Robot Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 2.8.7 Robot Aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 2.8.8 How to Add S4 Robot Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 2.8.9 How to Add IRC5 Robot Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 2.8.10 Connecting Other Device Types to a Data Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 2.8.11 Plant Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 2.8.12 Checking System Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 3 WebWare Server Module 85
3.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
3HAC031359-001 Revision: B 3
Table of Contents
3.2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 3.2.2 Settings Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 3.2.3 Devices Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 3.2.4 Data Collector Setup Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 3.2.5 Database Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 3.2.6 How to Restore an Archived Database to a New Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 3.2.7 Backup Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 3.2.8 How to Configure Backup and Archive File Folder Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 3.2.9 How to Configure IIS when Storing the Windows User Name in the Backup Log . . . . . . . . . . 115 3.2.10 Reports Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
3.3 License Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
3.3.1 ABB Robotics License Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 3.3.2 WebWare License Priority. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
3.4 User Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
3.4.1 Help Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 3.4.2 Documentation Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 3.4.3 How to Add Content to the Documentation Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 4 WebWare Report Module 127
4.2.1 Info Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 4.2.2 Data Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 4.2.3 WebWare Server Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 4.2.4 Relocating a WebWare Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 4.2.5 Creating a New WebWare Server Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 4.2.6 Custom Database Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 4.2.7 How to Enable WebWare Reports for Custom Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 4.2.8 Data Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 4.2.9 WebWare Data Event Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 4.3.1 Reports Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.2 Report Viewer Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.3 Report Manager Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.4 How to Build a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.5 Report Builder Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.6 How to Edit Reports You've Created . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.7 How to Run a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.8 How to Add an Existing Module to Your Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.9 How to Create a Chart/Table Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.10 How to Set Up Chart/Table Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.11 How to Build a Database Query. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.12 How to Use the Query Builder Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.13 How to Apply Design-Time Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.14 How to Apply Chart Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.15 How to Apply Table Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.16 HTML Module Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.17 How to Add an HTML Module to Your Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.18 How to Export a Table to Excel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.19 How to Export Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.20 How to Import Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.21 How to Enable Log Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.22 Service Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 167 168 169 170 172 173 174 175 176 177 178 188 190 191 192 193 194 195 196 197 199
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
3HAC031359-001 Revision: B
Table of Contents
4.3.23 How to configure Service Information System (SIS) for IRC5 . . . . . . . . . . . . . . . . . . . . . . . . . 202 4.3.24 Service Information System (SIS) Logs Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 5 WebWare Backup Module 205
5.2.1 Network File System (NFS) Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 5.2.2 How to Configure NFS at the Device Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 5.2.3 How to Configure an NFS Mount for an S4 Robot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 5.2.4 How to Configure an NFS Mount for an IRC5 Robot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 5.2.5 How to Restore Files from an NFS Mount Using the Robot Teach Pendant. . . . . . . . . . . . . . . . 214 5.2.6 How to Restore Files from an NFS Mount Using the Robot Flex Pendant . . . . . . . . . . . . . . . . . 216 5.2.7 File Management Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
5.3 WebWare Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
5.3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 5.3.2 How to Configure WebWare Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 5.3.3 How to Configure WebWare NFS Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 5.3.4 Backup Control Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 5.3.5 How to Use On-Demand Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 5.3.6 Backup Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 5.3.7 Backup Status Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 5.3.8 Backup Schedule Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 5.3.9 Schedule Manager Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 5.3.10 How to Schedule Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 5.3.11 Backup Results Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 5.3.12 How to Display Backup Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 5.3.13 Backup Restore Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 5.3.14 How to Use the WebWare File Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 5.3.15 How to Use the Restore Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 5.3.16 How to Restore a Backup Using WebWare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 5.3.17 Backup Summary Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
5.4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 5.4.2 How to Set Up a Data Collector as a Ramdisk Mirror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
5.5 WebWare Visual SourceSafe Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
5.5.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 5.5.2 Configuring WebWare Visual SourceSafe Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 5.5.3 WebWare Visual SourceSafe Module Screen Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 5.5.4 Retrieving Latest File Version from Visual SourceSafe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259 5.5.5 Retrieving Selected File Version from Visual SourceSafe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 5.5.6 Viewing File Differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 5.5.7 Assigning File Types in Visual SourceSafe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262 6 System Reference 263
6.2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 6.2.2 General Installation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 6.2.3 Installing Internet Information Services (IIS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 6.2.4 Enabling Administrative Tools in Start Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 6.2.5 Accessing the IIS Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 6.2.6 Configuring IIS to Host WebWare as a Virtual Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 6.2.7 Selecting the Default Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 6.2.8 Enabling Execute Permissions for WWBin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
3HAC031359-001 Revision: B 5
Table of Contents
6.2.9 Running the .Net Installation Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 6.2.10 Configuring IIS with Personal Web Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 6.2.11 Custom Installation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 6.2.12 Configuring IIS to Host WebWare as a Default Web Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 6.2.13 Installed Files and Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
6.3 Windows Service Pack Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
6.3.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3.2 ABB WebWare Security Settings Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3.3 Windows Firewall Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3.4 DCOM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.4.1 WebWare RAPID Module (WebWare.sys) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291 6.4.2 Controlling WebWare Backup from WebWare.sys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292 6.4.3 RAPID Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296 6.4.4 WWRestore Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 6.4.5 WebWare RAPID Restore Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299 6.4.6 WWStartBackup Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 6.4.7 WWIncrCounter Instruction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 6.4.8 WWStartTimer Instruction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 6.4.9 WWStopTimer Instruction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313 6.4.10 WWLogTimedEvent Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315 6.4.11 WWSetProgramInfo Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 6.4.12 WWSetLabels Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318 6.4.13 WWSetField Instruction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319 6.4.14 WebWare Server Link State Heartbeat Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
6.5 Return Status Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
3HAC031359-001 Revision: B
6.5.1 Return Status Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5.2 RPC Communications Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5.3 InterLink Module Communication Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5.4 General Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5.5 InterLink FTP Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5.6 InterLink Error Code Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5.7 InterLink Monitor Connecting Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5.8 Variable Handling Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5.9 Program Handling Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5.10 File Handling Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5.11 Configuration Handling Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5.12 Log Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.6 WebWare Server Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
321 322 323 325 326 327 329 331 333 334 335 336 338
Overview
Overview
About This Manual This manual contains information and procedures to install, configure, administer and use the ABB WebWare Server. Usage This manual should be used during installation, configuration, administration and use of the ABB WebWare Server. Who Should Read This Manual? This manual is intended for: Prerequisites The reader should:
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Be familiar with basic robot concepts. Have knowledge and understanding of computers and computer networks as well as robots and robot controllers. Know generic program handling on a computer with the Windows operating system. Know how to administer, configure and install the Microsoft Windows operating system.
Contents
Introduction to WebWare Server and network topology. How to install WebWare Server on a PC and connect robot controllers and other devices on the WebWare network to it. It also describes how to install the WebWare Server Web Client. How to administer WebWare Server. Describes the features of the WebWare Server Report Module that allows you to remotely monitor the state of the devices connected to your WebWare Server network. It also describes how to create custom reports to display production and service status information about devices on the WebWare Server network.
Contents
Describes the features of the WebWare Server Backup Module that allows you to move files on and off robot controllers to backup the investment you have made in robot programming, even using popular version control systems such as Microsoft Visual SourceSafe. Reference information containing detailed information on the rich user interfaces provided by WebWare Server and its components, as well as error code explanations and more.
6. System Reference
References Reference
-
Document Id
Revisions Revision
A B Released with WebWare 4.9.
Description
First release
3HAC031359-001 Revision: B
3HAC031359-001 Revision: B
Glossary
Glossary
Important Terms The table below defines terms as we will use them in describing concepts in WebWare products. Term
Alarms
Definition
OPC events that indicate a problem with some part of the system. OPC alarms include several conditions, including type, severity, state, name, etc. The named instance of a robot controller accessed by InterLink. The list of files, robot program modules, log files, etc. that you selected for backup from a robot controller. ABB robot controller operating system software. Counters count event occurrences over a given time frame. Typical WebWare counters are ideal for counting parts per hour and failures per hour, often set from RAPID robot controller counter functions. Any computer that has InterLink software installed on it. A Data Collector collects data from robot controllers and pushes that data up to WebWare Server. The WebWare Data Event Editor allows you to increment WebWare counters or start and stop WebWare timers based on an OPC tags state. A data source name (DSN) is a data structure that contains information about a specific database that an Open Database Connectivity (ODBC) driver needs to connect to it. Included in the DSN, which resides either in the registry or as a separate text file, is information such as the name, directory and driver of the database, and depending on the type of DSN, the user ID and password. A default web site is the first site that will appear when a browser is pointed to http://hostname where hostname is the name of the server PC. Program that allows users to configure robot aliases and profiles for use in the WebWare system. File that stores event messages from the robot. Something that happens. In WebWare, typical events include StatusChanged events, Help events etc.
Data Collector
Data Event
Extensible Markup Language XML, a formal recommendation from the World Wide Web (XML) Consortium (W3C), is similar to the language of today's Web pages, the Hypertext Markup Language (HTML). XML is a markup language for documents containing structured information. Hypertext Transfer Protocol (HTTP) Protocol used for transferring files (text, graphic images, sound, video, and other multimedia files) on the World Wide Web.
Hypertext Markup Language The set of markup symbols or codes inserted in a file intended (HTML) for display on a World Wide Web browser page. InterLink Module The ABB InterLink Module provides the core communications support needed for ABB WebWare products.
Definition
Utility program that allows users to monitor the connection status of devices connected to the WebWare network. The InterLink executable object that is installed in the registry database maintained by the Service Control Manager. The InterLink service, when installed, allows InterLink to be started at boot time by a boot program, by the system, or it can be started on demand by the Service Control Manager. The numeric Internet Protocol address that uniquely identifies each computer on a network that uses TCP/IP. The IP address is a 32-bit identifier made up of four groups of numbers, each separated by a period, such as 123.432.154.12. A license key allows you to use an application or a feature of an application that you have purchased from ABB. A license key is a data record in a license file. You will receive one or more license files each containing one or more license keys for the various applications that you have purchased from ABB. A request received either electronically or via mail, for a license key that will allow you to operate a piece of ABB software or a feature of an ABB software product. An additional application or device connected to the same Robot alias on a WebWare network. Individual error or event messages that are grouped into a log file. Microsoft Message Queuing (MSMQ) technology enables applications running at different times to communicate across heterogeneous networks and systems that may be temporarily offline. Applications send messages to queues and read messages from queues. MSMQ provides guaranteed message delivery, efficient routing, security and priority-based messaging. It can be used to implement solutions for both asynchronous and synchronous messaging scenarios. The ABB Network File System (NFS) option was originally designed to provide an alternative method for restoring files to a robot controller via a Teach Pendant.
IP Address
License Key
License Request
Open Database Connectivity An open standard application programming interface (API) for (ODBC) accessing a database. OLE for Process Controls (OPC) A standard interface developed by the OPC Foundation. It allows factory floor devices, business information and control systems to communicate with each other using a standard industrial protocol. The OPC specifications are available at http://www.opcfoundation.org. Any Object Linking and Embedding (OLE) for Process Controls (OPC) compliant device. Devices could include PLCs, HMI devices etc. The OPC Server is an ABB software product that provides an interface to all robot controllers using the OLE for Process Controls (OPC) specification. In RAPID, a variable that keeps its value between sessions.
OPC Device
OPC Server
Persistent Variables
Definition
This field contains the InterLink polling delay in milliseconds. The polling delay is the amount of time the robot interface sleeps between polling cycles. The default polling delay is 200 milliseconds. A profile is a group of properties and parameters that determine the behavior of a robot alias. In an ABB robot controller, a memory device located in the controllers RAM. Provides an application interface to the ABB Robot Controllers. RAP provides a set of services that you can use to control and monitor ABB Robots from an external computer. Programming language used to program ABB robots. The naming device used by InterLink to refer to a designated device on the WebWare network. RAPID programs consist of one or more modules. There are two types of modules:Program modules - contain the RAPID program statementsSystem modules - configuration parameters and robot settings A program, routine, or process that performs a specific system function to support other programs, particularly at a low (close to the hardware) level. An interface that allows InterLink to respond to all functions and methods, even though InterLink is not connected to a real robot controller. Used for application development. The Microsoft program that manages Structured Query Language (SQL) databases. When referring to the product or the server running the product, SQL is pronounced sequel and takes the article a when not preceded by Microsoft - for example, an SQL Server.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Profile Ramdisk Robot Application Protocol (RAP) RAPID Robot Alias Robot modules
Service
Simulated Interface
SQL Server
Structured Query Language (SQL) Tags Task scheduler Transfer Control Protocol (TCP) Timers
SQL is a standard interactive and programming language for getting information from and updating a database. A tag is a name or a label for a piece of data or a data point. WebWare uses tags to label data on various display pages. A Windows utility that can run a script, program or document at a pre-selected time, either on a one-time or repeating basis. A protocol used along with the Internet Protocol (IP) to send data in the form of message units between computers over the Internet. A software routine that causes the system to trigger an event whenever a specified interval elapsed or at user-defined intervals. Typical timers in WebWare are used to measure cycle time, squeeze time, hold time, etc. An address that uniquely identifies a location on the Internet. A URL for a World Wide Web site is preceded with http://, as in the fictitious URL http://www.example.microsoft.com. A URL can contain more detail, such as the name of a page of hypertext, usually identified by the file name extension .html or .htm. A virtual directory is addressed as http://hostname/vdir where vdir is the name of the virtual directory created by the site administrator.
Virtual Directory
Definition
A source code repository program from Microsoft used to store and maintain version control of software components. WebWare is a suite of products that provide a web site for process monitoring, file management, collection of production statistics and diagnostic information. The WebWare family consists of WebWare Server (the web site software) and the WebWare SDK for developing custom factory-floor PC operator stations. A WebWare utility that backs up a robot program or selected robot modules. WebWare Server is a standard software product used to present production data, statistics, and diagnostic information collected from S4 robot controllers, HMI applications, and other factory floor automation equipment. The computer that is the WebWare Server host computer. The machine where WebWare Server software is installed. Software that allows a remote computer to browse to the WebWare Server web site. Requires Windows Internet Explorer.
3HAC031359-001 Revision: B
13
14
Glossary
3HAC031359-001 Revision: B
WebWare Server comes with two optional modules, the Backup module and the Report module. The table below provides an overview of the optional modules. Function
Device Information Reports & Data Collection Backup Documentation Administration Login Help
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Server Module
X
Report Module
X
Backup Module
X X X X (X) (X)
Each of the following sections describes the major capabilities of WebWare Server and its modules. WebWare Backup Module Your plant network provides the communication infrastructure that WebWare Server uses for plant-wide file management. Any equipment that supports the FTP file transfer protocol can be included in WebWare Servers file management & backup system. WebWare Servers Backup module features accelerate fault recovery by providing ready access to the archive of production programs, allowing for rapid recovery in the event of equipment substitution or the need for post-repair software reloads. Additionally, version control of programs (available if you have Microsoft Visual SourceSafe) permits online visual review of change history to correlate program changes with quality problems. The ability to perform unattended, scheduled backups is practical for safeguarding critical part programs and tracking program changes. Once your production files are safely archived, you can restore them to the device controller or download them directly to your PC for offline program maintenance. WebWare Server includes built-in support for Microsoft Visual SourceSafe and NFS; this provides additional capabilities for efficient file handling and secure version control, including change history and version comparison.
For more information, see WebWare Server Database on page 135. WebWare RAPID Module You can also create custom tables in your WebWare Server database and populate those tables with information from your RAPID programs. For more information, see Custom Database Tables on page 145. WebWare SDK Applications Using the WebWare SDK, you can develop custom applications (gateways to other IT systems, factory devices, etc.) that can provide additional data to WebWare Server for archiving and subsequent access. The WWClientApp control, when embedded in an application that you have developed, can write records to the WebWare Server database, via InterLink. Remote Diagnostic & Service Information WebWare continuously monitors connected equipment, logging diagnostic information. By storing this information external to the equipment, it is readily available to local and remote users. Even if the production system is down, remote experts have access to the information through their web browser.
16
3HAC031359-001 Revision: B
xx0500001582
WebWare Server The WebWare Server is a host computer running WebWare Server software. The host collects and stores the data received from the Data Collectors in the SQL database (devicelog.mdf). WebWare Server uses Microsoft Internet Information Services (IIS) to present the web site. The browser-based user interface provides access to both dynamic and historical data. Data Collector In WebWare terminology, a Data Collector is a computer that communicates with one or more WebWare devices (robot controllers, WebWare HMI applications or OPC devices) and feeds that information to WebWare Server. The Data Collector concept was developed to streamline data collection and network traffic in large installations by distributing the data collection task.Typically, a Data Collector is a factory floor PC that may host an operator interface or other factory computer application. Since Data Collectors are usually installed close to robot controllers, they often serve as plant floor operator interfaces or cell controllers in addition to being WebWare Data Collectors. Continues on next page
3HAC031359-001 Revision: B 17
18
3HAC031359-001 Revision: B
xx0500001583
The following diagram depicts the key functional blocks needed to understand the WebWare Server communication architecture.
xx0500001584
The fact that the InterLink Module is installed on the WebWare Server host computer means that we can think of the host as a Data Collector as well as a server. The various communications paths are described in the following sections.
3HAC031359-001 Revision: B
21
22
3HAC031359-001 Revision: B
3HAC031359-001 Revision: B
23
Typical Implementation The table below lists the major phases of a WebWare Server installation project. 1. Determine your system design based on the number of devices you will connect to the WebWare Server system. 2. If necessary, install and configure the PC Interface on each robot that will be connected to the WebWare Server system. 3. Install the plant network infrastructure. 4. Install any external Data Collectors and connect them to the plant network. 5. Connect any other plant devices to the plant network. 6. Install the WebWare Server software on the host computer, and install the Data Collector software on any Data Collectors in the WebWare Server system. 7. Configure the devices in the system to communicate with WebWare Server.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
24
3HAC031359-001 Revision: B
Check that Microsoft Internet Explorer 6.0 is installed. You can download it from http:// www.microsoft.com/windows/ie/default.mspx. System Configuration Requirements Check that the Administrative Tools folder is available in the Start-menu of your Windows operating system. For details, see the following information: Enabling Administrative Tools on Windows 2000 Professional on page 269. Enabling Administrative Tools on Windows XP Professional on page 269.
Check your domain name and computer name. Open the Control Panel and then click System. The System Properties property sheet appears. Select the Computer Name tab and write down the following information for future reference. Full Computer Name:________________________________ Domain:__________________________________________
Network Domain Configuration Requirements Check that all Data Collectors and the WebWare Server has valid trust relationships established in the domain. If not, the system might not operate properly. Contact your server administrator to set up the proper trust relationships. WebWare Server Installation Install WebWare Server. For further details, see Installing WebWare Server on page 38. Request a license key. For further details, see License Key Installation on page 44. Reboot the machine when prompted to do so. Data Collector Installation Install the Data Collectors. For more information, see the following information: Setting Up a Data Collector - Medium & Large Systems on page 56. Creating Additional WebWare Data Collectors - Medium & Large Systems on page 60.
Data Collector Configuration Enable the WebWare Server Interface. For more information, see How to Configure the WebWare Server Interface in the Device Configuration Utility help file. Check that ABB InterLink Monitor has started. The ABB InterLink Monitor icon will be visible in the notification area. If not, start InterLink Monitor by clicking Start, point to Programs or All Programs, ABB Industrial IT, Robotics IT, WebWare Server, and then click InterLink Monitor.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
WebClient Installation Check that Microsoft Internet Explorer 6.0 is installed. You can download it from http:// www.microsoft.com/windows/ie/default.mspx. Check that the security settings allow you to download and run ActiveX controls. For more information, see User Security Settings on page 62. Install WebWare Server WebClient. For more information, see Overview on page 65. Robot Configuration NOTE: The robot must have the BaseWare Option "FactoryWare Interface" (S4systems) or "PC Interface" (IRC5-systems) installed. Check that the IP address is configured in the robot. TCP/IP is configured using an X-start. On the TeachPendant select Service, File, Restart + 159. Check that you have a connection to the robot. Open a command prompt and ping the IP address of the robot. Check that you have a list of IP addresses for all your robots for future reference. Check that you have loaded the WebWare.sys module. On the TeachPendant select Program, File, Open. The module is needed to e.g. restore files on the robot system disk using the TPU, but not essential for communicating with the robot. For more information about the WebWare.sys module, see WebWare RAPID Module (WebWare.sys) on page 291. Continues on next page
26 3HAC031359-001 Revision: B
At the Data Collector, check that ABB InterLink Monitor has started. The ABB InterLink Monitor icon will be visible in the notification area. If not, start InterLink Monitor by clicking Start, point to Programs or All Programs, ABB Industrial IT, Robotics IT, WebWare Server, and then click InterLink Monitor. At the Data Collector, use the Device Configuration Utility to check that WebWare Server is running. In the WebWare Server Interface Configuration dialog the WebWare Current Connection Status will state Running. For more information, see How to Configure the WebWare Server Interface in the Device Configuration Utility help.
3HAC031359-001 Revision: B
27
xx0500001585
By configuring the system so the WebWare Server host machine is set up to also function as the Data Collector, you save the expense of an additional computer to handle data collection duties. Small System Server Hardware Requirements The list below details the hardware requirements for the network server computer. Late Model Intel Processor (Pentium 4 or newer) 512 megabytes RAM 20 gigabytes available hard disk space plus enough hard disk space to store one backup for each robot system in the plant SVGA compatible display (1280 x 1024 resolution recommended) Microsoft-compatible mouse Network adapter configured for TCP/IP CD drive Backup system (Recommended) Uninterruptable Power Supply (Recommended) Continues on next page
28 3HAC031359-001 Revision: B
For service pack download information, see Operating System Service Packs on page 34. Medium Systems (6 - 30 Devices) The diagram below shows a medium-sized WebWare Server network.
xx0500001586
A medium size WebWare network requires a more robust server computer, especially if the server will also act as a Data Collector. For more information, see Data Collector on page 17. Normally, Data Collector computers are required on large systems. If your system will generate a large volume of network traffic, however, a separate Data Collector will improve performance significantly on a medium-sized system.
Medium System Server Software Requirements The list below details the software requirements for a medium-sized WebWare Server network. Microsoft Windows Server 2003 Standard Edition and Web Edition, or Microsoft Windows 2000 Server and Advanced Server Microsoft Internet Information Services (IIS), see Installing Internet Information Services (IIS) on page 266. Microsoft Internet Explorer 6.0 Microsoft SQL Server 2000 or later. Microsoft SQL Server is required to handle the performance required for the database writes that will occur on an active system. For details, see Microsoft SQL Server on page 37. Microsoft Visual SourceSafe 6.0 (Recommended). For details about configuring and using Microsoft Visual SourceSafe on your system, see WebWare Visual SourceSafe Module on page 255.
For service pack download information, see Operating System Service Packs on page 34.
xx0500001587
The following sections detail hardware and software requirements for the WebWare Server host computer and the Data Collector computers.
Large System Server Software Requirements The list below details the software requirements for the WebWare Server host computer: Microsoft Windows Server 2003 Standard Edition and Web Edition, or Microsoft Windows 2000 Server and Advanced Server Microsoft Internet Information Services (IIS) Microsoft Internet Explorer 6.0 Microsoft SQL Server 2000 or later. Microsoft SQL Server is required to handle the performance of the database writes that will occur on an active system. For details, see Microsoft SQL Server on page 37.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Microsoft Message Queuing (MSMQ) version 2.0 or later, installed and configured, see MSMQ on page 36. Microsoft Visual SourceSafe 6.0. For details about configuring and using Microsoft Visual SourceSafe on your system, see WebWare Visual SourceSafe Module on page 255.
For service pack download information, see Operating System Service Packs on page 34. Data Collector Computer Hardware Requirements The Data Collector hardware requirements are listed below. Late model Intel processor (Pentium 4 or newer) 512 megabytes RAM 5 gigabytes available hard disk space plus enough hard disk space to store one backup for each robot system in the plant SVGA compatible display (1280 x 1024 resolution recommended) Microsoft compatible mouse Network adapter configured for TCP/IP CD-drive
For service pack download information, see Operating System Service Packs on page 34. Data Collector Software Recommendations For best performance, especially in large systems, we recommend the following components, above and beyond the minimum requirements listed above: Microsoft Message Queuing 2.0 or later - especially for large (5+ robot) systems, see MSMQ on page 36. Requires no additional configuration.
How Many Data Collectors Are Needed? Determining how to dimension and set up your WebWare network depends on the robot application and use, amount of generated data traffic, polling cycle time, the network architecture, and of course, the number and physical location of robots on the network. Currently, we recommend that you install one Data Collector for every 30 robots on the network. Even for medium-sized systems, unless the server computer is a robust system with a large amount of memory and fast hard drives, you should seriously consider installing Data Collector computers for maximum system performance and reliability. The Data Collector is not required to be devoted only to WebWare Server tasks. Web Client Computer Requirements The web client computer is any computer that has the capability of browsing to the WebWare Server web site.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Hardware There are no minimum hardware requirements for a web client computer. We recommend, however, a SVGA compatible display (1280 x 1024 resolution recommended). Software Microsoft Windows XP Professional, or Microsoft Windows 2000 (any version) Microsoft Internet Explorer 6.0
For Service Pack Download information, see Operating System Service Packs on page 34. Administrative and Network Requirements To install WebWare Server, you must be a system administrator with an administrator password. IMPORTANT: All Data Collectors and the WebWare Server host computer must have valid trust relationships established in the domain in order to operate properly. Contact your server administrator to set up the proper trust relationships.
34
3HAC031359-001 Revision: B
3HAC031359-001 Revision: B
35
2.5.2. MSMQ
Overview At the server, Microsoft Message Queuing (MSMQ) provides data preservation if the database connection is lost. Likewise at the Data Collector, MSMQ preserves data if the connection to the server is lost. If you do not install MSMQ, the WWService.exe and InterLink demand larger amounts of memory. MSMQ writes the message queue in transit between senders and receivers to disk, rather than to the RAM, thereby protecting it and providing a place for receivers to look for messages when the receivers are ready to receive them. Applications use MSMQ to send messages and continue processing regardless of whether the receiving application is running or reachable over the network. The receiving application may be unreachable because of a network problem, or because of natural disconnection, as in the case of mobile users that only connect to the network periodically. When applications use the transactional delivery mode in MSMQ, MSMQ also makes sure that messages are delivered exactly one time, and that messages are delivered in the order that they were sent. Configuring MSMQ on the WebWare Server To properly configure MSMQ, you need to start WWService with a dependency on MSMQ using the -serviceMSMQ switch. 1. Unregister WWService as a service, as follows:
C:\Program Files\Common Files\ABB Automation\WebWare Server\WWService.exe -unregServer
2. Since unregistration removes the DCOM settings, configure the security settings by following the procedure in ABB WebWare Security Settings Utility on page 287. 3. Re-register WWService as a service, as follows:
C:\Program Files\Common Files\ABB Automation\WebWare Server\WWService.exe -serviceMSMQ
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
This setting creates a dependency allowing MSMQ to start before WWService. The dependency can be verified by opening the Services dialog (Control Panel, Administrative Tools), right-clicking the ABB WebWare Server and selecting Properties, and then clicking the Dependencies tab.
36
3HAC031359-001 Revision: B
To properly configure Microsoft SQL Server, you will need the following information: Database User Name and Password with read/write access in Microsoft SQL Server The name of the Microsoft SQL Server
3HAC031359-001 Revision: B
37
38
3HAC031359-001 Revision: B
4. Open your browser to http://localhost/webware/update.aspx. 5. Click Update. 6. When you run WebWare Server, your reports will appear in the Report Viewer page, the same as in the old web site. Uninstall Procedure To install a new version of WebWare Server, you must first uninstall the older version. Follow the steps below to unistall the old version of WebWare Server. 1. Click Start and select Control Panel. Click Add/Remove Programs. 2. Select WebWare Server from the program list. Click Remove. 3. A WebWare Server installation dialog appears. Click Next. 4. The Remove the Program dialog appears. If you wish to retain your existing WebWare Server database and the data stored locally on the host hard drive. Click Remove. If you wish to delete the existing WebWare Server database and the data stored locally, select Remove WebWare Application Data checkbox.
5. Click Remove.
7. Click Finish to close the Setup Program Completed dialog. 8. Go on to install the new version of the WebWare Server software. For details, see Complete Installation of WebWare Server on page 41.
40
3HAC031359-001 Revision: B
NOTE: The instructions above assume the drive letter for the CD-drive you are loading from is your D: drive. If you are using a different drive, substitute your drive letter in place of D: in the instructions. For example, if your CD-drive is E:, enter E:\SETUP. 3. The Welcome dialog will appear. Click Next to continue. 4. The License Agreement dialog will appear. Select I accept. Click Next. 5. The Customer Information dialog will appear. Enter the name of your company in the Organization field. Click Next. 6. The ABB WebWare Server modules dialog appears. Select the WebWare modules to install. Available modules are:
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
After you have made your selection, click Next. 7. The Setup Type dialog appears. Click: Complete - to install all features. This is the recommended installation. Custom - to choose which features are installed and their installation locations. The Custom Setup dialog will appear. For more information, see Custom Installation of WebWare Server on page 43.
After you have made your selection, click Next. 8. The Ready to Install dialog will appear. Select: Use this PC - to set up the PC as a Data Collector. Use this setting only for small (15 devices) or medium (6 - 30 devices) systems. For more information, see Data Collector on page 17. Install Support for S4 Controllers - to set up WebWare Server to support ABB S4 robot controllers. Install Support for IRC5 Controllers - to set up WebWare Server to support ABB IRC5 robot controllers. Create Desktop Shortcuts - to install desktop shortcuts to the Device Configuration Utility and InterLink Monitor on the WebWare Server desktop. Continues on next page
3HAC031359-001 Revision: B 41
42
3HAC031359-001 Revision: B
xx0500001588
Component
Select Window Space Button <Back Button Next> Button Cancel Button Change Button
Function
Contains an expandable tree view of all components that can be installed. Displays the Disk Space Requirements dialog, showing the available and required disk space for selected components. Display the previous dialog. Display the next dialog. If no custom selections were made, the installation continues, using the default settings To exit the installation program. Display the Change Current Destination dialog. This dialog allows you to create new folders or browse to alternate component installation locations.
3HAC031359-001 Revision: B
43
3. Browse to the WebWare Server Home page, e.g. http://localhost/webware. Verify that installed modules and installed licenses are correct. You might have to scroll down the page.
44
3HAC031359-001 Revision: B
xx0500002083
2.6.6. How to request and install a license key over the Internet
Overview The License Key Request Wizard generates a request for a license key that will allow you to access and run the product. Run the wizard to request and automatically install the license key over the Internet. This will allow you to access the product that you purchased and run it on your computer. Before you begin Procedure Follow the steps below to run the License Key Request Wizard: 1. Launch the License Key Request Wizard using one of the following methods: Run the wizard when prompted to do so during a product installation. In the Start menu, click Start, point to Programs, ABB Industrial IT, Robotics IT, Licensing, and then click License Key Request Wizard. Make sure that you have the License ID number that appears on the ABB License Certificate. You need this number to complete the license key request. Make sure you are working from the client workstation where the software product is installed. Make sure you are connected to the Internet.
2. The Welcome page appears. Click Next. 3. The Select Product page appears. When the wizard is launched from a product installation, it automatically selects the product you are installing. If the wizard is launched from the Windows Start menu, select the product for which you require a license. Click Next. 4. The Product License Information page appears. Enter the License ID number from the ABB License Certificate in the License ID box, and click Next. Note: A standalone License ID always starts with an R, whereas a network License ID, starts with an F. 5. The User Information page appears. Enter the appropriate information in each box. All boxes marked with an asterisk (*) are mandatory. Note: The license key will be sent to the e-mail address specified in this dialog box, not to where the e-mail is sent from. Select the country name from the list box and click Next. 6. The Standalone license page appears. Select an Ethernet adapter to which the license will be locked, and click Next. 7. The Obtaining your license key from ABB page appears. Select Internet and click Next.
46
3HAC031359-001 Revision: B
Procedure Follow the steps below to run the License Key Request Wizard. 1. Launch the License Key Request Wizard using one of the following methods: Run the wizard when prompted to do so during a product installation. In the Start menu, click Start, point to Programs, ABB Industrial IT, Robotics IT, Licensing, and then click License Key Request Wizard.
3. The Select Product page appears. When the wizard is launched from a product installation, it automatically selects the product you are installing. If the wizard is launched from the Windows Start menu, select the product for which you require a license. Click Next. 4. The Product License Information page appears. Enter the license ID number from the ABB License Certificate in the License ID box, and click Next. Note: A standalone license ID always starts with an R, whereas a network license ID starts with an F. 5. The User Information page appears. Enter the appropriate information in each box. All boxes marked with an asterisk (*) are mandatory Note: The license key will be sent to the e-mail address specified in this dialog box, not to where the mail is sent from. Select the country name from the list box and click Next. 6. The Obtaining your license key from ABB page appears. Select E-mail and click Next. 7. The Save your License Key Request page appears. Click Save to save the license key request form to your desktop, or browse first to a different location. Click Next.
48
3HAC031359-001 Revision: B
Procedure 1. Launch the License Key Installation Wizard using any of the following methods: Double-click a license key file (.xlkf extension). In the Start menu, click Start, point to Programs, ABB Industrial IT, Robotics IT, Licensing, and then click License Key Installation Wizard. Select the root node in the Software Product Administrator (SPA) and run the Install License Key command.
2. The Welcome page appears. If you double-clicked the license key file, the box will automatically display the path and file name of the file. If not, use this page to specify the location of the license key file from which to install the license keys. Click:
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Browse to open a dialog box to navigate to the location of the license key file. Next to verify that the selected file exists and is a valid license key file. If no such file exists or if the ABB License System determines that the file is not a valid license key file, an error message dialog box appears.
3. The License Information page appears. This step contains two different procedures, depending on the type of license you are installing. If you are installing a network license, select the Install the network license keys on the License Server computer check box to enable the Install button. If you are installing a standalone license, and if all relevant hardware parameters match, the Install button is already enabled. If the hardware fingerprint contained in the license key file does not match the fingerprint of the local computer: The Install button is disabled when a conflict is discovered in the license key file. The View Details button appears. The Permit these Standalone check box appears. A warning message appears.
4. Click Install to install the license key on the system. 5. Click Finish to exit the wizard.
50
3HAC031359-001 Revision: B
xx0500001590
NOTE: If WWService.exe is running it has to be restarted for the new license to take effect.
3HAC031359-001 Revision: B
51
52
3HAC031359-001 Revision: B
3HAC031359-001 Revision: B
53
2. Expand the Services and Applications tree, and click Services. The list of installed services will appear in the right hand panel. 3. At the Computer Management Console, right click on ABB WebWare and select Properties. 4. The Properties dialog box will appear. Select This Account. 5. Click Browse. The Select User dialog will appear. 6. Select the correct computer name from the Look In list box. This is the computer name that identifies the computer on the network. If you are not sure which name to use, open the System Properties function inside the Windows Control Panel and click on the Computer Name tab. 7. Select the logon user account from the list that appears and then click OK. Important: The user that you select must be a domain-authenticated user! If you are not sure, contact your network administrator for help! 8. The Log On tab appears. Enter and confirm the user log on password. 9. Click OK. The Computer Management console will reappear, and the Log On As column for WWService will now show the user name that you selected in step 7. 10. Reboot the computer before continuing with web site configuration tasks.
3HAC031359-001 Revision: B
55
2. Configure InterLink to run as a service. For more information, see Configure InterLink to Run as a Service on page 57. 3. Configure InterLink as a Recognized Domain User. For more information, see Configure InterLink as a Recognized User on page 57.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
4. Enable the WebWare Server interface. For more information, see Configure the Data Collector - WebWare Server Interface on page 58. 5. Verify the Data Collector-WebWare Server connection. For more information, see Overview on page 81. 6. Verify WebWare Server device connections. Refer to Verify Devices with the InterLink Monitor on page 82 for complete details. 7. For large systems, you may also need to install Microsoft Message Queuing (MSMQ) to preserve data in case a part of the network goes down. Refer to Microsoft documentation for that installation.
2. Click OK. Configure InterLink as a Recognized User Follow the steps below to configure InterLink to run as a recognized user on the WebWare Network. 1. Right click on My Computer and select Manage to open the Computer Management console. 2. Expand the Services and Applications tree, and click Services. The list of installed services will appear in the right hand pane. 3. At the Computer Management Console, right click on ABB InterLink and select Properties. The Properties dialog box will appear. 4. On the General tab, select Automatic from the Startup type list box and click Apply. 5. Open the Log On tab. Select the This Account radio button. 6. Click Browse. The Select User dialog will appear.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
7. Select the correct computer name from the Look In list box. 8. Select the logon user account from the list that appears and then click OK. 9. The Log On tab reappears. Enter and confirm the password. Click OK. The Computer Management console will reappear, and the Log On As column for ABB InterLink will now show the user name that you selected in the previous step. 10. Reboot the computer before continuing with the remaining Data Collector configuration tasks.
xx0500001592
2. Select the Enable WebWare Interface box. The Edit Host File button should now be enabled. Click Edit Host File. The Edit Host File dialog will appear.
xx0500001593
3. Click Add. The Add New Host Entry dialog will appear.
xx0500001594
xx0500001595
6. Click OK to start the interface. 7. Reboot the computer to have the changes take effect.
3HAC031359-001 Revision: B
59
2.6.14. Creating Additional WebWare Data Collectors - Medium & Large Systems
Introduction NOTE: Skip this section if you are installing a small WebWare network. Procedure You can create new Data Collectors from the WebWare Server web site using the Data Collector Setup page under the Admin menu. 1. Navigate to the WebWare Server web site. 2. Click on Admin. 3. Click on the Data Collector Setup submenu. 4. Follow the instructions on the page to download the InterLink Module to the Data Collector computer and automatically configure it to communicate with the server machine.
60
3HAC031359-001 Revision: B
NOTE! If you are the SQL Database administrator, set up a new user account using the SQL Enterprise manager with the settings listed above. NOTE! If Windows authentication is used the ASPNET user must be added as a database owner.
3HAC031359-001 Revision: B
61
xx0500001597
xx0500001598
5. Ensure that the following settings are set to Enabled or Prompt before attempting to download ABB WebWare Client (scroll down through the list, if necessary, to locate all of the settings):
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Download signed ActiveX controls (must remain enabled for proper functionality) Run ActiveX controls and plug-ins (must remain enabled for proper functionality) Script ActiveX controls marked safe for scripting File Downloads (must remain enabled for proper functionality)
Apply the security changes (if necessary) and close the Internet Options property page. NOTE: All downloadable ABB ActiveX controls, DLLs, and scripts that are included in the WebWare family are digitally signed for security.
3HAC031359-001 Revision: B
63
Windows XP SP2/SP3 and Windows Server 2003 SP1/SP2: Click More Options and select Always run software. Click Run to start the installation.
NOTE: For ABB WebWare Client to function correctly with ABB WebWare Server, Always run software must be selected. 3. The WWVerChk3 DLL will download and run. This file will inspect the version of ABB WebWare Client that is installed on the system, and then compare it with the version available for download on the WebWare web server. 4. If there is a newer web client version available, a page will prompt you to upgrade the ABB WebWare Client to the newer version. The first time WWVerChk3 runs, it will find no ABB WebWare Client, and the browser will be redirected to the WebWare Client Installation page.
xx0500001601
5. Click the WebWare Client graphic to download the installation file. The File Download dialog will appear. 6. Do one of the following: Click Open to install the WebWare Client from the server. Click Save to save the install files to the client computer for installation later.
64
3HAC031359-001 Revision: B
2.7.3. Overview
What is ABB WebWare Client? The ABB WebWare Client is a collection of ActiveX controls that allow you to access the WebWare Server web site and access all of the features of the site. You install ABB WebWare Client on any client computer that will be allowed to browse to the WebWare Server web site.
3HAC031359-001 Revision: B
65
2. Connect the Devices on your WebWare Server network: Find Robot IP addresses Create Robot Profiles Create Robot Aliases Create A Plant Model
3. Check System - make sure all devices are connected and communicating properly over the network.
66
3HAC031359-001 Revision: B
xx0500001611
3HAC031359-001 Revision: B
67
68
3HAC031359-001 Revision: B
xx0500001612
2. Select and open the Communication menu. Notice the entry called LAN1. If this entry is listed and uses the LAN port, no additional configuration is required; proceed to step 3. If it is not listed, use the Add button to add an entry called LAN1 that uses the LAN connector. 3. From the Types menu, select Transmission Protocols.
xx0500001613
4. From the Types menu, select Application Protocols. If there is an entry called RAP1, highlight it and click the Enter button to check its configuration. The values for RAP1 should be those shown in the figure below. If RAP1 does not exist, create it using the settings shown below.
xx0500001614
xx0500001615
6. Navigate to the last entry, Network Settings, and press Enter. The settings for the LAN port should resemble the following: LAN: Fixed IP (dont use DHCP) IP: 10.90.6.200 (this is an example, will be unique to each facility) Subnet Mask: 255.255.255.0 (typical, but may differ depending on facility. Consult local network administrators.) Gateway: 10.90.6.1 (Example. This value will be the same gateway that is used by PCs on the network. Consult local network administrators.)
7. If these values are not set or need to be changed, an X-Start or C-Start must be performed. See your robot controller documentation for more information.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
3HAC031359-001 Revision: B
71
For a complete discussion of all of the robot parameter settings available through the Device Configuration Utility, see System Reference on page 263.
72
3HAC031359-001 Revision: B
xx0500001616
Type in the profile name and click on the appropriate profile type radio button. Click OK. 4. The Profile Editor dialog appears. Click OK to save the new profile to \Documents and Settings\All Users\Application Data\ABB Automation\RobComCfg.
3HAC031359-001 Revision: B
73
74
3HAC031359-001 Revision: B
3HAC031359-001 Revision: B
75
1. At the DCU Robot Alias screen, click the Add New IRC5 Robot button. The Add IRC5 Robot Alias dialog appears. 2. Click Scan. The Scan Results list box will appear, showing a list of robots detected on the network. NOTE: If the controller resides on a different subnet than the Data Collector, that is a remote controller, it will not appear in the scan. Please contact your local ABB office for support. 3. Select the controller that you wish to create an Alias for from the list. If there are robots on the network that have not had Aliases created, the DCU displays those robots and highlights the first robot on the list. The DCU proposes a default name for the Alias in the Define the Alias Name field, based on the best available default Connection Criteria for the controller type. 4. Select the Connection Criteria that you wish to use to identify the robot. You may select more than one criterion. Be sure to check to see if the "Multiple Match" alert message appears.
3HAC031359-001 Revision: B
77
78
3HAC031359-001 Revision: B
xx0500001617
The left hand pane shows the new empty plant model. The right hand pane displays a list of devices. You can toggle the list between all available devices in the system (All Devices) or only devices that you havent used in your model (Unused Devices). 2. You must check-out the Plant Model before you can edit it. Click the Edit button to check out the Plant Model.
xx0500001618
Use the mouse to drag items from the right pane over to the left pane. Release the mouse button to drop the item into the plant model. 4. When you have finished arranging the items in the plant model the way you want them: Click the Save button to save the model. Click the Undo button to check in the model without saving any changes.
Adding Branches to Your Plant Model Click Add Branch to add a branch to the tree. Use branches to create work cells, plant lines, etc. You can then drag devices from the right hand pane to populate your model with devices.
xx0500001619
When you right click the mouse on an item in the tree control, a popup menu appears. The menu will only appear if the Plant Model is checked out.
80
3HAC031359-001 Revision: B
Verify the Data Collecter to Server Connection Browse to the WebWare web site and check the icons in the device tree. If an icon (B) at the Data Collector level (A) is broken, there may be a connectivity problem.
xx0500001620
To determine the type of problem, at the Data Collector, open the Device Configuration Utility and from the Tools menu, click Configure WebWare Server Interface. Look at the connection status in the WebWare Server Current Connection panel.
xx0500001621
The server IP address should be visible. The WebWare Server Current Connection box, which should read Running, probably reads Connecting. If there is a failure, the error condition should appear in the box at the bottom.
Notice that since we are working with a small system, our WebWare Server host machine is even acting as Data Collector. In a larger system, these could be different machines.
xx0500001622
(A) Indicates that the robot device named S4VC1 is connected. (B) Indicates that the robot device named S4VC3 is not connected, that is, connecting. (C) The same information is displayed in InterLink Monitor.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
If the state of an S4 device is continuously Connecting, check the value of the Min Poll, and compare it with the error codes in S4 InterLink Monitor min poll on page 329. If the state of an IRC5 device is continuously Connecting, check the value of the Max Poll and compare it with the error codes in IRC5 InterLink Monitor max poll on page 329. If the value of the Min Poll is 65536, check the value of the Max Poll and compare it with the error codes in S4 InterLink Monitor max poll on page 329.
3HAC031359-001 Revision: B
83
84
3HAC031359-001 Revision: B
WebWare Data Collector The second level of the WebWare Device Tree is populated with an entry for each of the WebWare Data Collectors configured on the network.
xx0500001623
S4 Robot Controller The Robot Controller WebWare Device appears when a real or virtual controller is configured on the network.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
xx0500001624
IRC5 Robot Controller - This icon appears when a real or virtual controller is configured on the network.
xx0500001625
OPC Device - The OPC Device icon appears for each OPC server configured on the network.
xx0500001626
OPC Alarm - This OPC Alarm icon appears for each OPC Alarm device configured on the network.
xx0500001627
OPC Data Access Device - This icon will appear for each OPC Data Access device configured on the network.
xx0500001628
File System - This icon will appear for each File System configured on the network.
xx0500001629
No Backup Module License - The number of backup licenses has been exceeded or not installed.
xx0500001861
No Report Module License - The number of report licenses has been exceeded or not installed.
xx0500001862
Unavailable - A "ghost" device, meaning a device that exsists in the plant model, but is not connected.
xx0500001635
86
3HAC031359-001 Revision: B
Each of the following sections provides for information on how to do all of the tasks listed above. Users and Roles In the WebWare context, think of a user as a person. Think of a role in WebWare Server as a group of users related by the access permissions they are granted. NOTE: Usernames are not case sensitive, for example Thomas is equal to thomas. Admin Page Order The first page of each Settings section primarily affects the existence of the items you can create or configure on your site (menus, titles, users, images, etc.).
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
You set permissions/parameters on subsequent pages that you navigate to. For example, the Settings page allows you to enter or delete a new web site title, images and/or new users and roles. In order to configure which roles/users are able to see a certain page or custom web page, you must drill down to the Menu Settings page. There you can grant the permissions for who will be able to access a particular page or menu.
3HAC031359-001 Revision: B
87
xx0500001636
To change the web site title, enter a new title in the Site Title field. To install a different site image, enter a new file name and relative path to the file in the Site Image field.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
To toggle the Default Device View, select Physical or Logical. The logical view displays the Plant Model at the web site. The Physical view displays the devices connected to each Data Collector. To manipulate the site menus: Click on the up arrow to move the highlighted menu item up in the list Click on the down arrow to move the highlighted menu item down in the list Click on + to add a new menu to the site. The Menu Settings page will open. Click on the pencil to edit an existing menu. The Menu Settings page will open. Click on the X to remove the highlighted menu entry from the site.
Make the desired changes and then click: Apply - to apply all changes to the site. The web site will refresh and return to the Home page. Cancel - to cancel the changes and remain at the Site Settings page.
4. In the Definition Type selection box, click: First Sub Menu - to add the first of several submenu items that will open separate web pages Page - to specify the relative path to a custom page (set up only a single-level menu item)
5. Set up the security rights for the new menu by selecting the users or roles that will be able to view the new pages. 6. If there are additional pages which should only be viewed by users who will be allowed to view the new menu, click the + link next to the Additional Secured Pages list box.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
7. The Page Definition page will appear. Enter the relative path to the new page source and click OK to make the change. NOTE: If you copy the path from another source (Windows Explorer, etc.), make sure that you change the slashes to forward slashes, or the page will not appear. 8. The Menu Settings page will appear again. Click on Additional Secured Pages + to add additional secured pages or click: OK at the bottom of the page to make the changes, or Apply to apply all changes and refresh the site.
How to Use Roles to Set Site Security You can create user IDs and Roles to apply security settings to the WebWare web site. Follow the steps below to create an Admin User and Role that will have sole access to the Admin pages. Our Administrator will have the user name Admin and a password and will be assigned to an Administrator role. 1. Navigate to the WebWare Admin Settings page. 2. Create a new Admin role. At the Roles field, click the + icon. 3. The Role Definition page appears. Type in the Role name (Administrator). Click Apply. 4. Create a User named Admin and apply the Administrator role to that user. Continues on next page
3HAC031359-001 Revision: B 89
xx0500001637
4.
If you want to create a submenu, then click the First Sub Menu radio button. Continue with How to Create Custom Menus and Submenus on page 90. If you want to link a content page directly to the menu without adding a submenu, then click the Page radio button. Continue with How to Link to Content Pages on page 91.
How to Link to Content Pages 1. On the Menu Settings page, click the Page radio button. The Page Source field will appear. 2. Enter the relative path to the content page. We recommend that you place the page in the following folder C:\Inetpub\wwwroot\WebWare\content of the WebWare web, site as show below. The absolute path
C:\Inetpub\wwwroot\WebWare\content\custommenu\information.htm
corresponds to the relative path content/custommenu/information.htm that you enter in the Page Source field.
xx0500001638
xx0500001639
When you click on Custom Menu, the Information page appears, as shown above. When you click on the link on the page, a document with the WebWare logo appears in the website content pane. How to Create a Custom Menu and Submenu In the following procedure, we will create a custom menu with a submenu named Information and assign a custom web page to that submenu. 1. After entering the name of the new menu that you will create on the Menu Settings page, click the + icon next to the SubMenus field. 2. The SubMenu Settings page appears. Enter the name of the new submenu that you will create. 3. Enter the path to the content page in the Page Source field. We recommend that you place the page in the folder C:\Inetpub\wwwroot\WebWare\content 4. Select the roles that will be allowed to access the page and move them to the Authorized field. 5. Click Apply to confirm the changes. When you click on the custom menu Custom SubMenu and its attached page will appear on the WebWare site.
92
3HAC031359-001 Revision: B
xx0500001640
How to Delete Devices 1. Click Devices to display the Devices drop-down panel. 2. Highlight the device that you want to remove and click X to delete the device from the site. NOTE: You can only delete devices that are disconnected from the WebWare Server network.
xx0500001641
How to Manage Device Sets 1. Click Device Sets to display the Device Sets drop-down panel. 2. To manage device sets: Click + to add a device set. The Device Set Manager page will open. Click the pencil icon to edit a highlighted device set. The Device Set Manager page will open. Click X to delete a highlighted device set.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
xx0500001642
Follow the steps below to create a new device set. 1. At the Device Manager page, click Device Sets to display the Device Sets drop-down panel. 2. Click +. The Device Set Manager page will open. 3. In the Device Set box, enter a name for the Device Set.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
4. In the WebWare Device Tree, select the devices that you will add to the Device Set. Click Add. 5. When you have made your changes, click: Apply - to apply all changes. The web page will refresh. Ok - to apply all changes. The web page will refresh and return to the Device Manager page. Cancel - to cancel the changes and return to the Device Manager page without any changes.
3HAC031359-001 Revision: B
95
96
3HAC031359-001 Revision: B
Default WebWare User Name and Password The default user name and password established for the database when WebWare Server is first installed is: User name: sa Password: webware User Interface - Database Configuration Panel
xx0500001643
Function
Indicates the current status of the WebWare database. Possible values are: Running - Database is connected and running. Stopped - Database is stopped. Reboot Required - WebWare Server must be rebooted to re-initialize the database. Archiving - Database is currently being archived. Displays database status and error messages. Number of messages currently in the queue. Indicates MSMQ status. Possible options are: True - MSMQ is installed and running. False - MSMQ is not running. For more information, see Overview on page 36. Click to update the database connection state.
Refresh button
Screen Components - WebWare Database Information The table below describes the function of the screen components in the WebWare Database Information section of the Database Configuration drop-down panel on the Database Administration page. Component
Size in MB
Function
This is the size of the Webware database in megabytes. The database has a default size allotted when WebWare Server is first installed. The database will continue to grow over time. If your system is using the MSDE version of the database this is an important field to monitor. For more information, see Archive Process on page 103. Date the currently installed database was first created. Database version (DeviceLog.mdf version). Software version.
Screen Components - Database Server Configuration The table below describes the function of the screen components in the Database Server Configuration section of the Database Configuration drop-down panel on the Database Administration page. Component
SQL Server Name SQL Instance Database Location
Function
This is the machine name of the SQL server. This is the name of the instance that WebWare will use. WWService.exe checks SQL Server to determine whether a database labeled DeviceLog.mdf exists. If the database exists, this field is ignored. If SQL Server does not recognize a database of the correct name, WWService.exe will create a database labeled DeviceLog.mdf at the path specified in this field.
Function
SQL can use two types of user authentication. Click on either: Windows - to use Windows-specific user name/ password when logging in to the database. SQL Server - to use SQL Server-specific user name/ password when logging in to the database. This field lists the user name that WebWare should use when accessing the database. NOTE: You are NOT setting the user name here - the name is set either by the Windows network or by the SQL database administrator. NOTE: For details about the default database user name and password established when WebWare Server is first installed, see Default WebWare User Name and Password on page 97. This field lists the password that WebWare should use when accessing the database. NOTE: You are NOT setting the password here - the password is set either by the Windows network or by the SQL database administrator. NOTE: For details about the default database user name and password established when WebWare Server is first installed, see Default WebWare User Name and Password on page 97. Verify the password entered in the Password field. Click to apply the settings.
User Name
Password
Troubleshooting
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
If you have forgotten the instance name, you can find it in the SQL Server Enterprise Manager. Some SQL Server Editions do not allow the creation of instances. If you do not have an instance name, leave the SQL Instance box empty. Some domain settings might block the use of PC designations. If so, instead of the PC name, enter the TCP/ID address of the SQL Server. Some SQL Server editions demand that you restart the SQL server PC before broadcasting a new database. If you place the database on another drive than C:\, then WebWare might not find the database files. If you have an attached database, insert a blankspace in the Database Location box. In some SQL networks, the sa account might be disabled. If so, either create a new SQL user for WebWare,or use Windows Authentication.
xx0500001644
Screen Components - Archive Storage The table below describes the function of the components on the Archive Storage part of the Archive Configuration drop-down panel on the Database Administration page. Component
Available Diskspace Number of archives to retain on harddisk Automatically shrink database check box Set Archive Options button
Function
Displays the available disk space on connected harddisks. Enter the number of recent archives you wish to retain on the harddisk. Default is 10 archives. Select to automatically shrink the transaction log of the database. For details, see Archive Process on page 103. Click to set archive options.
Retain all archives check box Select to retain all archives on the harddisk.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Screen Components - Manual Archive The table below describes the function of the components on the Manual Archive part of the Archive Configuration drop-down panel on the Database Administration page. Component
Archive Directory Format Reset button Test Format button Number of days to be retained in the database Retain all data check box
Function
Enter the format you wish to use for the folder that contains the archived WebWare database files. Click to reset the format to the last saved format. Click to display an example of what the database archive file folder name will look like. Enter the number of days worth of data to be retained in the database. Default is to retain all data. See Archive Creation on page 104. Select to retain all data in the database.
Function
Select to shrink the WebWare database, see Archive Process on page 103. NOTE: Shrinking the database locks the database while executing. Performance will be degenerated while this command is being executed. Click to start the archive process. The database will be copied to a folder created inside the folder containing the Robot Data folder and the DeviceLog.mdf file. The status of the manual archive procedure is displayed in the User Interface - Archive History Panel on page 102.
Screen Components - Scheduled Archive The table below describes the function of the components on the Scheduled Archive part of the Archive Configuration drop-down panel on the Database Administration page. Component
Archive Directory Format Reset button Test Format button Number of days to be retained in the database Retain all data check box Number of archives to be retained Run task: list boxes
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Function
Enter the format you wish you use for the folder that contains the archived WebWare database files. Click to reset the format to the last saved format. Click to display an example of what the database archive file folder name will look like. Enter the number of days worth of data to be retained in the database. Default is to retain all data. See Archive Creation on page 104. Select to retain all data in the database. Enter the number of scheduled archives to retain. Default is 5. Use these list boxes to set the archive frequency. Choose from: Frequency - Every, First, Second, Third, Fourth, Last Weekday - Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday Use this list box to select what time of day the scheduled archive should run. Choose from Midnight, 1 AM, 2 AM, etc. or 00, 01, 02, etc.
at list box
Set Archive Schedule button Click to apply the archive schedule to the system. The database will be backed up at the regularly scheduled date and time.
xx0500001879
Screen Components - Archive History The table below describes the function of the components in the Archive History Table part of the Archive History drop-down panel on the Database Administration page. Component
Refresh button Archive History table
Function
Click to refresh the Archive History Table. Displays a list of all archives done containing the following information: Archive Date - date and time the archive was executed. Path - location where the archive was stored. Size - file size of the archive in megabytes. Status - if the archive was successful or failed. Type - if the archive was manual or scheduled. Days retained - number of days to retain in the archive, possible options include All or a numeric value. Comment - Displays text confirming the status of the archive, e.g. Archive completed without errors or Archive completed with errors.
Shrinking a log is dependent on first truncating the log. Log truncation occurs at these points: At the completion of any BACKUP LOG statement. Every time a checkpoint is processed, provided the database is using the simple recovery model.
The archive process purges both default and custom tables from the database. When the Automatically Shrink Database check box is selected, the AUTO_SHRINK option of the WebWare database is turned on. SQL Server will periodically reduce the size of the WebWare database and transaction log. Be aware that this option resets the Recovery Model of the WebWare database to "Simple". Therefore, scheduled backups of the WebWare database transaction log will not be possible. AUTO_SHRINK only reduces the size of the transaction log if the database is set to SIMPLE recovery model or if the log is backed up. If your organization requires continual backups of the transaction log for maximum data protection, this option should not be selected. This option is used primarily by WebWare customers using the Microsoft SQL Server Desktop Engine which has a 2-GB size limit.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
The AUTO_SHRINK option causes files to be shrunk when more than 25 % of the file contains unused space. The file is shrunk to a size where 25 % of the file is unused space, or to the size of the file when it was created, whichever is greater. For additional information, please refer to your Microsoft SQL Server documentation or http://support.microsoft.com. Archive Locations Archived database files are located at the following default path:
C:\Program Files\Common Files\ABB Automation\WebWare Server\Robot Data\Archive
The folder name is configurable. The default archive folder name is:
%m-%d-%Y_%H_%M_%S
(read as Month-Day-Year_Hour_Minute_Second). For details on configuring the folder name, see How to Configure Backup and Archive File Folder Names on page 113. NOTE: The order of the day/date data can vary depending on local system settings.
104
3HAC031359-001 Revision: B
Restore Procedure Follow the procedure below to restore an archived database as the Webware database. 1. Open a Windows command prompt and change directory to the Archive folder. Typically, the path to the Archive folder will look something like:
C:\Program Files\Common Files\ABB Automation\WebWare Server\Robot Data\Archive
2. Create a new empty database for the archive to be moved to. At the Windows command prompt type:
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Typically, the command you type will look something like this:
osql -SWebServer\WebWareSQL -Usa
Press Enter. 3. Enter the SQL password and press Enter. The default password is webware. Note that the cursor will not change as you type the password. If you entered the password correctly the osql command prompt will appear:
1>
4. Type the following commands. Press Enter at the end of each line.
1> CREATE DATABASE MyArchive 2> go
5. If you typed everything correctly, a series of information messages may appear. If you entered a syntax error, an error message will appear, and you must re-enter all of the commands, correcting any mistakes before continuing. 6. To restore the archive to the new database, type the following commands, with all spaces and punctuation exactly as shown below. Use the real paths and file names from your system. Continues on next page
3HAC031359-001 Revision: B 105
7. If you typed everything correctly, a series of information messages may appear. If you entered a syntax error, an error message will appear, and you must re-enter all of the commands, correcting any mistakes before continuing. NOTE: In order to import data from one database to another please refer to Microsoft SQL Server documentation.
106
3HAC031359-001 Revision: B
For more information on the WebWare Server Backup system, see WebWare Backup on page 219. NOTE: You can make the changes to the backup parameters only at the WebWare Server host computer. User Interface - Backup Administration Page
xx0500001645
Function
Enter the number of backup sets to display on the Backup Restore page. If you set this parameter to zero (0), no backup sets will be displayed. Changing the number to ten (10) will display the ten most recent backup sets.
Function
Clear this check box to prevent displaying incomplete backups on the Backup Restore page. The default is to display both successful and unsuccessful backups. Unsuccessful backups are caused by: System time-outs (waiting for the robot to go to Auto mode, etc.) Attempts to backup program modules, etc. that do not exist on the robot (backups completed with errors) NOTE: If a backup fails and the folder structure is empty, WebWare Server will not create the empty folder structure on the host hard drive. Click to apply the settings.
Function
Enter the number of minutes before the system will retry backups on any devices that are not available due to communications errors. After the retry setting has timed out, any devices not backed up will have the status Timeout assigned to them in the Backup Status Table entry. NOTE: Scheduled backups will only complete if all devices to be backed up are in AUTO mode. Click to apply the setting.
Function
Select to require that a backup comment is added to the backup with no more than 1024 characters. The backup comment is displayed on the Backup Summary page. Toggles which user name to display in the backup comment. Available options are: Windows - the windows account (Domain/User name) is displayed. NOTE: You need to configure IIS when selecting this option. For more information, see How to Configure IIS when Storing the Windows User Name in the Backup Log on page 115. WebWare - the WebWare account is displayed. Click to apply the settings.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
xx0500001881
Function
Indicates the current state of the Visual SourceSafe storage system. Possible values are: Not Installed - Visual SourceSafe is not installed on the computer. Not Enabled- Visual SourceSafe is installed but has not yet been configured to connect with WebWare Server. Enabled - the Visual SourceSafe database is connected and running correctly. Broken - Visual SourceSafe is not connected or is not running. Check: 1. the error messages that appear at the top of the dropdown panel 2. that the path to SrcSafe.ini is correct 3. that the default SourceSafe project name is correct 4. that the user name and password are correct Select this check box to activate or deactivate the WebWare Server interface to Visual SourceSafe. Enter the complete path to the SourcSafe.ini file. Example: C:\VSS\ScrcSafe.ini Enter a project name to indicate where SourceSafe should store backup data. Example: $/WebWare Enter the SourceSafe user name that WebWare should use to access the Visual SourceSafe database. NOTE: You are not setting the user name here - the user name and password is set by the SourceSafe administrator. Enter the SourceSafe password that WebWare should use to access the Visual SourceSafe database. NOTE: You are not setting the password here - the user name and password is set by the SourceSafe administrator. Re-enter the SourceSafe password that WebWare should use to access the Visual SourceSafe database.
Retype Password
Function
Click to appply the parameters and test them to make sure that they are correct. The Current State field might change depending upon the results of the configuration testing.
Screen Components - Local File System Configuration The Local File System is the location where backup files are stored on the WebWare Server hard drive. This page allows you to enter the default path where backup files will be stored. The table below refers to the Backup drop-down panel in the Backup Administration page. Component
Backup Set Storage Limit field
Function
Enter the maximum number of backup sets to store in the local file system. When the storage limit is reached, the oldest backup set will be deleted after the latest backup set is created. NOTE: If you have 10 backup sets on your system and then you change this number from 10 to 5, the next time you run a backup, the five oldest backup sets will be deleted, so that the system maintains only the specified number of sets. If this checkbox is selected, WebWare Server will save unsuccessful backups (partial backups or backups completed with errors) on the host computer hard drive. Clear this checkbox to prevent WebWare Server from saving unsuccessful backups on the host hard drive. Enter the path to the location on the WebWare Server network server where robot backups should be stored when Visual SourceSafe is either not installed or not enabled. The default path is: C:\Program Files\Common Files\ABB Automation\WebWare Server\File Manager Data\
Master Backup Folder Name Enter the folder name of the folder that contains the master field backup. This will be displayed at the web site and on the teach pendant during the WebWare RAPID Restore routine. Last Successful Backup Folder Name field Backup Set Folder Name Format field Enter the folder name for the last successful backup. This will be displayed at the web site and on the teach pendant during the WebWare RAPID Restore routine. Enter the codes for the naming convention that you wish to use for the backup folder names. You can configure separate names for both successful backups and backups that contain errors. For complete details, see How to Configure Backup and Archive File Folder Names on page 113.
Set File Configuration button Click this button to save the new backup file folder naming codes. WebWare Server will use those codes to place the following backups at the location specified on this page in folders named using the codes that you entered. Reset button Test Format button Click this button to reset the folder naming codes to the last saved version. The Test Format button displays the results of your configuration codes using the current date and time. Note that both the successful and failed naming strings are shown. If you have not configured separate names for both successful and failed backups, the formatting for both strings will be the same.
xx0500001647
Screen Components - Restore Configuration The table below refers to the Restore drop-down panel in the Backup Administration page. Component
Restore backup folder name field Password required for restoring of backup check box Restore Password field Retype Password field Set Restore Configuration button
Function
Name of the folder on the robot controllers ramdisk where restored files are stored. The default name is "restore". Select this check-box to enable the restore password.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Type a restore password. The password must be a four-digit code. Only numbers 0-9 are allowed. Verify the password entered in the Password field. Click this button to set the restore configuration settings.
112
3HAC031359-001 Revision: B
Function\Result
Indicates a directory/subdirectory Place angle brackets around formatting string Place pair of angle brackets inside the string to enter an empty space. Use the pipe symbol to separate the success string from the failure string. For example, <SSS|FFF> - use SSS as success replacement, FFF as fail replacement. Month Day Year (short format) Year (long format) Minute Hour Second
%m %d %y %Y %M %H %S
Procedure Follow the steps below to create file folders named Good Backup <Date><Time> for successful backups and Contains Errors <Date><Time> for backups that contain errors. 1. Navigate to the Backup Administration page. Click the Backup drop-down panel. 2. Enter the following string in the Backup Set Folder Name Format field:
<Good Backup |Contains Errors >%m%d%y-%H%M
NOTE: There is a space in front of the pipe symbol and also in front of the closing bracket. This places spaces in the folder name in their proper places.
xx0500001648
4. If the results displayed match your needs, click Set File Configuration. The file name you specified will replace the previously saved name. Controlling the Folder Structure You can also create a folder structure to organize the backups to make them easier to find. For example, let's say you wanted to group all of the backups by month, and sort them by successful backups, bad backups, and then by time. Create the path as shown below:
<%m\Good Backup |Contains Errors >%d%m%y-%H%M
The Backup Restore page structure at the WebWare Server tree (and at the robot teach pendant) will be:
xx0500001649
114
3HAC031359-001 Revision: B
3.2.9. How to Configure IIS when Storing the Windows User Name in the Backup Log
Overview WebWare stores the backup user name as part of the backup comment added to a backup. The user name can be either the WebWare account or the Windows account. It is necessary to configure IIS for the Windows user name to be logged, as described in the following procedure. Procedure 1. Open Internet Information Services (IIS) Manager. Click Start, then browse to Control Panel, Administrative Tools and then click Internet Information Services (IIS) Manager. 2. Browse to the Default Web Site, right-click on it and select Properties. 3. Click the Directory Security tab. In the Authentication and access control part of the dialog, click Edit. The Authentication Methods dialog will appear. 4. In the Authentication Methods dialog, clear the Enable anonymous access check box. Click OK two times to return to the Internet Information Services (IIS) Manager dialog. NOTE: If you disable anonymous access this can affect the transfer of files to the robot from the web client, that is restore, file copy etc. 5. Restart the web site. To do this you right-click the Default Web Site and select Stop. Wait until Default Web Site (Stopped) appears in the tree on the left. Once again, right-click on Default Web Site and select Start.
3HAC031359-001 Revision: B
115
xx0500001650
How to Delete Custom Databases and Custom Tables 1. Select the database or table that you wish to delete. 2. Click the appropriate Delete button to remove the unwanted component. NOTE: Do NOT delete the last remaining Custom Table or you will not be able to delete the Custom Database. Empty Custom Databses are not displayed.
xx0500001651
How to Set Counter Resolution 1. Enter the new default resolution in the field provided. 2. Click Set Counter Resolution to apply the changes. For more information about WebWare counters, see Counters on page 136.
3HAC031359-001 Revision: B
117
License Enforcement Mechanism ABB uses license keys to grant or deny access to entire applications or only to specific application functions. A single application may require multiple license keys to allow access to optional features in addition to the basic application. A license key is expressed as a data record in a License Key File. After generating a License Key Request file with the License Key Request Wizard and sending it to ABB, the License Key File will be sent back to you. You will receive one or more License Key Files each containing one or more license keys for the various applications that you have purchased from ABB. Using the License Key Installation Wizard, you install Standalone License Keys on a workstation. A single license key can be used by multiple applications. A license key is encrypted in a manner such that it can only be decrypted by the ABB RoboticsIT License System. Installing a new license will delete the old license for the same product and version. Note: No warning will be shown before installing the new license.
Submenu
Server Module
No license License License License License License License
Report Module
Backup Module
Home Info Device General State User Version Data Reports Viewer Manager Service Backup Control Schedule Results Restore Summary Documentation Admin Settings
License Count License Count License Count License Count License Count License Count License Count License Count License No license
Menu
Submenu
Devices Data Collector Setup Database Reports Backup
Report Module
Backup Module
120
3HAC031359-001 Revision: B
NOTE: You need to restart WebWare Server to apply the changes. License Priority Configuration File Syntax The following XML code is a template for configuring the license priority. Text in bold face indicates entries that need to be configured. Add as many <DeviceName> entries as the number of licenses you have obtained.
<?xml version="1.0"?> <!-- Uncomment device name entries to use priority list --> <PriorityList> <!-- Backup license device list --> <License type="1">
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
<DeviceName>DATACOLLECTOR/DEVICE1</DeviceName> <DeviceName>DATACOLLECTOR/DEVICE2</DeviceName> </License> <!-- Report license device list --> <License type="2"> <DeviceName>DATACOLLECTOR/DEVICE1</DeviceName> <DeviceName>DATACOLLECTOR/DEVICE2</DeviceName> </License> </PriorityList>
3HAC031359-001 Revision: B
121
xx0500001789
122
3HAC031359-001 Revision: B
xx0500001790
3HAC031359-001 Revision: B
123
Name the folder any name that you would like. Note that the folder name cannot contain spaces. 3. Copy the files you want displayed on the Documentation page into the MyFolder folder you created. 4. Refresh the Documentation page and the new header, (the same name as your folder name) and the files that you put into the folder will appear on the page under the heading Customer Documents. To edit headings and document names, see Editing Heading and Document Names on page 124. Editing Heading and Document Names You can edit the headings and document names by following the steps below. 1. Using Windows Explorer, navigate to the customerdocs.xml configuration file, usually located at:
C:\Inetpub\wwwroot\WebWare\docs
2. Open the configuration file in Notepad. The file contains example entries that illustrate the correct syntax, see Configuration File on page 125. Note that the root location for relative links originates from the directory where the configuration file is located, i.e. C:\Inetpub\wwwroot\WebWare\docs 3. To change the header name, add a <DirectoriesReference entry similar to the example entries in the file and below.
<DirectoryRef> <DirecoryReference Path="FolderPath" Name="FolderName" /> . . . </DirectoryRef>
Essentially, you are changing the name of the folder as it will appear on the web page.
In this case, you are changing the name of the document as it will appear on the web page. 5. Save the file. 6. Refresh the Documentation page. If you did not complete the entries in the configuration file correctly, error text may appear on the web page, or your additions may not appear at all. Check your typing to make sure that your entries are accurate. Configuration File The configuration file contains example entries that show the syntax of the configuration file. Text in bold face indicate parts of the file that you are expected to modify to your needs.
<Documentation xmlns:xsi="http://www.w3.org/2001/XMLSchemainstance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <DirectoryRef> <DirectoriesReference Path="Folder1" Name="Misc Manuals"/> <DirectoriesReference Path="Folder2" Name="Monthly Reports"/> </DirectoryRef> <FileRef> <FileReference File="mymanual1.pdf" Name="My Device Manual"/> <FileReference File="report03.pdf" Name="Report for March"/>
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
</FileRef> </Documentation>
3HAC031359-001 Revision: B
125
126
3HAC031359-001 Revision: B
You use the tools listed below to monitor the status of the WebWare Server network: InterLink Monitor to determine connection status of robot aliases. For more information, see Using the ABB InterLink Monitor in the Device Configuration Utility help file. WebWare Server Info pages to determine connection status of Data Collectors, or use SIS to determine individual robot health. For more information, see Info Page on page 129. WebWare Server Data page to monitor device I/O status. For more information, see WebWare Server Database on page 135. Plant Model view to customize the tree view to match either physical or logical plant structures. For more information, see Plant Model on page 79.
Data Collection You use the tools listed below to collect and preserve historical data from your system: The WebWare RAPID Module provides functions to collect data from robots and store that data in the WebWare Server database. For more information, see WebWare RAPID Module (WebWare.sys) on page 291. You can create Custom Database tables to store non-standard data from robots. For more information, see Custom Database Tables on page 145. Continues on next page
3HAC031359-001 Revision: B 127
128
3HAC031359-001 Revision: B
xx0500001666
Data Collector Device Counts You can also highlight an individual Data Collector to display the Data Collector Device Counts page to view the connection status of the devices connected to that Data Collector. WebWare Device Information Highlight any device on the tree other than the network node. The Info page for that device will appear. The data shown in the figure can be assigned using one of three methods: If the WebWare Device is a real or virtual controller, the values can be set from RAPID using functions available in the WebWare System Module (WEBWARE.SYS). If the device is a WebWare Client Application, the values can be set using the WebWare ActiveX control. For more information about creating WebWare Client Applications, refer to the WebWare SDK online help. If the device is an OPC Device, these values are configured using the Device Configuration Utility. For complete details, see Configuring the Device Configuration Utility (DCU) in the Device Configuration Utility help file. Continues on next page
3HAC031359-001 Revision: B 129
xx0500001667
Robot devices have an additional view page available. The data shown is extracted from the robot controller and provides controller version and state information.
xx0500001668
Information Displayed
Status - connection state of the device. Icons indicate the device connection status. Version - the user-defined version (usually a WebWare Client Application). Company - the user-defined company name (usually defined in a WebWare Client Application or from OPC Device tags). Author - the user-defined Author name (usually defined in a WebWare Client Application or from OPC Device tags). Description - the user-defined description name (usually defined in a WebWare Client Application or from OPC Device tags). Status - connection state of the device. Icons indicate the device connection status. Operation - the operational state of the device (Automatic, Manual, etc.). Program - the operational state of the device program (Loaded, Initialized, etc.). Control - the operational state of the robot controller (E-Stopped, Auto, etc.). Prog/Ctrl - the operational state of the device program (Stopped, Auto, etc.). Interface - indicates whether the device interface is connected, disconnected or disabled. Status - connection state of the device. Icons indicate the device connection status. User Defined fields - these fields are all defined by the user.. Status - connection state of the device. Icons indicate the device connection status. Boot - the EEPROM version number (controller BIOS). RAP - indicates the version of RAP running on the robots. System - indicates the robot operation system version installed. Pendant - the Teach Pendant hardware and software version numbers. Control ID - the robot serial number..
State
User
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Version
3HAC031359-001 Revision: B
131
xx0500001669
Robot I/O Configuration File For S4 robots, the robot I/O configuration file must be loaded into the Device Configuration Utility (DCU) on the WebWare Data Collector for the robot I/O to be displayed in the WebWare Client interface. To learn more about this procedure, refer to the Device Configuration Utility help file. For IRC5 robots, robot I/O is displayed automatically and does not need to be configured. Views All of the I/O and variable data are dynamic and are updated when the WebWare Client receives new information about the device. The Views drop-down list allows you to select from digital I/O, analog I/O, group I/O, board and RAPID (perssistent data, variable data and constants). Each signal or variable is placed on a line in the table. Click the column header to sort the data in any column in ascending or descending order. Filters You can simplify the data view of the selected device by choosing one of the available filters. You can display different signal views, such as:
132
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
All signals Digital signals only Analog signals only Group signals only Board signals only RAPID program data only Continues on next page
3HAC031359-001 Revision: B
The figure below illustrates how to select a filter from the drop down menu.
xx0500001670
Column Header Definitions The table below defines the column headers for the robot I/O data page. Component
Name
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Function
I/O name. For I/O signals: Controller board name. For RAPID variables: Not used.
Type of signal. Possible values are: Digital I/O Analog I/O Digital Group I/O Analog Group I/O RAPID variable types (bool, num, string, etc.). Connection state of the signal. Possible values are: Connected Not Connected Current value of the I/O. For digital I/O, possible values are 0 and 1. For analog I/O, possible values are dependent on the type of signal being measured. A question mark indicates a disconnected signal. Date the I/O parameters were last modified. Quality of the data. Possible values are: Good (Connected) Bad (Disconnected)
Data State
Value
Modified Quality
Function
I/O name. Not used. Tag data type. Possible values are: Native Type Bool Short Long Double String Connection state of the signal. Possible values are: Connected Not Connected Varies depending on the tag data type. A question mark indicates a disconnected signal. Date the I/O parameters were last modified. Quality of the data. Possible values are: Good (hex value of C0) Bad (any other common OPC hex value 00, DF, AB, etc.)
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Data State
134
3HAC031359-001 Revision: B
Definition
This is the name of the WebWare device generating the log message. This is the number that identifies which log triggered the event. These are the log numbers used by both the S4 control and the WebWare ActiveX controls. 1. System State Events 2. System Errors 3. Hardware Errors 4. RAPID Program Events 5. Motion Control Events/Errors 6. Operator Events 7. IO and Communications Errors 8. S4 User Defined Events 9. Optional Product Events 10. S4 Internal Errors 11. ArcWeld Events 12. Spotweld Events 13. Paint Events 14. PC Application Events 15. InterLink Events For more information on error codes generated by WebWare Server see WebWare Server Error Codes on page 338. This is the number that identifies the type of the log event. The possible types are as follows: 1. State Change 2. Warning 3. Error
LogType
Definition
This is the log event number. The log events numbers vary with every logging function. This is a string containing lines of text used to identify the log event.
Counters The WebWare Server database includes a generic counter. WebWare counters are used to count event occurrences over a given time frame. RAPID programs and WebWare SDK Applications create counter records by calling a counter increment function with the counter name. WebWare creates counter records for each counter and increments the value given. Counter resolution must be considered very carefully in relation to several factors. Setting a counter resolution to a low number may result in fast database growth. The default, recommended resolution value is 60 minutes. The time frame for counters is set from the Counter Resolution panel of the Reports Page on page 116 of the WebWare Server web site. Counter records are ideal for counting things like Parts Per Hour or Failures Per Hour. The counter data can also be summed in a database query to produce reports like Parts Per Shift or Part Per Week. The WebWare Server database counter fields are described as follows: Field
Robot Name Counter Name Value Time
Definition
This is the name of the WebWare device managing the counter. This is the name of the counter. This is the current counter value for the specified time frame. This is the time and date for a given counter record. Counter times are always specified as the starting time of a specified time frame. e.g. 1/11/00 2:00:00 PM.
See also WWIncrCounter Instruction on page 309. Timers The WebWare Server database includes a generic timer record concept. WebWare timers are used to time events such as cycle time, squeeze time, hold time, etc. RAPID programs and WebWare SDK Applications create timer records by calling the StartTime, StopTime, and LogTimedEvent functions specifying the timer name used to identify the timer record. Each timer record represents a single timed event. If you are tracking Cycle Time, youll get a new timer record for each recorded cycle. The WebWare Server database timer fields are described as follows: Field
Robot Name Timer Name Start Time End Time
Definition
This is the name of the WebWare device writing the timer record. This is the name of the timer. This is the time that the timer was started. This is the time that the timer was stopped. If this field is blank, the timer is still active.
Definition
This is the duration of the timed event in milliseconds. This is only calculated when the End Time field is written.
See also WWStartTimer Instruction on page 311, WWStopTimer Instruction on page 313 and WWLogTimedEvent Instruction on page 315. OPC Alarm Tables WebWare tracks the following OPC alarms and conditions: Field
Source Message Time Event Type
Definition
This is the name of the alarm. This is the event notification message sent along with the alarm. This is the time that the alarm occurred. 1. Simple event 2. Tracking event 3. Condition-related event Displays whether the event is standard or vendor specific. Displays a severity range from 0 to 1000, with 0 being the most severe. This is the new state of an OPC condition. This is the OPC condition name. This is the name of the current sub-condition, for multi-state conditions. This is the quality associated with the condition state. This is the time that the OPC condition became active.
Backup Log WebWare tracks the following backup system events: Field
User Name Scheduled Start Time Type
Definition
Name of the user who started the backup. If the schedule process started the backup. The time the backup was started. 1. Backup all devices 2. Backup selected devices
Alias Backup Log WebWare tracks the state of the backup status according to the aliases in the system as shown below. Field
Device Name Backup ID Result
Definition
Name of device Backup Identification The result of the backup attempt for the given device. For complete information on these states see Backup Status Messages on page 232.
Definition
Indicates whether InterLink was able to pass backup file set to WWService, see Return Status Codes on page 321. The project that was backed up. The name of the user who cancelled the backup. The time and date that the backup requested completed. 0/1 whether backup configuration had Standard backup checked. Indicate whether full program request was successful. See Return Status Codes on page 321. 0/1 whether backup configuration had RAPID checked Indicates whether Program backup was successful. See Return Status Codes on page 321. The number of Modules backup configuration had set when RAPID was checked. Number of Modules written. The number of System Params backup configuration had set when Parameters checked. Number of System Parameters written. Whether backup configuration had Ramdisk checked. Total number of files on Ramdisk. Number of Ramdisk files backed up. The number of Log backup configuration had set when Event Logs is checked. Number of Log Files backed up. The name of the device that had the error. Backup Identification. A number indicating the type of backup the file was included in: 0. Unknown Error 1. Error backing up programs 2. Error during full backup 3. Error backing up program modules 4. Error backing up system parameters 5. Error backing up log files 6. Error during file push 7. Error backing up robot ramdisk See Return Status Codes on page 321. The time and date the error occurred.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
138
3HAC031359-001 Revision: B
3. Open the Computer Management console. Stop the following services: TIP! Alternatively, close all Internet Explorers that point to the WebWare server website. Open the Control Panel, point to Administrative Tools, and then click Services. Select the MSSQL$WEBWARESQL service. From the Action menu, click Stop.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Detaching and Moving the Database(s) Follow the steps below to detach DeviceLog.mdf from the MSDE Database Engine and move it to its new location. 1. Open a Windows command prompt and type the following command:
osql -S[Machine Name]\[Instance Name] -U[User Name]
Typically, the command you type will look something like this:
osql -SWebServer\WebWareSQL -Usa
Press Enter. 2. Enter the SQL password and press Enter. The default password is webware. Note that the cursor will not change as you type the password. If you entered the password correctly the osql command prompt will appear:
1>
Then press Enter. 4. If you typed everything correctly, a series of information messages may appear. If you entered a syntax error, an error message will appear, and you must re-enter all of the commands, correcting any mistakes before continuing. Repeat Steps 1 - 3 above for each custom database on your server. 5. Find the current DeviceLog.mdf using e.g. Windows Explorer, and copy the file to the new location. TIP! Alternatively, on the SQL server, click Start, point to Programs, point to Microsoft SQL Server and then click Enterprise Manager. Right-click the Devices database folder, point to All Tasks and then click Detach Database. Open Windows Explorer and browse to C:\Program Files\Common Files\ ABB Automation\WebWare Server\Robot Data. Copy the DeviceLog.mdf and the DeviceLog_log.LDF files. On the SQL server, create a folder structure where the database will reside and then paste the two files in the folder. Attaching the WebWare Database(s) to the Database Engine Follow the steps below to attach the DeviceLog.mdf and any custom databases to the MSDE database Engine from the new location. 1. Open a command prompt and type the following command:
osql -S[Machine Name]\[Instance Name] -U[User Name]
Typically, the command you type will look something like this:
osql -SWebServer\WebWareSQL -Usa
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Press Enter. 2. Enter the SQL password and press Enter. The default password is webware. Note that the cursor will not change as you type the password. If you entered the password correctly the osql command prompt will appear:
1>
3. Type the following commands, exactly as they appear below, pressing Enter after you complete each line:
1> sp_attach_db @dbname="DeviceLog", 2> @filename1 = "C:\WebWare Data\Robot Data\DeviceLog.mdf", 3> @filename2 = "C:\WebWare Data\Robot Data\DeviceLog_log.ldf" 4> go
NOTE: If you attempt to attach to a database file located on a remote computer, you will receive an error message that looks similar to:
File "[Database path and name]" is on a network device not supported for database files.
8. Restart the Service. Sharing the SQL Database Folder Follow the steps below to set up a share of the database: 1. Right-click on the folder where the DeviceLog.mdf file is located (on the SQL Server). 2. Select Sharing and Security. 3. Select Share this folder. 4. Set Share name to Database. 5. Set Permissions to the WebWare user created above. Configuring the Database in the WebWare Server Follow the steps below to configure the database: 1. From the physical WebWare server PC, open Internet Explorer and log on to http:// localhost/WebWare. 2. From the Admin menu, click Database and then scroll down to the Database Server Configuration panel. 3. In the SQL Server Name box, type the name of the SQL server PC. 4. In the SQL Instance box, type the name of the instance you created at SQL installation. Continues on next page
142 3HAC031359-001 Revision: B
3HAC031359-001 Revision: B
143
3. Open the Computer Management console. Stop the following services: ABB InterLink Module ABB WebWare Server
Click on the service and then click the Stop button. 4. Detach the database from the database server as described in Detaching and Moving the Database(s) on page 139. 5. Find the current DeviceLog.mdf using e.g. Windows Explorer, and any Custom Database you may have created and delete the databases. 6. Open the Computer Management console. Restart the following services: ABB InterLink Module ABB WebWare Server
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Click on the service and then click the Start button. 7. Restart IIS. 8. At the WebWare Server network server, go to the Robot Data directory and verify that a new DeviceLog.mdf has been created.
144
3HAC031359-001 Revision: B
Creating a Custom Database from RAPID Creating a WebWare Custom Database from RAPID code is a three-step process. The steps must be done in order, and the variables used must be declared as persistent variables. All WebWare Custom databases are created in the location indicated on the Database Configuration Page (see Database Page on page 97). In the following example, the name of the custom database is MyDatabase so the name of the database file will be MyDatabase.mdf. The MyDatabase.mdf file will be created in the WebWare data directory. It is recommended that table names in Custom Databases be unique to your SQL Server Instance. If two tables located in separate Custom Databases have the same name, data inconsistencies may arise when records are inserted or updated by RAPID programs. NOTE: WebWare Server will keep track of all databases and tables that have been created. That way a RAPID program will only have to go through the create database process once. After successfully creating MyDatabase an ODBC DSN labeled ww_MyDatabase will be created. NOTE: To use the RECORD type in RAPID to create custom databases, you need to have Advanced and Developer functions installed on the robot controller. Sample 1 Program Printout The printout below contains the complete RAPID program that will be referenced in the following sections.
%%% VERSION:1 LANGUAGE:ENGLISH
WaitUntil MyTableSts<1\MaxTime:=60\TimeFlag:=bWebTimeOut;
ww_command:="17,MyDatabase.MyTable,config";
For more information, see Update Records with SCWrite on page 152. Sample Code
MODULE SAMPLE . . PERS num MyTableSts:=1; . . PROC CreateCustDB() . . ww_command:="17,MyDatabase.MyTable,log"; SCWrite:=ww_command;
Config - This table is created with the purpose of storing single program or configuration data. Only one record is stored in a table. Existing fields are updated.
Define the SQL Datatype Follow the sample code below to define what SQL datatypes will be stored in the table. The possible datatypes include
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
int auto (int with automatic counter) float decimal bool varchar
The name of the variable, structure or array is important. The variable must be the same as the database name with Type appended to it. As the sample code displays, the name of the table is MyTable so the persistent variable that defines the data has to be named MyTableType. The SCWrite command will accept an array of strings which define the datatypes for each column in the table. A second parameter indicates if the column should be unique. If the column is defined as unique, a unique index is created on the column in the database.
ENDIF . .
Writing to a Custom Database After successfully creating a database via RAPID, the database is immediately ready for information to be written to it. To write to the database simply fill the record array with information.
!Fill MyTableRec array with information. SCWrite MyTableRec;
Error Handling Example Generally, it is a good idea to check for errors after doing the three SCWrite commands to determine if the table/database has been created. The sample code below would be used to determine if the record was written to the MyTable table.
WaitUntil MyTableSts<1\MaxTime:=30\TimeFlag:=bWebTimeOut; IF (bWebTimeOut) THEN TimeOutErr:=TimeOutErr+1; ELSEIF (MyTableSts<>0) THEN WriteErr:=WriteErr+1;
Checking if a Custom Database Table Already Exists Generally, it is a good idea to query if a table already exists. This can provide a slight performance improvement since Interlink will verify that the table already exists without doing a request to WWService. Notice that the ww_command number is 25. The sample code below could be used to determine if the MyTable table already exists.
PERS num ww_nTableExists; . . ww_command:="25,MyDatabase.MyTable"; ww_nTableExists:=0; SCWrite ww_command; WaitTime 1.0; TPWrite ww_nTableExists;
The variable ww_nTableExists will have one of the following values: 1 : Table exists. 2 : Table does not exist. -1 : Attempt to verify tables existence failed. (The command failed.)
Update Records with SCWrite A check is done of the MyDatabase.MyTable table in the DeviceLog database prior to all inserts into the custom database tables. If the table is listed as a config table, the INSERT SQL statement is prefixed by an IF EXISTS statement. If the table and one record already exists, the SQL statement conducted will be an UPDATE statement. Otherwise, it will be a normal INSERT statement.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Sample 2 Program Printout The printout below contains the complete RAPID program for a complex custom database RAPID program including error-checking, a user-interactive menu system, and routines to verify, create, and write to custom database tables. This example is much more complex than sample 1 but demonstrates some of the features provided by WebWares Custom database functions. It contains routines to check if a table exists in the database and provides feedback to the user reporting the status of each routine.
%%% VERSION:1 LANGUAGE:ENGLISH %%% MODULE CSBASIC_UserDef ! ! BASIC Table !
TPErase; ! Run Test bStopTest:=FALSE; ! This insures that the program executes until the ! user chooses to exit WHILE bStopTest=FALSE DO TestDB; ENDWHILE ERROR IF ERRNO=ERR_UNLOAD THEN TRYNEXT; ENDIF ENDPROC !
ErrWrite "Create Err: Time out - S4CustomDB.tblBasic", "Create Timeout Err: "+NumToStr(nError,2); TPWrite "Timeout Err: Time out - S4CustomDB.tblBasic "+NumToStr(nError,2); ELSE IF (nError<>0) THEN ErrWrite "Create Err: S4CustomDB.tblBasic", "Create Failed Err:"+NumToStr(nError,2); TPWrite "Failed Err: S4CustomDB.tblBasic "+NumToStr(nError,2); ELSE TPWrite "Create OK: S4CustomDB.tblBasic"; TPWrite " "; ENDIF ENDIF ENDPROC
3HAC031359-001 Revision: B
157
158
3HAC031359-001 Revision: B
3HAC031359-001 Revision: B
159
2. Set up the Boolean attributes of the data event. 3. Select the counter that will increment as a result of the data event. Set Up the Data Event Follow the steps below to add a new data event. 1. At the Device Configuration Utility, click the Data Events button. 2. The data event pane appears. Click the Add New Data Event button. 3. The Add Data Event dialog appears.
xx0500001671
Enter a name for the new data event and click OK. This name will appear in the Data Event pane in the DCU. Choose a descriptive, unique name.
xx0500001672
5. The Select OPC Server dialog appears (see Select OPC Server Dialog in the Device Configuration Utility help file). Select the OPC server where the tag you will use in your expression is located and click OK. 6. Select the OPC tag from the selected server that you will use in your data event. Click the second Browse button. 7. The Change Tag dialog appears. Navigate through the tree in the left hand pane to the device you will use. Then select from the available tags in the right hand pane and click Change Tag.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
xx0500001673
8. The Data Event dialog reappears, and the OPC server and tag that you have selected should appear in the two top fields of the dialog. Continue on and create the data event expression.
3. You can hard code the name of the timer or counter node by typing the name in the Counter node name field. OR If you wish to use an OPC Tag as the timer or counter node name, select the OPC Tag check box, and click Browse to display the Change Tag dialog. Choose the tag that will serve as the timer or counter.
xx0500001674
This dialog shows all of the WebWare Devices in the network. WebWare Devices identify the containers where the counter or timer operation will be stored in the WebWare database. Each counter or timer operation will be stored in the database using the device name you select from the list above as the key. You use the same device name to extract the data in a report. Click on the top left-hand button to view the nodes in Physical view, looking at the actual devices on the network. Click on the top right-hand button to view the logical plant model created in the DCU. 2. Click on the counter/timer node and then click OK. 3. The Data Event dialog will reappear.
xx0500001675
Click OK to save the data event and close the Data Event dialog. Edit an Existing Event Expression Follow the steps below to edit an existing Data Event expression. 1. At the Device Configuration Utility (DCU), click the Data Event button. 2. Double-click on the data event you wish to edit.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
3. The Data Event dialog appears. Change the data in the appropriate fields and click OK to save the revised expression. 4. Click: the top Browse button to open the Select OPC Server dialog to change the selected server the next Browse button to open the Change Tag dialog to select a different tag to use the IF list box to change the IF expression condition the THEN list box to change the result the Counter/Timer Name field to change the name of the counter or timer the Counter/Timer Node Name Browse button to select a new network counter/timer node
5. When you have completed your changes, click: OK to save the changes and return to the previous screen Cancel to close the dialog and return to the previous screen without making any changes Apply to save the changes and keep the dialog open.
164
3HAC031359-001 Revision: B
User Interface The Reports menu provides three choices: Viewer - A display page that allows you to select a report and run the report. When you click the View Report link (magnifying glass), WebWare Server updates the source data and renders the report on screen. Manager - A display page that lists the reports and report modules currently on the server available for processing. The Manager page allows you to add, delete or edit reports or report modules from the system. Service - A display page that displays service information for robots that have Service Information System (SIS) installed. Report Components A report is assembled from basic parts, or modules. There are three different types of modules available: Chart Module HTML Module Table Module
Each report is divided into five physical areas or panes. By default, when you add a component to your report, the system places the component in the center pane. You use the arrows to move the component from pane to pane to its desired location.
166
3HAC031359-001 Revision: B
xx0500001676
Screen Components The table below describes the function of the screen components that appear on the Report Manager page. Component
Reports List Box Magnifying Glass Icon
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Function
Lists the reports currently on the server ready to be viewed. Select a report and click the magnifying glass icon to view a report in the list.
3HAC031359-001 Revision: B
167
Screen Components The table below describes the function of the screen components that appear on the Report Manager page. Component
Reports List Box + Icon Modules List Box Pencil Icon X icon
Function
Lists the reports currently on the server ready to be run. Click to add a new report or module to the list. Opens the Report Builder page. Lists the modules (report components) on the server that can be assembled to form a report, or opened and edited. Click to open the selected item for editing. Click to delete the selected item from the server. Click to import a report pack onto the WebWare Server host machine.
xx0500001678
Click to export selected reports and modules as a WebWare Server report pack.
xx0500001679
168
3HAC031359-001 Revision: B
xx0500001677
4. The Report Builder page will appear. Choose the first module that will appear in your report. Click on one of the links in the Add: box: Chart - to add a bar chart or line chart HTML - to add a block of HTML code Table - to add a table of selected data sources and values
5. The Definition page for the item you selected will appear. Click on either: New - to create a new module for your report. For more details, see How to Add an HTML Module to Your Report on page 193 and How to Create a Chart/Table Module on page 175. Existing - to add an existing module already on the server to your report. For more information, see How to Add an Existing Module to Your Report on page 174.
6. Repeat steps 4 and 5 until your report is complete. 7. Enter a new report name in the Report Name field. 8. Enter any descriptive comments in the Report Description field. 9. Click on: Save - to save the completed report on the server under the name in the Reports: list box. Cancel - to blank all panes in the Report Builder and return to the Report Manager page
3HAC031359-001 Revision: B
169
xx0500001680
Screen Components The Item Numbers in the table below correspond to the callout numbers in the figure above. No.
1 2 3 4 5 6
Component
Reports Submenu Report Box Description Box Add menu Panes Right Arrow/Left Arrow
Function
Allows access to all Report functions. Displays the default name of the report that you will build. Displays a user-defined description. Click on a link to add a component to your report. Panes are the pre-defined containers that locate modules on your report page. Move the highlighted element listed in the pane to the pane to the right or to the left, depending on the arrow you click on. Move the highlighted element up in the current pane. If the item is the uppermost item in the pane, move the element to the next pane above on the page. Move the highlighted element down in the current pane. If the item is the lowermost item in the pane, move the element to the next pane below on the page. Edit the selected item in a pane. Delete the selected item from the pane. Click to save the report on the server.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Up Arrow
Down Arrow
9 10 11 170
Pencil X Finish
Component
Cancel
Function
Click to cancel the report build process. Clears all panes on the Report Builder page.
3HAC031359-001 Revision: B
171
4. When you have finished, click the Finish link at the bottom of the page.
172
3HAC031359-001 Revision: B
3HAC031359-001 Revision: B
173
174
3HAC031359-001 Revision: B
3HAC031359-001 Revision: B
175
2. When the Chart/Table Definition page appears, click New. 3. Click Next. The next Definition page appears. 4. Click on the Name field and enter the file name for the module. 5. Click on the Title field and enter the title that will appear on the chart/table when it is displayed on the screen. 6. Click Next. The Data Source Selection list box appears. 7. Select from one of the categories (database tables) to query. You can query from one of the following tables: Counters Timers Log Events OPC Alarms and Events Custom WebWare database tables
8. Click Next. The Query Builder page appears. Complete the database query. For more information, see How to Build a Database Query on page 177.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
176
3HAC031359-001 Revision: B
3HAC031359-001 Revision: B
177
xx0500001681
User Interface Components The table below lists the functions of the components on the Query Builder page. The Item Numbers in the table below correspond to the callout numbers in the figure above. No
1 2
Component
Design Pane Field Name
Function
Click to open or close the query constructor. These are the standard fields available to make up your query. To see all available standard fields for the query you are creating, click Add Field. User defined name for the column heading in the generated table. Perform simple operations on a field. For example, you can perform average, count, sum, etc. operations on numerical fields. The only operation that you can perform on string fields is the count operation. Click the down arrow to select a sort option from the list. Available sort options are: Ascending Descending None
3 4
Description View
Sort
Component
Output
Function
Click this check box to output the data. Leave this check box blank to process the data but not display this column of the query in the final results. Used only for timer queries to select the display units (hours, minutes, etc.) for the value field. If the criteria choices are available, click the down arrow to display the list of available choices. If the criteria field is editable, click on the field and enter the criteria to sort the data by. For details, see Refining a Query on page 181. Click on the arrow button and select a field to add to the query. The new field will be added to the right-hand side of the existing query. Use the arrow buttons to move the field to its correct position. Click to open the design-time Options pane. Click to open the Result pane. Move the module to the right or to the left, depending on the arrow you click on. Delete the selected item from the pane. Return to the Query Definition page. You will lose any changes you made to the query. Save the changes you made to the Query and return to the Report Manager page. Discard any changes made to the Query and return to the Report Manager page.
7 8
Format Criteria
10 11 12 13 14 15 16
Options Link Result Link Right Arrow/Left Arrow X Back Finish Cancel
Basic Concepts The query builder is designed to conceal some of the difficulties with creating SQL queries. In order to prevent you from getting bogged down in the details, some of the power of SQL is cloaked in the WebWare Server Query Builder interface. Because of the compromises that were made, some queries cannot be created via the query builder. To create a readable chart, follow these guidelines: Make the data set fairly small (less than 25 items) Make the first column in the query a text field. Make the next 1 - 5 columns numeric.
One of the most important things to remember about the WebWare Query Builder page is that the sort order applies to all columns in the query, from left to right.
The illustration below shows the page where you can select the data source for your query.
xx0500001682
As an example, if you decide to query Counter data, WebWare automatically selects the unique fields available for Counter type data. For counters you select from the following fields: Device Name Device Class Device Type Counter Name Time Value
A query can have duplicate fields. Each of the standard data types has a set of unique fields taken from a defined set of tables. This is different from Microsoft Access, where you build a query by selecting the tables to be included in a query. Continues on next page
180 3HAC031359-001 Revision: B
Function
Click to move the selected column to the left one column. Delete the column from the query. Click to move the selected column to the left one column. Select a column from this list box to add to your query. The column will be appended to the right side of the query.
Configuring the Data Shown Use the components listed below to configure the output results. Component
Description field View list box Sort list box Output check box Format list box
Function
Enter the column header text here. Choose from available view properties here. Choose either ascending or descending table record sort here. Check to show output in resulting table. Remove check to process data but not display results in final table. If the field contains information that can be formatted in multiple ways (timer data can be displayed in various time units, for example) this list box will appear and be populated with appropriate options. Enter the criteria to filter the results by here.
Refining a Query After you have selected a query type and the fields that you need in your query, you may have to refine the query to display only the data you are interested in. For example, you may want to create a query that displays values for just one counter, or for errors that occurred during a certain time span. It is simple to create queries that exclude/include certain text strings or a range of numbers. For example, in the Counter Query there is a field named Value. To refine a query to return all counters that contain a value greater than twenty and less than one hundred would be written using this syntax:
>20 AND <100
The operators that are allowed for number fields are: Operator
= != > < >= <= AND OR
Description
equal to not equal to greater than less than greater than or equal to less than or equal to logic AND logic OR
The operators that are allowed for text fields are: Operator
= != AND OR *
Description
equal to not equal to logic AND logic OR wildcard character
In WebWare Server, criteria are not case-sensitive. To denote a string, enclose the string text inside quote ( ) or quotation marks ( " " ). Boolean Criteria The Report builder interface allows selection of Boolean fields for custom tables. You can filter all True values or all False values. When filtering a selection for all true values, the system looks for values equal to True or 1. The True value is not case sensitive. When filtering a selection for all false values, the system looks for values equal to False or 0. The False value is not case sensitive. When the Criteria field is used, NULL values in Boolean fields are dropped from the result set. When no Criteria is specified in the criteria field, NULL values are displayed in the result set. If a Boolean field is NULL the value appears as a blank cell in the table.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
The Criteria field for Boolean values supports OR and AND operations. For Boolean values, the View field allows two selections: COUNT None
When View Field is set to COUNT the Boolean field is changed to a number and displays the number of records that match.When View Field is set to None the value of the Boolean field is displayed as True or False. Boolean values may be sorted, according to the following values: Device Name Criteria Use this criteria to: Allow the user to select the device or devices that the report will run against Allow the report to be run only against pre-selected devices chosen by the report designer when the report is created. Continues on next page
182 3HAC031359-001 Revision: B
None Ascending - all false values appear first, in alphabetical order Descending - all true values appear first, in alphabetical order
Timers have the following relationships: $CYCLE Value + $NOTINCYCLE Value = $ONLINE value. $CONNECT Value + $DISCONNECT Value = total query time span, if the device alias was defined during the entire query time span. If the $OFFLINE timer is running, neither the $CYCLE nor the $NOTINCYCLE timers can run. IMPORTANT: The $CYCLE timer does NOT measure how long a robot takes to complete one cycle! $CYCLE is how long the robot is in Auto Mode, Motors On, and the program is running.
xx0500001683
The following sections describe how WebWare Server handles partial time segments when measuring timer cycles. Partial Time Segments ON When the query runs, the timer values that fall between the User-defined start and end times will be included in the results. In the illustration, any of the black lines will be included in the results, while the dotted lines will be excluded.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
xx0500001684
xx0500001685
Timer Value Field The Value field supports the following View choices:
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Sum - The total time within the defined Time Range/Interval in which a timer is on Avg -The average time of timer cycles within the defined Time Range/Interval in which a timer is on Min -The minimum duration of all timer cycles within the defined Time Range/ Interval Max - The maximum duration of all timer cycles within the defined Time Range/ Interval StdDev - The standard deviation of all timer cycles within the defined Time Range/ Interval
The Value field supports the following Format choices: Hours Minutes Seconds Percent
Timer query results are rounded down to three significant digits (xx.x%, 0.0xxx hours, 230 seconds, 2.23 minutes, etc.)
Option Settings:
Time Range: Specified radio button selected Start Time End Time 00:00 Sunday February 1 23:59 Thursday April 15
Chart Options:
Title Legend Position Data Format Chart Type Category Label Value Label Timer Chart Top Series ID and Category ID in Columns Column Category Label Value Label
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
xx0500001686
3HAC031359-001 Revision: B
187
If you specify a time range setting for your report at design time, the User Defined time range option will be disabled, and the time range that you specified will be used every time you run that report. The same concept holds true for the Criteria fields in the query constructor. For example, if you change the [User Defined] criteria entry in the Device Name column of the query constructor, every time the report is run, it will use only data from the device with the name you specified to generate the report. Procedure Follow the steps below to set up the Design-Time options for your chart or table. 1. Set up the chart or table parameters. 2. Build and refine your query. 3. Click the Options link to open the Options pane.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
4. Select the Maximum number of rows checkbox and enter the number of rows you wish to see per page of results in the field on the right. 5. Select the time range you wish to apply to your query: User Defined - set up your module so that WebWare Server will display calendar controls to allow the user to select the time criteria used in the query when he or she runs the report. Named - apply a pre-configured range: Today - From 12 a.m. (midnight) to now Past 24 Hours - From now to 24 hours ago at this time. Yesterday - From 12 a.m. (midnight) the day before yesterday until midnight last night. Last Week - From 12 a.m. (midnight) on Sunday of the previous week to midnight of this past Sunday. This Week - From 12 a.m. (midnight) Sunday to Now. Last Seven Days This Month - From 12 a.m. on the first day of this month to now. Last Month - From midnight of the 1st of last month to midnight of the 1st of the current month.
3HAC031359-001 Revision: B
189
3. Click either: Preview Data - to display a pop-up window containing the data returned by the query you have created Preview Chart - to display the finished module in a pop-up window
190
3HAC031359-001 Revision: B
4. Click Finish to save the module. The module will appear in the Report Manager page Modules list box. Click Finish a second time to save the report that you created the module in.
3. Click either: Preview Data - to display a pop-up window containing the data returned by the query you have created Preview Table - to display the finished module in a pop-up window
4. Click Finish to save the module. The module will appear in the Report Manager page Modules list box. Click Finish a second time to save the report that you created the module in.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
3HAC031359-001 Revision: B
191
HTML modules can be placed anywhere on the report you create. You save modules at the server along with tables and charts that you have created.
192
3HAC031359-001 Revision: B
xx0500001687
Click on the HTML Snippet Name field and enter a title for the Snippet. 6. Click on the Content field and enter the HTML code that will make up the snippet. 7. Click the Preview button to display the snippet as it will appear on your report. 8. Click on: Back - to go back to the previous page (for example, you change your mind and decide to use an existing module instead of creating a new one). You will lose any changes you have made in the current page. Finish- to save the completed module on the server under the name that you assigned in the Html Snippet Name field. Cancel - return to the Report Builder page and blank all panes in the Report Builder.
3HAC031359-001 Revision: B
193
4. Click Finish to save the table. 5. Click Finish to save the report. 6. Open the report viewer and select the report you just created. 7. Click the magnifier link to run the report. In our example the report runs, generating a table as shown. Notice that the Export to Excel link in the lower right hand corner of the report. 8. Click the Export to Excel link. The File Download dialog will appear. 9. Click: Open, to open the file in Microsoft Excel, (if Excel is installed on the local machine) Save to save the file as an Excel file to the path and name you select. The file will have a default extension of .xls.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
194
3HAC031359-001 Revision: B
3HAC031359-001 Revision: B
195
196
3HAC031359-001 Revision: B
xx0500001688
4. Right-click on the content pane of the Registry Editor. From the pop-up menu, select New, and then click String Value.
xx0500001689
xx0500001690
8. Click OK. The string values should now appear in the Data column in the Device Log, next to the new key. 9. You may have to restart WWService.exe for the changes to take effect.
198
3HAC031359-001 Revision: B
xx0500001691
To display the SIS view, you select a Data Collector and view the SIS status for all robots connected to that Data Collector.
xx0500001692
The Status field is always visible. If the SIS status is Connected or SIS Not installed the SIS variable fields are not visible. If the SIS status is Not Connected the SIS variable fields are not visible. If the SIS values displays ??, the variable is unavailable or cannot be calculated. For example, if the robot is not in Auto Mode, the warning levels, calendar and production intervals cannot be read from the robot.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Component
Status Field
Function
Shows the status of the highlighted robot connection and SIS status. Valid values are: Not Connected SIS Installed SIS Not Installed
Function
Date when service was last performed on the robot. Elapsed time since service was last performed on the robot. Date when next service is scheduled. Shows the remaining time until the next scheduled service. Show the warning level percentage. When the service warning level is reached, the system generates a service log.
Function
Display the service level time in hours.
Function
Displayed in hours and minutes and shall show the motors on total run time since the last system start. Displayed in hours and minutes and shall show the motors on run time since last service. Displayed in hours and minutes and shall show the remaining time until next scheduled service. Displayed in hours and minutes and shall also show the warning level percentage.
Function
Shows the warning level percentage. Shows the following information for the robot joints: Joint number, consumed time (in percent), elapsed time and remaining time in hours. Service Level Exceeded message for any joints that have surpassed their service interval.
3HAC031359-001 Revision: B
201
202
3HAC031359-001 Revision: B
xx0500001693
Remember, the Log Number is actually the log event, or type of event that is being recorded. Log No
106 107 108 109 110 111
Robot Area
Service Message: Service is due! <n> calendar days since last service Service Message: Service is due! <n> calendar days to next service due Service Message: Service is due! <n> operational hours since last service Service Message: Service is due! <n> operational hours to next service due Service Message: Gearbox <n> requires service Service Message: X% of the service interval for gearbox <n>. has expired
3HAC031359-001 Revision: B
203
204
3HAC031359-001 Revision: B
3HAC031359-001 Revision: B
205
5.2 ABB WebWare Server & ABB Network File System 5.2.1. Network File System (NFS) Overview
Introduction The ABB Network File System (NFS) option was originally designed to provide an alternative method for restoring files to a robot controller via a TPU. The other alternatives that existed previously were: use the TPU to retrieve files from remote locations manually perform backup and restore functions from the robot TPU
WebWare, in combination with NFS, provides powerful configuration options for setting up and moving data around the WebWare network. Use the WebWare with the NFS option to: copy files from one robot to another provide more drive space for large programs provide faster backup speeds access backup archives from the TPU using the standard restore function
The View from 3rd Party NFS Servers Using a third-party NFS server, you would have to use the server software to configure the network. You would create the robot file system mounts and all of the information as shown in the table below. Mount List IDs
name 1 name n
Disk Directory
c:\directory path c:\directory path
Access Rights
All Read Only
Users
Username/Password 1 Username/Password n
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Each of the named IDs in the table above require configuration of a separate mount point. As you can see, this is much like setting up any standard network system. You create the users, give them rights, and establish their working directories. InterLink and NFS With InterLink, you must create an alias for each robot that will move files around the system. After that, everything else happens automatically: You create a robot alias. The system automatically creates a mount name using /. The system then automatically assigns a disk directory based on the alias name. The system actually identifies the alias to the system using the robots IP address. The system automatically assigns access rights to the alias.
All of the above appears to be very complicated, but remember - all you do is to configure a robot alias and activate NFS. The WebWare system takes care of the rest. The advantages of this approach are: It is much easier and faster to configure an InterLink based NFS network. You really create only one mount point - each robot gets its own disk space, which appears identically to all robots in the system. Continues on next page
206 3HAC031359-001 Revision: B
The directories that are created will appear differently, depending on where you are viewing them from: From the robot (TPU), the directory structure will appear as shown below:
/ /Backup /User Directory
These directories appear to be local to the robot. From the WebWare client view:
Backup:/ Backup:/Backup Backup:/User Directory
The path at the physical location with Visual SourceSafe installed and configured:
c:\FileManagerData\Data Collector Name\Robot Alias Name $\WebWare\Data Collector Name\Robot Alias Name\Backup c:\FileManagerData\Data Collector Name\Robot Alias Name\User Directory
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Notice that the only real difference is the path to the backup data, which is stored in SourceSafe as a project. This path is configured using the WebWare client SourceSafe Configuration page, in the Admin menu. For complete details on managing WebWare data with Visual SourceSafe, see WebWare Visual SourceSafe Module on page 255. Deleting Files Suppose, in your NFS system, you access the local file structure using Windows Explorer, and you delete a file. From any vantage point in the system, (TPU, WebWare Client) you will not see any immediate change, since file updates are not automatic. The file directory views are only updated when: the robot or Data Collector is re-started the contents are modified by the WebWare client the contents are modified by an NFS client a WebWare backup is executed.
208
3HAC031359-001 Revision: B
xx0500001694
xx0500001695
3. Click OK. The message shown in the previous figure indicating that the computer must be rebooted will appear. 4. Reboot the computer. The NFS function is now enabled in InterLink. 5. If necessary, restart DCU and define an alias for the robot. IMPORTANT: You must define an alias for the robot before NFS will work. No special profile settings are required for that alias. If no alias is defined, or if NFS is disabled, all NFS mounts are rejected and an error is reported at the robot controller.
3HAC031359-001 Revision: B
209
Procedure Follow the steps below to configure the robot as a Network File System (NFS) client so that the robot can backup files via NFS. 1. From the Teach Pendant Main screen, press the Other Windows key. 2. From the Other Windows menu, select System Parameters and press the Enter key. 3. The System Parameters screen appears. Highlight Communications and press the Enter key. 4. The list of available physical channels appears. Press the Types menu button. 5. Highlight Application Protocols and press the Enter key. 6. A list of configured communication protocols is displayed. If an entry for NFS exists, then highlight the entry and press the Enter key. Go on to step 12. If no entry for NFS exists, Go on to step 7.
7. Press the Add function key. The protocol configuration screen appears.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
8. Select the Name parameter and press the Enter key. 9. The S4c keyboard appears. Enter the text string for the new name (e.g. NFS) and press the OK function key. 10. Select the Type parameter and press the Enter key. A list of available protocols is displayed. NOTE: If NFS is not displayed in the list the robot software option is not installed and therefore cannot be used. 11. Select NFS and press the OK function key. 12. Select Trans. Prot. and press the Enter key. A list of available protocols appears. Select the protocol that you will use, e.g. TCP/IP, press OK. 13. Highlight Server IP Addr (S4C+) or Server Address (S4C) and press the Enter key. 14. The S4c keyboard appears. Enter the text string for the Data Collector IP address e.g.130.110.69.222 and press OK. NOTE: This address must be a fixed IP Address! 15. Highlight Local Path, and then press the Enter key. The S4c keyboard will appear. Enter a meaningful name for the Local Path (pc: for example), the name that will be used to identify the mount on the robot, and then press the OK key.
3HAC031359-001 Revision: B
211
Procedure Follow the steps below to configure the robot as a Network File System (NFS) client so that the robot can backup files via NFS. 1. Open RobotStudio Online. 2. Open preferred robot view or create a new. 3. In the Robot View Explorer, select robot controller and expand the robot controller tree by clicking the plus sign. 4. The System Parameters appears. Expand the Configuration tree by clicking the plus sign. 5. Highlight Communication. 6. From the Controller menu select Configuration > Configuration Editor... The Configuration Editor appears. 7. From the Type name window, select Application Protocol. 8. A list of configured communication protocols is displayed. If an entry for NFS exists, double click the entry and go on to step 12.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
9. Right click Application Protocol and select Add Application Protocol. NOTE: If Add Application Protocol is not selectable; on the Controller menu, select Request Write Access. 10. The Edit Application protocol(s) dialog appears. Highlight the Name parameter and enter a new name in the Value box (e.g. "NFS"). 11. Highlight the Type parameter and select NFS from the drop-down list in the Value box. NOTE: If NFS is not displayed in the list the robot software option is not installed and therefore cannot be used. 12. Highlight the Transmission protocol. From the Value box drop-down list, select the protocol that you will use, e.g. "TCP/IP". 13. Highlight Server address and enter the text string for the Data Collector IP address e.g.130.110.69.222. NOTE: This address must be a fixed IP Address! 14. Highlight Local Path. Enter a meaningful name for the Local Path (pc: is default), the name that will be used to identify the mount on the robot.
3HAC031359-001 Revision: B
213
5.2.5. How to Restore Files from an NFS Mount Using the Robot Teach Pendant
Introduction It is possible to restore Webware backups from an NFS mount using the robot teach/flex pendant, if NFS is enabled, and Microsoft Visual SourceSafe is disabled. It is also possible to restore robot backups from an NFS mount that were initiated from the robot teach/flex pendant. It is not possible to restore Webware backups with Microsoft Visual SourceSafe enabled or if NFS is disabled as the files are invisible to the robot controller. In this case the restore function available in the WebWare RAPID module (WEBWARE.SYS) must be used. In this case, use the RAPID command, WWRestore. To enable the WWRestore procedure, a program needs to be written that restores named files or folders to a specified controller location (on the ramdisk). For more information, see WebWare RAPID Restore Procedure on page 299. Using the NFS restore command from the robot teach/flex pendant, all files in a backup are loaded into controller memory using a single command. Procedure Follow the steps below to restore a backup file set to a controller using the NFS Restore command at the robot TPU. 1. From the robot teach pendant, press the Other Windows button. 2. Highlight the Service menu and press the button. 3. Select File and then Restore from the teach pendant menu. The restore screen will appear.
xx0500001696
xx0500001697
Press the Unit button until the Massmemory Unit is: PC:. The teach pendant will display a list of directories available on the NFS mount. NOTE: All the NFS backups initiated from WebWare Server will be located under the backup directory on the NFS mount. The backup folder will contain subfolders in the following format: DD-MM-YYYY HH_MM. 5. Select a directory to restore from and press the OK button. 6. Press the OK button at the following teach pendant screen to initiate the restore.
xx0500001698
7. The robot will begin restoring files beginning with the system parameters. Once the system parameters are restored the robot will perform a warm start and continuing restoring the program and any system or program modules. 8. Upon completion of the restore verify that all files have successfully restored.
3HAC031359-001 Revision: B
215
5.2.6. How to Restore Files from an NFS Mount Using the Robot Flex Pendant
Introduction It is possible to restore Webware backups from an NFS mount using the robot teach/flex pendant, if NFS is enabled, and Microsoft Visual SourceSafe is disabled. It is also possible to restore robot backups from an NFS mount that were initiated from the robot teach/flex pendant. It is not possible to restore Webware backups with Microsoft Visual SourceSafe enabled or if NFS is disabled as the files are invisible to the robot controller. In this case the restore function available in the WebWare RAPID module (WEBWARE.SYS) must be used. In this case, use the RAPID command, WWRestore. To enable the WWRestore procedure, a program needs to be written that restores named files or folders to a specified controller location (on the ramdisk). For more information, see WebWare RAPID Restore Procedure on page 299. Using the NFS restore command from the robot teach/flex pendant, all files in a backup are loaded into controller memory using a single command. Procedure Follow the steps below to restore a backup file set to a controller using the NFS Restore command at the robot flex pendant. 1. From the robot flex pendant press the ABB logo. 2. The main menu appears. Select Backup and Restore. 3. The Backup and Restore screen appears. Select Restore System...
xx0600003104
xx0600003105
5. The Select Folder screen appears. Press the browse-up-icon until the Massmemory Units are displayed (e.g. Hard Drive etc.). NOTE: All the NFS backups initiated from WebWare Server will be located under the backup directory on the NFS mount. The backup folder will contain subfolders in the following format: Backup_ YYYY MM_DD. 6. Press PC:. The flex pendant will display a list of directories available on the NFS mount. 7. Select a directory to restore from and press OK. 8. The robot will begin restoring files beginning with the system parameters. Once the system parameters are restored the robot will perform a warm start and continuing restoring the program and any system or program modules. 9. Upon completion of the restore verify that all files have successfully restored.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
3HAC031359-001 Revision: B
217
Robot Ramdisk
X X
Backup Files
Robot Floppy
X X
X X
File Maintenance It is always good policy to check network hard disk file space. WebWare Server performance is impacted significantly by the number of files on network drives. On Local File Systems - systems without Visual SourceSafe installed, you are required to manually delete old or duplicate files. Each WebWare backup that is run creates new data folders, and therefore the number of files and folders on network drives will increase over time. On systems with Visual SourceSafe installed, only files that change are automatically archived. If you delete or rename robots, however, you may need to delete files from Visual SourceSafe archives. Use the Visual SourceSafe client to manage these types of tasks.
218
3HAC031359-001 Revision: B
WebWare Server backup represent the simplest form of backup available through the WebWare family. All data is transferred within the WebWare network via InterLink, and the backup data is archived on WebWare Server. All backup requests are initiated from WebWare Server, and depending on network topology, may be forwarded directly to subordinate robots or directed to WebWare Data Collectors, which act as slaves to the server and masters to subordinate robots. Robots write backup information from their Ramdisk or Flashdisk to WebWare Server or to a Data Collector, and the information is stored in the File Manager portion of WebWare Server. WebWare Server Restore WebWare Restore enables quick and efficient restore capabilities to robot installations. Complete backup sets or single files can be restored to the robot controllers ramdisk using the WebWare Client or the TechPendant/FlexPendant. The restore function can be protected by a password to prevent unauthorized use. WebWare Server NFS Backup NFS backups offer performance improvements to WebWare Server, as the burden of backup data transfers is removed from the WebWare components, e.g. InterLink, and managed directly by individual client devices. S4C and later robot controllers are capable of mounting NFS drives, and the controller writes its backup data directly to the NFS device. NFS backups are enabled through the WebWare Server web site, and are requested by WebWare Server just like a standard backup. NFS backup clients are identi-fied by their profile in InterLink, and NFS backup requests are initiated by WebWare Server or a Data Collector when the server requests a backup. Instead of passing through the robot mass storage device, to a Data Collector, to the WebWare Server File Manager, the data is written directly to the NFS device.
xx0500001699
The diagram below shows a system where the WebWare network Data Collector is configured as an NFS server. The backup requests originate at the server, move through the Data Collector to the robot. The robot then copies the selected files directly to the WebWare
xx0500001700
If the network is connected to a SourceSafe database, the data is then moved into the database. The SourceSafe database might be located at the WebWare network server, or remotely from the server.
xx0500001701
xx0500001702
Robot Files Not Backed Up Files with extensions matching those in the list below are NOT backed up by WebWare Backup: *.bin *.chk *.cmd *.dir *. id *.ini *.tpu
3HAC031359-001 Revision: B
225
xx0500001703
NOTE: The illustration above shows the S4 Profile Editor dialog. In the IRC5 ProfileEditor, the FTP tab does not appear. 3. Select the data to be backed up. Check: Standard Backup - backup all of the following: RAPID programs and modules Ramdisk (S4C+ controllers) System Parameters
OR to select individual items or groups, click: RAPID - backup selected programs and modules only Event Logs - backup selected event logs only System Parameters - backup selected system parameters only.
NOTE: If you select Standard Backup, any other check boxes except for the Event Logs and Ramdisk check boxes will be cleared. The RAPID button to the right of the check boxes will also be disabled. Continues on next page
226 3HAC031359-001 Revision: B
3HAC031359-001 Revision: B
227
228
3HAC031359-001 Revision: B
xx0500001704
Screen Components The buttons on the Backup Control page are defined on the page.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
The Backup Comment text field can be used to add a comment of up to 1024 characters to a manual backup of a device set or selected devices. The comment along with the user name and backup task are stored in the WebWare database. The Backup Summary items in the table below represent a snapshot of the backup status of all the devices in the tree that can be backed up. Current Backup Status Component
In progress:
Function
This is the number of devices that have a backup in progress at the present time. You might have multiple selected backups scheduled, and the number of backups remaining will appear in this field. This is the number of device that are in an Idle backup state. These devices may or may not be available for backup.
Idle
Function
This is the number of backups that completed successfully. This is the number of backups that completed with errors. Go to the Backup Results page to examine the error details. This is the number of backups that failed due to time-outs, etc.
3HAC031359-001 Revision: B
229
xx0500001704
Select the devices to be backed up by clicking on the corresponding checkboxes next to the devices in the device tree pane. Click Start Selected Backup or Start Full Backup to begin backing up files immediately.
To backup a Device Set: Aborting Backups Once you have clicked the Start Selected Backup command button, the check boxes only indicate the devices that will be backed up. Simply uncheck-ing a box will not prevent the corresponding device from being backed up, once you have clicked a Start button. To abort the backup of a Selected Device for any reason, uncheck the box corre-sponding to devices that will be backed up, make sure the check the box(es) of the device(s) that will be aborted are checked, then click the Abort Selected Backups button. To abort the backup of all of the Selected Devices or a Full Backup for any reason, click the Abort All Backups button. Select the Device Set to be backed up from the drop-down list. Click Start Device Set to begin backing up files immediately.
230
3HAC031359-001 Revision: B
xx0500001705
During The backup status messages appear as the backup process initializes, checks the robot state and then actually begins the backup. Notice that the Final Status and Duration blank out, indicating that the backup process is underway.
xx0500001706
After... After the backup completes, the Final Status and Duration appear.
xx0500001707
3HAC031359-001 Revision: B
231
Message
No license
Task/Event
2 3 4
No backup is running. Backup is configured and started. Initialization is complete. Waiting for Auto Mode at the robot. Waiting for ww_StopProgram to be true, so that the robot program can be stopped. WebWare Server is now performing a standard backup.
Wait.
6 7
Save program
WebWare Server is now Wait. backing up selected RAPID programs. WebWare Server is now Wait. backing up selected RAPID modules. WebWare Server is now Wait. backing up selected configuration parameters. WebWare Server is now backing up selected log files. Wait.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Save modules
10
Save configuration
11
12
WebWare Server is now Wait. backing up the robot ramdisk/flashdisk contents. NFS is being initialized. This message will usually flash by so fast that you will not see it.
13
Commit to NFS
14
Push to Server
The command is sent to Wait. WebWare Server to receive files. Files are moved from the data collector to the WebWare Server network server computer. Wait.
15
Message
Completed
Task/Event
Backup was completed successfully.
Backup Final State Messages The table below lists the messages that appear in the final results table on the WebWare Server Backup Results page. The table also lists the related ID that is displayed in the Backup Log. For details, see How to Display Backup Results on page 243. ID
1
Message
Successful
Task/Event
The backup session completed successfully, without errors.
The backup session Use the WebWare Server completed successfully, but Results Page to examine errors occurred. the errors and determine what course of action to take. Backup was cancelled by Use the Backup Control the user (clicked one of the page to initiate a backup or Abort buttons). wait for the next scheduled backup, if one is scheduled. An external event caused the backup to fail. Restart the system or investigate the problem.
Aborted
4
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Failed Timeout
The backup session did not Investigate the problem or complete within the timeout initiate another backup period set at the WebWare session. Server Backup Schedule page. No backup is configured for Go to the DCU. the selected robot. Select the robot profile and click Edit Profile. Click the Backup file set tab and select the backup parameters needed. Install a WebWare Server License. See License Administration Page and License Key Request Process. WebWare Server has attempted to start a backup on a data collector (DC) that does not exist. Check network connections. Make sure the Data Collector is operating properly.
Not configured
No license
DC COM error
Message
Simulated mode
Task/Event
The robot alias is set to Either ignore this message simulate the interface at the or correctly configure the DCU. alias at the ICU (remove the Simulate Interface selection). The robot alias selected at WebWare Server for backup does not exist at the DCU. Use the WebWare Server Admin Page to delete the alias or configure the alias at the DCU.
10
No Alias found
11
In progress
Backup is cancelled before Redo the backup. Backup it is completed. folders are created in the robots File Manager Data folder, but they are empty. You may want to delete the empty folders. Backup has never been run Run a backup session. on this system. The Data Collector (DC) computer is disconnected from the WebWare network. The backup session timed out before the initialization step was completed. Check network connections. Make sure the Data Collector is operating properly. Check the interface connections between the network server and the Data Collector.
12 13
14
Timeout Init
15
Timeout Robot Ready Wait The backup session timed out before the robot status checking steps were completed. Timeout Robot Ready The backup session timed out before the robot indicated that it was ready to backup. The session timed out before the ww_backupOK variable was set. This could be related to RAPID programming. Increase the timeout interval at the Backup Control page.
16
17
The backup session timed Make sure the network out because the connection connections are communito the robot was lost. cating. The backup session timed out before the robot was placed in Auto mode. Make sure robot is placed in Auto Mode.
18
19
Timeout Backup
The actual backup steps Investigate the problem or did not complete within the initiate another backup timeout period set at the session. WebWare Server Backup Schedule page. The backup session timed Make sure out while waiting for ww_StopProgram is being ww_StopProgram to be set set to TRUE. to TRUE.
20
Message
Timeout Stopping Cycle
Task/Event
The backup session timed Look for external factors out while waiting for the that may be restarting the robot to reach a cycle stop. robot program (PLC's, SDK apps, etc.)
3HAC031359-001 Revision: B
235
xx0500001708
Screen Components The Backup Schedule page has the following components: Component
Sort by list + icon Pencil icon X icon
Function
This drop-down list lets you sort the list of scheduled backups according to Device Set, Frequency and Time Add a new scheduled backup. Edit the selected scheduled backup. Delete the selected scheduled backup.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
236
3HAC031359-001 Revision: B
xx0500001709
Screen Components The Backup Schedule page has the following components:
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Component
Device set list Start Time list
Function
This list box contains all of the available named groups of devices (device sets) that have been created. This list box contains all of the start times that have been entered into the system. Displayed with either 24-hour format or AM/PM-format depending on the Regional Settings. This list box contains all of the settings that determine how often a scheduled backup is performed, for details see Frequency Details on page 238. Available options include: Once Daily Weekly Monthly Here you set the date or set which day(s) of the week the backup will run. The display changes depending on the selected Frequency. Click apply to add the new scheduled backup to the list of scheduled backups without returning to the Scheduled Backup page. Click OK to add the new scheduled backup to the list of scheduled backups and return to the Scheduled Backup page.
Frequency list
Apply
OK
Function
Click Cancel to return to the Scheduled Backup page without adding the Scheduled Backup. Add a comment to a scheduled backup of a device set. The comment along with the user name and backup task are stored in the WebWare database.
Frequency Details If Once is selected from the Frequency drop-down-list, you may select a start time and a date for the backup. If Daily is selected from the Frequency drop-down-list, you may select a start time. If Weekly is selected from the Frequency drop-down-list, you may select a start time and which weedays the backup will run. If Monthly is selected from the Frequency drop-down-list, you may select a start time and either the day of the month to run the backup, or the first, second, third, fourth or last specified weekday of the month(s).
238
3HAC031359-001 Revision: B
3HAC031359-001 Revision: B
239
xx0500001710
Screen Components
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Component
Refresh Button
Function
Click to update the system and display the latest backup sessions available. You may need to use this button if you navigate to the Backup Results page before a backup session has completed. From this list you can select to display the results for all backups or backups related to a specific device set.
Results for Selected Devices Click to display the backups related to the device set selected button in the Device Tree. An additional page will be displayed. Table Entries Each row in the Results table becomes a hyperlink to a second table containing detailed information on the results of the backup session. Result codes are listed in Return Status Codes in the System Reference section. Click the hyperlinks, displayed at the botton left corner of the table, to display additional pages of the backup results table.
xx0500001711
When you click the Results for Selected Devices button on the Backup Results page, and you have selected one or more devices on the device tree, the Backup Results - Selected Device page will be displayed. This page contains information about the date of the last backup, the
xx0500001712
242
3HAC031359-001 Revision: B
xx0500001711
The upper table (A) shown in the Backup Results window provides a summary of the backup sessions that have been performed. Numbered hyperlinks at the bottom left of the table lead to any additional pages of backup sessions available. Each entry in the upper table provides a hyperlink to the Device Detail Result Table (B). The Device Detail Result Table provides details for all of the devices that were backed up during the selected session. The table includes the initiation time interval, the backup time interval and the storage time interval. The values are in seconds. The figure earlier illustrates the relationship between the three tables that can appear on the Backup Results page. Each of the red-highlighted entries in the upper tables are hyperlinked to the table below it on the page. The bottom table (C) is the Error Detail table. This table provides a list of all of the errors that occurred on the backup. It provides a good place to start troubleshooting problems with a backup session. For a complete list of WebWare error codes, see Return Status Codes in the System Reference section.
3HAC031359-001 Revision: B
243
Screen Components - Action Buttons The buttons above and right of the table headers may be disabled (grayed out), or enabled, depending on the current path and focus of the Backup Restore page. Component Function
Read-/Write mode Makes it possible to change the read-/ write mode on the selected file.
xx0600003084
Restore Copies the selected backup files to the robot controllers RamDisk.
xx0500001717
xx0500001718
Up Directory Moves the Backup Restore pages target directory up one level in the current path.
xx0500001719
xx0500001715
xx0500001721
Delete Permanently deletes the selected file or directory from the devices file store on the WebWare Server.
xx0500001724
Differences Displays a page showing all of the additions, changes and deletions between two selected files.
xx0500001726
Screen Components - Icons The icons that appear in the file manager are briefly described in the table below. Component
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Function
Folder icon.
xx0500001727
xx0500001729
xx0500001730
246
3HAC031359-001 Revision: B
3HAC031359-001 Revision: B
247
Notice the red and green icons - the red ones represent backups that contain errors. The content pane shows the contents of the highlighted folder. The Master Backup is depicted with a yellow circle. Backups are stored on the Backup Disk (0:/Backup folder) . This directory is read-only. Local Disk (1:) is visible only when RamDisk Mirroring is enabled. Last Successful Backup Folder To make it easier to locate the last backup run on the system, you can use the Admin Backup page to configure WebWare Server to save the last backup in a folder that you name. This is depicted as the folder Last Successful in the figure below.
xx0500001736
xx0500001735
xx0500001737
Using Visual SourceSafe The illustration below shows how the user interface changes when SourceSafe is installed, configured and started on the system.
xx0500001738
The icons for the backup folders have changed, but the red/green schema is still in place - red icons indicate backups that are incomplete or contain errors. The last successful backup folder schema is also still in place - the contents of that folder will be overwritten each time a new backup is run. The master backup folder schema is also still in place.
3HAC031359-001 Revision: B
249
4. If you are required to enter a restore password, a dialog will appear. Enter the four digit password and click OK to continue.
xx0500001740
5. The restore procedure will begin copying files to the robot controller. 6. To complete the procedure you need restore the files into the robot controller. This is done at the teach pendant. For details, see the robot controller documentation.
250
3HAC031359-001 Revision: B
xx0500001739
xx05001716
3HAC031359-001 Revision: B
251
<Root directory>\<Alias>\Ramdisk
Server Ramdisk Mirror Directory The ramdisk mirror is also stored under the servers preferred data directory. This directory is specified in the WebWare Data Configuration section of the WebWare Servers Admin page.
<Preferred Data Dir>\<Data Collectors PC Name>\<Alias>\Ramdisk
How Ramdisk Mirroring Works - Sequence of Events Each time InterLink is started, the existing ramdisk mirror on the Data Collector is deleted. The existing mirror on the WebWare Server is also deleted. The ramdisk is then mirrored to the Data Collector as well as the Server. This ensures that the mirror image contains the most current data.
3HAC031359-001 Revision: B
253
254
3HAC031359-001 Revision: B
Users can use the WebWare client to view the contents of the Visual SourceSafe project databases and select files to restore based on version dates. For example, if you change a robot configuration file on the floor and then later notice that the robot is not running correctly, you could use the Visual SourceSafe module to:
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
look up the project and check file versions determine if a file has changed select the file and upload the file to the robot, restoring it to its last known good operating condition compare versions of a file stored in Visual SourceSafe
Installing Microsoft Visual SourceSafe For complete instructions on installing, configuring and using Microsoft Visual SourceSafe, consult the Installation Notes on the Visual SourceSafe installation CD. For details about configuring WebWare to work with Microsoft Visual SourceSafe, see Configuring WebWare Visual SourceSafe Module on page 256. Installing Microsoft Visual SourceSafe Database on a Remote Computer IMPORTANT: For best system performance, install the Visual SourceSafe database on the WebWare Server host computer. In some situations your company may require that you install the Visual SourceSafe database on a remote computer. If this is the case, there are three critically important points to remember: 1. All computers on the WebWare network should be trusted members of the same domain, including the Visual SourceSafe server computer. 2. The ABBWebWare service must be set to use a user account that has permission to access and run programs on the computer that hosts the Visual SourceSafe database. 3. Both the WebWare Server host computer and the Visual SourceSafe server must use the same account to login to Visual SourceSafe.
3HAC031359-001 Revision: B 255
In this example, SrcSafe.ini file resides on the same system as the WebWare Server. A network path to another machine is also an acceptable location for the SrcSafe.ini file, for example \\[servername]\[vss shared folder]\SrcSafe.ini 3. In the Default SourceSafe Project field, enter a project name to indicate where SourceSafe should store backup data, for example $/WebWare For this configuration, the project name is WebWare, and the name must be formatted as a SourceSafe project name, such as $/[ProjectName]. NOTE: We recommend that you enter a project name other than the $/ default project name. The folder tree has many levels. Having all of the robot folders and files stored at the root project level in SourceSafe will make it difficult to navigate the SourceSafe interface. 4. Enter the SourceSafe user name and password that WebWare should use to access the Visual SourceSafe database. Contact your SourceSafe System Administrator for a user name and password for SourceSafe. NOTE: You are not setting the user name and password here, the user name and password are set by the SourceSafe Administrator. 5. Select the Enable SourceSafe checkbox, and then click the Set SourceSafe configuration button. If the SourceSafe interface is successfully configured, the SourceSafe Integration status message will change to Enabled. 6. After performing system backups, the stored files can be inspected using the Visual SourceSafe Explorer. In Visual SourceSafe Explorer, a new project will appear, ready to accept files.
xx0500001646
256
3HAC031359-001 Revision: B
xx0500001742
Component
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Function
Click to display the tree for the selected file. Click to move up to the next higher level in the tree. Click to create a new folder in your specified working directory, as shown in the figure above. You can use this folder as a destination when downloading files from SourceSafe. Click to download a copy of a file from SourceSafe. Click to upload a file to the robot. You can use this function to update robot files remotely. Click to delete the highlighted file from the browser window. This button is disabled when viewing any SourceSafe file or folder. Click to rename selected file. This button is disabled when viewing any SourceSafe file or folder. Click to display file history for the selected file. The File History dialog is displayd showing showing all the versions of the selected file in the system.
xx0500001743
The table below defines the column headers shown in the figure earlier. Component
Name Version Date Description
Function
The Name column shows the file name. The version column shows the version of that file. The date column shows the version date of the file. The description column describes the action that was applied to the file version on the date shown.
258
3HAC031359-001 Revision: B
3HAC031359-001 Revision: B
259
260
3HAC031359-001 Revision: B
xx0500001744
3HAC031359-001 Revision: B
261
Repeat this procedure for each file stored with an incorrect file type.
262
3HAC031359-001 Revision: B
6 System Reference
6.1. Overview
6 System Reference
6.1. Overview
What Youll Learn in This Section This section contains detailed information on: Custom Web Site Configuration Procedures Windows Service Pack Issues WebWare Rapid Module Resturn Status Codes Null Modem Cable Diagrams Installing WebWare with RobotStudio, QuickTeach or ProgramMaker
3HAC031359-001 Revision: B
263
6 System Reference
6.2.1. Overview
264
3HAC031359-001 Revision: B
6 System Reference
6.2.2. General Installation Process
2. Install WebWare Server. For complete details, see Complete Installation of WebWare Server on page 41. Complete all the procedures for installing the software and a software license, and then return to this table and complete the rest of the steps. 3. Configure IIS to host WebWare as a Virtual Directory or a Default Web Site (Windows 2000 Server/Advanced Server only). Windows 2000 Professional: See Configuring IIS to Host WebWare as a Virtual Directory on page 271. Windows 2000 Server/Advanced Server: See Configuring IIS to Host WebWare as a Default Web Site on page 279. 4. Set Default.aspx to be the default document. For complete details, see Selecting the Default Document on page 272.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
5. Configure the execute privileges on WWBIN. For complete details, see Enabling Execute Permissions for WWBin on page 273. 6. Install the .Net framework components. For complete details, see Running the .Net Installation Utility on page 274. 7. Apply a WebWare License. For complete details, see License Key Installation on page 44.
3HAC031359-001 Revision: B
265
6 System Reference
6.2.3. Installing Internet Information Services (IIS)
6. When prompted, click Finish. 7. Continue with Enabling Administrative Tools in Start Menu on page 269. Installing IIS on Windows Server 2003 Systems Follow the steps below to install IIS on Windows Server 2003. IIS is installed by default only on Windows Server 2003 Web Edition. If IIS is already installed, go to section Configuring IIS to Run ASP.NET Applications on Windows Server 2003 Systems on page 268. 1. Click Start, then click Control Panel. 2. Click Add/Remove Programs. 3. Click Add/Remove Windows Components. 4. In the Components list, select Application Server, and then click Details.
6 System Reference
6.2.3. Installing Internet Information Services (IIS) Continued 5. In the Subcomponents of Application Server list, select the ASP.NET check box. (This will allow ASP.NET applications to run.) Make sure Internet Information Services (IIS) is selected (it should be selected by default).
xx0500001745
6. Click OK. 7. Click Next to install IIS. You might be prompted to insert your installation CD. 8. When prompted, click Finish.
6 System Reference
6.2.3. Installing Internet Information Services (IIS) Continued Configuring IIS to Run ASP.NET Applications on Windows Server 2003 Systems A default installation of IIS on Windows Server 2003 systems does not permit the operating system to run ASP.NET. ASP.NET is required for the WebWare Server web site to function. Follow the steps below to allow the ASP.NET extensions to run on Windows Server 2003 systems. 1. Launch the Internet Information Services (IIS) Manager. Click Start, point to Administrative Tools and then select Internet Information Services (IIS) Manager. 2. Expand the Internet Information Services tree to display Web Service Extensions. 3. From the list of Web Service Extensions highlight ASP.NET v1.1.4322 and right-click and select Allow as illustrated in the figure below. If ASP.NET does not exist in the list of Web Service Extensions follow the steps in section Installing IIS on Windows Server 2003 Systems on page 266.
xx0500001746
268
3HAC031359-001 Revision: B
6 System Reference
6.2.4. Enabling Administrative Tools in Start Menu
3HAC031359-001 Revision: B
269
6 System Reference
6.2.5. Accessing the IIS Management Console
270
3HAC031359-001 Revision: B
6 System Reference
6.2.6. Configuring IIS to Host WebWare as a Virtual Directory
3HAC031359-001 Revision: B
271
6 System Reference
6.2.7. Selecting the Default Document
xx0500001748
2. Select the Documents tab. Note that the appearance of the Default.aspx document indicates that the .Net framework has been installed.
xx0500001749
3. Click the up arrow to move default.aspx to the top of the default list. 4. Click OK to close the dialog.
272
3HAC031359-001 Revision: B
6 System Reference
6.2.8. Enabling Execute Permissions for WWBin
xx0500001750
3. The WWBin Properties dialog appears. Select the Scripts and Executables from the drop down menu. Click OK.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
xx0500001751
3HAC031359-001 Revision: B
273
6 System Reference
6.2.9. Running the .Net Installation Utility
274
3HAC031359-001 Revision: B
6 System Reference
6.2.10. Configuring IIS with Personal Web Manager
xx0500001752
6 System Reference
6.2.10. Configuring IIS with Personal Web Manager Continued Selecting the Home Directory Follow the steps below to modify the home directory for the web server. 1. Click Advanced. The Advanced Options dialog will appear. Scroll down the Virtual Directories list and select WebWare.
xx0500001753
2. Click Edit Properties... The Edit Directory dialog appears. Click Browse, and select the directory where WebWare Server was installed. The default location is C:\Inetpub\wwwroot\WebWare. Verify that Access permissions are set to Read and Application permissions are set to Scripts.
xx0500001754
3. Click OK. The Advanced Options dialog will reappear. Enabling Execute Permission on WWBin Follow the steps below to assign execute permissions to the WWBin directory. 1. To create a virtual directory named WWBin in the Personal Web Manager, select <Home> at the Personal Web Manager Advanced Options page. 2. Click Add The Add Directory dialog appears.
6 System Reference
6.2.10. Configuring IIS with Personal Web Manager Continued 3. Click Browse and browse to the WWBin directory that can be found just below the directory where WebWare Server is installed.
xx0500001755
4. In the Alias field, enter WWBin as the directory alias. 5. Select the Execute (including scripts) radio button. 6. Click OK. 7. Continue with Setting the Default Document on page 277. Setting the Default Document WebWare uses Default.aspx as the default document (web page). At the Personal Web Manager Advanced Options dialog, click on the Default Document(s) field and change the order of the documents so that the first document is Default.aspx.
xx0500001756
3HAC031359-001 Revision: B
277
6 System Reference
6.2.11. Custom Installation Procedures
If you have decided to host WebWare as a Virtual Directory: Continue with Configuring IIS to Host WebWare as a Virtual Directory on page 271. DO NOT perform the procedure titled Configuring IIS to Host WebWare as a Default Web Site on page 279.
278
3HAC031359-001 Revision: B
6 System Reference
6.2.12. Configuring IIS to Host WebWare as a Default Web Site
xx0500001757
3. On the pop-up menu, point to New and then select Web Site from the sub-menu. The Web Site Creation Wizard welcome dialog will appear.
xx0500001758
6 System Reference
6.2.12. Configuring IIS to Host WebWare as a Default Web Site Continued 4. Click Next to continue. The Web Site Description dialog appears.
xx0500001759
5. Enter a description for the web site and then click Next to continue. The IP Adress and Port Settings dialog will appear.
xx0500001760
6. Select the computer's IP address. If your network is configured, you will find your computer's IP address in the drop down list box. If there is no IP address in the list box, cancel this Web Site Creation Wizard and specify an IP address via the Network configuration application found under the Windows Control Panel. If there are several IP addresses in the list box, then your system has more than one network adapter. Proceed with caution, and make sure you choose the correct IP address to host the web site on. Port 80 is the default port for the HTTP protocol and in general it should not be modified. Click Next to continue.
6 System Reference
6.2.12. Configuring IIS to Host WebWare as a Default Web Site Continued 7. The Web Site Home Directory dialog will appear.
xx0500001761
Enter the directory where you installed WebWare Server, e.g. C:\Inetpub\wwwroot\WebWare. Click Next to continue. 8. The Web Site Access Permissions dialog will appear.
xx0500001762
Normally the default settings are desired. Refer to Microsoft's Internet Information Server Resource Kit for further information on net security. Click Next to display the final dialog. Click Finish to exit the Web Site Creation Wizard.
6 System Reference
6.2.12. Configuring IIS to Host WebWare as a Default Web Site Continued Selecting the Default Document Follow the steps below to set up the default document for the web site. 1. Right click on the WebWare site entry found under the computer name in the IIS Management Console.
xx0500001763
xx0500001749
3. Click the up arrow to move Default.aspx to the top of the default list. 4. Click OK to close the dialog.
6 System Reference
6.2.12. Configuring IIS to Host WebWare as a Default Web Site Continued Enabling Execute Privilege for WWBin Follow the steps below to access the WWBin folder properties and set the execute permissions to allow scripts and executables to operate. 1. In the Management Console, expand the WebWare Site folder, if it is not already expanded. 2. Right click on the WWBin folder and select Properties.
xx0500001750
3. The WWBin Properties dialog appears. Select the Scripts and Executables from the drop down menu. Click OK.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
xx0500001751
3HAC031359-001 Revision: B
283
6 System Reference
6.2.13. Installed Files and Folders
WebWare Server Installation Files that are part of the WebWare Server web-site are installed in the following locations:
C:\Inetpub\wwwroot\WebWare C:\Inetpub\wwwroot\WebWare\admin C:\Inetpub\wwwroot\WebWare\Adobe C:\Inetpub\wwwroot\WebWare\bin C:\Inetpub\wwwroot\WebWare\client C:\Inetpub\wwwroot\WebWare\content C:\Inetpub\wwwroot\WebWare\data C:\Inetpub\wwwroot\WebWare\Docs C:\Inetpub\wwwroot\WebWare\framework C:\Inetpub\wwwroot\WebWare\help C:\Inetpub\wwwroot\WebWare\images C:\Inetpub\wwwroot\WebWare\InterlinkModuleInstall C:\Inetpub\wwwroot\WebWare\WWBIN C:\Inetpub\wwwroot\WebWare\wwscripts
Files that are part of the WebWare Server application are installed in the following locations:
C:\Program Files\Common Files\ABB Automation\WebWare Server C:\Program Files\Common Files\ABB Automation\WebWare Server\File Manager Data C:\Program Files\Common Files\ABB Automation\WebWare Server\Robot Data
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
WebWare Data Collector Installation Files that are part of the Data Collector application are installed in the following locations:
C:\Program Files\Common Files\ABB Automation\InterLink C:\Program Files\Common Files\ABB Automation\InterLink\Include C:\Program Files\Common Files\ABB Industrial IT\Robotics IT\RobInstallAPI C:\Program Files\Common Files\ABB Industrial IT\Robotics IT\RobAPI C:\Program Files\Common Files\OPC Foundation\Bin C:\Program Files\Common Files\OPC Foundation\Install C:\Document and Settings\All Users\Desktop C:\Document and Settings\All Users\Start Menu\Programs\ABB Industrial IT\Robotics IT\Licensing C:\Document and Settings\All Users\Start Menu\Programs\ABB Industrial IT\Robotics IT\WebWare Server
6 System Reference
6.2.13. Installed Files and Folders Continued Microsoft .NET Framework Installation Files that are part of the Microsoft .NET framework are installed in the following location:
C:\WINNT\Microsoft.NET\Framework
ABB Licence Application Files that are part of the licence application are installed in the following location:
C:\Program Files\Common Files\ABB Industrial IT\Robotics IT\Licensing
Adobe Acrobat Reader Installation Files that are part of Adobe Acorbat Reader are installed in the following location:
C:\Program Files\Adobe\Acrobat 6.0 CE\Esl C:\Program Files\Adobe\Acrobat 6.0 CE\Help C:\Program Files\Adobe\Acrobat 6.0 CE\Reader C:\Program Files\Adobe\Acrobat 6.0 CE\Resource
3HAC031359-001 Revision: B
285
6 System Reference
6.3.1. Overview
286
3HAC031359-001 Revision: B
6 System Reference
6.3.2. ABB WebWare Security Settings Utility
You have reregistered InterLink/WW Service. You have installed a Windows Service Pack or hotfix. Your Windows Firewall was disabled during installation, but subsequently enabled.
6. A question dialog might appear asking if you would like to configure your system with needed security settings. Click Yes to continue the configuration. If you click No, or if the Windows Firewall is disabled, you must manually configure the DCOM settings, see DCOM Configuration on page 289. 7. When the configuration is complete, the InstallShield Wizard Completed dialog will appear. Click Finish.
3HAC031359-001 Revision: B
287
6 System Reference
6.3.3. Windows Firewall Settings
ABB RobNetScanHost
C:\Program Files\Common Files\ABB Industrial IT\Robotics IT\RobAPI\RobNetScanHost.exe
Remote Assistance
C:\Windows\system32\sessmgr.exe
ABB WW Service
C:\Program Files\Common Files\ABB Automation\WebWare Server\WWService.exe
288
3HAC031359-001 Revision: B
6 System Reference
6.3.4. DCOM Configuration
With the My Computer properties sheet still open, in the COM Security tab, click Edit Limits to edit the security limits for Access Permissions and Launch and Activation Permissions according to the tables below. Access Permissions Anonymous Logon
Local Access Remote Access Allow Allow
Everyone
Allow Allow
Everyone
Allow Allow Allow Allow
6 System Reference
6.3.4. DCOM Configuration Continued TIP! NOTE: If the group or user names ANONYMOUS LOGON or Everyone are missing, click Add and complete the Select Users, Computers, or Groups dialog box. Application-Specific DCOM Settings The DCOM settings need to be configured for the following applications: ABB InterLink Module ABB WebWare
To configure application-specific DCOM settings, in the tree view of the Component Services dialog, expand first Component Services, then Computers, then My Computer, and finally DCOM Config. Right-click the application entry you are going to configure (ABB InterLink Module or ABB WebWare) and then click Properties to bring up a properties sheet. On the the General tab, set Authentication Level to None. On the the Security tab, edit the settings for Launch and Activation Permissions and Access Permissions according to the tables below. Launch and Activation Permissions Anonymous Logon
Local Launch Remote Launch Local Activation Remote Activation Allow Allow Allow Allow
Everyone
Allow Allow Allow Allow
Everyone
Allow
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Allow
290
3HAC031359-001 Revision: B
6 System Reference
6.4.1. WebWare RAPID Module (WebWare.sys)
2. Before starting the virtual controller, verify that FactoryWare Interface is enabled. For example by starting the Virual Robot Browser and verifying the configuration settings for the currently selected robot. 3. Start the virtual controller and click the Program button. 4. Click the File menu button and select Open. Navigate to the location of the WebWare RAPID module file (i.e.,WebWare.sys), see Obtaining the WebWare RAPID Module on page 291. 5. Select OK to load the WebWare RAPID module into the virtual controller. The RAPID program will now be able to reference any of the WebWare RAPID API functions.
3HAC031359-001 Revision: B
291
6 System Reference
6.4.2. Controlling WebWare Backup from WebWare.sys
The bool variables can be set on the robot teach pendant by selecting the Program Window, View / Data Types menu command and then selecting the bool data type. The bool variables can be set to TRUE or reset to FALSE. These variables can also be set programmatically in your RAPID program. For instance, you may only want to allow backups at certain times, such as between production cycles. Example:
! Cycle complete ww_BackupOK:=TRUE; _! Cycle start received ww_BackupOK:=FALSE;
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Default Behavior If these variables are deleted or commented out in the WebWare.sys module, the default behavior is:
bool ww_BackupOK:=TRUE; bool ww_StopProgram:=FALSE; bool ww_AutoRestart:=FALSE; bool ww_BackupRunOK:=FALSE; bool ww_HeartBeatOn:=FALSE; string ww_ProjectName=Project1; num ww_nRequestType:=1; num ww_BackupState:=2; num ww_BackupResult:=0;
6 System Reference
6.4.2. Controlling WebWare Backup from WebWare.sys Continued This means that the backup can proceed, the robot program will NOT be stopped , the robot program will NOT be restarted after the backup and the backup will NOT run during program execution. All backup files will be copied to a folder named Project1, all backup sets will be displayed during the restore routine, the backup state is in IDLE mode, and the backup result is unknown. ww_BackupOK When ww_BackupOK is set to TRUE or is undefined backups to the WebWare Server are allowed. When ww_BackupOK is set to FALSE backups to the WebWare Server are not allowed. ww_StopProgram NOTE: For IRC5, do NOT set ww_StopProgram to TRUE. This will result in a timeout. When ww_StopProgram is set to TRUE, WebWare Server will attempt to stop the robot program to perform the backup. When ww_StopProgram is set to FALSE or is undefined, WebWare Server will NOT stop the robot program. The backup will processed depending on the setting of ww_BackupRunOK. If the robot program is running and ww_BackupRunOK is FALSE, then the backup will not proceed. Also when ww_StopProgram is set to FALSE, ww_AutoRestart is ignored. ww_AutoRestart NOTE: Exercise caution when using this setting to avoid safety concerns or accidents. When ww_AutoRestart is set to TRUE the WebWare Server WILL restart the robot program after the backup is completed if:
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
The program was running with the robot in Auto mode and The program was stopped by WebWare backup and ww_AutoRestart is set to TRUE and ww_StopProgram is set to TRUE.
In other words, WebWare Server will not restart the robot unless WebWare Server stopped the program and the controller is in Auto mode. When ww_AutoRestart is set to FALSE or is undefined, WebWare Server will NOT restart the robot program after the backup is completed. ww_ProjectName This string variable allows you to specify the location where the backup files will be copied. As an example, if the robot is running two different programs, one in the morning and another in the evening, you could set the variable to copy files into one folder during the morning shift and then into another folder to backup the program files from the evening program. The default value is Project1.
6 System Reference
6.4.2. Controlling WebWare Backup from WebWare.sys Continued ww_BackupRunOK This boolean variable works with RobotWare versions 4.0.60 or later. Using this variable with earlier versions will result in an error. When ww_BackupRunOK is set to TRUE, WebWare Server will run the backup. WebWare Server will not check to see if the robot program is stopped and will not stop the program. When ww_BackupRunOK is set to FALSE, WebWare Server will check to see if the robot program is stopped before running the backup. If the program is stopped, the backup will proceed. NOTE: For S4, this variable works with standard backups. If you have selected to backup only certain programs or program modules, the robot program must be stopped before the backup can proceed. NOTE: For IRC5, this variable works with standard backups and program modules, not programs. ww_HeartBeaton When the ww_HeartBeatOn is set to TRUE, the ww_ LinkState will be checked. NOTE: The HeartBeatOn variable can only be used in overloaded ww_SCWrite method. ww_nRequestType This num variable is used to select if all backups, only master backup or last successful backup are displayed at the teach pendant when receiving backup sets in the restore routine. When ww_nRequestType is set to 1, all backups are displayed. When ww_nRequestType is set to 2, only the master backup is displayed. When ww_nRequestType is set to 4, only the last successful backup is displayed.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
NOTE: The Last Successful Folder Name and Master Backup Folder Name must be configured for the master and last successful backups to be displayed at the teach pendant. For details, see Backup Page on page 107. ww_BackupState This num variable is used by InterLink to update the setting of the backup state throughout the backup procedure. Notice that the backup state changes rapidly and all settings might not be displayed. Before initiating a new backup, you need to verify that the backup state is in IDLE mode. This is to avoid that more that one backup is initiated at a time. When the backup has completed, the backup state will return to IDLE mode. The possible values are listed below. For more information, see Backup State Messages on page 232.
0 = UNKNOWN "Unknown backup state" (1 = NOLICENSE "No license available") 2 = IDLE "Backup idle" 3 = INITIATE "Initializing" 4 = OKCHECK "Checking run permission" 5 = CYCLESTOPCHECK "Checking for cycle stop permission" 6 = WAITFORCYCLESTOP "Waiting for cycle stop" 7 = FULLBACKUP "Full system backup" 8 = PROGRAM "Program backup"
6 System Reference
6.4.2. Controlling WebWare Backup from WebWare.sys Continued
9 = MODULES "Module backup" 10 = SYSPAR "System parameters backup" 11 = LOGFILES "Backup log files" 12 = RAMDISK "Backup local disk contents" 13 = COMMIT "Backup commit to NFS" 14 = INITIATEPUSH "Starting file push to server" 15 = WAITFORPUSHCOMPLETE "Waiting for server file push to complete" 16 = COMPLETE "Backup completed"
ww_BackupResult This num variable is used by InterLink to update the setting of the backup result. ww_BackupResult reflects the result of the latest backup. The possible values are listed below. When interlink is started, the variable is set to UNKNOWN (0). For more information, see Backup Final State Messages on page 233.
0 = UNKNOWN "Backup result unknown" 1 = SUCCESSFUL "Backup successful 2 = ERRORS "Backup completed with errors" 3 = CANCELLED "Backup cancelled" 4 = ABORTED "Backup aborted" 5 = TIMEOUT "Backup timeout" 6 = NOTCONFIGURED "No backup configured" 7 = NOTLICENSED "No license" 8 = NODATACOLLECTOR "DataCollector not responding" 9 = SIMULATED "Cannot backup simulated aliases" 10 = NOALIAS "Alias not configured" 11 = INPROGRESS "Backup in progress" 12 = NOTRUN "Backup not performed" 13 = DATACOLLECTORNOTCONNECTED "DataCollector not Connected"
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
14 = TIMEOUT_INIT "Backup timeout during Init" 15 = TIMEOUT_ROBOT_READY "Backup timeout Waiting Robot" 16 = TIMEOUT_BACKUP "Backup timeout during Backup" 17 = TIMEOUT_NO_CONNECTION "Backup timeout Waiting Connection" 18 = TIMEOUT_AUTO_MODE "Backup timeout Waiting Auto Mode" 19 = TIMEOUT_BACKUP_OK "Backup timeout Waiting Backup OK" 20 = TIMEOUT_CYCLE_STOP_CHECK "Backup timeout Waiting Cycle Stop Check" 21 = TIMEOUT_WAIT_CYCLE_STOP "Backup timeout Waiting for Cycle Stop"
3HAC031359-001 Revision: B
295
6 System Reference
6.4.3. RAPID Instructions
WWStopTimer Instruction on page 313 WWLogTimedEvent Instruction on page 315 WWSetProgramInfo Instruction on page 317 WWSetLabels Instruction on page 318 WWSetField Instruction on page 319
296
3HAC031359-001 Revision: B
6 System Reference
6.4.4. WWRestore Instruction
Standard backups can be loaded back into the robot using the Backup and Restore, Restore menu command. Tasks and Programs can be loaded into the robot using the Program Editor, Tasks and Programs, File, Load Program...menu command. Modules can be loaded into the robot using the Program Editor, Modules, File, Load Module...menu command. Parameters can be loded into the robot using the Control Panel, Configuration, Load Saved Parameters menu command.
Arguments
WWRestore;
Program Execution WWRestore must be run with the robot in Auto mode. If the robot is not in Auto mode, an error screen will be displayed prompting you to switch to Auto mode. This is because the WebWare Server needs to write backup and file set data to the robot. Example A call to the WWRestore instruction can be placed in a RAPID routine.This routine can be called by moving the PP (Program Pointer) to the routine or by calling the WWRestore instruction in your RAPID program.
PROC Restore WWRestore; ENDPROC
6 System Reference
6.4.4. WWRestore Instruction Continued Error Handling When an error occurs while sending data to the WebWare Server, a RAPID ErrWrite command is executed. This displays the error at the robot teach pendant and also records the error into the user error log (S4) or event log (IRC5) for later viewing. The error code is 80001 WWRestore Error. Error getting data from WebWare Server. At this point you should check the WebWare Server to determine the cause for the error, such as loss of the communication link to the robot, failure of the WebWare Server PC or a fault in the network cabling. The bool variable bStopOnSCWrtErr can be used to stop the robot program when an SCWrite error occurs. The default setting is FALSE, in which case the robot program is not stopped. If the variable is set to TRUE, the robot program will stop when an error occurs in any WebWare.sys routine.
298
3HAC031359-001 Revision: B
6 System Reference
6.4.5. WebWare RAPID Restore Procedure
6 System Reference
6.4.5. WebWare RAPID Restore Procedure Continued Restore a Complete Backup Set 1. If you have enabled the WebWare RAPID Restore Password feature, the password screen will be displayed first. Enter the four-digit password and press OK to continue.
xx0500001770
If you have not enabled the WebWare RAPID Restore Password feature, the startup screen is displayed first. Press OK to continue.
xx0500001771
2. A screen with the number of backup sets currently stored on the WebWare Server is displayed. In this example there are 12 backup sets available. Press VIEW to continue.
6 System Reference
6.4.5. WebWare RAPID Restore Procedure Continued
xx0500001772
3. A list of available backup sets stored on the WebWare Server is displayed. Four backup sets are displayed at a time. The first listed backup set is the Master Backup. The second listed backup set is the Last Successful Backup. Each backup set is described with its folder or project name (for Visual SourceSafe) and the backup date and time. When more than four backup sets are available, the PREV and NEXT function keys appear that are used to display the four previous or four next backup sets in the list. Press RESTORE to restore a complete backup set.
xx0500001773
6 System Reference
6.4.5. WebWare RAPID Restore Procedure Continued 4. When you press RESTORE, you are prompted to choose which of the displayed backup sets you want to restore. Press the function key labeled with the number of the backup set you want to restore.
xx0500001774
5. Wait a few minutes while the backup set is transferred to the robot controllers ramdisk. In this example 66 files are transferred.
xx0500001775
6 System Reference
6.4.5. WebWare RAPID Restore Procedure Continued 6. When the restore procedure has completed the following screen is displayed. Press EXIT to leave the WebWare RAPID Restore Procedure. Press BACK to select more backup sets or files to restore.
xx0500001776
7. To complete the restore procedure, load the file into the robot controller. For details, see the robot controller documentation.
6 System Reference
6.4.5. WebWare RAPID Restore Procedure Continued Restore a Single File in a Backup Set 1. If you have enabled the WebWare RAPID Restore Password feature, the password screen will be displayed first. Enter the four-digit password and press OK to continue.
xx0500001770
If you have not enabled the WebWare RAPID Restore Password feature, the startup screen is displayed first. Press OK to continue.
xx0500001771
2. A screen with the number of backup sets currently stored on the WebWare Server is displayed. In this example there are 12 backup sets available. Press VIEW to continue.
6 System Reference
6.4.5. WebWare RAPID Restore Procedure Continued
xx0500001772
3. A list of available backup sets stored on the WebWare Server is displayed. Four backup sets are displayed at a time. The first listed backup set is the Master Backup. The second listed backup set is the Last Successful Backup. Each backup set is described with its folder or project name (for Visual SourceSafe) and the backup date and time. When more than four backup sets are available, the PREV and NEXT function keys appear that are used to display the four previous or four next backup sets in the list. Press VIEW to restore a single file in a backup set.
xx0500001773
6 System Reference
6.4.5. WebWare RAPID Restore Procedure Continued 4. When you press VIEW, you are prompted to choose which of the displayed backup sets you want view the file contents of. Press the function key labeled with the number of the backup set you want to view.
xx0500001777
5. A list of available files in the backup set stored on the WebWare Server is displayed. Four files are displayed at a time. Each file is described with its folder path and filename. When more than four files are available, the PREV and NEXT function keys appear that are used to display the previous or next four files in the list. Press RESTORE to continue.
xx0500001778
6 System Reference
6.4.5. WebWare RAPID Restore Procedure Continued 6. When you press RESTORE, you are prompted to choose which of the displayed files you want to restore. Press the function key labeled with the number of the file you want to restore.
xx0500001779
7. When the restore procedure has completed the following screen is displayed. Press EXIT to leave the WebWare RAPID Restore Procedure. Press BACK to select more files to restore.
xx0500001780
8. To complete the restore procedure, load the file into the robot controller. For details, see the robot controller documentation.
3HAC031359-001 Revision: B
307
6 System Reference
6.4.6. WWStartBackup Instruction
Parameter
username comment
Data Type
string string
Definition
The username of the backup administrator. Backup comment (optional).
Program Execution WWStartBackup must be run with the robot in Auto mode. If the robot is not in Auto mode, an error screen will be displayed prompting you to switch to Auto mode. This is because the WebWare Server needs to write backup and file set data to the robot. Example A call to the WWStartBackup instruction can be placed in a RAPID routine. This routine can be called by moving the PP (Program Pointer) to the routine or by calling the WWStartBackup instruction in your RAPID program.
PROC StartBackup WWStartBackup "username"; ENDPROC
Error Handling When an error occurs while sending data to the WebWare Server, a RAPID ErrWrite command is executed. This displays the error at the robot teach pendant and also records the error into the user error log (S4) or event log (IRC5) for later viewing. The error code is 80001 WWRestore Error. Error getting data from WebWare Server. At this point you should check the WebWare Server to determine the cause for the error, such as loss of the communication link to the robot, failure of the WebWare Server PC or a fault in the network cabling. The bool variable bStopOnSCWrtErr can be used to stop the robot program when an SCWrite error occurs. The default setting is FALSE, in which case the robot program is not stopped. If the variable is set to TRUE, the robot program will stop when an error occurs in any WebWare.sys routine.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
308
3HAC031359-001 Revision: B
6 System Reference
6.4.7. WWIncrCounter Instruction
Parameter
name stepsize
Data Type
string num
Definition
The name of the counter. The value of the increment/decrement.
Remarks The stepsize parameter is treated as an integer, any trailing decimals are truncated. Separate counters are created for each counter name. The counter name is determined by the name parameter passed to the WWIncrCounter instruction. Leading and trailing blanks are not allowed in the name parameter, if any are found they are removed. Empty strings are not allowed for the name parameter, the instruction will stop and display an error if an empty string is found. The first time a new counter name is used, that counter is created and incremented. For example, every hour a new instance of each counter is created, based on the time setting of the PC clock. Thus a particular counter counts for example from 1:00 PM to 1:59 PM, and at 2:00 PM a new instance of the counter is created, with the count restarting at 0.The counter values are stored in the WebWare Server database and can be viewed and queried using the WebWare Server report features. Program Execution When WWIncrCounter is executed the counter named using the name parameter is incremented by the stepsize amount. To decrement a counter, use a negative number for stepsize. Example A procedure call to the WWIncrCounter instruction can be placed in a RAPID routine.
WWIncrCounter "Part Count", 1;
6 System Reference
6.4.7. WWIncrCounter Instruction Continued Error Handling When an error occurs while sending data to the WebWare Server, a RAPID ErrWrite command is executed. This displays the error at the robot teach pendant and also records the error into the user error log (S4) or event log (IRC5) for later viewing. The error code is 80001 WWIncrCounter Error. Error sending data to WebWare Server". At this point you should check the WebWare Server to determine the cause for the error, such as loss of the communication link to the robot, failure of the WebWare Server PC or a fault in the network cabling. The bool variable bStopOnSCWrtErr can be used to stop the robot program when an SCWrite error occurs. The default setting is FALSE, in which case the robot program is not stopped. If the variable is set to TRUE, the robot program will stop when an error occurs in any WebWare.sys routine.
310
3HAC031359-001 Revision: B
6 System Reference
6.4.8. WWStartTimer Instruction
Parameter
name
Data Type
string
Definition
The name of the timer to be started.
Remarks If a non-existent timer name is specified, it will automatically be created in the WebWare Server database. The WWStartTimer instruction always creates a new record in the database as determined by the name parameter. The WWStopTimer instruction never creates a new record, but instead completes the matching WWStartTimer record with the same name. Thus the WWStartTimer and WWStopTimer instructions must be used in pairs, with each pair corresponding to a single database record. The time duration between the WWStartTimer event and the WWStopTimer event is recorded in the database in seconds. Leading and trailing blanks are not allowed for the string name parameter, so if any are found, they are removed. Empty strings are not allowed for the name parameter, the instruction will stop and display an error if an empty string is found. The primary difference between using WWStartTimer/WWStopTimer pairs and the WWLogTimedEvent is the ability to time events that occur under the duration of a second. WWLogTimedEvent has an extra parameter used to give the duration that is stored in the database in milliseconds. The timer values are stored in the WebWare Server database and can be viewed and queried using the WebWare Server report features. Program Execution When WWStartTimer is executed, the timer name is started. Example A call to the WWStartTimer instruction can be placed in a RAPID routine.
WWStartTimer "Cycle Time";
This will start the timer named Cycle Time.WWStartTimer and WWStopTimer are used in pairs. WWStopTimer will stop the timer with the same name started by WWStartTimer, as defined by the name parameter.
WWStopTimer "Cycle Time";
6 System Reference
6.4.8. WWStartTimer Instruction Continued Error Handling When an error occurs while sending data to the WebWare Server, a RAPID ErrWrite command is executed. This displays the error at the robot teach pendant and also records the error into the user error log (S4) or event log (IRC5) for later viewing. The error code is "80001 WWStartTimer Error. Error sending data to WebWare Server." At this point you should check the WebWare Server to determine the cause for the error, such as loss of the communication link to the robot, failure of the WebWare Server PC or a fault in the network cabling. The bool variable bStopOnSCWrtErr can be used to stop the robot program when an error occurs. The default setting is FALSE. If the variable is set to TRUE, the robot program will stop when an error occurs in any WebWare.sys routine.
312
3HAC031359-001 Revision: B
6 System Reference
6.4.9. WWStopTimer Instruction
Parameter
name
Data Type
string
Definition
The name of the timer to be stopped.
Remarks The WWStopTimer instruction never creates a new record, but instead completes the matching WWStartTimer record with the same name. The WWStartTimer instruction always creates a new record in the database as determined by the name parameter. The WWStartTimer and WWStopTimer instructions are expected to be used in pairs, with each pair corresponding to a single database record. The time duration between the WWStartTimer event and the WWStopTimer event is recorded in the database. Leading and trailing blanks are not allowed for the string name parameter, so if any are found, they are removed. Empty strings are not allowed for the name parameter, the instruction will stop and display an error if an empty string is found. The primary difference between using WWStartTimer/WWStopTimer pairs and the WWLogTimedEvent is the ability to time events that occur under the duration of a second. WWLogTimedEvent has an extra parameter used to give the duration that is stored in the database in milliseconds. The timer values are stored in the WebWare Server database and can be viewed and queried using the WebWare Server report features. Program Execution When WWStopTimer name is executed, the timer associated with the name parameter is stopped. Example A procedure call to the WWStopTimer instruction can be placed in a RAPID routine.
WWStartTimer "Cycle Time";
6 System Reference
6.4.9. WWStopTimer Instruction Continued WWStartTimer and WWStopTimer are used in pairs. WWStopTimer will stop the timer with the same name started by WWStartTimer, as defined by the name parameter.
WWStopTimer "Cycle Time";
This will stop the timer named Cycle Time. Error Handling When an error occurs while sending data to the WebWare Server, a RAPID ErrWrite command is executed. This displays the error at the robot teach pendant and also records the error into the user error log (S4) or event log (IRC5) for later viewing. The error code is "80001 WWStopTimer Error. Error sending data to WebWare Server. At this point you should check the WebWare Server to determine the cause for the error, such as loss of the communication link to the robot, failure of the WebWare Server PC or a fault in the network cabling. The bool variable bStopOnSCWrtErr can be used to stop the robot program when an error occurs. The default setting is FALSE, in which case the robot program is not stopped. If the variable is set to TRUE, the robot program will be stopped when an error occurs in any WebWare.sys routine.
314
3HAC031359-001 Revision: B
6 System Reference
6.4.10. WWLogTimedEvent Instruction
Parameter
name duration
Data Type
string num
Definition
The name of the timer to store the timed event in. The duration of the timed event in seconds (with two decimals). Stored in the database in milliseconds.
Remarks The WWLogTimedEvent procedure differs from the WWStart/StopTimer instructions in that the RAPID programmer is assumed to have timed a complete event using the robot controller real-time clock. In this case, the event duration is specified. The event stop-time is assumed to be the time at which the WWLogTimedEvent instruction is called, and the start-time is determined by subtracting the specified duration from the stop-time. A new instance of the timer will be created in the WebWare Server database every time WWLogTimedEvent is called. Leading and trailing blanks are not allowed for the string name parameter, so if any are found, they are removed. Empty strings are not allowed for the name parameter, the instruction will stop and display an error if an empty string is found.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
The num duration parameter is truncated to two decimal places. The primary difference between using WWStartTimer/WWStopTimer pairs and the WWLogTimedEvent is the ability to time events that happen under a second. WWLogTimedEvent has an extra parameter used to give the duration that is stored as Milliseconds in the database. The timer values are stored in the WebWare Server database and can be viewed and queried using the WebWare Server report features. Program Execution When WWLogTimedEvent name is executed, the name timer stores the value supplied in the duration parameter. The event stop-time is assumed to be the time at which the WWLogTimedEvent function is called, and the start-time is determined by subtracting the specified duration from the stop-time.
6 System Reference
6.4.10. WWLogTimedEvent Instruction Continued Example A procedure call to the WWLogTimed instruction can be placed in a RAPID routine. The RAPID clock instructions ClkStart, ClkStop, ClkReset and ClkRead can be used to time the timed event.
ClkStart clock1; ! Routine call to fixture1 production routine fixture1; ClkStop clock1; WWLogTimedEvent "Fixture 1 Cycle Time",ClkRead(clock1); ClkReset clock1;
Error Handling When an error occurs while sending data to the WebWare Server, a RAPID ErrWrite command is executed. This displays the error at the robot teach pendant and also records the error into the user error log (S4) or event log (IRC5) for later viewing. The error code is 80001 WWLogTimedEvent Error. Error sending data to WebWare Server. At this point you should check the WebWare Server to determine the cause for the error, such as loss of the communication link to the robot, failure of the WebWare Server PC or a fault in the network cabling. The bool variable bStopOnSCWrtErr can be used to stop the robot program if an error occurs. The default setting is FALSE, in which case the robot program is not stopped. If the variable is set to TRUE, the robot program will stop when an error occurs in any WebWare.sys routine.
316
3HAC031359-001 Revision: B
6 System Reference
6.4.11. WWSetProgramInfo Instruction
Parameter
author version company description
Data Type
string string string string
Definition
The author of the RAPID program. The version of the RAPID program. The name of the company. A description of the RAPID program.
Remarks Leading and trailing blanks are not allowed for the string author, version, company or description parameters, so if any are found, they are removed. To clear a value or have a blank value simply pass a blank (i.e., empty) string. Program Execution When WWSetProgramInfo is executed the four string parameters are displayed on the WebWare Info General page. Example A procedure call to the WWSetProgramInfo instruction can be placed in a RAPID routine.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Error Handling When an error occurs while sending data to the WebWare Server, a RAPID ErrWrite command is executed. This displays the error at the robot teach pendant and also records the error into the user error log (S4) or event log (IRC5) for later viewing. The error code is 80001 WWSetProgramInfo Error. Error sending data to WebWare Server. At this point, check the WebWare Server to determine the cause for the error, such as loss of the communication link to the robot, failure of the WebWare Server PC or a fault in the network cabling. The bool variable bStopOnSCWrtErr can be used to stop the robot program when an error occurs. The default setting is FALSE, in which case the robot program is not stopped. If the variable is set to TRUE, the robot program will stop when an error occurs in any WebWare.sys routine.
3HAC031359-001 Revision: B
317
6 System Reference
6.4.12. WWSetLabels Instruction
Parameter
label1 label2 label3 label4
Data Type
string string string string
Definition
Text for label 1. Text for label 2. Text for label 3. Text for label 4.
Remarks Leading and trailing blanks are not allowed for the string label1, label2, label3 or label4 parameters, so if any are found, they are removed. Empty strings are allowed. Program Execution When WWSetLabels is executed, the four string parameters are displayed on the User Defined section of the WebWare Info Devices page. Example A procedure call to the WWSetLabels instruction can be placed in a RAPID routine.
WWSetLabels "Production Part 1","Production Part 2","Production Part 3","Production Part 4";
Error Handling When an error occurs while sending data to the WebWare Server, a RAPID ErrWrite command is executed. This displays the error at the robot teach pendant and also records the error into the user error log (S4) or event log (IRC5) for later viewing. The error code is 80001 WWSetLabels Error. Error sending data to WebWare Server. At this point you should check the WebWare Server to determine the cause for the error, such as loss of the communication link to the robot, failure of the WebWare Server PC or a fault in the network cabling. The bool variable bStopOnSCWrtErr can be used to stop the robot program when an error occurs. The default setting is FALSE, in which case the robot program is not stopped. If the variable is set to TRUE, the robot program will stop when an error occurs in any WebWare.sys routine.
318
3HAC031359-001 Revision: B
6 System Reference
6.4.13. WWSetField Instruction
Parameter
fieldnumber value
Data Type
num string
Definition
Defines which of the four fields numbered 1 to 4 will be set. The text for the field.
Remarks Leading and trailing blanks are not allowed for the string value parameter, so if any are found, they are removed. Empty strings are allowed. Program Execution When WWSetField is executed the selected field 1 to 4 is displayed on the User Defined section of WebWare Info Devices page. Example A procedure call to the WWSetField instruction can be placed in a RAPID routine.
WWSetField 1,"Widget 1";
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
Error Handling When an error occurs while sending data to the WebWare Server, a RAPID ErrWrite command is executed. This displays the error at the robot teach pendant and also records the error into the user error log (S4) or event log (IRC5) for later viewing. The error code is 80001 WWSetField Error. Error sending data to WebWare Server. At this point you should check the WebWare Server to determine the cause for the error, such as loss of the communication link to the robot, failure of the WebWare Server PC or a fault in the network cabling. The bool variable bStopOnSCWrtErr can be used to stop the robot program when an error occurs. The default setting is FALSE, in which case the robot program is not stopped. If the variable is set to TRUE, the robot program will stop when an error occurs in any WebWare.sys routine.
3HAC031359-001 Revision: B
319
6 System Reference
6.4.14. WebWare Server Link State Heartbeat Function
Description
WebWare Server interface disabled.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
WebWare Server interface enabled, but InterLink cannot contact the WebWare Server. WebWare Server interface enabled and InterLink is connected to the server.
320
3HAC031359-001 Revision: B
6 System Reference
6.5.1. Return Status Codes
3HAC031359-001 Revision: B
321
6 System Reference
6.5.2. RPC Communications Errors
Remote Errors Not all of the possible RPC errors are included in this table.
6 7 8 9 10 11 12 Rpc versions not compatible. Authentication error. Program not available. Program version mismatched. Procedure unavailable. This usually means that the software loaded in the robot controller does not support the requested method. Decode arguments error. Generic other problem.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
322
3HAC031359-001 Revision: B
6 System Reference
6.5.3. InterLink Module Communication Errors
Description
Unable to contact robot controller. Internal connection error. Variable read error. Variable write error. Internal connection failure due to invalid handle. Spontaneous message support failed. Invalid communications timeout value specified. Program module load error. Program module save error. Program load error. Program save error. Program prep error. Program delete error. Mode set error. Mode get error. Program start error. Program stop error. File open error. File close error. File rename error. File delete error. PC file access error. File read error. File write error. Directory access error. Communications timeout. Module delete error. RAP test read error. Internal error. Blocking call in progress. No reply from RAP server. Protection key access error. Read block error. Read device list error. Restart error.
-16 -17 -18 -19 -20 -21 -22 -23 -24 -25 -26 -27 -28 -29 -30 -31 -32 -33 -34 3HAC031359-001 Revision: B
6 System Reference
6.5.3. InterLink Module Communication Errors Continued Code
-35 -36
Description
Load parameters error. Save parameters error.
324
3HAC031359-001 Revision: B
6 System Reference
6.5.4. General Error Messages
Description
Too many concurrent services (= Max poll 10100). No available communication buffers (= Max poll 10101). Master request rejected (= Max poll 10102). The requested resource is used by another master. Wrong operating mode for requested service. Try again. File not found or could not be opened fro reading (= Max poll 10103). Not right privilege (= Max poll 10104). Wrong program controller id. Wrong operating mode for requested service. Controller is busy. Try again later. Invalid program state (= Max poll 10105). Not right program state for requested service. Operation is illegal in current execution or task state. Invalid program controller state. Not right program controller state for requested service (= Max poll 10106). Cannot find spontaneous message response program in client. The specified port number may be wrong (= Max poll 10107). Too many concurrent connections (= Max poll 10108). No such host defined. The host was not defined in the system parameters or opened with rapgen_open (= Max poll 10109). Initialization not finished. The initialization is not finished. Please retry (= Max poll 10110). Invalid program number or invalid task name. Helper initialized with invalid URL (= Max poll 10111).
-103 -104
-105
-110 -111
3HAC031359-001 Revision: B
325
6 System Reference
6.5.5. InterLink FTP Error Codes
Description
FTP General Failure. FTP Local File Error. FTP Invalid Operation. FTP Login Failure. FTP Invalid Username. FTP Invalid Password. FTP Cannot Connect. FTP Connection Aborted. FTP Connection Reset. FTP Host Not Found. FTP Path Not Found. FTP Timeout. FTP Force Retry. FTP Busy. FTP Path Exists. FTP Bad Logon Parameter. FTP Syntax Error. FTP Host File Error. FTP Network Failure. FTP Not Connected.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
326
3HAC031359-001 Revision: B
6 System Reference
6.5.6. InterLink Error Code Definitions
Description
The robot alias list is full, unable to add new alias. Invalid handle passed to RIM function. Invalid robot id passed to RIM function. InterLink robot interface task is dead. Invalid signal name referenced. Signal name not found in the I/O configuration file. Invalid period referenced in subscription. Unable to locate event in event table. Invalid IO number passed to S4IOCfg. Invalid result spec number. Invalid board number passed to S4IOCfg. Invalid contact type passed to S4IOCfg. Missing IO configuration table. Invalid variable reference. Internal error reading S4 or IRC5 variable. Invalid variable object reference. XData variable data is too large for InterLink to handle. Invalid license encountered/no license found. Invalid alias object reference. Invalid linked alias operation. Invalid S4 array dimensions. Invalid S4 array element size. S4 array memory allocation failed. Invalid index passed to method. Array object data was corrupted. RAPID array object type has not been set. Function is not supported using the specified interface. The InterLink Module is currently disabled, because it hasnt finished initializing the interface. An attempt has been made to access a device managed by InterLink that has not been properly opened or initialized. InterLink request has been aborted. InterLink returns this error when it cannot complete a request. A reference has been made to an invalid or missing Profile. An attempt has been made to delete a Profile that is still being used by an Alias. Use the Device Configuration Utility to determine which Alias definitions are using the Profile. InterLink was unable to delete the specified Profile file.
-518 -519 -520 -521 -522 -523 -524 -525 -526 -527 -528 -529 -530 -531
-532
6 System Reference
6.5.6. InterLink Error Code Definitions Continued Code
-533 -534 -535 -536 -537
Description
An invalid custom database table definition has been received. The table definition parameters are incorrect. An invalid custom database table definition has been received. The table definition does not match the existing custom database table format. An attempt has been made to access a WebWare Server function when the WebWare Serevr interface is not enabled or connected. An internal InterLink error has been detected. Contact ABB Customer Service with the details. Returned or invalid variable objects. Unspecified error creating a custom table. WebWare Server reports this error. Possible causes are incorrect server configuration, directory access permission settings, or disk full. Unspecified error writing to a custom table. WebWare Server reports this error. Possible causes are incorrect server configuration, directory access permission settings, or disk full. InterLink detected a file access error while performing a file operation. The file is read-only. Command is not Asynchronous (USED by FWEB_ISAPI and StateManager). The Plant Model is already checked out. Create failed, name already exists and is in use. Function timeout/did not complete. Cannot read the System.DIR file (for S4C+). Unable to communicate with web site/ISAPI error. Error communicating with ABB WebWare Service. Error communicating from WWService to Data Collector. Error accessing Visual SourceSafe. Error accessing the WebWare Data Engine. Undefined Error was returned from the robot. Invalid restart mode. An invalid restart mode has been specified in the rapgen_restart command.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
-538
-539 -540 -541 -542 -543 -544 -545 -546 -547 -548 -549 -550 -600
328
3HAC031359-001 Revision: B
6 System Reference
6.5.7. InterLink Monitor Connecting Failure
Description
S4SubReset S4SubLog S4SubSCWrite S4CtlVersionGet S4CtlIdGet S4PageDelete S4FileDevices VarPage.RemoveAll BuildIOPollList BuildpageDefinition S4BIOFCloseAll ResetSISPolling ReadCurrentSystemName See S4 InterLink Monitor max poll on page 329.
Description
Unknown host Unable to contact controller Unable to contact controller Too many connections (>256) If the max poll exceeds 10000, subtract it from 10000 to get the error code, and then see General Error Messages on page 325.
2 4 5 6 >10000
Description
No response IRC5CONFAIL_BADNETSCAN IRC5CONFAIL_CLIENTREG IRC5CONFAIL_BADUAS IRC5CONFAIL_CTRLINIT IRC5CONFAIL_NOPCINTERFACE IRC5CONFAIL_ENVVARINIT IRC5CONFAIL_CTLVERGET IRC5CONFAIL_CTLIDGET
6 System Reference
6.5.7. InterLink Monitor Connecting Failure Continued Code
9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
Description
IRC5CONFAIL_ROBDATAINIT IRC5CONFAIL_ROBRAPIDINIT IRC5CONFAIL_INITTASKLIST IRC5CONFAIL_ROBRAPIDTASKINIT IRC5CONFAIL_IOSYSTEMINIT IRC5CONFAIL_IOSIGNALINIT IRC5CONFAIL_IOSIGNALSUB IRC5CONFAIL_RAPIDNAMESPACEINIT IRC5CONFAIL_ROBFILEBROWSERINIT IRC5CONFAIL_ROBEVENTLOGINIT IRC5CONFAIL_ELOGTEXTINIT IRC5CONFAIL_GETLASTLOGNUM IRC5CONFAIL_GETLASTLOGNUM2 IRC5CONFAIL_GETDEVICELIST IRC5CONFAIL_LIMITREACHED *) IRC5CONFAIL_ALREADYLOGGEDON IRC5CONFAIL_VERSIONNOTSUPPORTED
*) There is a limit of number of clients accessing an IRC5 controller. This means that a RobotStudio or OPC connection can block the access of InterLink. The maximum number of connected network clients using RobAPI is three on the LAN port and one on the service port. The total number of concurrent connected FTP clients is four.
330
3HAC031359-001 Revision: B
6 System Reference
6.5.8. Variable Handling Error Messages
Description
No program to store. Invalid program controller state. Invalid program state. Invalid controller state. Invalid operating state not in Auto mode. Too many concurrent variable services. Invalid variable name, or invalid domain. Invalid type name, or invalid domain. Missing the work or tool frame definition. Invalid domain number. Invalid transfer type number. Invalid subscribe parameters. Invalid cancel parameters. Mastership request rejected - requests mastership RAPID domain. The parameter value is too large. Invalid system state. Invalid write parameters. Write request was sent to the controller, but the controller returned an error. Invalid signal name. Invalid value. Invalid parameter. Too many subscriptions. Invalid subscription log group. Clockdata does not correspond to a valid date and time. The system clock could not be read. The system clock could not be written. Variable and type mismatch. The variable exists but is not of the specified type. Variable not persistent. The variable exists but is not persistent. Illegal dimension. The specified dimension must be in the range 0 to 3. Illegal array index. Array index must be larger than 0, and the second index must be larger than the first. Array index out of bounds. Array index not within the bounds defined for the array. Array size violation. The requested array size is too large to be handled in one call. Divide the array into smaller parts and read or write them with more than one call. Dimension violation. The array dimension of the requested variable does not correspond to the request parameters.
-1130
6 System Reference
6.5.8. Variable Handling Error Messages Continued Code
-1131 -1132 -1133 -1134 -1135 -1136 -1137 -1138 -1139 -1140 -1141
Description
Variable is not an array. The requested variable is not an array. Variable is an array. The requested variable is an array. Illegal structure. The XData structure does not correspond to the structure of the requested data type. Too many page descriptions. The maximum number of page descriptions has already been used. Non-existing page definition. No page definitions with the specified number exists. Illegal page definition number. The specified page definition number is either larger than the maximum number of page definitions or smaller than 1. Illegal number of page elements. The number of page elements is either larger than the maximum number of page elements or less than 1. Illegal variable type for page. The specified variable type is not possible to read or write in a page. Invalid domain for arrays. Variables in the specified domain cannot be arrays. Arrays can only exist in the RAPID domain. The variable can not be written. This variable is read-only. The variable can not be read. This variable is write-only.
332
3HAC031359-001 Revision: B
6 System Reference
6.5.9. Program Handling Error Messages
Description
Invalid module. Operation completed but with syntax error(s). The filename does not comply to the ISO-8859-1 (ISO-Latin-1) encoding. Module is read proteced. Invalid module name. RAPID symbol was not found. Ambiguous module name. Invalid program. Invalid run mode. Invalid stop mode. Invalid procedure name. Invalid parameters. Helper initialized with invalid URL. Unable to initiate the helper for the specified task/invalid pgmId value. No program deleted. Robot not on path. The robot is not on the path. To regain path answer the dialog on the teach pendant. Start the program from the teach pendant. Break during start order. The robot was stopped during path regain.
3HAC031359-001 Revision: B
333
6 System Reference
6.5.10. File Handling Error Messages
Description
General file handling error. Too many files open. No such path or too long file name (8.3). Write error. Device full. The RAPID heap memory is full. Error when opening device. Invalid file descriptor. End of file. Invalid open flags. Illegal access mode. File exists. RAPFIL_RENAME returns this error code if a file with the new file name exists. Directory exist. Directory not empty. Directory does not exist. Service is not supported. The service is not supported in this version of the controller.
334
3HAC031359-001 Revision: B
6 System Reference
6.5.11. Configuration Handling Error Messages
Description
General configuration handling error. Invalid topic. Unable to open file for writing. Invalid path name. Topic name invalid. Wrong operating mode. The robot must be in auto mode when loading and saving parameters. Version too old. The version of the parameter file on the disk is too old. Invalid type. A type name in the parameter file is invalid. Input error. Error in input file or file not found. Line error. The length of a line in the parameter file is longer than 80 characters. Range error. An input value in the parameter file is out of range. Duplicate parameter name. Two or more parameters in the input file has the same name. Invalid load mode. The load mode is invalid. Invalid attribute. The name of a parameter attribute is invalid.
3HAC031359-001 Revision: B
335
6 System Reference
6.5.12. Log Error Messages
Description
Invalid log type. Valid log types are 0-14. Values outside of this range are rejected. The log cant be read. Cant open file. There was an error creating the temporary file. Can't write log. Empty log. Backup error. The directory does not exist. At least one module name is too long. Tree structure cannot be created. Error saving or reading config file. The structure is to deep. The directory contains items that are to be created. Error while writing to backinfo file. Restore error. The directory does not exist. The backup system is not correct. The backup directory is not a completed backup. The structure is too deep. The backinfo file cannot be opened. Loading of a module failed. Some configuration error. Too long file name. The restore service is not supported since the option is missing. General error for log.
-5107
Description
Invalid log type. Valid log types are 0-14. Values outside of this range are rejected. The log cant be read. Cant open file. There was an error creating the temporary file. Empty log.
6 System Reference
6.5.12. Log Error Messages Continued Code
-5105
Description
Backup error. The directory does not exist. At least one module name is too long. Tree structure cannot be created. Error saving or reading config file. The structure is to deep. The directory contains items that are to be created. Error while writing to backinfo file. Restore error. The directory does not exist. The backup system is not correct. The backup directory is not a completed backup. The structure is to deep. The backinfo file cannot be opened. Loading of a module failed. Some configuration error. Too long file name. General error for log. The restore service is not supported since the option is missing. Cant write to log file.
-5106
3HAC031359-001 Revision: B
337
6 System Reference
6.6. WebWare Server Error Codes
Description
Incorrect number of parameters sent to %. Invalid counter name sent to IncrCounter. Invalid timer name sent to StartTimer. Invalid timer name sent to StopTimer. Invalid timer name sent to LogTimedEvent. Invalid timer duration sent to LogTimedEvent. Failed to create WebWare table. Incorrect SCWrite type definition variable. Failed to create WebWare table. Invalid field name SCWrite definition. Failed to create WebWare table. Unable to access table status variable. Table write request failed. Invalid record data received.
WebWare Service Command Error The following error codes originate in WWServer: Code
15013 15014 15015 15015 15015 15015 15015 15015
Description
DC COM pointer invalid. HR=%x. DC disconnected due to heartbeat timeout. EndTime parameter is NULL or invalid. StartTime of %s is later then EndTime of %s. CWWTimerRs::TimerRecordUpdate(TimerKey) Error number: 0x%x %s. %s : %s. Timer %s with start time of %s has been removed by update timer.
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
338
3HAC031359-001 Revision: B
6 System Reference
6.7.1. RS-232 Cable Diagrams
Technical Name
DCD RXD (RD) TXD (TD) DTR SG (0V) DSR RTS CTS
Connect to
Pin 4 and 6 TXD (robot side) RXD (robot side) Pin 1 and 6 0V (robot side) Pin 1 and 4 Pin 8 Pin 7
Technical Name
TXD (TD) RXD (RD) RTS CTS DSR 0V DCD DTR
Connect to
RXD (robot side) TXD (robot side) Pin 5 Pin 4 Pin 8 and 20 0V (robot side) Pin 6 and 20 Pin 6 and 8
6 7 8 20
Robot Side Connections Pin number, depending on connector (see Product Manual). Pin
See product manual. See product manual. See product manual. See product manual. See product manual. See product manual.
Technical Name
TXD RXD CTS RTS DTR DSR
Connect to
RXD on PC side TXD on PC side RTS (robot side) CTS (robot side) DSR (robot side) DTR (robot side)
6 System Reference
6.7.1. RS-232 Cable Diagrams Continued Diagram The diagram below is an illustration of one example of the connections required if you need to build a cable on site.
xx0500001781
340
3HAC031359-001 Revision: B
6 System Reference
6.7.2. S4 Controller Diagrams
xx0500001782
9-Pin PC Port
xx0500001783
6 System Reference
6.7.2. S4 Controller Diagrams Continued S4C XB1 Connector Shown below are wiring diagrams for standard 25-pin and 9-pin RS-232 connectors. The diagrams shown are for attaching to sio1: in the S4C controller (XB1 connector). 25-Pin PC Port
xx0500001784
9-Pin PC Port
xx0500001785
6 System Reference
6.7.2. S4 Controller Diagrams Continued S4C X1 Connector Shown below are the wiring diagrams for standard 25-pin and 9-pin RS-232 connectors. The diagrams shown are for attaching to sio1: in the S4C controller (X1 connector). 25-Pin PC Port
xx0500001786
9-Pin PC Port
xx0500001787
3HAC031359-001 Revision: B
343
6 System Reference
6.8.1. Overview
6.8 Installing WebWare Server with RobotStudio, QuickTeach or ProgramMaker 6.8.1. Overview
Introduction To run WebWare Server on the same computer together with RobotStudio, QuickTeach or ProgramMaker, you must run InterLink as a server or else communication will fail. By default, InterLink is installed as a service. The following procedure will guide you to successfully run WebWare Server on a computer with RobotStudio, QuickTeach or ProgramMaker. NOTE: The applications need to be installed in the order specified, or you will receive error messages when using the applications. Procedure 1. Log in with local administrator rights. Close all applications. 2. Install RobotStudio, QuickTeach or ProgramMaker. NOTE: Read the Release Notes located on the installation CD for RobotStudio, QuickTeach or ProgramMaker before you begin the installation. 3. Install WebWare Server: In the Ready to Install the Program dialog, select Use this PC as a Data Collector in a WebWare Network. Select Install Support for S4/IRC5 Controllers (as appropriate). Click Install.
4. Register InterLink as a server: A. Open a Windows Command Prompt. Click Start, then Run... and type cmd. B. Change directory to: C:\Program Files\Common Files\ABB
Automation\InterLink
Copyright 1999-2006, 2008-2009 ABB. All rights reserved.
C. At the prompt type: interlink -unregServer D. At the prompt type: interlink -regServer 5. Now you should be able to run WebWare Server with RobotStudio, QuickTeach or ProgramMaker.
344
3HAC031359-001 Revision: B