p09201: test plan - edge.rit.eduedge.rit.edu/edge/p09201/public/p09201_testplanrev1.pdf · u2 -...

P09201: Test Plan

Revision: 1January 23, 2009

P09201 Test Plan, Rev 1

of 22

Table of ContentsAbstract 4

Required Materials 4

Hardware Test 5Purpose 5Required Materials 5Assumptions/Constraints 5Steps 5

Joystick API (JSAPI) 6Purpose 6Required Materials 6Assumptions/Constraints 6Steps 6

User Interface 7Purpose 7Required Materials 7Assumptions/Constraints 7Steps 7

Link Layer/Serial Port (CLAPI) 9Purpose 9Required Materials 9Assumptions/Constraints 9Steps 9

Protocol Stack Test 10Purpose 10Required Materials 10Assumptions/Constraints 10Steps 10

Bridge <=> PC Communication Testing 11Purpose 11Required Materials 11Assumptions/Constraints 11Steps 11Bridge <=> PC Test 11Module <=> Bridge <=> PC Test 11Module <=> Bridge <=> Bridge <=> PC Test 12

System Level Test (SLT) 13


of 22

Purpose 13Required Materials 13Assumptions/Constraints 13Steps 13One Light, One Thruster 13Two Lights 15Two Thrusters 15Gamma Device Tests 15

Appendix 17Chip Information 17U5 - LM2674-5.0 17U2 - Atmega 168 17U19 - MAX3223 18U18 - MAX3100 18U21 - 74AHC1G04 19U22 - SN65176BD 20U20 - MM74HC154 20U23-U25 - CD4001BC 21


of 22

AbstractThis test plan serves as a documentation of the steps to be taken by the P09201 design team and anyone modifying or building P09201 software/hardware to ensure that the resulting product behaves as expected. This test plan covers the following hardware and software modules:

• P09201 bridge PCB (Hardware test)• Joystick API driver code• Link-layer (serial port) code• Protocol stack• Bridge to PC connection• Bridge daisy-chaining• GUI functionality• System level test

It is recommended that a hardware test be the first test performed in order to verify the basic performance of the P09201 bridge.

Required Materials

In order to fully implement this test plan, access to the following materials is required:

• Two P09201 bridge modules, fully populated.• Two P09201 test fixtures.• Access to a 24 V power supply.• A digital multimeter.• One host computer with at least two serial ports or two computers, each with at least

one serial port.• If no serial port is available, then the means of emulating one (e.g. via a USB-

Serial port converter). WARNING: the WinChipHead USB-Serial port converter is only supported on the Windows operating system.

• Access to the P09201 code repository (https://edge.rit.edu/dav/P09201/)• The SWIG (http://www.swig.org/) and SDL (http://www.libsdl.org/) libraries installed on

the test PC.• The ability to compile C, C++, and Java.


of 22

https://edge.rit.edu/dav/P09201/

https://edge.rit.edu/dav/P09201/

http://www.swig.org

http://www.swig.org

http://www.libsdl.org

http://www.libsdl.org

Hardware TestPurposeThe hardware test is intended to verify that the power is reaching all components on expected pins.

Required Materials• P09201 PCB, fully populated.• Digital multimeter

Assumptions/ConstraintsBridge will not be connected to any thrusters, lights, or test benches for this test. A simple power-on test for all ICs will verify all chips are operational. Bridge will be connected to DC Power supply with a voltage set at +24V and a current limit set at 100mA.

Steps1. Plug supplied power pigtail P1 to J16. Free leads plug directly into DC Power supply

(HPE3631A). Ensure output is off, plug red wire into red socket, black wire into black socket labeled ʻCOMʼ on power supply.

2. Verify bridge power switch SW1 is in the OFF position.3. Turn on power supply output.4. Switch on bridge power using SW1.5. Measure voltage referenced to ground (J16-GND) at the following nodes, record in

table 1.Chip-Pin# Ideal Actual

U5-7 +24V

U5-4 +5V

U2-4 , 6, 18, 19, 22 +5V

U20-13 +5V

U23-14 +5V

U24-14 +5V

U25-8, 9, 12, 13, 14 +5V

U22-8 +5V

U10-8 +5V

U21-5 +5V

U18-7, 16 +5V

U19-19, 20 +5V

Table 1 - Recorded Chip Voltage


of 22

Joystick API (JSAPI)PurposeThe JSAPI test is intended to verify the functionality of the joystick abstraction code.

Required Materials• USB joystick with X, Y translational axes, Z rotational axis and a slider control.

Assumptions/ConstraintsJoystick must not be unplugged/plugged in during test (JSAPI does not support hot plugging/unplugging). Joystick drivers must be installed on operating system (may not be possible, e.g. drivers do not exist for operating system).

Steps1. Run whatever operating system joystick calibration program you may have.

a. On Linux, use the jscal program.b. On Windows, use the one provided with the joystick driver (if it exists).c. On Mac: not necessary.

2. Navigate to the code/js_api/swig directory within the P09201 project directory.3. Run the build script for your operating system.

a. On Linux, run the command “./build_linux.sh”b. On Windows, run the command “build_windows.bat”c. On Mac, run the command “./build_mac.sh”

4. Navigate into the code/js_api/swig/test directory within the P09201 project directory.5. Run the TestOpenGL program.

a. On Linux, run the command “./java_linux.sh TestOpenGL”b. On Windows, run the command “TODO”c. On Mac, run the command “./java_mac.sh TestOpenGL”

6. Run the calibration routine of the program (available from the “Options” menu).7. Follow on screen directions.8. Verify that left, forward, right, back on the joystick correspond to the left, down, right,

and up arrows of the GUI.9. Verify that rotating the joystick clockwise and counterclockwise correspond to the

correct rotation arrows.10. Verify that the slider forward and backward correspond to the forward and backward

arrows.


of 22

User Interface

PurposeThe user interface test is intended to verify the functionality of vital user interface components and the interfaceʼs ability to use the communications protocol.

Required MaterialsComputer running MS Windows, Linux, or Mac OS with Java installed.

Assumptions/ConstraintsNo serial ports will be connected or in use by the system during the test. No peripheral hardware will be connected to the system during the test.

Steps1. Navigate to the code/TBD directory within the P09201 project directory.2. Run the test build script for your operating system.

a. On Linux, run the command “./test_build_linux.sh”b. On Windows, run the command “test_build_windows.bat”c. On Mac, run the command “./test_build_mac.sh”

3. Verify that the main program window appears.4. Open the Options menu and click on “Show Log Window.”5. Verify that the log window appears, empty. Verify that the Show Log Window

command has become “Hide Log Window.”6. Open the Communications menu and click on “Select Serial Comms Port.”7. Select a serial port using the input dialog that appears.8. Verify that the light module window appears containing a single set of light controls

and that the module displays the requested serial port. Verify that the master light control console has appeared in the main window. Verify that the log window displays a message being sent to the communications protocol.

9. Click on the Choose Color button and select an available color or click Choose…to select a different color.

10.Verify that the lightʼs panel has changed to the requested color. Verify that the log window displays a new message being sent to the communications protocol.

11.Open the Communications menu, click on “Select Serial Comms Port” and select a different serial port.

12.Verify that another light module appears in the light window alongside the previous module and that the new module displays the new serial port. Verify that the log window displays another message being sent to the communications protocol.

13.Click on the Choose Color button of the new light module and select a different color.14.Verify that the new light moduleʼs panel has changed to the requested color and that

the previous light moduleʼs panel remains unchanged. Verify that the log window displays one new message being sent to the communications protocol.

15.Click on the “Link All” check box in the main window.16.Verify that both light modulesʼ “Link to Master” check boxes become checked.


of 22

17.Use the master light control console in the main window to select a new color and click the “Set” button.

18.Verify that both light modulesʼ panels change to the requested color. Verify that the log window displays two new messages being sent to the communications protocol.

19.Click the Emergency Stop button.20.Verify that the log window displays a new message being sent to the

communications protocol. Verify that the Choose Color buttons in the light window become disabled. Verify that using the master light control console has no effect on linked light modules.

21.Click the Emergency Resume button.22.Verify that the log window displays a new message being sent to the

communications protocol. Verify that the Choose Color buttons in the light window become enabled. Verify that the light controls can be used to effect again.

23.Open the Communications menu, click on “Select Serial Comms Port” and select one of the current light modulesʼ ports.

24.Verify that the selected portʼs light module disappears from the light window.25.Open the Communications menu, click on “Select Serial Comms Port” and select the

other light moduleʼs port.26.Verify that the light window disappears.27.Open the Communications menu and click on “Select Thruster.”28.Select a thruster port using the input dialog that appears.29.Verify that the thruster module window appears containing a single set of thruster

controls and that the module displays the requested port. Verify that the main window indicates the presence of thrusters. Verify that the log window displays a message being sent to the communications protocol.

30.Open the Communications menu, click on “Select Thruster,” and select a different port.

31.Verify that a new thruster module appears in the thruster window alongside the current module. Verify that the log window displays a new message being sent to the communications protocol.

32.Verify that the thruster controls allow the thrusters to be configured as Forward Left, Forward Right, Lateral, or Pitch control.

33.Use the “Select Thruster” command of the Communications menu to select one of the current thruster modulesʼ ports.

34.Verify that the selected portʼs thruster module disappears.35.Use the “Select Thruster” command of the Communications menu to select the other

thruster moduleʼs port.36.Verify that the thruster window disappears.37.Click on the Save Log Window button in the log window.38.Use the save file dialog to save the contents of the log window as a text file.39.Verify that the newly created text file bears the contents of the log window.40.Click on the Clear Log Window button in the log window.41.Verify that the contents of the log window are erased.42.Click on the “Hide Log Window” command from the Options menu.43.Verify that the log window disappears.44.Close the program.


of 22

Link Layer/Serial Port (CLAPI)PurposeThe CLAPI test is intended to verify the functionality of the link layer abstraction code.

Required Materials• Serial (RS-232/EIA-232) cable.• Means of connecting cable to two computers (or one computer twice).

• If using USB to serial converter, drivers for converter must be installed on host computer. (WARNING: the WinChipHead converter is only supported on the Windows operating system).

• One or two computers.• If one computer, computer must have two serial ports.• If two computers, each computer must have a serial port.

Assumptions/ConstraintsCable must be plugged in and drivers must be installed for converters (if any are being used) before test program is run. Cable must remain plugged in during full run of test program (test program does not support hot plugging/unplugging).

Steps1. Connect two computers together with a serial cable (or connect one computer to itself

over two serial ports).2. Navigate to the code/cl_api/swig directory within the P09201 project directory.3. Run the build script (on both computers) for your operating system.

a. On Linux, run the command “./build_linux.sh”b. On Windows, run the command “build_windows.bat”c. On Mac, run the command “./build_mac.sh”

4. Navigate into the code/cl_api/test directory within the P09201 project directory.5. Run the TestAPI program on both computers (or run two instances if using one

computer).a. On all operating systems, run the command “java TestAPI”

6. Enter the information that you are prompted for, being sure to enter the same information on both computers.

7. Verify that the test program prints “All tests passed!”.


of 22

Protocol Stack TestPurposeThe stack test programs will verify the C implementation of the protocol stack code (which eventually resides on the microcontroller), and verify that the GUI is sending and receiving packets correctly.

Required Materials• Serial (RS-232/EIA-232) cable.• Means of connecting cable to two computers (or one computer twice).


• One or two computers.• If one computer, computer must have two serial ports.• If two computers, each computer must have a serial port.


Steps1. Navigate into the code directory within the P09201 repository and compile the

protocol test programs.a. On Windows, run “make -f test.mak”b. On Linux and Mac, run “make -f test.mak”

2. Run the basic stack test program.a. On Windows, run “test_stack.exe”b. On Linux and Mac, run “./test_stack”

3. Follow the on screen prompts.4. Verify that the test reports a PASS condition.5. Next, run the protocol decoder test program.

a. On Windows, run “test_TODO.exe”b. On Linux and Mac, run “./test_TODO”

6. Follow the on screen prompts for that program.7. Once that program has been properly setup, run the GUI program TODO: how?8. TODO: specific list of steps to take within GUI (e.g. click thruster, click light).9. Verify that the protocol decoder test program outputs a PASS condition.


of 22

Bridge <=> PC Communication TestingPurposeVerifies communications between bridge and PC over CIP (Common Interface Protocol) and BCP (Bridge Configuration Protocol).

Required Materials• One P09201 Bridge.• One computer.• Serial (RS-232/EIA-232) cable.• Means of connecting cable to computer.



Steps

Bridge <=> PC Test1. Connect a bridge (BR1) to host PC via serial cable and power on bridge using SW1.2. Navigate into the code directory within the P09201 repository and compile the

protocol test programs.a. On Windows, run “make -f test.mak”b. On Linux and Mac, run “make -f test.mak”

3. Run the bridge to PC test program.a. On Windows, run “test_TODO.exe”b. On Linux and Mac, run “./test_TODO”

4. Follow the on screen prompts of the test program.5. Verify that the program reports a PASS condition.

Module <=> Bridge <=> PC Test6. Power off the bridge using SW1, and the perform the following test once for each

RS-485 connection on the bridge:(1) Connect a test fixture emulating a Gamma device to the bridge.(2) Power on the bridge using SW1.(3) On Windows, run “test_TODO.exe”, on Linux and Mac run “./test_TODO”(4) Follow the on screen prompts of the test program.(5) Verify that the program reports a PASS condition.(6) Power off the bridge using SW1.


of 22

Module <=> Bridge <=> Bridge <=> PC Test7. Power off bridge 1 using SW1 and connect a second bridge (BR2) to BR1 using the

daisy-chaining port. Repeat steps 6.1 through 6.5, this time connecting the test fixture to BR2 instead of BR1, and making sure to power off both bridges between iterations of the test.


of 22

System Level Test (SLT)PurposeThe system level test is intended to verify the functionality of the fully assembled product, focusing on the interaction between all modules, not the modules themselves.

Required Materials• Two test fixture boards.• Two P09201 bridges.• USB Joystick with X, Y translational axes, Z rotational axis and a slider control.• Computer running Windows, Linux, or Mac OS X.• Serial (RS-232/EIA-232) cable and means of connecting serial cable to computer.


Assumptions/ConstraintsJoystick must not be unplugged/plugged in during test (hot plugging/unplugging of joystick is not supported).

Steps

One Light, One Thruster1. As shown in figure 1, connect one test fixture (TF1) to one bridge (BR1). Connect

BR1 to the other bridge (BR2). Connect the other test fixture (TF2) to BR2. You should have a setup where the bridges are daisy chained together, with each bridge having one test fixture.

Figure 1: Connection Diagram for Test Fixtures, Bridges, and


of 22

2. Connect BR2 to the computer using the serial cable.3. Set TF1 to emulate a thruster, and TF2 to emulate a light. TODO: how?4. For the remainder of this section, verify that TF1ʼs LED lights never turn on, and

TF2ʼs fan never spins.5. Power on BR1, BR2, and both test fixtures. TODO: whatʼs the power on process? Are

bridges running off battery? Test fixtures off bench power supply?6. Run the main P09201 GUI program. TODO: how?7. In the GUI program, navigate to the Options > Calibrate Joystick menu item. Select

this item and follow the on screen instructions in order to calibrate the joystick.8. In the GUI program, navigate to the Options > Open Port... menu item and select the

appropriate serial port to open for communication with the connected system.9. Verify that a thruster window and a light window pop up, each displaying that one

module is connected (one light module and one thruster module).10.Verify that, in the GUI, the light module is reported as turned OFF.11.Turn the light off and verify that TF2ʼs multicolor light turns off.12.Set the lightʼs intensity to full, set its color to white, turn the light on, and verify that

the light shines brightly with a white color.13.Decrease the lightʼs intensity and verify that the intensity of the light dims.14.Set the light back to full intensity, color it red, and verify that TF2ʼs light is bright red.15.Set the light to green and verify that TF2ʼs light is bright green.16.Set the light to blue and verify that the TF2ʼs light is bright blue.17. In the thruster window of the GUI, set the connected thruster as the left-right

thruster.18.Move the joystick full left and verify that the fan on TF1 increases speed.19.Move the joystick full right and verify that the fan on TF1 reverses direction but

maintains a high speed.20.Center the joystick and verify that the fan on TF1 stops.21.Move the joystick forward-backward, rotate the stick, and move the slider, all without

moving the joystick left-right and verify that the fan on TF1 does not move during any of these inputs.

22. In the thruster window of the GUI, set the connected thruster as the forward-left thruster.

23.Move the slider on the joystick forward and verify that the fan on TF1 increases speed.

24.Move the slider on the joystick backward and verify that the fan on TF1 reverses direction but maintains a high speed.

25.Center the joystick and verify that the fan on TF1 stops.26.Verify that neither moving the joystick left-right nor forward-backward affect the fan

on TF1.27.Rotate the joystick clockwise and verify that the fan on TF1 increases speed.28.Rotate the joystick counterclockwise and verify that the fan on TF1 reverses

direction but maintains a high speed.29.Push the slider on the joystick forward while simultaneously rotating it

counterclockwise and verify that the fan on TF1 decreases in speed. It doesnʼt


of 22

necessarily need to stop, but its speed should be less than if the joystick was only pushed forward, or only rotated counterclockwise.

Two Lights30.Quit GUI program and power down bridge-test fixture system. TODO: how to power

down? Whatʼs the sequence?31.Set TF1 to emulate a light. TODO: how?32.Power up the bridge-test fixture system and then run the GUI program and navigate

to the Options > Open Port... menu item and selecting the serial port to open for communication with the connected system.

33.Verify that two light module controls are displayed in the GUIʼs light module window.34.Set both lights to full intensity and white color. Verify that both lights are bright white.35.Set one light to full intensity blue and the other to full intensity red. Verify that one

light is blue and the other is red. TODO: GUI displays hardware address. Should add ability to control hardware address via physical access to test fixture.

Two Thrusters36.Quit GUI program and power down bridge-test fixture system. TODO: how to power

down? Whatʼs the sequence?37.Set both TF1 and TF2 to emulate a thruster. TODO: how?38.Power up the bridge-test fixture system and then run the GUI program. In the GUI

program, navigate to the Options > Calibrate Joystick menu item. Select this item and follow the on screen instructions in order to calibrate the joystick.

39.Navigate to the Options > Open Port... menu item and select the serial port to open for communication with the connected system.

40.Verify that two sets of thruster controls are displayed in the GUIʼs thruster control module window

41. In the GUI thruster window, set one thruster to left-right and one thruster to up-down.42.Verify that pushing the joystick forward causes one fan to increase speed, while the

other fan does not move at all. TODO: GUI displays hardware address. Should add ability to control hardware address via physical access to test fixture.

43.Center the joystick and then move the joystick right. Verify that the fan that stationary in the previous step now increases in speed, while the up-down fan from the previous step is now stationary. TODO: GUI displays hardware address. Should add ability to control hardware address via physical access to test fixture.

44.Move the joystick backward and to the left. Verify that both fans are now spinning.45.Center the joystick and verify that both fans stop moving.

Gamma Device Tests46.Quit GUI program and power down bridge-test fixture system. TODO: how to power

down? Whatʼs the sequence?47.Set TF2 and TF1 to both emulate a Gamma Device. TODO: how?48.Power up the bridge-test fixture system and then run the GUI program and select the

appropriate serial port to open for communication with the connected system.49.Verify that two Gamma Devices are reported as present by the GUI.


of 22

50.Adjust the POT on TF2 and verify that the “value” for the POT displayed by the GUI reflects this change.

51.Stop adjusting the POT on TF2 and change the POT on TF1. Verify that the GUI stops showing changes on the POT for TF2 and starts showing them for the POT on TF1.

52.Through the GUI, change the seven-segment display value for TF1. Verify that the seven-segment display on TF1 reflects this change, but the seven-segment display on TF2 remains the same.

53.Through the GUI, change the seven-segment display value for TF2. Verify that the seven-segment display on TF2 reflects this change, but the seven-segment display on TF1 remains the same.


of 22

AppendixChip Information1. U5 - LM2674-5.0

Figure 1 - LM2674 - 5.0 Power Regulator

Figure 2 - LM2674 - 5.0 tolerance data2. U2 - Atmega 168

Figure 3 - Atmega 168 Package/Pin numbers


of 22

3. U19 - MAX3223

Figure 4 - MAX3223 Package/Pin Numbers

Figure 5 - MAX3223 DC Characteristics

4. U18 - MAX3100

Figure 6 - MAX3100 Package/Pin Numbers


of 22

Figure 7 - MAX3100 Logic characteristics

5. U21 - 74AHC1G04

Figure 8 - 74ACH1G04 Package/Pin Numbers

Figure 9 - 74AHC1G04 DC Characteristics


of 22

6. U22 - SN65176BD

Figure 10 - SN65176BD Package/Pins

Figure 11 - SN65176BD DC Characteristics

7. U20 - MM74HC154

Figure 12 - MM74HC154 Package/Pins


of 22

Figure 13 - MM74HC154 DC Characteristics

8. U23-U25 - CD4001BC

Figure 14 - CD4001BC Package/Pins


of 22

Figure 15 - CD4001BC DC Characteristics


of 22

p09201: test plan - edge.rit.eduedge.rit.edu/edge/p09201/public/p09201_testplanrev1.pdf · u2 -...

Documents