[FTC]: USB controler problems

[VeedotJaydot]

We have been programming our robot for FTC and so far, we haven't been able to make the robot to respond to the USB controller through the bluetooth network with the robot. We have set the bluetooth network up to the robot academy tutorial's standards, we also have calibrated the controller and made sure it is working properly. We may have coded it wrong, but even the default code Here(2 Joystick Drive Program) won't respond when we use the controller. Long story short, are there special VIs that are needed for use of the controller, or is there some other possibility that I'm over looking or I'm ignorant of?

[Michael Coleman]

1. Are you using the FTC version of LabVIEW from the kit-of-parts?
2. Did you install the LabVIEW FTC Toolkit updates: Dual Controller Update, Motor and Encoder Update, and Sketch Example Update? These updates are found here: zone.ni.com/devzone/cda/tut/p/id/7956
3. Does the software match how the HiTechnic controller are wired?
4. Are you trying to control the robot with the National Instruments FTC Controller Station or the Field Management System (FMS)?
5. Does the FTC Controller Station or the FMS indicate that it has established a Bluetooth connection with the NXT?
6. Is the correct program running on the NXT?
7. If you are using the FTC Controller Station. Is the robot enabled? Are the correct controllers selected in the drop down boxes shown in the virtual Logitech controllers?
8. Is the external HiTechnic battery pack connected, turned on and charged?
9. Does the HiTEchnic battery pack have a blown fuse?
10. Are the battery connections to the HiTechnic controller firmly attached? Pull on the wires to test.

Michael

[VeedotJaydot]

1. Yes
2. Those VIs are not relevent to my issues currently, but it was nice of you to post that link, I may need them in the future.
3. Yes, I should have specified that we have tested the code with a bizzare mock-up limit switch controller before posting
4. I don't really know what this means, so this might be the problem, if someone could post some information about this, I would be very greatful, in the meantime, I'll be doing my own research about this. I'm pretty sure this is our problem
5. same as 4
6. yes
7. same as 4
8. Yes
9. No
10. Yes

--------
Update
--------
I found that our problem was the fact that we weren't using the FMS, silly me, however, we don't know how to make the FMS accept our teleop code, I think this might be because our teleop code is not in .rxe format, however I have no idea how to export our code like this. I might also be mistaken and the teleop.rxe is some kind of default program that the FMS should have come with, anyway, we don't have it and I would appreciate it if someone could help me.


Thanks for the help!

[Michael Coleman]

Great! I am glad the problem is solved.

At the end of the autonomous period, the FMS stops the autonomous program and starts the program specified in the FTCConfig.txt file on the NXT.

Teams using NXT-G or LabVIEW run a program located on the NXT called Program Chooser. In the Program Chooser, select "Dual" with the NXT arrow buttons and press the Orange button to confirm. Then use the arrow buttons to select the name of the tele-op program. Confirm the selection with the Orange button.

The Program Chooser is written to the NXT by the National Instruments FTC Controller Station. This is done the first time the FTC Controller Station connects to the NXT.

The FTC Controller Station is installed when the FTC version of LabVIEW is installed. It is located in the following folder:

Program Files/National Instruments/LabVIEW 8.5/examples/FTC Toolkit/FTC Controller Station

Teams using ROBOTC select the name of the tele-op file in the Joystick Control Debug window. ROBOTC writes the Tele-op file name to the FTCConfig.txt file on the NXT.

Michael