## For instruction on writing tutorials
## http://www.ros.org/wiki/WritingTutorials
####################################
##FILL ME IN
####################################
## for a custom note with links:
## note =
## for the canned note of "This tutorial assumes that you have completed the previous tutorials:" just add the links 
## note.0= 
## descriptive title for the tutorial
## title = Using Test Manager
## multi-line description to be displayed in search 
## description = Covers using, debugging and running Test Manager.
## the next tutorial description (optional)
## next =
## links to next tutorial (optional)
## next.0.link=
## next.1.link=
## what level user is this tutorial for 
## level= BeginnerCategory
## keywords =
####################################

<<IncludeCSTemplate(TutorialCSHeaderTemplate)>>

<<TableOfContents(4)>>

== Overview ==

Test Manager is a tool used in the WG Hardware Test Systems. It is intended for WG personnel only, and will not work outside WG. 

== Starting Test Manager ==

=== Applications Menu ===

Test Manager should be started from the Applications menu of your testing station. Go to "WG Testing Applications" and select "Test Manager".

=== Command-Line ===

You can also start Test Manager from the command line:
{{{
rosrun life_test test_manager.py
}}}

== Running Tests ==

To start a test, scan the serial number of the test into Test Manager's "Start Tests" tab and press "Proceed".
{{attachment:tm_start.png}}

A new tab will open for this device. 
 * Select the test "bay" (which machine to run on). 
 * Plug in the cables from that machine into the device-under-test.
 * Set the device to run for a certain number of hours, or select "Continuous" mode.
 * Press "Launch".

{{attachment:tm_launch.png}}

After a test has completed the required hours, it will terminate automatically. Press "Close" to close the test tab when finished.

=== Test Status ===

Test status is indicated by the colored "Test Status" bar in the center of each tab. Devices can be in one of four states:
 * Running
 * Warning - Abnormal condition, but not stopped. Example: "Uncalibrated"
 * Error - Error condition. Test is stopped.
 * Stale - No updates from the device or instrumentation.

To restart any device, press the "Run" button on the appropriate panel.

{{attachment:tm_running.png}}

== Debugging ==

=== Motors Halted ===

The "Motors Halted" message appears any time the motors of a device halt. When this happens, check the "Diagnostics" panel.

{{attachment:tm_halted.png}}

=== Transmission Broken ===

Test Manager monitors the transmission status of all devices under test. This check is designed to check for damaged belts, calibration sensors or encoders. 

Check the diagnostics for more information about transmission errors.

==== Caster Slip ====

Casters are monitored for slipping during the caster test. If air pressure is not applied properly, the casters will slip on the fixtures and they will be halted.

{{attachment:tm_trans_broken.png}}

=== Camera Error ===

The "Camera Error" message means that the WGE100 camera has lost contact or had an error during the test.

To debug:
 * Look at the "Diagnostics" panel to error messages for the camera. 
 * Look for dropped packets or other errors.
 * Use a cable tester to check that the communication and power cables to the camera are OK.

{{attachment:cam_error.jpg}}

=== No Heartbeat ===

The message "No Heartbeat" means a loss-of-communication between Test Manager and any of the devices. If you see this message, run:
{{{
rosrun topic_tools relay heartbeat heartbeat
}}}

And press "Run" for any devices that have stopped.

## AUTOGENERATED DO NOT DELETE 
## TutorialCategory
## FILL IN THE STACK TUTORIAL CATEGORY HERE