FCS is running circles during the Teleop time

[FrostBots_AK]

Our robot worked beautifully this weekend at tournament, but now that we are home and have re-flashed our Samantha with our router information our robot is running in circles....

When we run the FCS program we are able to connect the Samantha to the program, then we run the autonomous mode and it runs fine (both tires move together to run in a straight line). Then the program moves to teleop mode and when we start the match our robot immediately turns to the left by moving one motor alone. There is no difference in the teleop program that we ran this weekend that had no issues. We are wondering if this might be a program version issue as we are using last year's programs and also the computer we are running on doesn't have the FTC toolkit. Does the toolkit affect the Field Control System or just the Labview program?

Thanks for your help, Kristin

[mathterizer]

========================================================================================= Are you up to date? Is it an anomaly? Is it hardware fail?

Make sure your controller has the switch on the bottom set to 'd'  (not 'x'). And that the 'mode' button is not on (little green light on controller). You might also try a different controller, in case a joystick is stuck.

Make sure all your battery levels are full (NXT and 12-volt)

Instructions for verifing that you have an up to date LabVIEW Installation

https://decibel.ni.com/content/message/61863#61863     on the ni site

http://ftcforum.usfirst.org/showthread.php?2356-Installing-LabVIEW-and-the-MCT-Toolkit-(for-Windows)...    on the FTC forum

Try turning everything off (on the robot), exit LabVIEW, restart LabVIEW, reconnect, turn things back on - try again. Even a computer restart might help.

We've had this happen randomly too, for years now - more often when the NXT battery is low.

=========================================================================================== From another angle (technically):

The FCS is the same as last year V3.0.6 - so it is no surprise that it would work fine with last years software (LVLM 2010/FTC Toolkit).

If you have some strange blend of LabVIEW you have compiled files to the NXT with - all bets are off.

=========================================================================================== From still another angle (Software inspection and FTC Rules):

FIRST does require that all team use the LVLM 2012 for competitions this season. Prior to 11/06/13 this was not a possibility. However, after the release of the new MCT Toolkit update, the new version of LVLM 2012/MCT is stable and should work for everyone. (LabVIEW f5, NXT Module f3, MCT f1)

Follow the installation instructions from the pdf I have attached, do not skip any steps. You can perform a 'share' on last years project (LVLM 2010) and open it in the new LVLM 2012/MCT installation. Take a close look at the vi's and see if it all looks good. Reload your firmware. Reload the Program Chooser and samostat as directed in the attached pdf. You need to use the new 'autonomous mode' template provided by the 'Arm & Gripper' project.

get the document pdf I mentioned from my post found here: https://decibel.ni.com/content/thread/19824?tstart=0    (file called ni and first LV post V2.pdf

If you need any more help to accomplish this, please ask.

Message was edited by: Lori Hanson to add 2 new angles ======

[FBHS_FTC]

Kristin,

Is your robot still doing this?  Ours are too and I can't figure out what is going on.  Like you, autonomous runs fine and our testing through LabView works perfectly (even in the telelop testing part).  Once that FCS hits the telelop mode, Our robots loses his mind and starts spinning.  If you figured something out, can you please let me know?  We have a qualifier this weekend we need to get ready for.

Thanks

T. Graham

Flour Bluff High School

[mathterizer]

This thread addresses the issue, and contains some strategy and troubleshooting tips.It appears to have resolved their problem: http://ftcforum.usfirst.org/showthread.php?2721-HELP-w-Labview-FCS-issue&highlight=labview

It may have been as simple as the controller not having the switch (on the bottom) in the 'D' position.