Happy kickoff, I know that many of you have been asking about software for MAX & NEO along with some other details. I wanted to start a new thread with some information and to act as a main place to post and collect feedback (rather than spread across a few different posts).
SPARK MAX API - We needed to take a couple extra days to update these due to some late feedback we received. We are in the process of packing things up and running our internal tests and will be rolling these out over the next several days. All of the information will be posted here https://www.revrobotics.com/sparkmax-software/#api-info
The Labview API is out now and available to install and run
The documentation for C++ is also posted (direct link), and the API will follow shortly
The Java will be the last one to post, but it still should be out this coming week.
FIRMWARE UPDATE - As part of the new API release, we are also going to push a firmware update, which fixes some of the things beta teams were reporting (forward/backward switching delays, etc).
We want to be careful with the number of Firmware releases we do in the season to make it easy for teams, but these bugs were cause for a quick update.
I’ll make a post here when it is out, but it follows a similar time frame as the JAVA API
SPARK MAX Client We posted an update to the client today that fixes a few bugs, especially with teams who are using Windows 7, as it now installs the needed drivers automatically. We will be periodically updating this client adding new features throughout the season.
NEO Data sheet/curves - This is now posted on the product page (direct link).
As I mentioned previously there were some challenges we had with getting this data (I’ll save that for a later post).
We have published both our internal tested data and the theoretical performance data, This was done due to the fact that the NEO and MAX are a coupled system in FRC and we wanted to show the expected performance in FRC, but also what we expect the motor to be independent of the controller.
Admittedly (and probably obviously) we were working towards a smoother launch of MAX & NEO than we have done, but again we do appreciate the patience the community has shown and we will keep working around the clock to make sure you can get the experience that we had in mind when we designed the controller and motor.