@rhauch rhauch released this Feb 11, 2017 · 2 commits to master since this release

Assets 4

This is the second official release for the Strongback Java Library that works with the 2017 WPILib for Java (version 2017.1.1), the CTRE TalonSRX library (version 2017_v1), and the navX-MXP library (version 3.0.323). This release of Strongback is not compatible with versions of the WPILib for 2016 or earlier.

This release has the following changes since the 2017.1.0 release:

  • Fix the checkTolerance and initTable methods in SoftwarePIDController
  • Allow TalonControllers to be built from existing CANTalon instances.
  • Fix incorrect indices for Microsoft Sidewinder
  • Fix retract method in MockSolenoid
  • Added MecanumDrive functionality

To install or upgrade the Strongback Java Library on your computer, download and use the new standalone Strongback CLI client. You can use this utility to switch between any version of the Strongback Java Library as well as show what you already have installed. See the Getting Started guide for details.

This release uses the updated versioning scheme, in which the major release number now signifies the FRC season in which it was introduced. The WPILib for Java versioning scheme has also changed in a similar fashion, so it should be easier to match up a Strongback Java Library version with the appropriate versions of WPILib for Java.

@rhauch rhauch released this Jan 15, 2017 · 18 commits to master since this release

Assets 4

This is the first official release for the Strongback Java Library that works with the 2017 WPILib for Java (version 2017.1.1), the CTRE TalonSRX library (version 2017_v1), and the navX-MXP library (version 3.0.314). This release of Strongback is not compatible with versions of the WPILib for 2016 or earlier.

This release introduces the new versioning scheme, in which the major release number now signifies the FRC season in which it was introduced. The WPILib for Java versioning scheme has also changed in a similar fashion, so it should be easier to match up a Strongback Java Library version with the appropriate versions of WPILib for Java.

To install or upgrade the Strongback Java Library on your computer, download and use the new standalone Strongback CLI client. You can use this utility to switch between any version of the Strongback Java Library as well as show what you already have installed. See the Getting Started guide for details.

There are a few significant changes in this release compared to earlier 1.x releases:

  • Strongback 1.2 deprecated a number of APIs when it removed some unused features and simplified how Strongback is configured, and these deprecated APIs have now been removed.
  • The edu.wpi.first.wpilibj.CANTalon class in earlier versions of WPILib has been removed and superseded by the com.ctre.CANTalon class in the CTRE 3rd party dependency. If the CANTalon is used in robot code, simply change the import to the new package. However, not all robots that use Strongback will have used this class, and if so then no import changes will be required.
  • This version includes 3rd party libraries for CTRE's TalonSRX and Kauai Lab's navX-MXP devices. The new Strongback CLI client will automatically install these JARs and Strongback Java Library JAR as WPILib user libraries, which WPILib's deploy mechanisms will automatically deploy with your robot code.
  • If you want to write unit tests, you still need to install the Strongback User Library in Eclipse. See these instructions and the strongback new-project ... command in the Strongback CLI client.

Changes relative to the 2017.1.0-RC1 release candidate include:

  • Support for the officially released 2017.1.1 version of WPILib
  • Issue #93 that corrects the Hardware.Motors.victorSP(...) method that now properly uses the supplied speed limiter function
  • Issue #95 that adds support for the RevRobotics Spark Motor Controller
  • Issue #56 that simplifies the "cheesy drive" algorithm, but adds new overloaded methods to switch between this and the previous algorithm
Pre-release

@rhauch rhauch released this Jan 7, 2017 · 26 commits to master since this release

Assets 4

This is the first release candidate for the Strongback Java Library that works with the second release candidate (beta) of the 2017 WPILib for Java (version 2017.1.1.rc-2). This release of Strongback is not compatible with versions of the WPILib for 2016 or earlier.

This release introduces the new versioning scheme, in which the major release number now signifies the FRC season in which it was introduced. The WPILib for Java versioning scheme has also changed in a similar fashion, so it should be easier to match up a Strongback Java Library version with the appropriate versions of WPILib for Java.

To install or upgrade the Strongback Java Library on your computer, download and use the new standalone Strongback CLI client. You can use this utility to switch between any version of the Strongback Java Library as well as show what you already have installed. See the Getting Started guide for details.

There are a few significant changes in this release compared to earlier 1.x releases:

  • Strongback 1.2 deprecated a number of APIs when it removed some unused features and simplified how Strongback is configured, and these deprecated APIs have now been removed.
  • The edu.wpi.first.wpilibj.CANTalon class in earlier versions of WPILib has been removed and superseded by the com.ctre.CANTalon class in the CTRE 3rd party dependency. If the CANTalon is used in robot code, simply change the import to the new package. However, not all robots that use Strongback will have used this class, and if so then no import changes will be required.
  • This version includes 3rd party libraries for CTRE's TalonSRX and Kauai Lab's navX-MXP devices. The new Strongback CLI client will automatically install these JARs and Strongback Java Library JAR as WPILib user libraries, which WPILib's deploy mechanisms will automatically deploy with your robot code.
  • If you want to write unit tests, you still need to install the Strongback User Library in Eclipse. See these instructions and the strongback new-project ... command in the Strongback CLI client.

@rhauch rhauch released this Jan 3, 2017 · 43 commits to master since this release

Assets 4

This release of Strongback is compatible with the 2016 WPILib released for the 2016 season, and has been tested with WPILib version 201602112135, 0.1.0.201601151923 and 0.1.0.201601072029. This release of Strongback is not compatible with 2015 (or earlier) versions of WPILib.

This release changes how Strongback runs its execution thread to be more efficient and to correct when warnings about delayed execution are generated. This change does not remove or change any public API methods, and therefore no robot code needs to be changed. However, a few of the Strongback configuration options available in previous versions are no longer supported, so the corresponding methods in Strongback and its configurator are now deprecated and may no longer have any affect.

If you are upgrading a system that has an older version of Strongback, first remove the existing strongback installation directory completely before downloading and unpacking this newer version. The rest of your system (e.g., path, Eclipse workspace, or Eclipse projects) can be unchanged, and everything will simply pick up the new version. To verify you have the new version installed, the command line tool will now output the Strongback version if you run strongback.sh version on OS X and Linux, or strongback.bat version on Windows.

Pre-release

@rhauch rhauch released this Jan 2, 2017 · 45 commits to master since this release

Assets 4

Do not use this release. The new executor model had a serious bug such that Strongback never ran the medium and low priority executables. See issue #89.

This release of Strongback is compatible with the 2016 WPILib released for the 2016 season, and has been tested with WPILib version 201602112135, 0.1.0.201601151923 and 0.1.0.201601072029. This release of Strongback is not compatible with 2015 (or earlier) versions of WPILib.

This release changes how Strongback runs its execution thread to be more efficient and to correct when warnings about delayed execution are generated. This change does not remove or change any public API methods, and therefore no robot code needs to be changed. However, a few of the Strongback configuration options available in previous versions are no longer supported, so the corresponding methods in Strongback and its configurator are now deprecated and may no longer have any affect.

If you are upgrading a system that has an older version of Strongback, first remove the existing strongback installation directory completely before downloading and unpacking this newer version. The rest of your system (e.g., path, Eclipse workspace, or Eclipse projects) can be unchanged, and everything will simply pick up the new version. To verify you have the new version installed, the command line tool will now output the Strongback version if you run strongback.sh version on OS X and Linux, or strongback.bat version on Windows.

Pre-release

@rhauch rhauch released this Dec 22, 2016 · 49 commits to master since this release

Assets 4

More fixes after testing with real hardware.

Pre-release

@rhauch rhauch released this Dec 22, 2016 · 50 commits to master since this release

Assets 4

Additional fixes after testing with real hardware.

Pre-release

@rhauch rhauch released this Dec 22, 2016 · 51 commits to master since this release

Assets 4

Fixed several NPEs due to startup logic problems.

Pre-release

@rhauch rhauch released this Dec 21, 2016 · 54 commits to master since this release

Assets 4

This release of Strongback is compatible with the 2016 WPILib released for the 2016 season, and has been tested with WPILib version 201602112135, 0.1.0.201601151923 and 0.1.0.201601072029. This release of Strongback is not compatible with 2015 (or earlier) versions of WPILib.

This release changes how Strongback runs its execution thread to be more efficient and to correct when warnings about delayed execution are generated. This change does not remove or change any public API methods, and therefore no robot code needs to be changed. However, a few of the Strongback configuration options available in previous versions are no longer supported, so the corresponding methods in Strongback and its configurator are now deprecated and may no longer have any affect.

If you are upgrading a system that has an older version of Strongback, first remove the existing strongback installation directory completely before downloading and unpacking this newer version. The rest of your system (e.g., path, Eclipse workspace, or Eclipse projects) can be unchanged, and everything will simply pick up the new version. To verify you have the new version installed, the command line tool will now output the Strongback version if you run strongback.sh version on OS X and Linux, or strongback.bat version on Windows.