|
Re: why blame the programmers??
We had a driving chassis this year to test code on. It was a 6WD where our competition robot had 4, but it still worked reasonably well to test drive code. When it came to programming the attachment, we had to write hypothetical code and test how well it worked by attaching servos and limit switches and encoders to the test robot, and running the drive motors in place of the attachment motors. We were able to do some testing, but never had a complete robot before ship. Afterwards, our arm was completely redesigned and included in our withholding allowance.
We still had many errors that were blamed on programming, some of which were our fault, but many weren't  I guess we are first to blame because they don't know exactly what our code is doing, and because they can't see any obvious problems with the mechanical or electrical. My favourite error of the year, we had next to nothing working on the robot, except for one servo that ran when a jag should have. Programming was blamed immediately, but it turned out that the sidecars were plugged into the wrong ports, so the command for 4,6 was going to 6,6.
__________________
Cale Peister - Team 781 Alumni
Mechanical Engineering Student at Waterloo
Attended: WAT'07, WAT'08, GTR'08, WAT'09, GTR'09, WAT'10, GTR'10, WAT'11, GTRE/W'11, BUCKEYE'11, CMP'11, GTRE'12, WAT'12, GTRW'12, WAT'13, WAT'14, WAT '15
|