Quote:
|
Originally Posted by ace123
|
I've used RoboEmu2 myself, it is a very valuable thing if you arent at your place of work.
I myself have also used a straight RC with a tethered OI with power to it (thanks sparkies) and loaded code on that and tested it. Using IFI Dashboard straight up, it's probably as close as a simulation as you will ever get without the actual robot.
If a second RC or OI isnt available (either another 2005 ordered or 2004 edition) RoboEmu2 is a VERY valuable tool for debugging.
The best solution would be to vocally protest the destruction of this years robot until say week 4 of the build season next year so the programmers can test code on it.
This year, we built the kit bot the first week and tested all our pneumatic code on that, 'ported' last years arm code to this year's arm, and tested our drive code on last year's drive base.
Sure there were differences such as last years robot being a 4-motor 6 wheel drive and this year being 6-motor 6-wheel, but a testing bed is a testing bed.
I would urge every team to try and keep a robot around for a few weeks of build to allow programmers to get some robot time..... a little time goes a LONG way.