Robotic device tester

Patent metadata

Field	Value
Publication number	US-10144133-B2
Application number	US-201715788660-A
Country	US
Kind code	B2
Filing date	Oct 19, 2017
Priority date	Apr 18, 2008
Publication date	Dec 4, 2018
Grant date	Dec 4, 2018

Abstract

A system, method, and device may include software and hardware which simplify and quicken configuration of the system for testing a device, enhance testing procedures which may be performed, and provide data via which to easily discern a cause and nature of an error which may result during testing. A camera may capture still images of a display screen of a tested device and another camera may capture video images of the tested device and a partner device. A wizard may be used to generate a configuration file based on one previously generated for a similar device. A mount for a tested device may be structured so that: it is suitable for mounting thereon a plurality of differently structured devices; and adjustments in a vertical direction and a horizontal direction in a plane and adjustments of an angle of the device relative to the plane may be easily made.

First claim

What is claimed is:

1. A device testing system, comprising:
one or more processors;
a memory storing a plurality of screenshots associated with a display screen of a first device;
a platform;
a first camera arranged such that an axis that extends through a lens of the first camera extends approximately perpendicularly towards the platform such that at least a portion of the platform is within a field of view of the first camera;
a robotic arm; and
instructions stored on the memory that, when executed by the processor, cause the system to:
cause the first camera to transmit a captured image to the processor;
cause the robotic arm to operate the first device when the first device is arranged on the platform;
compare images received from the first camera during the operation of the first device with the stored plurality of screenshots;
determine that an error has occurred if compared images do not match; and
store in the memory at least one of the images associated with the error.

2. The device testing system of claim 1 , further comprising:
a force sensor configured to sense a force generated by the robotic arm;
wherein:
the processor is configured to generate a configuration file in accordance with which the operation of the first device is performed, the generation of the configuration file including, for at least a subset of a plurality of buttons of the first device:
extending the robotic arm in a direction perpendicular to a face of the button until a predetermined force value is sensed by the force sensor; and
recording in the configuration file a coordinate of a position of the robotic arm along an axis extending perpendicularly to the face of the button;
the operation of the first device includes manipulation of each of at least one of the subset of buttons sufficient to cause generation in the first device of a respective signal identifying the manipulation of the respective button; and
for each of the at least one of the subset of buttons, the manipulation is performed by extending the robotic arm based on the configuration file in the direction perpendicular to the face of the respective button until a position of the robotic arm corresponds to the coordinate recorded in the configuration file for the respective button.

3. The device testing system of claim 1 , further comprising:
a mini-workstation that includes a camera arrangement, a processor, and a platform underneath the camera arrangement, the mini-workstation not including a robotic arm via which the first device is operable;
wherein:
the operation of the first device is in accordance with one or more configuration files associated with the first device; the one or more configuration files include the screenshots of the display screen to which the captured images are compared during the operation of the first device; and
at least a portion of the one or more configuration files is generated by capturing the screenshots using the camera arrangement of the mini-workstation.

4. A device testing method, comprising:
operating, with a robotic arm, a first device having a touch-sensitive display screen according to stored test sequences;
capturing images of the touch-sensitive display screen using a first camera;
comparing, in a first comparison step, the captured images with stored screenshots associated with the first device;
determining that an error has occurred based on the comparison; and
storing, in a memory, at least one captured image associated with the error.

5. The device testing method of claim 4 , further comprising:
locating a code region within an image that is captured by the camera in whose field of view is the first device;
processing the code region to obtain a code encoded in the code region; and
obtaining a configuration file based on an association of the code with the configuration file;
wherein the operation of the first device is in accordance with the configuration file.

6. The device testing method of claim 5 , wherein the code is a barcode.

7. The device testing method of claim 4 , further comprising:
detecting a position of the display screen with respect to a field of view of the first camera, the comparing step being performed in accordance with the detected position.

8. The device testing method of claim 5 , further comprising:
a processor automatically operating a light fixture to produce light, during the step of locating the code region, at a first level;
subsequent to the step of locating the code, the processor automatically operating the light fixture such that the light fixture does not produce light during the step of detecting a position of the display screen; and
subsequent to the step of detecting the position of the display screen, the processor automatically operating the light fixture to produce light, during the steps of capturing the images, at a second level.

9. The device testing method of claim 4 , further comprising:
generating a configuration file in accordance with which the operation of the first device is performed, the generation of the configuration file including, for at least a subset of a plurality of buttons:
extending a robotic arm in a direction perpendicular to a face of the button, until a predetermined force value is sensed by a force sensor; and
recording in the configuration file a coordinate of a position of the robotic arm along an axis extending perpendicularly to the face of the button;
wherein:
the operation of the first device is performed via the robotic arm and includes manipulation of each of at least one of the subset of buttons sufficient to cause generation in the first device of a respective signal identifying the manipulation of the respective button; and
for each of the at least one of the subset of buttons, the manipulation is performed by extending the robotic arm based on the configuration file in the direction perpendicular to the face of the respective button until a position of the robotic arm corresponds to the coordinate recorded in the configuration file for the respective button.

10. The device testing method of claim 4 , further comprising:
generating a first-device-configuration-file in accordance with which the operation of the first device is performed, the generation of the first-device-configuration-file including:
retrieving a second-device-configuration-file associated with a second device similar to the first device;
storing a copy of the second-device-configuration-file as the first-device-configuration-file; and
updating the first-device-configuration-file to reflect received user input identifying differences between the first device and second device.

11. The device testing method of claim 10 , wherein the generation further includes:
in response to receipt of user input describing features of the first device, determining that the second device is similar to the first device, wherein the second-device-configuration-file is retrieved responsive to the determination of a similarity between the first and second devices.

12. The device testing method of claim 10 , wherein the second-device-configuration-file is retrieved responsive to user input selecting the second-device-configuration-file.

13. The device testing method of claim 4 , further comprising:
generating a configuration file in accordance with which the operation of the first device is performed, the generation of the configuration file including, in accordance with a file identifying a plurality of test tasks, for each identified test task:
outputting a prompt for information identifying a respective set of device operation sequences usable to perform the

Assignees

• T Mobile Usa Inc

Inventors

• Jenkinson David Ross
• Lee Bobby
• Liaw Gavin

Classifications

• B25J11/00

  Manipulators not otherwise provided for · CPC title

• H04M1/24

  Arrangements for testing · CPC title

• Y10S901/47

  Optical · CPC title

• Y10S901/02

  Arm motion controller · CPC title

• G01R31/01 Primary

  Subjecting similar articles in turn to test, e.g. "go/no-go" tests in mass production; Testing objects at points as they pass through a testing station (testing of cables continuously passing the testing apparatus G01R31/59; testing dielectric strength or breakdown voltage G01R31/12) · CPC title