- The behavior of setGlobalErrorMsg() is changed. Note that this is an SDK internal method that is not meant to be used by team software or third party libraries. Teams or libraries using this method should find another means to communicate failure. The design intent of setGlobalErrorMsg() is to report an error and force the user to restart the robot, which in certain circumstances when used inappropriately could cause a robot to continue running while Driver Station controls are disabled. To prevent this, processing of a call to setGlobalErrorMsg() is deferred until the robot is in a known safe state. This may mean that a call to setGlobalErrorMsg() that does not also result in stopping a running OpMode will appear as though nothing happened until the robot is stopped, at which point, if clearGlobalErrorMsg() has not been called the message will appear on the Driver Station and a restart will be required. Addresses issue 1381
- Fixes getLatestResult in Limelight3A so if the Limelight hasn't provided data yet, it still returns an LLResult but valid will be false
- If you previously used to check and see if this was
nullto see if the Limelight had been contacted, you now need to useisValid()on the result. That is because now it always returns an LLResult even before it talks to the Limelight, but if it doesn't have valid data, theisValid()will befalse.
- If you previously used to check and see if this was
- Changed all omni samples to use front_left_drive, front_right_drive, back_left_drive, back_right_drive
- This is only breaking for you if you copy one of the changed samples to your own project and expect to use the same robot configuration as before.
- The redesigned OnBotJava new file workflow allows the user to use a lowercase letter as the first character of a filename. This is a regression from 10.2 which required the first character to be uppercase. Software will build, but if the user tries to rename the file, the rename will fail.
- Improved the OBJ new file creation flow workflow. The new flow allows you to easily use samples, craft new custom OpModes and make new Java classes.
- Added support for gamepad edge detection.
- A new sample program
ConceptGamepadEdgeDetectiondemonstrates its use.
- A new sample program
- Adds a blackboard member to the Opmode that maintains state between opmodes (but not between robot resets). See the ConceptBlackboard sample for how to use it.
- Updated PredominantColorProcessor to also return the predominant color in RGB, HSV and YCrCb color spaces. Updated ConceptVisionColorSensor sample OpMode to display the getAnalysis() result in all three color spaces.
- Adds support for the GoBilda Pinpoint
- Also adds
SensorGoBildaPinpointsample to show how to use it
- Also adds
- Added
getArcLength()andgetCircularity()to ColorBlobLocatorProcessor.Blob. Added BY_ARC_LENGTH and BY_CIRCULARITY as additional BlobCriteria. - Added
filterByCriteria()andsortByCriteria()to ColorBlobLocatorProcessor.Util.- The filter and sort methods for specific criteria have been deprecated.
- The updated sample program
ConceptVisionColorLocatorprovides more details on the new syntax.
- Add Help menu item and Help page that is available when connected to the robot controller via Program and Manage. The Help page has links to team resources such as FTC Documentation, FTC Discussion Forums, Java FTC SDK API Documentation, and FTC Game Information.
- Self inspection changes:
- List both the Driver Station Name and Robot Controller Name when inspecting the Driver Station.
- Report if the team number portion of the device names do not match.
- -rc is no longer valid as part of a Robot Controller name, must be -RC.
- Use Robot Controller Name or Driver Station Name labels on the inspection screens instead of WIFI Access Point or WIFI Direct Name.
- Fixes issue 1478 in AnnotatedHooksClassFilter that ignored exceptions if they occur in one of the SDK app hooks.
- Fix initialize in distance sensor (Rev 2m) to prevent bad data in first call to getDistance.
- Fixes issue 1470 Scaling a servo range is now irrespective of reverse() being called. For example, if you set the scale range to [0.0, 0.5] and the servo is reversed, it will be from 0.5 to 0.0, NOT 1.0 to 0.5.
- Fixes issue 1232, a rare race condition where using the log rapidly along with other telemetry could cause a crash.