FTC RobotController(SDK) v6.2发布

FTC RobotController(SDK) v6.2发布

张北一 -
回帖数:0

Version 6.2 (20210218-074821)

Enhancements

  • Attempts to automatically fix the condition where a Control Hub's internal Expansion Hub is not working by re-flashing its firmware
  • Makes various improvements to the WiFi Direct pairing screen, especially in landscape mode
  • Makes the Robot Controller service no longer be categorically restarted when the main activity is brought to foreground
    • (e.g. the service is no longer restarted simply by viewing the Self Inspect screen and pressing the back button)
    • It is still restarted if the Settings menu or Configure Robot menu is opened

Bug fixes

  • Fixes FtcRobotController issue #71 Cannot open OpModes in v6.1 Blocks offline editor
  • Fixes FtcRobotController issue #79 6.1 causes a soft reboot on the Motorola E5 Play
  • Fixes issue where the Control Hub OS's watchdog would restart the Robot Controller app if the Control Hub was not able to communicate with its internal Expansion Hub
  • Fixes certain I2C devices not showing up in the appropriate HardwareMap fields (such as hardwareMap.colorSensor)
  • Fixes issue where performing a WiFi factory reset on the Control Hub would not set the WiFi band to 2.4 GHz
  • Fixes issue where OnBotJava might fail to create a new file if the option to "Setup Code for Configured Hardware" was selected
  • Fixes issue where performing certain operations after an Op Mode crashes would temporarily break Control/Expansion Hub communication
  • Fixes issue where a Control Hub with a configured USB-connected Expansion Hub would not work if the Expansion Hub was missing at startup
  • Fixes potential issues caused by having mismatched Control/Expansion Hub firmware versions
  • Fixes ftc_app issue 673 Latest matchlog is being deleted instead of old ones by RobotLog
  • Fixes ConceptVuforiaUltimateGoalNavigationWebcam sample opmode by correctly orienting camera on robot.
  • Fixes issue where logcat would be spammed with InterruptedExceptions when stop is requested from the Driver Station (this behavior was accidentally introduced in v5.3). This change has no impact on functionality.
  • Fixes issue where the blocks editor fails to load if the name of any TeleOp opmode contains an apostrophe.