Re: WPILib Suite 2017
 

What is the difference between the 2016 C++ toolchain and the one for this year (2017)? I can't seem to find a changelog, and they're supposedly the same GCC version.

Re: WPILib Suite 2017
 

The installer itself had a few bugs fixed, and it has a new sysroot to match the 2017 image. The compiler version itself is the same.

Re: WPILib Suite 2017
 

Does anybody know where the API/Documentation is for the CTRE CANTalon library? It is not on the first wpilib documentation and I can't find it anywhere on the CTRE site.

My team uses Java. Last year the CANTalon library used to be built in to the WPILib but now it is part of the 3rd party libraries from CTRE. I have gotten that setup on my development machine but I can't find any documentation anywhere on classes in the library (javadoc).

Re: WPILib Suite 2017
 

http://wpilib.screenstepslive.com/s/...arty-libraries should be of use. This page should be in a sticky somewhere, it's crucial and really hard to find...

Re: WPILib Suite 2017
 

The repository that the page references doesn't seem to have any 2017 releases yet? I'm not finding any reference to "athena" like the page says, though that could be unfamiliarity with the maven structure

EDIT: Never mind, found it

Re: WPILib Suite 2017
 

I already followed those instructions and have the CTRE 3rd party libraries installed. I was just wondering where the documentation is for the library. I think the CANTalon Library is exactly the same as the wpilibj CANSpeedController. Does anybody know if this is right?

Re: WPILib Suite 2017
 

So where does one find out what the appropriate import statement is? I have not been able to locate any doc for the CTRE library.

Re: WPILib Suite 2017
 

Sadly, the documentation is lacking for the 2017 CTRE library.

The import statements are:

import com.ctre.CANTalon; // The main CAN talon device

import com.ctre.CANTalon.FeedbackDevice; // The modifiers for the CAN talon device
import com.ctre.CANTalon.StatusFrameRate;
import com.ctre.CANTalon.TalonControlMode;

After that use them as per last year.
For teams that did not keep last year's javadoc (or don't have a 2016 install) there isn't any source on the CTRE web site yet. I'm hoping that they will remedy this soon.

Re: WPILib Suite 2017
 

Migrating from 2016 to 2017 is explained in section 3.1.1 of the Talon SRX Software Reference Manual.

Re: WPILib Suite 2017
 

Hi Ozrien,
is it possible to get a javadoc to go with the new library, or is the SRM the only reference available?

Re: WPILib Suite 2017
 

We'll put up a javadoc soon, stay tuned. But in the mean time, I would take a look at the ref manual and our github examples.

Re: WPILib Suite 2017
 

Sorry I'm late to the party all. Are we saying that there is no javadoc up yet for the CANTalon library?

Re: WPILib Suite 2017
 

Has anyone actually written a sample program in either CPP or JAVA using the CTRE 2017 download for CANTALON (as opposed to TALON)?

In particular., declaring a m_cantalon object, instantiating the m_cantalon object, and creating both an open-loop and and a closed-loop mode for the m_cantalon object. For me TALON works(no closed-loop obviously), but CANTALON doesn't.

Both CPP and JAVA replies to this post will be appreciated.

Re: WPILib Suite 2017
 

Of course that was done, by us and by beta teams. And for the most part all you need to do is add an import/include for pre2016 cpp/java projects to work. Is there a specific problem you are seeing? Did you follow the steps in section 3.1.1 of the Talon srx software reference manual?

Re: WPILib Suite 2017
 

I'm probably confused by the maven repo structure, but I don't see anything from 2017 under http://first.wpi.edu/FRC/roborio/maven/release/. Am I looking in the wrong spot?