Software Design

Document
for
Robotic automation for button
functionality
Contents
1. Introduction.........................................................................................................................................2
2. Problem statement..............................................................................................................................2
3. Solution...............................................................................................................................................2
4. Detailed System Design.......................................................................................................................3
4.1. Responsibilities............................................................................................................................3
4.2. Composition.................................................................................................................................3
4.3. Uses/Interactions.........................................................................................................................4
Flow Chart...............................................................................................................................................5
5. Conclusion...........................................................................................................................................6
 1. Introduction

Device testing is one of the fundamental requirements to ensure product quality. Manual
testing practices demand the operator to be attentive and execute the repetitive testing
procedure. It makes the operator lose interest due to the monotonic nature of testing routines.
A change in firmware and product up gradation also demands testing at the development stage.
This degrades the testing quality and can severely affect the brand reputation of the company.
Hence, it is vital to execute the testing procedure with the same level of precision all the time.

Robotic systems can provide promising solutions to these problems associated with device
testing. A robot arm connected with a finger-like end-effecter can imitate the operator’s action
to interact with the devices. Being a précised machine, robots can operate and execute testing
procedures at a consistent level of precision. However, the robot is electro-mechanical
hardware whose efficiency can be evaluated only after deployment. Hence, the industries are
reluctant to adapt to robot-based DUT testing

2. Problem statement

Longer on boarding time – The design of automated robot-based DUT testing is a series process
where the software development starts after the robot installation. This increases the
deployment process and other testing procedures. The robot calibration required for
coordinated transformation can only be performed after installations.

ROI estimation – Besides installation cost, the ROI depends on run-time parameters such as
execution time, quality of testing, and movement space requirements. Assessment of the
testing quality can be carried only after the deployment of such robotic solutions.

Choice of the robot – Any change of other robot deployment incurs intense rework and
installation cost. Analysis of the best suitable robot to operate the DUT and optimize the space
requirement is highly demanding.

Testing visualization and robot collision – Visualization of the robot at work is always possible
only after deployment. Robot self and environmental collision can be examined at this stage.

3. Solution

A possible solution for the problem stated before would be a robotic arm. Robotic arms are
widely used for different purposes such as facial recognition, object tracking, image capture
systems, pick and place, etc. A robotic arm can be easily adapted for specific needs by adding
some extra functionality on the end effecter which makes it a perfect tool for universal testing.
The Dobot Magician was chosen for this task. This 4 DoF robotic arm can perform movements
using 4 different axes and is therefore especially flexible. It supports different possibilities on
how to control it. It also includes different approaches of grippers and it is also possible to
design.
The hardware configuration is the base of our work since all written software depends on it.
The robotic arm should be placed on a platform which can be transported easily without the
need to disassemble anything. The platform should provide the possibility to hide and organize
loose cables and should be easily modifiable.
Next up we describe the needed software for the robot. On the lowest level, the robotic arm
uses python script to receive commands and execute them. The robotic arm also provides an
API which can be used to send commands to the robot which translates those into messages.
After the co-ordinates of button are given the robot slowly approaches to goal step by step.

4. Detailed System Design

4.1. Responsibilities

The main responsibility of Mission Planning is to utilize robotic arm to automate the button
functionality test so that it can perform the tasks provided to it.

4.2. Composition
A suitable Graphic User Interface (GUI) was built to enable the robot operator input the desired
control parameters with ease.

Figure 4.1. GUI screen

 4.3. Uses/Interactions

The algorithm used to control the robot parameters are written in a python code that computes:
 Position the robot's end effecter to the home coordinates specified by the user.
 Specifies the desired 'functional' position by inputting the desired coordinates of the
button for the end-effecter for the 'functionality'.
 The user then clicks the 'START' button to commence task.
 On clicking the button, the angle through which each joint will rotate in order to
position the end-effecter at the specified point coordinate.
 After pushing a button, the end effecter rests on it for a brief period of time to
guarantee the button's operation.
 The same procedure is repeated for the different button position.
 Inputs the number of functionality cycles.
 sets the desired velocity and acceleration
 The user can click the emergency button when there is any error in robot motion and
can click ‘Stop’ button if pause in operation required.
Flow Chart
START

NO
Connecti
Display Error
on
Status
YES

Home position xyz

Button 1 Button 2

Pos 1 Pos
Display error Display error
1

Hold for 5sec Hold for 5sec

Pos 2 Pos
Display error Display error
2

Hold for 5sec Hold for 5sec

Pos 3 Display error Pos

Display error
3

Hold for 5sec Hold for 5sec

STOP
 5. Conclusion

The robotic arm is electro-mechanical hardware, which can be controlled by software to

achieve the desired motion/task. Deployment of such robotic hardware for DUT testing
automation consumes a higher installation cost and demands accurate ROI estimation. Using a
robotic arm can address the problem associated with the robotic solution development for
automated DUT testing. It allows the development of software architecture and wide range of
DUT versions often requires reworking on mechanical fixtures and automation scripts.