Robot Not a Dev? Pre-order Now
Not a Dev?

12.10.18 Release Notes

release-notes
misty-i

#1

Welcome, Misty I Developers!

This release contains improvements to Misty’s computer vision system, enhancements to the over-the-air (OTA) update process, and a few changes to the commands for taking pictures and saving image assets. Because the release is being delivered as an OTA update, Misty will automatically update herself at her next reboot. You also have the option of starting the update yourself via:

Important: Misty reboots once during a system update. Please do not send any commands to Misty or disconnect her from her power source until her eyes are fully open again.

As always, we look forward to your feedback!

Note: If you have issues with a system upgrade or need technical assistance for other reasons, for the quickest response you can:

  • Post a message to the Support category here in the Community forums.
  • Mention @support with your post.
  • Post a message in MistyCommunity Slack in the technical_support channel.

RELEASE CONTENTS

New Features

Note: Capabilities released as “alpha” quality are not feature complete, may change in the future, and have had minimal testing.

  • Ability to change the size of images you upload to Misty. Access this functionality with the SaveImageAssetToRobot command.
  • Ability to resize photos captured by Misty’s 4K camera and save them directly to your robot without performing Base64 to byte array conversions. Access this functionality with the TakePicture “alpha” command.
  • Misty’s screen now displays dynamic update messages indicating the download status and the software or firmware being updated during each stage of the OTA update process.
  • Blockly GetHelp command now returns data in an easy-to-read format.
  • Ability to install an update for a specific component of the robot should a component fail to update with the rest of the system. Access this functionality with the PerformTargetedUpdate “alpha” command.

Bug Fixes and Improvements

  • Improved over-the-air (OTA) update architecture to stabilize OTA updates, incorporate specific error messages, and improve logging.
  • Enhanced system to improve the reliability of computer vision and camera commands. These enhancements include:
    • System better handles negotiation between the 4K and Occipital Structure Core camera systems.
    • System is now notified when the 4K camera is in error. If you try to use the 4K camera while it is in error, Misty returns a message asking you to try again in a couple of minutes.
    • Misty now uses a new Occipital Structure Core SDK with various reliability fixes and enhancements.
  • Fixed an issue with drive commands where a combined linear and angular velocity of greater than 100 caused the robot not to move.
  • API Explorer now automatically attempts to re-establish disrupted WebSocket connections instead of sending an error to the console.
  • Improved API Explorer responsiveness for head movement sliders and controls that use map data.
  • Fixed an issue with the SaveImageAssetToRobot command where the userAddedAsset property always returned the value false.

Known Issues

Network, Audio, Battery

  • Blank/empty passwords or networks with multi-layer security are not currently supported for network onboarding.
  • Audio files played in the browser by the GetAudioFile command are at a very low volume.
  • The battery charger will only charge the robot if it is replugged into the robot after each time that the robot is turned on.

Driving, Mapping, Navigation

  • The Halt command sometimes fails to stop the motors controlling Misty’s head.
  • The covering for the time-of-flight sensors can create false positives for close distance detection, which causes the robot to refuse to move. A workaround is to force the robot to detect a further distance by standing in front of it.
  • Inconsistent behavior with the LocomotionTrack command when attempting to drive the robot backward.
  • Issues with the speed/reliability of data coming from the Occipital Structure Core depth sensor’s USB connection is causing the robot to have issues with successfully obtaining pose.
  • The FollowPath command results in the robot driving to specified waypoints only about 30% of the time.
  • Observed issues with retrieving a new map after completing the start/stop mapping process in API Explorer.
  • Misty’s chest LED and time-of-flight sensors can stop working after Misty is turned on for a long period of time.

Image Handling and Computer Vision

  • Misty’s 4K camera does not currently take photos at 4K resolution. Currently this camera takes photos at a default resolution of 1600 x 1200 pixels, and the size and resolution of captured photos cannot be increased above the default.
  • Specifying values for the width and height parameters of SaveImageAssetToRobot does not work to resize images with a .png file type extension.
  • Images are not correctly centering themselves when a user-added image is displayed on Misty.
  • Performance issues with head movement and display commands after the robot has been continuously on for about an hour.

Companion App

  • When onboarding a robot with the Misty Companion app, even though it says it’s connected, the IP address and battery % may not be displayed initially. Closing the app and repeating the connection process will allow that data to be displayed.
  • Attempts to create a map with the Misty Companion app results in mapping failing for the remainder of the session about 10% of the time.
  • The Misty Companion app on Moto z2 devices contains overlapping buttons on the map screen.
  • It takes longer than it should to retrieve a “no map” response after a failed mapping attempt on the Misty Companion app.
  • There is an observable delay between joystick movement and the robot driving while using the Misty Companion app.
  • When changing networks via the Misty Companion app, the older IP address remains for several seconds after the network has been changed.

#2

Great release!


#3

#4

when I read through the release notes, there are a lot of different version numbers.
do I need to check every component in order to be sure that the update completed?
or is there some simple “all-up-to-date” feedback message that I can get?


#5

There’s not a straightforward message like that at this time, although that’s good feedback. Not all of these numbers are equally weighted in importance with every release. The most important numbers to check are typically the version numbers for the Home Robot App, the Motor Controller firmware, the RT firmware, and the Sensory service app.


#6

I made a small Python program that checks component version numbers against expected values.


#7

Tried this out on Windows 10 under Cygwin with python 3.6m. Worked great. My only modification was to add a
print(‘Successful. All versions match.’)
after the call to check_deviceinfo.


#8

@miker thanks for trying it!

I added a link at https://gist.github.com/slivingston/feb5d4682d4af02ecf3e5a1f673ce430 to your comment here so we remember to include your edit (print() success) if the code is merged into some significant repository.