Software Simulation

[JimS]

Has anyone tried to run the Default program on the IDE simulator or can it be done.I attemped it but gor nothing but errors. Can anyone help

JimS

[dm0ney]

I could not get it work as a true debugger.

What errors were you getting?

[ace123]

Check out RoboEmu2:
http://www.robbayer.com/re2.shtml

It will require that you compile your source code using GCC, but if you can get it all working, it's a great solution!

With lots of hacking, it allows you to use autonomous mode, disabled mode and user mode and, with even more hacking, can simulate pots, encoders and even a camera as it runs through native code.

Of course, it won't probably simulate wierd problems like state variables randomly getting set to 0 by interrupts or other such nastiness. (I had this last Friday, and had to tear out the entire autonomous code between matches.) Small things like code loops or what happens if somebody has a certain switch on as it enters auton mode can be tested, and this program has helped me fix some obscure bugs in the code.

[dm0ney]

Originally Posted by ace123

Check out RoboEmu2:
http://www.robbayer.com/re2.shtml

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.

[JimS]

Originally Posted by dm0ney

I could not get it work as a true debugger.

What errors were you getting?

The errors I get are various but some of them are :
Missing arguments
Symbol not defined
Illegal Characters(On comment entries)
Illegal op codes

JimS