Welcome!

This GitHub repository contains the source code that is used to build an Android app to control a FIRST Tech Challenge competition robot. To use this SDK, download/clone the entire project to your local computer.

If you are new to the FIRST Tech Challenge software and control system, you should visit the online wiki to learn how to install, configure, and use the software and control system:

      https://github.com/ftctechnh/ftc_app/wiki

Note that the wiki is an "evergreen" document that is constantly being updated and edited. It contains the most current information about the FIRST Tech Challenge software and control system.

Downloading the Project

It is important to note that this repository is large and can take a long time and use a lot of space to download. If you would like to save time and space, there are some options that you can choose to download only the most current version of the Android project folder:

• If you are a git user, FIRST recommends that you use the --depth command line argument to only clone the most current version of the repository:

            git clone --depth=1 https://github.com/ftctechnh/ftc_app.git

• Or, if you prefer, you can use the "Download Zip" button available through the main repository page. Downloading the project as a .ZIP file will keep the size of the download manageable.

• You can also download the project folder (as a .zip or .tar.gz archive file) from the Downloads subsection of the Releases page for this repository.

Once you have downloaded and uncompressed (if needed) your folder, you can use Android Studio to import the folder ("Import project (Eclipse ADT, Gradle, etc.)").

Getting Help

User Documentation and Tutorials

FIRST maintains an online wiki with information and tutorials on how to use the FIRST Tech Challenge software and robot control system. You can access the wiki at the following address:

      https://github.com/ftctechnh/ftc_app/wiki

Javadoc Reference Material

The Javadoc reference documentation for the FTC SDK is now available online. Visit the following URL to view the FTC SDK documentation as a live website:

      http://ftctechnh.github.io/ftc_app/doc/javadoc/index.html

Documentation for the FTC SDK is also included with this repository. There is a subfolder called "doc" which contains several subfolders:

• The folder "apk" contains the .apk files for the FTC Driver Station and FTC Robot Controller apps.
• The folder "javadoc" contains the JavaDoc user documentation for the FTC SDK.

Online User Forum

For technical questions regarding the SDK, please visit the FTC Technology forum:

      http://ftcforum.usfirst.org/forumdisplay.php?156-FTC-Technology

---

Release Information

---

Version 4.3 (built on 18.10.31)

• Includes missing TensorFlow-related libraries and files.

---

Release Information

---

Version 4.2 (built on 18.10.30)

• Includes fix to avoid deadlock situation with WatchdogMonitor which could result in USB communication errors.
  • Comm error appeared to require that user disconnect USB cable and restart the Robot Controller app to recover.
  • robotControllerLog.txt would have error messages that included the words "E RobotCore: lynx xmit lock: #### abandoning lock:"
• Includes fix to correctly list the parent module address for a REV Robotics Expansion Hub in a configuration (.xml) file.
  • Bug in versions 4.0 and 4.1 would incorrect list the address module for a parent REV Robotics device as "1".
  • If the parent module had a higher address value than the daisy-chained module, then this bug would prevent the Robot Controller from communicating with the downstream Expansion Hub.
• Added requirement for ACCESS_COARSE_LOCATION to allow a Driver Station running Android Oreo to scan for Wi-Fi Direct devices.
• Added google() repo to build.gradle because aapt2 must be downloaded from the google() repository beginning with version 3.2 of the Android Gradle Plugin.
  • Important Note: Android Studio users will need to be connected to the Internet the first time build the ftc_app project.
  • Internet connectivity is required for the first build so the appropriate files can be downloaded from the Google repository.
  • Users should not need to be connected to the Internet for subsequent builds.
  • This should also fix buid issue where Android Studio would complain that it "Could not find com.android.tools.lint:lint-gradle:26.1.4" (or similar).
• Added support for REV Spark Mini motor controller as part of the configuration menu for a servo/PWM port on the REV Expansion Hub.
• Provide examples for playing audio files in an Op Mode.
• Block Development Tool Changes
  • Includes a fix for a problem with the Velocity blocks that were reported in the FTC Technology forum (Blocks Programming subforum).
  • Change the "Save completed successfully." message to a white color so it will contrast with a green background.
  • Fixed the "Download image" feature so it will work if there are text blocks in the op mode.
• Introduce support for Google's TensorFlow Lite technology for object detetion for 2018-2019 game.
  • TensorFlow lite can recognize Gold Mineral and Silver Mineral from 2018-2019 game.
  • Example Java and Block op modes are included to show how to determine the relative position of the gold block (left, center, right).

---

Release Information

---

Version 4.1 (released on 18.09.24)

Changes include:

• Fix to prevent crash when deprecated configuration annotations are used.
• Change to allow FTC Robot Controller APK to be auto-updated using FIRST Global Control Hub update scripts.
• Removed samples for non supported / non legal hardware.
• Improvements to Telemetry.addData block with "text" socket.
• Updated Blocks sample op mode list to include Rover Ruckus Vuforia example.
• Update SDK library version number.

---

Release Information

---

Version 4.0 (released on 18.09.12)

Changes include:

• Initial support for UVC compatible cameras

  • If UVC camera has a unique serial number, RC will detect and enumerate by serial number.
  • If UVC camera lacks a unique serial number, RC will only support one camera of that type connected.
  • Calibration settings for a few cameras are included (see TeamCode/src/main/res/xml/teamwebcamcalibrations.xml for details).
  • User can upload calibration files from Program and Manage web interface.
  • UVC cameras seem to draw a fair amount of electrical current from the USB bus.
    • This does not appear to present any problems for the REV Robotics Control Hub.
      • This does seem to create stability problems when using some cameras with an Android phone-based Robot Controller.
      • FTC Tech Team is investigating options to mitigate this issue with the phone-based Robot Controllers.
  • Updated sample Vuforia Navigation and VuMark Op Modes to demonstrate how to use an internal phone-based camera and an external UVC webcam.

• Support for improved motor control.

  • REV Robotics Expansion Hub firmware 1.8 and greater will support a feed forward mechanism for closed loop motor control.
  • FTC SDK has been modified to support PIDF coefficients (proportional, integral, derivative, and feed forward).
  • FTC Blocks development tool modified to include PIDF programming blocks.
  • Deprecated older PID-related methods and variables.
  • REV's 1.8.x PIDF-related changes provide a more linear and accurate way to control a motor.

• Wireless

  • Added 5GHz support for wireless channel changing for those devices that support it.
    • Tested with Moto G5 and E4 phones.
  • Also tested with other (currently non-approved) phones such as Samsung Galaxy S8.

• Improved Expansion Hub firmware update support in Robot Controller app

  • Changes to make the system more robust during the firmware update process (when performed through Robot Controller app).

  • User no longer has to disconnect a downstream daisy-chained Expansion Hub when updating an Expansion Hub's firmware.

    • If user is updating an Expansion Hub's firmware through a USB connection, he/she does not have to disconnect RS485 connection to other Expansion Hubs.

  • The user still must use a USB connection to update an Expansion Hub's firmware.

  • The user cannot update the Expansion Hub firmware for a downstream device that is daisy chained through an RS485 connection.

  • If an Expansion Hub accidentally gets "bricked" the Robot Controller app is now more likely to recognize the Hub when it scans the USB bus.

    • Robot Controller app should be able to detect an Expansion Hub, even if it accidentally was bricked in a previous update attempt.

  • Robot Controller app should be able to install the firmware onto the Hub, even if if accidentally was bricked in a previous update attempt.

  • Resiliency

  • FTC software can detect and enable an FTDI reset feature that is available with REV Robotics v1.8 Expansion Hub firmware and greater.

    • When enabled, the Expansion Hub can detect if it hasn't communicated with the Robot Controller over the FTDI (USB) connection.

  • If the Hub hasn't heard from the Robot Controller in a while, it will reset the FTDI connection.

  • This action helps system recover from some ESD-induced disruptions.

  • Various fixes to improve reliability of FTC software.

  • Blocks

  • Fixed errors with string and list indices in blocks export to java.

  • Support for USB connected UVC webcams.

  • Refactored optimized Blocks Vuforia code to support Rover Ruckus image targets.

  • Added programming blocks to support PIDF (proportional, integral, derivative and feed forward) motor control.

  • Added formatting options (under Telemetry and Miscellaneous categories) so user can set how many decimal places to display a numerical value.

  • Support to play audio files (which are uploaded through Blocks web interface) on Driver Station in addition to the Robot Controller.

  • Fixed bug with Download Image of Blocks feature.

  • Support for REV Robotics Blinkin LED Controller.

  • Support for REV Robotics 2m Distance Sensor.

  • Added support for a REV Touch Sensor (no longer have to configure as a generic digital device).

  • Added blocks for DcMotorEx methods.

    • These are enhanced methods that you can use when supported by the motor controller hardware.

  • The REV Robotics Expansion Hub supports these enhanced methods.

  • Enhanced methods include methods to get/set motor velocity (in encoder pulses per second), get/set PIDF coefficients, etc..

  • Modest Improvements in Logging

  • Decrease frequency of battery checker voltage statements.

  • Removed non-FTC related log statements (wherever possible).

  • Introduced a "Match Logging" feature.

    • Under "Settings" a user can enable/disable this feature (it's disabled by default).

  • If enabled, user provides a "Match Number" through the Driver Station user interface (top of the screen).

    • The Match Number is used to create a log file specifically with log statements from that particular Op Mode run.
    • Match log files are stored in /sdcard/FIRST/matlogs on the Robot Controller.
    • Once an op mode run is complete, the Match Number is cleared.
    • This is a convenient way to create a separate match log with statements only related to a specific op mode run.

  • New Devices

  • Support for REV Robotics Blinkin LED Controller.

  • Support for REV Robotics 2m Distance Sensor.

  • Added configuration option for REV 20:1 HD Hex Motor.

  • Added support for a REV Touch Sensor (no longer have to configure as a generic digital device).

  • Miscellaneous

  • Fixed some errors in the definitions for acceleration and velocity in our javadoc documentation.

  • Added ability to play audio files on Driver Station

  • When user is configuring an Expansion Hub, the LED on the Expansion Hub will change blink pattern (purple-cyan) to indicate which Hub is currently being configured.

  • Renamed I2cSensorType to I2cDeviceType.

  • Added an external sample Op Mode that demonstrates localization using 2018-2019 (Rover Ruckus presented by QualComm) Vuforia targets.

  • Added an external sample Op Mode that demonstrates how to use the REV Robotics 2m Laser Distance Sensor.

  • Added an external sample Op Mode that demonstrates how to use the REV Robotics Blinkin LED Controller.

  • Re-categorized external Java sample Op Modes to "TeleOp" instead of "Autonomous".

Known issues:

• Initial support for UVC compatible cameras

  • UVC cameras seem to draw significant amount of current from the USB bus.
    • This does not appear to present any problems for the REV Robotics Control Hub.
  • This does seem to create stability problems when using some cameras with an Android phone-based Robot Controller.
  • FTC Tech Team is investigating options to mitigate this issue with the phone-based Robot Controllers.
  • There might be a possible deadlock which causes the RC to become unresponsive when using a UVC webcam with a Nougat Android Robot Controller.

• Wireless

  • When user selects a wireless channel, this channel does not necessarily persist if the phone is power cycled.
    • Tech Team is hoping to eventually address this issue in a future release.
  • Issue has been present since apps were introduced (i.e., it is not new with the v4.0 release).
  • Wireless channel is not currently displayed for WiFi Direct connections.

• Miscellaneous

  • The blink indication feature that shows which Expansion Hub is currently being configured does not work for a newly created configuration file.
    • User has to first save a newly created configuration file and then close and re-edit the file in order for blink indicator to work.

---

Release Information

---

Version 3.6 (built on 17.12.18)

Changes include:

• Blocks Changes
  • Uses updated Google Blockly software to allow users to edit their op modes on Apple iOS devices (including iPad and iPhone).
  • Improvement in Blocks tool to handle corrupt op mode files.
  • Autonomous op modes should no longer get switched back to tele-op after re-opening them to be edited.
  • The system can now detect type mismatches during runtime and alert the user with a message on the Driver Station.
• Updated javadoc documentation for setPower() method to reflect correct range of values (-1 to +1).
• Modified VuforiaLocalizerImpl to allow for user rendering of frames
  • Added a user-overrideable onRenderFrame() method which gets called by the class's renderFrame() method.

---

Release Information

---

Version 3.5 (built on 17.10.30)

Changes with version 3.5 include:

• Introduced a fix to prevent random op mode stops, which can occur after the Robot Controller app has been paused and then resumed (for example, when a user temporarily turns off the display of the Robot Controller phone, and then turns the screen back on).
• Introduced a fix to prevent random op mode stops, which were previously caused by random peer disconnect events on the Driver Station.
• Fixes issue where log files would be closed on pause of the RC or DS, but not re-opened upon resume.
• Fixes issue with battery handler (voltage) start/stop race.
• Fixes issue where Android Studio generated op modes would disappear from available list in certain situations.
• Fixes problem where OnBot Java would not build on REV Robotics Control Hub.
• Fixes problem where OnBot Java would not build if the date and time on the Robot Controller device was "rewound" (set to an earlier date/time).
• Improved error message on OnBot Java that occurs when renaming a file fails.
• Removed unneeded resources from android.jar binaries used by OnBot Java to reduce final size of Robot Controller app.
• Added MR_ANALOG_TOUCH_SENSOR block to Blocks Programming Tool.

---

Release Information

---

Version 3.4 (built on 17.09.06)

Changes with version 3.4 include:

• Added telemetry.update() statement for BlankLinearOpMode template.
• Renamed sample Block op modes to be more consistent with Java samples.
• Added some additional sample Block op modes.
• Reworded OnBot Java readme slightly.

---

Version 3.3 (built on 17.09.04)

This version of the software includes improves for the FTC Blocks Programming Tool and the OnBot Java Programming Tool.

Changes with verion 3.3 include:

• Android Studio ftc_app project has been updated to use Gradle Plugin 2.3.3.
• Android Studio ftc_app project is already using gradle 3.5 distribution.
• Robot Controller log has been renamed to /sdcard/RobotControllerLog.txt (note that this change was actually introduced w/ v3.2).
• Improvements in I2C reliability.
• Optimized I2C read for REV Expansion Hub, with v1.7 firmware or greater.
• Updated all external/samples (available through OnBot and in Android project folder).
• Vuforia
  • Added support for VuMarks that will be used for the 2017-2018 season game.
• Blocks
  • Update to latest Google Blockly release.
  • Sample op modes can be selected as a template when creating new op mode.
  • Fixed bug where the blocks would disappear temporarily when mouse button is held down.
  • Added blocks for Range.clip and Range.scale.
  • User can now disable/enable Block op modes.
  • Fix to prevent occasional Blocks deadlock.
• OnBot Java
  • Significant improvements with autocomplete function for OnBot Java editor.
  • Sample op modes can be selected as a template when creating new op mode.
  • Fixes and changes to complete hardware setup feature.
  • Updated (and more useful) onBot welcome message.

Known issues:

• Android Studio
  • After updating to the new v3.3 Android Studio project folder, if you get error messages indicating "InvalidVirtualFileAccessException" then you might need to do a File->Invalidate Caches / Restart to clear the error.
• OnBot Java
  • Sometimes when you push the build button to build all op modes, the RC returns an error message that the build failed. If you press the build button a second time, the build typically suceeds.

---

Version 3.2 (built on 17.08.02)

This version of the software introduces the "OnBot Java" Development Tool. Similar to the FTC Blocks Development Tool, the FTC OnBot Java Development Tool allows a user to create, edit and build op modes dynamically using only a Javascript-enabled web browser.

The OnBot Java Development Tool is an integrated development environment (IDE) that is served up by the Robot Controller. Op modes are created and edited using a Javascript-enabled browser (Google Chromse is recommended). Op modes are saved on the Robot Controller Android device directly.

The OnBot Java Development Tool provides a Java programming environment that does NOT need Android Studio.

Changes with version 3.2 include:

• Enhanced web-based development tools
  • Introduction of OnBot Java Development Tool.
  • Web-based programming and management features are "always on" (user no longer needs to put Robot Controller into programming mode).
  • Web-based management interface (where user can change Robot Controller name and also easily download Robot Controller log file).
  • OnBot Java, Blocks and Management features available from web based interface.

• Blocks Programming Development Tool:

  • Changed "LynxI2cColorRangeSensor" block to "REV Color/range sensor" block.
  • Fixed tooltip for ColorSensor.isLightOn block. Added blocks for ColorSensor.getNormalizedColors and LynxI2cColorRangeSensor.getNormalizedColors.

• Added example op modes for digital touch sensor and REV Robotics Color Distance sensor.

• User selectable color themes.

• Includes many minor enhancements and fixes (too numerous to list).

Known issues:

• Auto complete function is incomplete and does not support the following (for now):
  • Access via this keyword
  • Access via super keyword
  • Members of the super cloass, not overridden by the class
  • Any methods provided in the current class
  • Inner classes
  • Can't handle casted objects
  • Any objects coming from an parenthetically enclosed expression

---

Version 3.10 (built on 17.05.09)

This version of the software provides support for the REV Robotics Expansion Hub. This version also includes improvements in the USB communication layer in an effort to enhance system resiliency. If you were using a 2.x version of the software previously, updating to version 3.1 requires that you also update your Driver Station software in addition to updating the Robot Controller software.

Also note that in version 3.10 software, the setMaxSpeed and getMaxSpeed methods are no longer available (not deprecated, they have been removed from the SDK). Also note that the the new 3.x software incorporates motor profiles that a user can select as he/she configures the robot.

Changes include:

• Blocks changes
  • Added VuforiaTrackableDefaultListener.getPose and Vuforia.trackPose blocks.
  • Added optimized blocks support for Vuforia extended tracking.
  • Added atan2 block to the math category.
  • Added useCompetitionFieldTargetLocations parameter to Vuforia.initialize block. If set to false, the target locations are placed at (0,0,0) with target orientation as specified in https://github.com/gearsincorg/FTCVuforiaDemo/blob/master/Robot_Navigation.java tutorial op mode.
• Incorporates additional improvements to USB comm layer to improve system resiliency (to recover from a greater number of communication disruptions).

---

Additional Notes Regarding Version 3.00 (built on 17.04.13)

In addition to the release changes listed below (see section labeled "Version 3.00 (built on 17.04.013)"), version 3.00 has the following important changes:

1. Version 3.00 software uses a new version of the FTC Robocol (robot protocol). If you upgrade to v3.0 on the Robot Controller and/or Android Studio side, you must also upgrade the Driver Station software to match the new Robocol.
2. Version 3.00 software removes the setMaxSpeed and getMaxSpeed methods from the DcMotor class. If you have an op mode that formerly used these methods, you will need to remove the references/calls to these methods. Instead, v3.0 provides the max speed information through the use of motor profiles that are selected by the user during robot configuration.
3. Version 3.00 software currently does not have a mechanism to disable extra i2c sensors. We hope to re-introduce this function with a release in the near future.

---

Version 3.00 (built on 17.04.13)

Use this version of the software at YOUR OWN RISK!!!

This software is being released as an "alpha" version. Use this version at your own risk!

This pre-release software contains SIGNIFICANT changes, including changes to the Wi-Fi Direct pairing mechanism, rewrites of the I2C sensor classes, changes to the USB/FTDI layer, and the introduction of support for the REV Robotics Expansion Hub and the REV Robotics color-range-light sensor. These changes were implemented to improve the reliability and resiliency of the FTC control system.

Please note, however, that version 3.00 is considered "alpha" code. This code is being released so that the FIRST community will have an opportunity to test the new REV Expansion Hub electronics module when it becomes available in May. The developers do not recommend using this code for critical applications (i.e., competition use).

Use this version of the software at YOUR OWN RISK!!!

Changes include:

• Major rework of sensor-related infrastructure. Includes rewriting sensor classes to implement synchronous I2C communication.
• Fix to reset Autonomous timer back to 30 seconds.
• Implementation of specific motor profiles for approved 12V motors (includes Tetrix, AndyMark, Matrix and REV models).
• Modest improvements to enhance Wi-Fi P2P pairing.
• Fixes telemetry log addition race.
• Publishes all the sources (not just a select few).
• Includes Block programming improvements
  • Addition of optimized Vuforia blocks.
  • Auto scrollbar to projects and sounds pages.
  • Fixed blocks paste bug.
  • Blocks execute after while-opModeIsActive loop (to allow for cleanup before exiting op mode).
  • Added gyro integratedZValue block.
  • Fixes bug with projects page for Firefox browser.
  • Added IsSpeaking block to AndroidTextToSpeech.
• Implements support for the REV Robotics Expansion Hub
  • Implements support for integral REV IMU (physically installed on I2C bus 0, uses same Bosch BNO055 9 axis absolute orientation sensor as Adafruit 9DOF abs orientation sensor). - Implements support for REV color/range/light sensor.
  • Provides support to update Expansion Hub firmware through FTC SDK.
  • Detects REV firmware version and records in log file.
  • Includes support for REV Control Hub (note that the REV Control Hub is not yet approved for FTC use).
  • Implements FTC Blocks programming support for REV Expansion Hub and sensor hardware.
  • Detects and alerts when I2C device disconnect.

---

Version 2.62 (built on 17.01.07)

• Added null pointer check before calling modeToByte() in finishModeSwitchIfNecessary method for ModernRoboticsUsbDcMotorController class.
• Changes to enhance Modern Robotics USB protocol robustness.

---

Version 2.61 (released on 16.12.19)

• Blocks Programming mode changes:
  • Fix to correct issue when an exception was thrown because an OpticalDistanceSensor object appears twice in the hardware map (the second time as a LightSensor).

---

Version 2.6 (released on 16.12.16)

• Fixes for Gyro class:
  • Improve (decrease) sensor refresh latency.
  • fix isCalibrating issues.
• Blocks Programming mode changes:
  • Blocks now ignores a device in the configuration xml if the name is empty. Other devices work in configuration work fine.

---

Version 2.5 (internal release on released on 16.12.13)

• Blocks Programming mode changes:
  • Added blocks support for AdafruitBNO055IMU.
  • Added Download Op Mode button to FtcBocks.html.
  • Added support for copying blocks in one OpMode and pasting them in an other OpMode. The clipboard content is stored on the phone, so the programming mode server must be running.
  • Modified Utilities section of the toolbox.
  • In Programming Mode, display information about the active connections.
  • Fixed paste location when workspace has been scrolled.
  • Added blocks support for the android Accelerometer.
  • Fixed issue where Blocks Upload Op Mode truncated name at first dot.
  • Added blocks support for Android SoundPool.
  • Added type safety to blocks for Acceleration.
  • Added type safety to blocks for AdafruitBNO055IMU.Parameters.
  • Added type safety to blocks for AnalogInput.
  • Added type safety to blocks for AngularVelocity.
  • Added type safety to blocks for Color.
  • Added type safety to blocks for ColorSensor.
  • Added type safety to blocks for CompassSensor.
  • Added type safety to blocks for CRServo.
  • Added type safety to blocks for DigitalChannel.
  • Added type safety to blocks for ElapsedTime.
  • Added type safety to blocks for Gamepad.
  • Added type safety to blocks for GyroSensor.
  • Added type safety to blocks for IrSeekerSensor.
  • Added type safety to blocks for LED.
  • Added type safety to blocks for LightSensor.
  • Added type safety to blocks for LinearOpMode.
  • Added type safety to blocks for MagneticFlux.
  • Added type safety to blocks for MatrixF.
  • Added type safety to blocks for MrI2cCompassSensor.
  • Added type safety to blocks for MrI2cRangeSensor.
  • Added type safety to blocks for OpticalDistanceSensor.
  • Added type safety to blocks for Orientation.
  • Added type safety to blocks for Position.
  • Added type safety to blocks for Quaternion.
  • Added type safety to blocks for Servo.
  • Added type safety to blocks for ServoController.
  • Added type safety to blocks for Telemetry.
  • Added type safety to blocks for Temperature.
  • Added type safety to blocks for TouchSensor.
  • Added type safety to blocks for UltrasonicSensor.
  • Added type safety to blocks for VectorF.
  • Added type safety to blocks for Velocity.
  • Added type safety to blocks for VoltageSensor.
  • Added type safety to blocks for VuforiaLocalizer.Parameters.
  • Added type safety to blocks for VuforiaTrackable.
  • Added type safety to blocks for VuforiaTrackables.
  • Added type safety to blocks for enums in AdafruitBNO055IMU.Parameters.
  • Added type safety to blocks for AndroidAccelerometer, AndroidGyroscope, AndroidOrientation, and AndroidTextToSpeech.

---

Version 2.4 (released on 16.11.13)

• Fix to avoid crashing for nonexistent resources.
• Blocks Programming mode changes:
  • Added blocks to support OpenGLMatrix, MatrixF, and VectorF.
  • Added blocks to support AngleUnit, AxesOrder, AxesReference, CameraDirection, CameraMonitorFeedback, DistanceUnit, and TempUnit.
  • Added blocks to support Acceleration.
  • Added blocks to support LinearOpMode.getRuntime.
  • Added blocks to support MagneticFlux and Position.
  • Fixed typos.
  • Made blocks for ElapsedTime more consistent with other objects.
  • Added blocks to support Quaternion, Velocity, Orientation, AngularVelocity.
  • Added blocks to support VuforiaTrackables, VuforiaTrackable, VuforiaLocalizer, VuforiaTrackableDefaultListener.
  • Fixed a few blocks.
  • Added type checking to new blocks.
  • Updated to latest blockly.
  • Added default variable blocks to navigation and matrix blocks.
  • Fixed toolbox entry for openGLMatrix_rotation_withAxesArgs.
  • When user downloads Blocks-generated op mode, only the .blk file is downloaded.
  • When user uploads Blocks-generated op mode (.blk file), Javascript code is auto generated.
  • Added DbgLog support.
  • Added logging when a blocks file is read/written.
  • Fixed bug to properly render blocks even if missing devices from configuration file.
  • Added support for additional characters (not just alphanumeric) for the block file names (for download and upload).
  • Added support for OpMode flavor (“Autonomous” or “TeleOp”) and group.
• Changes to Samples to prevent tutorial issues.
• Incorporated suggested changes from public pull 216 (“Replace .. paths”).
• Remove Servo Glitches when robot stopped.
• if user hits “Cancels” when editing a configuration file, clears the unsaved changes and reverts to original unmodified configuration.
• Added log info to help diagnose why the Robot Controller app was terminated (for example, by watch dog function).
• Added ability to transfer log from the controller.
• Fixed inconsistency for AngularVelocity
• Limit unbounded growth of data for telemetry. If user does not call telemetry.update() for LinearOpMode in a timely manner, data added for telemetry might get lost if size limit is exceeded.

---

Version 2.35 (released on 16.10.06)

• Blockly programming mode - Removed unnecesary idle() call from blocks for new project.

---

Version 2.30 (released on 16.10.05)

• Blockly programming mode:
  • Mechanism added to save Blockly op modes from Programming Mode Server onto local device
  • To avoid clutter, blocks are displayed in categorized folders
  • Added support for DigitalChannel
  • Added support for ModernRoboticsI2cCompassSensor
  • Added support for ModernRoboticsI2cRangeSensor
  • Added support for VoltageSensor
  • Added support for AnalogInput
  • Added support for AnalogOutput
  • Fix for CompassSensor setMode block
• Vuforia
  • Fix deadlock / make camera data available while Vuforia is running.
  • Update to Vuforia 6.0.117 (recommended by Vuforia and Google to close security loophole).
• Fix for autonomous 30 second timer bug (where timer was in effect, even though it appeared to have timed out).
• opModeIsActive changes to allow cleanup after op mode is stopped (with enforced 2 second safety timeout).
• Fix to avoid reading i2c twice.
• Updated sample Op Modes.
• Improved logging and fixed intermittent freezing.
• Added digital I/O sample.
• Cleaned up device names in sample op modes to be consistent with Pushbot guide.
• Fix to allow use of IrSeekerSensorV3.

---

Version 2.20 (released on 16.09.08)

• Support for Modern Robotics Compass Sensor.
• Support for Modern Robotics Range Sensor.
• Revise device names for Pushbot templates to match the names used in Pushbot guide.
• Fixed bug so that IrSeekerSensorV3 device is accessible as IrSeekerSensor in hardwareMap.
• Modified computer vision code to require an individual Vuforia license (per legal requirement from PTC).
• Minor fixes.
• Blockly enhancements:
  • Support for Voltage Sensor.
  • Support for Analog Input.
  • Support for Analog Output.
  • Support for Light Sensor.
  • Support for Servo Controller.

---

Version 2.10 (released on 16.09.03)

• Support for Adafruit IMU.
• Improvements to ModernRoboticsI2cGyro class
  • Block on reset of z axis.
  • isCalibrating() returns true while gyro is calibration.
• Updated sample gyro program.
• Blockly enhancements
  • support for android.graphics.Color.
  • added support for ElapsedTime.
  • improved look and legibility of blocks.
  • support for compass sensor.
  • support for ultrasonic sensor.
  • support for IrSeeker.
  • support for LED.
  • support for color sensor.
  • support for CRServo
  • prompt user to configure robot before using programming mode.
• Provides ability to disable audio cues.
• various bug fixes and improvements.

---

Version 2.00 (released on 16.08.19)

• This is the new release for the upcoming 2016-2017 FIRST Tech Challenge Season.
• Channel change is enabled in the FTC Robot Controller app for Moto G 2nd and 3rd Gen phones.
• Users can now use annotations to register/disable their Op Modes.
• Changes in the Android SDK, JDK and build tool requirements (minsdk=19, java 1.7, build tools 23.0.3).
• Standardized units in analog input.
• Cleaned up code for existing analog sensor classes.
• setChannelMode and getChannelMode were REMOVED from the DcMotorController class. This is important - we no longer set the motor modes through the motor controller.
• setMode and getMode were added to the DcMotor class.
• ContinuousRotationServo class has been added to the FTC SDK.
• Range.clip() method has been overloaded so it can support this operation for int, short and byte integers.
• Some changes have been made (new methods added) on how a user can access items from the hardware map.
• Users can now set the zero power behavior for a DC motor so that the motor will brake or float when power is zero.
• Prototype Blockly Programming Mode has been added to FTC Robot Controller. Users can place the Robot Controller into this mode, and then use a device (such as a laptop) that has a Javascript enabled browser to write Blockly-based Op Modes directly onto the Robot Controller.
• Users can now configure the robot remotely through the FTC Driver Station app.
• Android Studio project supports Android Studio 2.1.x and compile SDK Version 23 (Marshmallow).
• Vuforia Computer Vision SDK integrated into FTC SDK. Users can use sample vision targets to get localization information on a standard FTC field.
• Project structure has been reorganized so that there is now a TeamCode package that users can use to place their local/custom Op Modes into this package.
• Inspection function has been integrated into the FTC Robot Controller and Driver Station Apps (Thanks Team HazMat… 9277 & 10650!).
• Audio cues have been incorporated into FTC SDK.
• Swap mechanism added to FTC Robot Controller configuration activity. For example, if you have two motor controllers on a robot, and you misidentified them in your configuration file, you can use the Swap button to swap the devices within the configuration file (so you do not have to manually re-enter in the configuration info for the two devices).
• Fix mechanism added to all user to replace an electronic module easily. For example, suppose a servo controller dies on your robot. You replace the broken module with a new module, which has a different serial number from the original servo controller. You can use the Fix button to automatically reconfigure your configuration file to use the serial number of the new module.
• Improvements made to fix resiliency and responsiveness of the system.
• For LinearOpMode the user now must for a telemetry.update() to update the telemetry data on the driver station. This update() mechanism ensures that the driver station gets the updated data properly and at the same time.
• The Auto Configure function of the Robot Controller is now template based. If there is a commonly used robot configuration, a template can be created so that the Auto Configure mechanism can be used to quickly configure a robot of this type.
• The logic to detect a runaway op mode (both in the LinearOpMode and OpMode types) and to abort the run, then auto recover has been improved/implemented.
• Fix has been incorporated so that Logitech F310 gamepad mappings will be correct for Marshmallow users.

---

Release 16.07.08

• For the ftc_app project, the gradle files have been modified to support Android Studio 2.1.x.

---

Release 16.03.30

• For the MIT App Inventor, the design blocks have new icons that better represent the function of each design component.
• Some changes were made to the shutdown logic to ensure the robust shutdown of some of our USB services.
• A change was made to LinearOpMode so as to allow a given instance to be executed more than once, which is required for the App Inventor.
• Javadoc improved/updated.

---

Release 16.03.09

• Changes made to make the FTC SDK synchronous (significant change!)
  • waitOneFullHardwareCycle() and waitForNextHardwareCycle() are no longer needed and have been deprecated.
  • runOpMode() (for a LinearOpMode) is now decoupled from the system's hardware read/write thread.
  • loop() (for an OpMode) is now decoupled from the system's hardware read/write thread.
  • Methods are synchronous.
  • For example, if you call setMode(DcMotorController.RunMode.RESET_ENCODERS) for a motor, the encoder is guaranteed to be reset when the method call is complete.
  • For legacy module (NXT compatible), user no longer has to toggle between read and write modes when reading from or writing to a legacy device.
• Changes made to enhance reliability/robustness during ESD event.
• Changes made to make code thread safe.
• Debug keystore added so that user-generated robot controller APKs will all use the same signed key (to avoid conflicts if a team has multiple developer laptops for example).
• Firmware version information for Modern Robotics modules are now logged.
• Changes made to improve USB comm reliability and robustness.
• Added support for voltage indicator for legacy (NXT-compatible) motor controllers.
• Changes made to provide auto stop capabilities for op modes.
  • A LinearOpMode class will stop when the statements in runOpMode() are complete. User does not have to push the stop button on the driver station.
  • If an op mode is stopped by the driver station, but there is a run away/uninterruptible thread persisting, the app will log an error message then force itself to crash to stop the runaway thread.
• Driver Station UI modified to display lowest measured voltage below current voltage (12V battery).
• Driver Station UI modified to have color background for current voltage (green=good, yellow=caution, red=danger, extremely low voltage).
• javadoc improved (edits and additional classes).
• Added app build time to About activity for driver station and robot controller apps.
• Display local IP addresses on Driver Station About activity.
• Added I2cDeviceSynchImpl.
• Added I2cDeviceSync interface.
• Added seconds() and milliseconds() to ElapsedTime for clarity.
• Added getCallbackCount() to I2cDevice.
• Added missing clearI2cPortActionFlag.
• Added code to create log messages while waiting for LinearOpMode shutdown.
• Fix so Wifi Direct Config activity will no longer launch multiple times.
• Added the ability to specify an alternate i2c address in software for the Modern Robotics gyro.

---

Release 16.02.09

• Improved battery checker feature so that voltage values get refreshed regularly (every 250 msec) on Driver Station (DS) user interface.
• Improved software so that Robot Controller (RC) is much more resilient and “self-healing” to USB disconnects:
  • If user attempts to start/restart RC with one or more module missing, it will display a warning but still start up.
  • When running an op mode, if one or more modules gets disconnected, the RC & DS will display warnings,and robot will keep on working in spite of the missing module(s).
  • If a disconnected module gets physically reconnected the RC will auto detect the module and the user will regain control of the recently connected module.
  • Warning messages are more helpful (identifies the type of module that’s missing plus its USB serial number).
• Code changes to fix the null gamepad reference when users try to reference the gamepads in the init() portion of their op mode.
• NXT light sensor output is now properly scaled. Note that teams might have to readjust their light threshold values in their op modes.
• On DS user interface, gamepad icon for a driver will disappear if the matching gamepad is disconnected or if that gamepad gets designated as a different driver.
• Robot Protocol (ROBOCOL) version number info is displayed in About screen on RC and DS apps.
• Incorporated a display filter on pairing screen to filter out devices that don’t use the “-“ format. This filter can be turned off to show all WiFi Direct devices.
• Updated text in License file.
• Fixed formatting error in OpticalDistanceSensor.toString().
• Fixed issue on with a blank (“”) device name that would disrupt WiFi Direct Pairing.
• Made a change so that the WiFi info and battery info can be displayed more quickly on the DS upon connecting to RC.
• Improved javadoc generation.
• Modified code to make it easier to support language localization in the future.

---

Release 16.01.04

• Updated compileSdkVersion for apps
• Prevent Wifi from entering power saving mode
• removed unused import from driver station
• Corrrected "Dead zone" joystick code.
• LED.getDeviceName and .getConnectionInfo() return null
• apps check for ROBOCOL_VERSION mismatch
• Fix for Telemetry also has off-by-one errors in its data string sizing / short size limitations error
• User telemetry output is sorted.
• added formatting variants to DbgLog and RobotLog APIs
• code modified to allow for a long list of op mode names.
• changes to improve thread safety of RobocolDatagramSocket
• Fix for "missing hardware leaves robot controller disconnected from driver station" error
• fix for "fast tapping of Init/Start causes problems" (toast is now only instantiated on UI thread).
• added some log statements for thread life cycle.
• moved gamepad reset logic inside of initActiveOpMode() for robustness
• changes made to mitigate risk of race conditions on public methods.
• changes to try and flag when WiFi Direct name contains non-printable characters.
• fix to correct race condition between .run() and .close() in ReadWriteRunnableStandard.
• updated FTDI driver
• made ReadWriteRunnableStanard interface public.
• fixed off-by-one errors in Command constructor
• moved specific hardware implmentations into their own package.
• moved specific gamepad implemnatations to the hardware library.
• changed LICENSE file to new BSD version.
• fixed race condition when shutting down Modern Robotics USB devices.
• methods in the ColorSensor classes have been synchronized.
• corrected isBusy() status to reflect end of motion.
• corrected "back" button keycode.
• the notSupported() method of the GyroSensor class was changed to protected (it should not be public).

---

Release 15.11.04.001

• Added Support for Modern Robotics Gyro.
  • The GyroSensor class now supports the MR Gyro Sensor.
  • Users can access heading data (about Z axis)
  • Users can also access raw gyro data (X, Y, & Z axes).
  • Example MRGyroTest.java op mode included.
• Improved error messages
  • More descriptive error messages for exceptions in user code.
• Updated DcMotor API
• Enable read mode on new address in setI2cAddress
• Fix so that driver station app resets the gamepads when switching op modes.
• USB-related code changes to make USB comm more responsive and to display more explicit error messages.
  • Fix so that USB will recover properly if the USB bus returns garbage data.
  • Fix USB initializtion race condition.
  • Better error reporting during FTDI open.
  • More explicit messages during USB failures.
  • Fixed bug so that USB device is closed if event loop teardown method was not called.
• Fixed timer UI issue
• Fixed duplicate name UI bug (Legacy Module configuration).
• Fixed race condition in EventLoopManager.
• Fix to keep references stable when updating gamepad.
• For legacy Matrix motor/servo controllers removed necessity of appending "Motor" and "Servo" to controller names.
• Updated HT color sensor driver to use constants from ModernRoboticsUsbLegacyModule class.
• Updated MR color sensor driver to use constants from ModernRoboticsUsbDeviceInterfaceModule class.
• Correctly handle I2C Address change in all color sensors
• Updated/cleaned up op modes.
  • Updated comments in LinearI2cAddressChange.java example op mode.
  • Replaced the calls to "setChannelMode" with "setMode" (to match the new of the DcMotor method).
  • Removed K9AutoTime.java op mode.
  • Added MRGyroTest.java op mode (demonstrates how to use MR Gyro Sensor).
  • Added MRRGBExample.java op mode (demonstrates how to use MR Color Sensor).
  • Added HTRGBExample.java op mode (demonstrates how to use HT legacy color sensor).
  • Added MatrixControllerDemo.java (demonstrates how to use legacy Matrix controller).
• Updated javadoc documentation.
• Updated release .apk files for Robot Controller and Driver Station apps.

T. Eng November 5, 2015

---

Release 15.10.06.002

• Added support for Legacy Matrix 9.6V motor/servo controller.
• Cleaned up build.gradle file.
• Minor UI and bug fixes for driver station and robot controller apps.
• Throws error if Ultrasonic sensor (NXT) is not configured for legacy module port 4 or 5.

T. Eng October 6, 2015

---

In this latest version of the FTC SDK (20150803_001) the following changes should be noted:

• New user interfaces for FTC Driver Station and FTC Robot Controller apps.
• An init() method is added to the OpMode class.
  • For this release, init() is triggered right before the start() method.
  • Eventually, the init() method will be triggered when the user presses an "INIT" button on driver station.
  • The init() and loop() methods are now required (i.e., need to be overridden in the user's op mode).
  • The start() and stop() methods are optional.
• A new LinearOpMode class is introduced.
  • Teams can use the LinearOpMode mode to create a linear (not event driven) program model.
  • Teams can use blocking statements like Thread.sleep() within a linear op mode.
• The API for the Legacy Module and Core Device Interface Module have been updated.
  • Support for encoders with the Legacy Module is now working.
• The hardware loop has been updated for better performance.

T. Eng August 3, 2015