View Single Post
  #26   Spotlight this post!  
Unread 13-12-2006, 19:51
chris31 chris31 is offline
Team 2021 Captain
AKA: Chris Davidson
FRC #2021 (FA Robotics)
Team Role: Mentor
 
Join Date: Nov 2005
Rookie Year: 2006
Location: Atlanta, GA/ Fredericksburg,VA
Posts: 949
chris31 has a reputation beyond reputechris31 has a reputation beyond reputechris31 has a reputation beyond reputechris31 has a reputation beyond reputechris31 has a reputation beyond reputechris31 has a reputation beyond reputechris31 has a reputation beyond reputechris31 has a reputation beyond reputechris31 has a reputation beyond reputechris31 has a reputation beyond reputechris31 has a reputation beyond repute
Send a message via AIM to chris31
Re: Microsoft Robotics Studio

Quote:
Originally Posted by Tom Bottiglieri View Post
Thats not the point. Embedded devices are much harder to code for than applications on a PC. The whole point of this is you can develop intricate programs on the PC that have access to all the processing power and memory available to them. You can write code that accesses SQL databases, gets data off the internet, or runs algorithms that are way too complex and intensive to run on the PIC... You get the point? They've included a Visual programming language (looks a bit like the easyC we've come to know, except WAY more powerful), or you can code in any visual studio editor. (C++, C#, VB.. etc..)

This also gives you a full suite of simulation capabilities. I dont know one FIRST team out there who has had enough time to fully program their robot in the build season. Theoretically, this simulation system will stop that problem.

I'll be working on getting this to interact with FIRST hardware. Even if its only good for prototyping and tuning individual system, it beats having to hard code everything.
I understand the simulation part. But I am confused as to the actual hardware they expect this to be running on.