search

roboticlemon / cmd-robot

Automatically exported from code.google.com/p/cmd-robot
1 stars 1 forks source link

Testing Phase #34

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Here is a list of tests that must be performed before a full deployment on 
Friday.

* Motors:
 - Do they turn on?
 - Test current draw from each motor with to resistance
 - Test current draw from each motor with high resistance
 - Test current draw from battery

* Arduino Sketch
 - Test to see if it works
 - Test for each side of the vechile
 - Test for forwards and backwards
 - Test for turning (left and right)
 - Test for reverse turning
 - Test for pivot turning left
 - Test for pivot turning right
 - Test current draw when pivoting
 - Check fuses
 - Check for any other problems with sketch

REFER TO WIKI FOR ASSISTANCE

* LED testing - cover
 - Test for power going to LEDs at the right time
 - Check for correct responce on Status bar
 - Check for logic errors in the software involving LEDs
 - Check again and fix any mistakes

* Wireless
 - Check for successful boot on network CAT5e'd(three times)
 - Check for successful boot standalone (three times)
 - Ping test (looking for home many packets get dropped)
 - Remote Desktop connection test (bandwidth test)
 - Limit bandwidth to 1Mbits for better stability (CIAN TO DO)
 - Check for any other instablities
 - Once the system test has been complete - CONDUCT a Wireless Range Test

* Wireless Range Test:
 Walk away from the house with your phone / laptop and see how far you can get before signal level is below 90%, 75%, 50%, 25% and 1%.  Hopefully you stop walking before then. :D

* System Test
 - Check for wiring faults
 - Check for wheel mount errors / faults
 - Check for cover faults
 - Check for Gertboard problems
 - Check RPi Power supply from 5 volt regulator and 6 volt battery
 - Check for other electrical problems

* Software
 - Check that TCP server starts correctly on boot.
 - Check that all files are in correct locations for boot
 - back up SD card.

* Full System Test (without movement)
NOTE: You will require the Joystick and CMD3C for the following tests!!

 - Start RPi (off battery)
 - Wait 35 seconds for network to come up
 - Connect to network
 - ping device
 - Attempt connection to TCP server via CMD3C
 - Check that Joystick Working.
 - Slowly increase speed
 - DO ALL OF THE MOTOR && ARDUINO TESTS AGAIN

Run the System Test again outside!

IF CMDoverwatch PASSES ALL THE ABOVE TESTS, THEN IT IS READY FOR DEPLOYMENT!!

Good Luck.

Original issue reported on code.google.com by cian.by...@sydstu.catholic.edu.au on 3 Apr 2013 at 11:22

GoogleCodeExporter commented 9 years ago 
Two more tests:

* TCP Server:
 - Unplug wireless card from Raspberry Pi and see if Server stops motors.
 - Unplug wireless card from PC and see if Sever stops motors
 - Disconnect from network while program running and see what happens (motors should stop)

Original comment by cmdenterpriseshq on 3 Apr 2013 at 10:03

GoogleCodeExporter commented 9 years ago 
Wireless testing results:

We seem to have STABLE WIRELESS NETWORK!!  I have rebooted the Raspberry Pi 
Three times and each time it comes online correctly.  (on CAT5).  There is no 
internet connection but that is correct! :p

Original comment by cian.by...@sydstu.catholic.edu.au on 3 Apr 2013 at 11:23

GoogleCodeExporter commented 9 years ago 
* Motors:
 - no load = 0.3 Amps / motor   (0.6 total for two)
 - ON LOAD = 1.17 Amps (two motors)

Original comment by cian.by...@sydstu.catholic.edu.au on 4 Apr 2013 at 5:11