|
|
|
 Here, and in general, avoid jumping to conclusions without research. This will serve you well in life.
- DonRotolo [more] |
 |
|
|||||||
|
||||||||
 |
| Thread Tools | Rate Thread | Display Modes |
|
|
|
| Here, and in general, avoid jumping to conclusions without research. This will serve you well in life.
- DonRotolo [more] |
|
|
|||||||
|
||||||||
|
| Thread Tools | Rate Thread | Display Modes |
|
#1
|
||||
|
||||
|
Check lists and debuging lists needed
Hey,
Team 3784 realized when we went to CowTown that there were a lot of little things that impared our performance. We're making check lists for everything from packing and tools needed to debugging and troubleshooting. Where could we find samples of other teams' lists? Thanks Ashley Painter Team Captain Last edited by Ashley Painter : 12-11-2011 at 12:08. Reason: Adding more detail 
|
|
#2
12-11-2011, 18:27
|
|||
|
|||
|
Re: Check lists and debuging lists needed
Quote:
 I'll comment on the pit list, we look at all the things that have wear and tear and build a check list based on that. We then look at the "oh, so that's why the robot didn't move last match" and put them on the list. The list is posted in the pits so it's a constant reminder what to do. The list is in order of time. For example if the wheels need treads, that takes lots of time, so it's early in the list. Last on the list is things that may be a problem but quick to check. For example, did the programming team load new code? Then is the ethernet cable to the Wifi plugged back into the CRio? Last thing on the list is a check of the list. Read the list out loud and wait for a crew member to yell "Done". We've had times where that didn't happen and there were failures in the match. Learn the list, work the list, love the list.
|
|
#3
12-11-2011, 23:50
|
|||
|
|||
|
Re: Check lists and debuging lists needed
It is also important for the drive team to have a check list for queing and on the field. This can include things such as, checking the ethernet to the crio, checking that the correct autonomous mode is set, checking the minibot is on, checking the pressure gauge is closed, etc.
|
|
#4
13-11-2011, 08:51
|
||||
|
||||
|
Re: Check lists and debuging lists needed
Always debug moving from mechanics to code.
For example, if you have a limping drivetrain, you check the wheels, then the chain, then the gearbox, then the motors, then the encoders, then the victors, then the power distribution board, then the digital sidecar, then the cRIO, and lastly the code.
|
|
#5
13-11-2011, 13:53
|
||||||
|
||||||
|
Re: Check lists and debuging lists needed
Searching for checklist found this recent thread with a lot of good information: http://www.chiefdelphi.com/forums/sh...ight=checklist
|
|
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Linear Mode
