View Single Post
  #2   Spotlight this post!  
Unread 10-02-2010, 10:14
Chris Hibner's Avatar Unsung FIRST Hero
Chris Hibner Chris Hibner is offline
Eschewing Obfuscation Since 1990
AKA: Lars Kamen's Roadie
FRC #0051 (Wings of Fire)
Team Role: Engineer
 
Join Date: May 2001
Rookie Year: 1997
Location: Canton, MI
Posts: 1,488
Chris Hibner has a reputation beyond reputeChris Hibner has a reputation beyond reputeChris Hibner has a reputation beyond reputeChris Hibner has a reputation beyond reputeChris Hibner has a reputation beyond reputeChris Hibner has a reputation beyond reputeChris Hibner has a reputation beyond reputeChris Hibner has a reputation beyond reputeChris Hibner has a reputation beyond reputeChris Hibner has a reputation beyond reputeChris Hibner has a reputation beyond repute
Re: paper: Using a Virtual Robot Model – Testing and Debugging Autonomous Code Throug

We started using simulation to test and debug autonomous code since the first year autonomous mode was introduced. Way back then (in 2003), we designed and implemented our autonomous control in Simulink+Stateflow (kind of similar to LabVIEW, but from The Mathworks instead of NI).

Using Simulink, we were able to create a nice simple robot model to fully test and debug our autonomous code. We then auto-coded our autonomous code directly from the Simulink/Stateflow models, just like what what teams are doing today with LabVIEW.

Now that FIRST is using LabVIEW, we ported the same simple robot model concept over to the LabVIEW framework. Thanks to simulation, our autonomous code is now fully debugged and working even though we don't have a robot yet.

Simulation is a great tool, and not just for FIRST. This is the way it is often done in the real world. I hope this is useful to some teams.
__________________
-
An ounce of perception is worth a pound of obscure.
Reply With Quote