Re: [FTC]: Control at Compititions
 

If you can't find the FTC Controller Station software look in this folder (assuming default installation). C:\Program Files\LEGO Software\LEGO MINDSTORMS Edu NXT\examples\FTC Toolkit\FTC Controller Station\FTC Controller Station.exe. It is also located in C:\Program Files\National Instruments\LabVIEW 8.5\examples\FTC Toolkit\FTC Controller Station\FTC Controller Station.exe. You should probably just right-click on either one of those and "Send To Desktop (create shortcut)" to make it easier to launch.

Re: [FTC]: Control at Compititions
 

While not the only reason for slow installations, I have found that many programs with slow installs load extensive libraries (whether required or not), many of which require extensive registry changes.

A program that requires 30 minutes to load from disk (with viral software disabled) is indicative to me of a bloated program--registry changes or not. It is just a development environment, after all.

I do not recall the install time for RobotC, but I belive that it was less than 5 minutes.

Re: [FTC]: Control at Compititions
 

Thanks, I eventually found the video that described this on the RobotC web site.

Re: [FTC]: Control at Compititions
 

Since the packet from the PC or FMS indicates whether it is autonomous or tele-op mode, do you really need two programs? Wouldn't it be simpler to have one program and eliminate the need to use the program chooser?

Re: [FTC]: Control at Compititions
 

It's possible to write a program this way but you'll find that you then have just enough flexibility to allow you to unintentionally mess up your match. For example, if you write your autonomous code to do something that takes longer than the autonomous period lasts, you might not be able to control your robot when teleop starts. By splitting it into two programs, the field management system can unconditionally stop your autonomous code, even if it's gone astray.

Re: [FTC]: Control at Compititions
 

No, you can incude "tags" that allows the fms to switch between driver controlled and autonomous code seamlessly (at least you can in RobotC- not sure about labview).