View Single Post
  #7   Spotlight this post!  
Unread 10-05-2011, 23:59
kamocat's Avatar
kamocat kamocat is offline
Test Engineer
AKA: Marshal Horn
FRC #3213 (Thunder Tech)
Team Role: Mentor
 
Join Date: May 2008
Rookie Year: 2008
Location: Tacoma
Posts: 894
kamocat is just really nicekamocat is just really nicekamocat is just really nicekamocat is just really nicekamocat is just really nice
Send a message via AIM to kamocat Send a message via MSN to kamocat
Re: Labview / Simulation

Well, I certainly don't mind being proven wrong, but I don't yet understand how this works. If you're not simulating the motion of the robot, what are you simulating?

Perhaps I was over-generalizing, but I'll explain why I said what I did. The primary issues that stop me when programming aren't actually programming issues. What stop me are issues like mechanical binding or improper motor/gearbox selection. These aren't things that are going to be caught in a simulation for testing programming (nor should they be).


If what you mean by simulating is simply running your subVIs without the robot, then my view is completely different. Yes this will catch programming errors. Unit testing is one of the steps anyone should take when developing software.
__________________
-- Marshal Horn
Reply With Quote