Remote FlexPendant Tester - IDT

We reserve all rights in this document and in the information contained therein. Reproduction, use or disclosure to third parties without express authority is strictly forbidden.
© ABB Automation Technology Products, Robotics; 2007
CONTENTS
Type des. Part no.
Prep. Olof Kjellgren Doc. kind No. of p.
Appr.
Resp. dept. RCI
Remote FlexPendant Tester
1. INTRODUCTION ....................................................................................................... 2
1.1 Purpose........................................................................................................ 2
1.2 Definitions .................................................................................................... 2
1.3 Equipment.................................................................................................... 2
2. Installation and setup .............................................................................................. 3
3. FlexPendant TestMaker........................................................................................... 5
3.1 Overview of the GUI..................................................................................... 5
3.2 Detailed Description ..................................................................................... 6
3.2.1 Controls.......................................................................................... 6
3.2.2 Test ................................................................................................ 6
3.2.3 Settings .......................................................................................... 6
3.2.4 Actions............................................................................................ 6
3.2.5 Testcase treeview........................................................................... 6
3.2.6 Tips and Tricks ............................................................................... 6
4. FlexPendant RobotTester........................................................................................ 8
4.1 Overview of the GUI..................................................................................... 8
4.2 Detailed description...................................................................................... 9
4.2.1 Run Section.................................................................................... 9
4.2.2 Execution Section........................................................................... 9
4.2.3 Settings Section.............................................................................. 9
4.2.4 Tips and Tricks ............................................................................... 9
ABB Automation Technology Products
BAU Robotics
Title Remote FlexPendant Tester
Doc. no. Lang. Rev. ind. Page
! " #$ % # & ' % % ( # ! ) * ( ! $ * + , -. / -0 / / 1 2 / 3 4 / / %
W
0.1
1

1. INTRODUCTION
1.1 Purpose
1.2 Definitions
1.3 Equipment
The purpose of this document is to describe how to setup tests for the FlexPendant run by
remote control.
Word Description
FP FlexPendant
RSO Robot Studio Online
GUI Graphical User Interface
TestMaker Program to record tests
RemoteTester Program to replay tests
• Test Rack
• FlexPendant
• Computer with 2 network cards
ABB Automation Technology Products
BAU Robotics
Doc. no. Lang. Rev. ind. Page
2

2. Installation and setup
Follow these steps to install and set up the testing system.
1. Connections
The Computer running the tests must be able to communicate directly with the FP. Set up
a switch and configure the second network card to have the IP address 192.168.126.x
(where x = 2 – 253) and subnet mask 255.255.255.0.
2. FlexPendant logging
The FlexPendant sends information, e.g., when error occurs. This information can be
displayed using a tool called nclog. The program (nc.exe) is located at
S:\Product Development\DevelopmentProjects\GTPU\Tools\netcat
In the command window, write “nc –lup 9998”. It is recommended to have the nclog
running from this point on.
3. Verify connection
Power on the Test Rack and verify that it is possible to get in contact with the FP by using
“ping 192.168.126.10” from a command window.
4. FTP Server
Install and configure the FTP server. There is a Free-ware FTP Server, zFTPServer
available at http://www.zftpserver.com/.
It is possible to use any FTP server.
Create the following usergroup:
Name: FPTest
Home directory: c:\temp\FPTests
File rights: All
ABB Automation Technology Products
BAU Robotics
Doc. no. Lang. Rev. ind. Page
3

Folder rights: Read, +subfolders
Create the following user belonging to FPTest
Name: ps
Password: ps
5. FlexPendant Viewer
Install the FlexPendant Viewer from
Z:\integration\rel5_xx\mmi\BuildLib\Tools\FlexPendant Viewer
6. Naming the Controller
Set name of the controller to “RemoteTest”.
This is because images are compared by the FlexPendant and the controller name is
always displayed.
This can be done in RSO. Add the Controller. Press Controller->Properties->Rename.
You need Write Access to be able to do this.
7. Install software
Install the RobotWare.
8. Create a System
Create a new system using RSO.
Set name of the system to “SystemRemoteTest”. This is because images are compared of
the FlexPendant and the system name is always displayed.
9. Start FTP Server
Start the FTP Server if it is not running.
10. Start FlexPendant Viewer
Start the FlexPendant Viewer if it is not running. This application will make it possible to
remotely control the FlexPendant.
ABB Automation Technology Products
BAU Robotics
Doc. no. Lang. Rev. ind. Page
4

3. FlexPendant TestMaker
3.1 Overview of the GUI.
Start/Stop capturing
coordinates and
Save Test.
Test Name and
Folder to save tests
into.
Current test. Test is
not affected if you
enter or delete text
directly into it.
ABB Automation Technology Products
BAU Robotics
Clear: Deletes all
actions and begin
from scratch.
Reload: update
test folder
Commands for
tests.
Snap: captures
image
Restart: restarts
FP only
Wait: holds tests
for X seconds.
Include Test: call
another test.
Always snap:
Automatically
snaps image after
each click after 8
seconds. Use
carefully!
Under
\ABB
or
\Quick
Set it is possible to
collect small
testactions which
can be included
into another test.
This makes test
creation much
more rapid. These
tests show up
here.
Doc. no. Lang. Rev. ind. Page
5

3.2 Detailed Description
3.2.1 Controls
• Start: Starts the mouse capturing functionality. The “Pos:”-label will start to update with screen
coordinates.
When this is active, only press on the RemoteDisplay window of the FP to save action as a click.
This click will also update the FP normally.
• Stop: Stops mouse capturing.
• Save: Saves all actions so far to the given path with the given filename.
3.2.2 Test
• New Test: This button sets up all folders necessary for the test in the folder.
• Folder: This sets up the folder. Under this all created tests will be saved.
3.2.3 Settings
• Computer IP: Select which IP the network card has, that is connected to the FP net.
3.2.4 Actions
These instruction are available from the Test-script language of Remote FlexPendant Tester.
• Snap: Takes a snapshot from the FP. The command is sent via socket communication to the FP
which uploads the image to an FTP on the computer. An FTP-Server has to be installed to use
this feature.
• Restart FP: Orders a restart from the FP. The command is sent via socket communication to the
FP.
• Wait Xs: Orders system to wait. Useful after example ordering a restart or after clicking on a view
that takes a substantial amount of time to open.
• Include test: Executes a whole other test as an instruction. Useful to build test hierarchies with
low level test scripts that combines into high level test scripts.
3.2.5 Testcase treeview
The testcase treeview (the view to the right on the testmaker) is a library of tests that the user can
create. These tests are loaded from the ‘ABB’ and ‘QuickSet’ subfolders under the .
3.2.6 Tips and Tricks
A recommended way to create tests is first to create a new subfolder under called
‘LowLevelTests’ or something similar. Then create several tests that contain only one click. For example
“ClickABB-Button” or “ClickJoggingView” etc. Then create a new test called OpenJoggingView that
includes these two tests and place it under \ABB\Jogging. This test it not meant to be run
itself, but as a ‘medium level’ test. Combining several medium level tests and adding images
comparisons and the other functions can make a base for very rapid and powerful test creations that are
also robust. If a button in the FP GUI were to change place, all you have to do is replace the low level
test that press that button and all tests pressing the button will work again.
ABB Automation Technology Products
BAU Robotics
Doc. no. Lang. Rev. ind. Page
6

To create reliable tests, it’s important that each test “cleans up” after itself (undo all actions), so each test
will start with system in the same state. Otherwise all test cases have to be run in a specific order to be
successful, and any failed tests will probably make all following tests fail as well.
The following picture illustrates how test cases can be built up. For example, if the ABB-button changes
location on the touch screen, only the pressABBButton test case needs to be changed for all tests
pressing that button to work.
ABB Automation Technology Products
BAU Robotics
Doc. no. Lang. Rev. ind. Page
7

Reloads list.
List of availble
test cases.
Button for
stopping
execution.
Debug
information.
4. FlexPendant RobotTester
4.1 Overview of the GUI
ABB Automation Technology Products
BAU Robotics
Adds tests to
be run.
Clears list.
Buttons for
running tests.
Controller IP. Computer IP. Extra
Where
waittime
before next
instrucition.
Default = 5.
tests are to
be saved.
Tests
selected
for
execution
Failed tests
end up
here.
Doc. no. Lang. Rev. ind. Page
8

4.2 Detailed description
4.2.1 Run Section
• Reload: Unloads and loads the list of available test cases.
• Add: Add test to execution list.
• Clear: Clears execution list.
• Run All Once: Runs all tests in execution list one time from top to bottom.
• Run All, Loop Last: Runs all tests in execution list one time from top to bottom until last test which
it repeats infinitely.
4.2.2 Execution Section
• Stop: Stops execution of tests. Will stop after current test has finished executing.
• Debug windows: The left window displays debug information about the tests if something has
failed.
The right window displays failed tests, if there are any.
4.2.3 Settings Section
• Controller: IP address to Controller which will press the screen.
• This Computer. IP address to the computer running the program.
• Windows: test folder defines the path to the test folder.
• Execution: Seconds to wait between actions defines extra time to wait after a test has been
completed.
4.2.4 Tips and Tricks
If regular tests are performed, just select the tests you want to run and click ‘Run All Once’-button. Then
watch the execution section to see if any tests failed or not.
If you want to stress the system in any way, i.e. look for memory leakage, it sometimes can be useful to
use the ‘Run All, Loop Last’-button. The first test can be to open a specific view or put the system in a
specific state before the last test loops over and over again.
You can display the FP memory by typing: fpcmd “-memShow” in a console window. Typing fpcmd “memShow
–h” displays possible switches in the nclog (see section 3.2) window.
To follow this information over time you can spawn a task on the controller that repeats this command.
To do this type: period 1,fpcmd,”-memShow”. 1 is the time interval in seconds, fpcmd is the function
followed by the parameter “-memShow”.
ABB Automation Technology Products
BAU Robotics
Doc. no. Lang. Rev. ind. Page
9

REVISION
Rev.
ind.
Page (P)
Chapt.(C)
Description Date
Dept./Init.
W 0.1 Initial version 2007-05-
04/olkje
ABB Automation Technology Products
BAU Robotics
Doc. no. Lang. Rev. ind. Page
10