Can't configure WPI_MotorControlOpen.vi for "CAN Talon SRX" motor controller

[daveshike]

When we create a WPI_MotorControlOpen.vi in LabVIEW, the motor controller type selection dropdown does not include "CAN Talon SRX" as shown on page 22 of the Talon SRX Software Reference Manual. Any suggestions on what we are missing in order to configure the motor open vi for the CAN Talon SRX?

Thanks!

[Mark McLeod]

Does yours look anything like this one?
What else seems to be missing? Is the Victor SP missing too?

Have you copied any old code or opened any old projects?

[daveshike]

Ours looks similar, but we only have the following selections: Jaguar, CAN Jaguar, Victor and Talon.

I'm not sure if any of the team members have copied old code into the project.

[jman4747]

Originally Posted by daveshike

Ours looks similar, but we only have the following selections: Jaguar, CAN Jaguar, Victor and Talon.

I'm not sure if any of the team members have copied old code into the project.

Did you by chance create a project with CRio target instead of a RoboRio target?

[Mark McLeod]

You have last year's vi for some reason.

[daveshike]

Ok. Is there a way to replace last year's vi with the updated one? BTW, when a create a new project from scratch, "CAN Talon SRX" shows up.

[daveshike]

Originally Posted by jman4747

Did you by chance create a project with CRio target instead of a RoboRio target?

I didn't create the project. Do you know a way to check that we have the correct target?

[Mark McLeod]

Check to see where the Motor Open is being loaded from.
In the Project Explorer window, click on the Files tab and you should see something like the attached.

Look for any paths out of the LabVIEW 2014 tree structure.
The only two directory trees you should see are the LabVIEW 2014 and the Users -> ... -> Documents -> LabVIEW Data -> your project name

[jman4747]

Originally Posted by daveshike

I didn't create the project. Do you know a way to check that we have the correct target?

Open project the explorer and see my attachments.

Edit: What Mark said too.

[ozrien]

Did you uninstall last year's LV before installing this years software? I always wondered what to expect if that was skipped.

"Uninstall Old Versions (Recommended)"...
http://wpilib.screenstepslive.com/s/...5-labview-only

[daveshike]

Thanks, everyone, for your help and advice. We'll continue working on this tomorrow. Hopefully we'll get it all sorted.

[Greg McKaskle]

The uninstall doesn't cause this. I have three year's of FRC on my same VM. The conflicts, if any, will be at the library and drivers, not the VIs or EXE.

Greg McKaskle

[daveshike]

Thanks, Mark, Josh, Omar, and Greg. The project was using the wrong API location. We found the needed VIs in the correct API location and used them.