The Spot SDK documentation is best viewed via our developer site at dev.bostondynamics.com.
The bosdyn-api and bosdyn-choreography-protos packages have been rebuilt to support the latest protobuf package. They now require a minimum protobuf version of 3.6.1.
Added payloads and lidar transform in GraphNav's WaypointSnapshot to help with:
- Not getting lost when a big payload occluded the lidar.
- Determine which payloads were used to record a map.
Same as 3.1.0
Same as 3.1.0
Network Compute Bridge (updated) Modified server to use user confidence value as a threshold for returning detections
To improve safety when operating on stairs, the robot may now autonomously walk off staircases in scenarios where it may have previously entered a sit. In the event of communication loss, critically low battery state of charge, or a Safe Power Off Request, the robot will walk off the staircase before sitting and powering off. The direction of travel will generally be to descend the stairs unless the robot has already reached the top landing. This includes automatic sit-and-power-off cases such as from low battery or the E-stop SETTLE_THEN_CUT level, as well as any client SafePowerOff commands. It does not affect immediate power cut cases such the PowerOff command or the E-stop CUT level.
To override this behavior for SafePowerOff commands, there is a new unsafe_action field in SafePowerOffCommand which can be set to UNSAFE_FORCE_COMMAND to force the command to take place immediately. To override this behavior for E-stop or battery power off, set the disable_stair_error_auto_descent field in the mobility params for the robot commands.
As part of this change, a new TerrainState message in RobotState contains the is_unsafe_to_sit value to report when the robot considers the terrain unsafe to sit on.
The behavior of the robot and leases is changed when the lease owner fails to retain the lease. Prior to 3.1, the robot would sit down and power off, and the lease would be revoked. This behavior allowed a new owner to smoothly take control of the robot in the case that a previous owner left without first returning the lease, but has proved to be frustrating when short comms losses trigger this behavior.
Starting in 3.1, failing to retain the lease will cause the lease to become “stale”. If the lease is stale, another client can acquire the lease and begin using the robot. However, if the original owner returns and begins retaining the lease or sending commands before another client acquires ownership, the lease will become “fresh” again without the original owner needing to re-acquire the robot. This staleness is reported via the new stale_time field in the LeaseResource message.
This change means that the robot will no longer sit down and power off if the lease owner disappears. For clients that still want that behavior, it is recommended to use an E-stop endpoint with the owner (which is already the common case), so that a comms interruption will cause the robot to sit and power off via the E-stop system.
A new tutorial provides a walk-through of integrating new sensors with the data acquisition system. It explains how to write, deploy, and use image services and data acquisition plugins with Spot, and how to process the resulting data.
In addition to images and data capabilities, DataAcquisitionRequests can specify network compute actions to perform on captured images by adding a NetworkComputeCapture in the acquisition request list. This capture will save the image and any computed data from the network compute response. This currently only operates on images and will only save the data returned in the response. For use cases that require sending other input data or saving other kinds of output data, it is still recommended to implement a data acquisition plugin to do that work.
Robot image services now report which image formats and pixel formats they support via new fields in the ImageSource message. When requesting images, clients can specify a desired pixel format, and also a resize ratio. These options allow for reduced bandwidth in cases where the client only needs a smaller image or a grayscale image. New status errors STATUS_UNSUPPORTED_PIXEL_FORMAT_REQUESTED and STATUS_UNSUPPORTED_RESIZE_RATIO_REQUESTED can now be returned if the client makes a request that is unsupported. User image services should also report the options they support. The VisualImageSource constructor now includes an optional argument for a list of supported pixel formats.
A new AlertData message has been added for the purpose of triggering live alerts for various events that can happen during a mission. These alerts can be saved into the DataAcquisitionStore service using the new StoreAlertData RPC and queried using the ListStoredAlertData RPC. Additionally, the alert data can be added to the response from a network compute bridge worker, where it will be automatically saved into the data acquisition store when captured as part of a data acquisition request. If a client calls the network compute bridge service itself, the alert data will be returned to the client in the response but not automatically saved to the data acquisition store.
GripperCameraParamService – Set or query various modes and options on the camera in the robot’s gripper.
RayCastService – Find intersections between a ray and the robot’s representation of the environment.
The Self-Right command now provides feedback in the SelfRightCommand.Feedback message as to whether it has successfully completed.
When Stand commands come to rest at their final pose, they will now enter a “frozen” state with locked joints. This keeps the robot more stationary for sensor data collection. Disturbances will still cause the robot to adjust and react to recover its position. The status of this “frozen” state is provided by the new StandingState enum in StandCommand.Feedback.
A new option, enable_robot_locomotion has been added to ConstrainedManipulationCommand.Request. When set to true, the robot will take steps to keep the hand in the workspace during a constrained manipulation command.
A new message, BodyAssistForManipulation, has been added to the BodyControlParams to allow clients to specify whether the body height or yaw should be used to assist the arm in manipulation. This new option cannot be used together with body offset trajectories specified in the base_offset_rt_footprint field.
-
image.depth_image_to_pointcloud()to convert depth images to numpy point clouds. -
image_service_helpers.convert_RGB_to_grayscale()to convert color images to grayscale. -
math_helpersnow includesVec2andVec3objects. -
robot_command.arm_joint_move_helper()constructs RobotCommands for joint trajectories. -
robot_command.blocking_sit()androbot_command.blocking_selfright()command sit and self-right commands and block until they complete. -
robot_command.block_for_trajectory_cmd()will block until the feedback for a given body trajectory command indicates that it is complete. -
util.add_payload_credentials_arguments()adds a–payloads-credentials-fileargument that can be used in place of the–guidand–secretarguments. This simplifies deployment to payload computers that contain a file with the correct credentials. -
util.read_payload_credentials()reads payload GUID and secret values from a file for use with payload registration and authentication. -
util.get_guid_and_secret()is a helper that will return the guid and secret, regardless of if the user used–guidand--secretor--payload-credentials-file. -
world_object.draw_sphere()andworld_object.draw_oriented_bounding_box()can be used to set objects in the world object service for debugging purposes.
A new ListAllSequences RPC allows clients to list all of the available sequences that are known to the robot and can be executed.
A new node type, ClearBehaviorFaults will allow a mission to autonomously clear behavior faults when desired.
In the python client library the LeaseKeepAlive context manager continually sends RetainLease commands to the robot to keep ownership of a lease. It has been upgraded to support more complete lease management by acquiring the lease if it is not owned when created and an option to return it when it exits. To preserve backwards compatibility, the initial acquisition is allowed to fail, and it does not return it by default. There are two options that control this behavior: must_acquire=True means that any exceptions that are raised during acquisition are not caught and are raised to the code creating the keep-alive, and return_at_exit=True means that the lease will be returned when exiting or shutting down the keep-alive. Both of these options default to False currently.
Arm joint trajectories now include self-collision avoidance to prevent hitting the body or payload with the arm.
The DockProperties of the docks from the World Object Service have an additional from_prior field that can indicate when that particular object comes from prior map knowledge and was not directly detected. Docking Feedback includes a new failure case STATUS_ERROR_UNREFINED_PRIOR, for situations in which the dock prior could not be confirmed as a real dock.
Certain commands may be unavailable when the robot is docked (such as rolling over to change the battery). In those cases, the command response will fail with the new STATUS_DOCKED.
Many gRPC services on the robot have now enabled support gRPC compression, which will be used if the client gRPC library supports it.
The bosdyn.client metrics command will print the metrics correctly again.
When localizing to a graph nav map, the SetLocalization, UploadGraph, and UploadWaypointSnapshot RPCs can fail with the new STATUS_INCOMPATIBLE_SENSORS if the map was recorded using a different sensor setup than the robot currently has onboard. For example, if the map was recorded with a lidar scanner, and the robot does not currently have one equipped. For UploadWaypointSnapshot, the new status enum will not be known to clients using older versions of the SDK and thus they will not recognize it as an error.
The new SensorCompatibilityStatus in the responses will report whether the map and/or robot have lidar data for these error cases.
Clearing the map when in the middle of recording would break the recording process. Requesting to clear the map in this case will now return STATUS_RECORDING. Clients using older versions of the SDK will not know about this new status field and will not treat it as an error case.
Spot Check now has two extra states that it can report being in: STATE_GRIPPER_CAL and STATE_SIT_DOWN_AFTER_RUN. It also has two extra error types it can detect and report: ERROR_GRIPPER_CAL_TIMEOUT as a top-level error and ERROR_INVALID_RANGE_OF_MOTION for joints.
Automatic data buffer logging of gRPC messages is deprecated. The gRPC messages will continue to be available for download via HTTP in 3.1, but support will be removed in a future release.
FollowArmCommand’s disable_walking is deprecated. To reproduce the robot's behavior of disable_walking == true, issue a StandCommand setting the enable_body_yaw_assist_for_manipulation and enable_hip_height_assist_for_manipulation MobilityParams to true. Any combination of the enable_*_for_manipulation are accepted in stand giving finer control of the robot's behavior.
When commanding door opening, the options SWING_DIRECTION_INSWING and SWING_DIRECTION_OUTSWING have been renamed to SWING_DIRECTION_PULL and SWING_DIRECTION_PUSH.
The signature of CameraInterface.image_decode() for user image services has changed from passing individual parameters such as image_format and quality_percent to directly passing in the image request proto. This change makes it easier to add new options to image requests without breaking existing image service implementations. Services can access the previous parameters via the image request proto, as well as accessing new parameters such as pixel_format and resize_ratio.
The –username and –password command line options are deprecated in the Python SDK. There are security concerns with using usernames and passwords on the command line. Instead of using bosdyn.client.util.add_common_arguments(parser) we recommend using bosdyn.client.util.add_base_arguments(parser) which will not include those options, and then authenticating via bosdyn.client.util.authenticate(robot), which will read from the BOSDYN_CLIENT_USERNAME and BOSDYN_CLIENT_PASSWORD environment variables. The bosdyn.client and bosdyn.client.bddf_download programs will continue to support the old options for now but usage should be switched to the environment variable method instead.
We have changed the LeaseKeepAlive helper to handle more of the lease life-cycle management, where it can acquire and return the lease itself. However, we have kept its default behavior largely unchanged for now to not break existing code. In a future release we may change the defaults for return_at_exit and must_acquire to True. Applications that desire the previous behavior should explicitly set must_acquire and return_at_exit to False to preserve that behavior across a change in the defaults.
The DARK option for auto white balance for the Spot CAM stream has been deprecated.
The original names still exist, but are deprecated.
bosdyn.client.graph_nav.UnrecongizedCommandError has been renamed to bosdyn.client.graph_nav.UnrecognizedCommandError.
bosdyn.bddf.message_reader.channel_name_to_series_decriptor() has been renamed to bosdyn.bddf.message_reader.channel_name_to_series_descriptor()
The from_obj() methods on the math helper classes have been renamed to from_proto().
Because leases are no longer revoked when the owner fails to check in, there are two changes that must be accounted for:
- The robot will not automatically sit down and power off if the owner times out. It will still sit down and power off if an E-stop endpoint times out. For use cases that want the owner’s absence to cause the robot to sit and power off, make sure that the owner is also maintaining an E-stop endpoint.
- Any client calling
ListLeasesto try to determine if the robot is owned will need to check thestale_timeof theLeaseResource. Instead of callingListLeasesbeforeAcquireLease, we recommend just callingAcquireLeasefirst, and reacting to anySTATUS_RESOURCE_ALREADY_CLAIMEDstatus in the response.
The new safety features to avoid powering off and sliding down stairs means that there is a behavioral change to SafePowerOff commands, powering off due to low battery, and powering off due to an E-stop LEVEL_SETTLE_THEN_CUT. While the new behavior should be safer, be aware that these commands will now cause locomotion before sitting and powering off.
The robot may not be commanded to go to the battery change pose when docked.
The Graph Nav map may not be cleared in the middle of recording.
The DataAcquisitionStore service is queryable for the IDs of items that have been stored by it. It would previously track everything that had been stored since the last time that the robot had been restarted. As of 3.1, it will track only the last 10,000 items stored.
The bosdyn-client package no longer depends on requests.
When a network transport failure occurs, depending on the particular operating system and version of gRPC installed, the error from the python SDK may not always be the most specific error possible, such as UnknownDnsNameError. It may instead be raised as either a generic RpcError, or another generic failure type such as UnableToConnectToRobotError.
Spot CAM LED illumination levels are not currently recorded or played back in Autowalk missions.
If you write a custom data acquisition plugin or image service, do not change its DataAcquisitionCapability or ImageSource set once it is running and registered. New capabilities may not be detected, and old capabilities may still be listed as available in the Data Acquisition service. To change the capabilities of a service: unregister it from the directory, wait until its capabilities are no longer listed in the Data Acquisition service, and then re-register it. This waiting also applies to restarting a service if its capabilities will be different upon restart.
If you write a custom data acquisition plugin without using our helper class, its GetStatus() rpc is expected to complete immediately. If it takes too long to complete it can cause timeouts when requesting GetStatus() of the data acquisition service.
If you register a new service with the robot, calling robot.ensure_client() to create a client for that service may result in a UnregisteredServiceNameError.
- Workaround: call
robot.sync_with_directory()beforerobot.ensure_client()
SE2VelocityLimits require care. Correct usage of the SE2VelocityLimit message requires the user to fully fill out all the fields, setting unlimited values to a large number, say 1e6.
All examples have been changed to read the username and password from environment variables instead of taking --username and --password arguments.
Additionally, most examples now use the LeaseKeepAlive for complete lease management by setting the must_acquire and return_at_exit arguments to True at construction. This helps ensure that the lease is properly returned when the example is complete.
The arm and manipulation examples have been updated to use the new block_until_arm_arrives() helper instead of sleep() calls.
The included Dockerfiles now contain default command line arguments for their entrypoints where appropriate. This means that it is not necessary to specify any command line arguments when running them in their default configuration (on the Spot CORE). However when running in a non-default configuration, all command line arguments will need to be specified.
Comms Mapping (new) Creates an image service that can be selected on the tablet controller that displays a map of wifi signal strength.
Gripper Camera Params (new) Demonstrates how to control the capture parameters for the gripper camera.
Ray Cast (new) Demonstrates how to perform ray-casting queries using the new RayCastService.
Animation Recorder (updated) First checks if the robot has the correct license for choreography.
Arm Force Control (updated)
Updated to use the new BodyAssistForManipulation parameters.
Arm Gcode (updated)
Some updates to parsing gcode files. Added a new --test-file-parsing option to only try to read the file, without executing it.
Arm joint move (updated) Added a more advanced example that shows how to send a continuous trajectory with many points.
BDDF download (updated) Fixed the ping check on Windows.
Data Acquisition (updated) Includes a new example plugin that saves battery data. This is used as part of the Data Collection Tutorial
Get Image (updated)
Supports a new --pixel-format option to be able to specify the desired format.
Graph Nav Command Line (updated)
The recording example correctly handles the NotReadyYetError response when stopping recording.
Ricoh Theta (updated) Includes support for pixel format and resize ratio.
Spot CAM (updated) Fixed a memory leak related to audio streams.
Tester Programs (updated) The image service tester only requests image and pixel formats that the service reports that it supports, and it will check that the returned type matches the requested type. It will also report a summary at the end of all errors and warnings it found.
Upload Choreographed Sequence (updated)
Checks that the robot is correctly licensed for choreography before running.
Includes a new --upload-only option that will upload the sequence without running it.
Basic Streaming Visualizer (updated) Added an example to draw gripper depth data as a point cloud.
Web Cam Image Service (updated) Includes support for pixel format and resize ratio.
World Object Mutations (updated) Demonstrate using the new drawing helper.
Xbox Controller (updated) Cleaner lease usage throughout.
Reduced RPC calls to the Fault service in image_service_helpers.py.
Example documentation cleanup and improvements.
Same as 3.0.0
Added GetSystemLog RPC in SpotCAM Health service to retrieve an encrypted log of system events, for factory diagnosis of possible issues.
Fixed UploadEdgeSnapshot typo in GraphNav client.
Fixed usage of SE2Trajectory robot commands in mission service.
Same as 3.0.0
Added COLORMAP_INFERNO and COLORMAP_TURBO as SpotCAM IR color map options.
The new base_tform_sensor fields in SpotCAM protos have the transform in the right direction. The old base_tfrom_sensor fields, now deprecated, had the inverse transform.
Deprecated field base_tfrom_sensor in SpotCAM camera proto and added field base_tform_sensor so it follows the intended naming convention.
Deprecated field base_tfrom_sensor in SpotCAM logging proto and added field base_tform_sensor so it follows the intended naming convention.
Deprecated the decode_token() and log_token_time_remaining() functions in bosdyn.client.sdk. The SDK no longer supports decoding tokens. If you need to decode one, use pyjwt directly.
Same as 3.0.0
Arm Constrained Manipulation (updated) Cleanup to clamp normalized velocity and also use normalized velocity for knob.
GraphNav Command Line (updated) Improved handling in certain failure cases
Spot Cam (updated) Handle new IR color map options and removed the usage of the deprecated pose fields
Map Processing The new map processing service provides two ways to process the data in a graph nav map:
- adding new waypoints and edges to close loops and add connections in a map
- optimizing “anchorings” of a map, which will generate optimized positions of waypoints in the world for display or navigation.
Navigate to Anchor A new NaviagateToAnchor RPC can be used to command GraphNav to drive the robot to a specific place in an anchoring. GraphNav will find the waypoint that has the shortest path length from the robot's current position but is still close to the goal.
See the Graph Nav documentation for more information.
Auto Return is a service which can be configured to take control of the robot in the event of a communication loss, and return it back along its recently traveled route to attempt to regain communications with its user. See the Auto Return documentation for more details.
The Choreography API now provides 'choreography logging' which will capture timestamped data about the robot's pose and joint state for either a user defined time period or for the duration of a dance. See the Choreography Service documentation for more details.
Users can now create animated moves using timestamped keyframes; these can be built through common animation software (like Autodesk Maya), handwritten, or constructed from choreography log data. The animated moves can be uploaded to the robot and used within dances like the base moves. See the Animations Overview documentation for more details.
The constrained manipulation API provides the functionality to manipulate objects such as cranks, levers, cabinets and other similar objects with Spot. The API allows for the selection of a task type along with the desired task velocity to manipulate the object.
API and tablet support for opening pushbar doors. The AutoPush API command takes a push point which the robot uses to detect the door and push it open at the specified location. See door.proto or arm_door.py for more details.
New SetPtzFocus and GetPtzFocus RPCs allow for control over the focus of the PTZ camera.
Payload registration now supports mounting payloads to the wrist or gripper of the arm. The new MountFrameName enum contains the valid mounting locations.
A new UpdatePayloadAttached RPC allows for attaching and detaching payloads while the robot is operating.
Missions have a new STATUS_STOPPED state that can be triggered by the new StopMission rpc. This state differs from a paused mission in that it means that the mission is no longer running and cannot be resumed.
New mission node types:
BosdynNavigateRoute: Use GraphNav via NavigateRouteBosdynRecordEvent: Record an API event in the data buffer.SpotCamLed: Change the brightnesses of the LEDs on a SpotCam.SpotCamResetAutofocus: Reset the autofocus on a SpotCam PTZ.StoreMetadata: Attach metadata to some data stored by a DataAcquisition node.RetainLease: Keep mission leases alive while the mission is running. This allows the mission to run a larger variety of missions without requiring the mission service’s client to keep the lease alive.RestartWhenPaused: Restarts its child tree when a mission resumes, rather than resuming its child from the state it was in when it paused.
A new IREnableDisable service and request have been added. This request allows clients to enable/disable the robot's IR light emitters in the body and hand sensors. This new service supports special situations where Spot's emitters may interfere with a custom attached payload. Disabling the IR emission will cause a SystemFault to be raised and have a negative effect on mobility since the robot's perception system is hindered.
For RPCs that can fail because the robot is impaired, the response message now includes a RobotImpairedState message providing details about the nature of the impairment.
NavigationFeedbackStatus now includes body_movement_status to make it simple to determine when the body has come to rest after completing navigation.
Directed exploration and alternate route finding can now be disabled using new fields in TravelParams.
RouteFollowingParams have been added to NavigateRouteRequest to specify the desired behavior in certain situations (not starting from the start of the route, resuming a route, and becoming blocked on a route).
New methods navigate_to_full() and navigate_route_full() has been added to the Graph Nav client which will return the full response instead of just the command id.
Additional statuses have been added to NavigateRouteResponse (STATUS_NO_PATH and STATUS_NOT_LOCALIZED_TO_MAP) to capture possible errors.
UploadGraph can fail with STATUS_INVALID_GRAPH when the specified graph is invalid, for example containing missing waypoints referenced by edges.
DownloadWaypointSnapshotRequest has an additional option to not include point cloud data. The new has_remote_point_cloud_sensor field in WaypointSnapshot indicates that the point has point cloud data from a remote service.
Starting to record a new map can fail with the new status STATUS_TOO_FAR_FROM_EXISTING_MAP.
The RPC for creating a new waypoint can now be provided a list of world objects to include in that waypoint’s snapshot.
For very large missions, a new RPC has been added to the mission service to stream the mission to the robot in chunks, rather than as a single message. The chunks should still deserialize to the same LoadMissionRequest message when assembled.
When a mission node fails to compile, the resulting FailedNode message has a new string that lists the protobuf type of the node implementation.
We have improved the feedback for ArmJointMoveCommand Requests to now include the status of the underlying trajectory planner and to return the planner’s solved trajectory, which is the trajectory the robot will execute.
The ManipulationFeedbackState contains extra enum values for additional placing states that the robot can be in during manipulation.
By default, the robot will assume all grasped items are not “carriable”. We have modified ApiGraspOverride to be able to override the carry state to one of CARRIABLE, NOT_CARRIABLE, or CARRIABLE_AND_STOWABLE.
If holding an item, the stowing behavior is:
NOT_CARRIABLEandCARRIABLE- The arm will not stow, instead it will stopCARRIABLE_AND_STOWABLE- The arm will stow while continuing to grasp the item
In addition, the communication loss behavior of the arm when it is holding an item is also modified:
NOT_CARRIABLE- The arm will release the item and stowCARRIABLE- The arm will not stow, instead entering stopCARRIABLE_AND_STOWABLE- The arm will stow while continuing to grasp the item
The docking state includes additional “in-between” states, DOCK_STATUS_UNDOCKING and LINK_STATUS_DETECTING that indicate that a process is still on-going.
Additional errors have been added to DockingCommandResponse for particular ways that docking can fail (STATUS_ERROR_GRIPPER_HOLDING_ITEM, STATUS_ERROR_NOT_AVAILABLE, STATUS_ERROR_SYSTEM).
The feedback also has a new error status: STATUS_ERROR_NOT_AVAILABLE.
See the protobuf documentation for more details.
The docking python client include a new docking_command_full() call which returns the full response instead of only the command id. Additionally a new docking_command_feedback_full() returns the full feedback instead of only the status.
Models can now have a list of labels associated with them.
When the image is requested to be rotated, the rotation angle will be returned in the response.
DataAcquisitionCapabilities can now also report the plugin service name of the service that will be performing that acquisition.
The DataAcquisitionClient has a new acquire_data_from_request() that takes a full request proto, instead of building it internally.
The DataService client has been updated to have the correct service name.
Power commands can now report a STATUS_OVERRIDDEN if the robot overrides the power command and disables motor power.
Power command responses and feedback will report system faults if a fault blocks the power command from succeeding.
LeaseUseResults have been added to messages for RobotCommand and ManipulationApi
New helpers safe_power_off_robot() and safe_power_cycle_robot() can completely power off the robot or power cycle the robot from any robot state.
Additional options have been added to ObstacleParams for tuning obstacle avoidance by turning off negative obstacle avoidance or body assist for avoiding foot obstacles.
Leases represent ownership over the robot. Leases have been updated to support ownership over only part of the robot, so that you can delegate control to different services, such as using Graph Nav to control robot mobility while simultaneously controlling the robot’s arm via a user-written script. Details are in the lease documentation, but in general users can just continue to use the “body” lease and everything will work as expected.
The image service will now report PixelFormat for JPEG image sources even though the pixel format can be determined from the JPEG header.
Spot Check has some additional failure statuses that it can report.
Events logged to the data buffer may now include a LogPreserveHint to tell the robot whether this event is worth preserving a log for.
RobotState now includes additional data about the terrain under each foot.
Additional properties have been added to world objects to assist in image processing.
An additional level of hierarchy has been added for transport-level errors to simplify most error cases. RpcError has two new subclasses: PersistentRpcError and RetryableRpcError. PersistentRpcError indicates an error such that attempting to retry the call will fail again. RetryableRpcError means that the call may succeed if retried.
Calling ensure_secure_channel() directly will now result in max message sizes not being correctly.
Invalid RobotCommands will no longer result in STATUS_INVALID_REQUEST in the RobotCommandResponse message, but will instead use the CODE_INVALID_REQUEST error in the common header, like other RPCs do. In the python client library, this will still raise the same InvalidRequestError as before.
E-stops may not be unregistered from the estop service while the robot’s motors are powered. This prevents accidentally powering the robot off. A new STATUS_MOTORS_ON status will be returned in the response to indicate this error. To unregister an estop, first safely power off the robot.
RPCs to the AuthService and PayloadRegistration service are now rate-limited to 5 and 10 requests/second respectively. Requesting more than that will result in an HTTP 429 error, or raising the TooManyRequestsError if using the python client.
The “obstacle_distance” local grid inadvertently included some generated obstacles used only for foot-placement control. These grids no longer include those generated obstacle regions.
The python function bosdyn.client.lease.test_active_lease previously took an optional make_sublease argument. That has been replaced with an optional sublease_name argument so that if a sublease is desired, it gets created with a client name correctly.
The StraightStaircase message has been moved to bosdyn/api/stairs.proto so that it can be used in more places. This is compatible with existing serialized protobufs, but any code that is manually creating these messages will need to be updated.
The enable_grated_floor field is superceded by the new grated_surfaces_mode which will auto-detect the need for grated surface handling.
The safe_power_off() helper has been replaced by the less ambiguous safe_power_off_motors() helper.
The docking_command_feedback() method of DockingClient incorrectly raised an exception if the docking command had encountered lease errors, and has been replaced by docking_command_feedback_full() which returns the full feedback response.
For limiting the speed on an edge, use the vel_limit in mobility_params instead of the Edge annonation’s vel_limit.
Docking nodes should not use the child node anymore. If a mission needs to react to docking results, it should use the responses written into the blackboard by the docking node.
The guid and secret fields on payload registration RPCs have been replaced with a standardized PayloadCredentials message.
Many helpers for writing services and filling out responses have been moved from bosdyn.client.util to bosdyn.client.server_util.
bosdyn.mission.server_util.set_response_header() has been moved to bosdyn.client.server_util.set_response_header(), so that it can be used by any service, not only those depending on missions.
When a network transport failure occurs, depending on the particular operating system and version of gRPC installed, the error from the python SDK may not always be the most specific error possible, such as UnknownDnsNameError. It may instead be raised as either a generic RpcError, or another generic failure type such as UnableToConnectToRobotError.
Spot CAM LED illumination levels are not currently recorded or played back in Autowalk missions.
If you write a custom data acquisition plugin or image service, do not change its DataAcquisitionCapability or ImageSource set once it is running and registered. New capabilities may not be detected, and old capabilities may still be listed as available in the Data Acquisition service. To change the capabilities of a service: unregister it from the directory, wait until its capabilities are no longer listed in the Data Acquisition service, and then re-register it. This waiting also applies to restarting a service if its capabilities will be different upon restart.
If you write a custom data acquisition plugin without using our helper class, its GetStatus() rpc is expected to complete immediately. If it takes too long to complete it can cause timeouts when requesting GetStatus() of the data acquisition service.
If you register a new service with the robot, calling robot.ensure_client() to create a client for that service may result in a UnregisteredServiceNameError.
- Workaround: call
robot.sync_with_directory()beforerobot.ensure_client()
SE2VelocityLimits require care. Correct usage of the SE2VelocityLimit message requires the user to fully fill out all the fields, setting unlimited values to a large number, say 1e6.
Animation Recorder (new) Demonstrates recording motion made with the tablet and then playing it back with the choreographer service.
Arm Constrained Manipulation (new) Demonstrates using constrained manipulation to turn a crank.
Auto Return (new) Demonstrates setting up and triggering the Auto Return service.
Data Buffer (new) Demonstrates adding several different kinds of data to the data buffer.
Get Depth Plus Visual Image (new)
Demonstrates how to use the depth_in_visual_frame image sources to visualize depth in a visual image.
Graph Nav Extract Point Cloud (new) Demonstrates opening and parsing a GraphNav map and extracting a globally consistent point cloud from it.
Post-Docking Callbacks (new) Builds docker images for mission callbacks that can upload data acquired during a mission.
Disable IR Emission (new) Demonstrates enabling and disabling IR light emitters via the IREnableDisableService Client.
Arm Gaze (updated)
Updated to use block_until_arm_arrives() instead of a sleep()
BDDF Download (updated) Now provides a Qt-based downloading UI.
Data Acquisition Service (updated) Now provides a plugin for capturing data from the network compute bridge.
Frame Trajectory Command (updated) Now takes arguments that specify how to move instead of performing fixed motions.
Graph Nav Command Line (updated) Now can navigate to a position in an anchoring. The recording example provides options to automatically close loops in the map or optimize the map's anchoring.
View Map (updated) Now can display the map according to the anchoring.
Mission Recorder (updated) New option to build a mission from the graph on the robot. New command to automatically close loops in the graph. Uses NavigateRoute to follow waypoints in order.
Network Compute Bridge (updated) Now includes options to run and test a worker without needing a robot. Also includes files to build docker images for deployment.
Payloads (updated) Now includes an example of how to attach and detach a payload.
Replay Mission (updated) Now includes extra options for playing back Autowalk missions, as well as disabling directed exploration.
Ricoh Theta (updated) Now includes a "live stream" option that provides a higher frame rate at the cost of lower-quality stitching. (Thanks Aaron Gokasian!)
Spot Cam (updated) New options for getting and setting PTZ focus, audio capture channel, and audio capture gain. Also an option for enabling congestion control for the stream quality.
WASD (updated) The Escape key can now be used to stop the robot.
Webcam Image Service (updated) New resolution options allow for capturing from the webcam at different resolutions.
Added InitializeLens rpc, which resets the PTZ autofocus without needing to power cycle the Spot CAM.
A new sync option has been added to RecordDataBlobsRequest which specifies that the RPC should not return a response until the data has been fully committed and can be read back.
This is exposed through the optional write_sync argument to the add_blob() and add_protobuf() methods of the DataBufferClient.
When running with a Spot CAM+ (PTZ) running 2.3.5, the SetPowerStatus and CyclePower endpoints will now return an error if the PTZ is specified. These endpoints could previously cause the WebRTC feed to crash. These RPCs are still safe to use for other devices, but due to hardware limitations, resetting the PTZ power can possibly cause the Spot CAM to require a reboot to regain the WebRTC stream.
RetryableUnavailableError was raised in more cases than it should have been, and it is now more selectively raised.
The EstopKeepAlive expected users to monitor its status by popping entries out of its status_queue. If the user did not do so, the queue would continue to grow without bound.
The queue size is now bounded and old unchecked entries will be thrown away. The queue size is specified with the max_status_queue_size argument to the constructor.
As stated above, the behavior of SetPowerStatus and CyclePower endpoints have been changed for Spot CAM+ units when attempting to change the power status of the PTZ. They now return an error instead of modifying the power status of the PTZ. They remain functional for the Spot CAM+IR. Clients using these SDK endpoints to reset the autofocus on the PTZ are recommended to use InitializeLens instead. Other clients are encouraged to seek alternative options.
The ResponseContext helper class has been moved to the bosdyn-client package (from the bosdyn-mission package), so that it can be used for gRPC logging in data acquisition plugin services in addition to the mission service. The new import location will be from bosdyn.client.server_util, and the original import location of bosdyn.mission.server_util has been deprecated.
Same as 2.3.0
New options have been added to the Power Service to allow for power cycling the robot and powering the payload ports or wifi radios on or off. Additional fields have been added to the robot state message to check the payload and wifi power states. Support has also been been added to the bosdyn.client command line interface for these commands.
These new options will only work on some Enterprise Spot robots. Check the HardwareConfiguration message reported by a particular robot to see if it supports them.
Fixed an issue that could cause payload registration or directory registration keep-alive threads to exit early in certain cases.
Fixed a couple issues with the webcam example: updated the Dockerfile to create a smaller container specifically with python 3.7, added new optional argument to specify the video codec, and programmatically prevent substring arguments other than the --device-name argument to avoid accidental confusion with the docker container's --device argument.
Same as 2.3.0
A new tutorial has been added to walk through using machine learning, the Network Compute Bridge, and Manipulation API to play fetch with Spot.
The python Graph Nav client now allows setting an offset to the destination, for navigating to a position relative to the final waypoint instead of exactly matching the final waypoint position and orientation.
Fixed issues where the data acquisition download helpers did not handle absolute paths on windows and did not clean filenames correctly. (Thanks David from Levatas!)
Zip file names from the data download service no longer contain difficult characters.
Fixed an issue where Graph Nav would sometimes report the robot was impaired on the first usage after restarting the robot.
Errors returned from Network Compute Bridge workers will be better propagated in the Network Compute Bridge response.
Updated background threads for the payload and directory registration helpers to silently ignore transient errors.
Fixed an issue where requesting thermal images with PTZ/Pano images in a single data acquisition action caused thermal images to either not be collected or saved as “blank” images.
The estop service will now refuse to change configuration if the robot is already powered on, returning a status of STATUS_MOTORS_ON. This prevents accidentally cutting power while the robot is in operation.
Same as 2.3.0
Network Compute Bridge Updated to provide appropriate error messages from the workers.
The SpotCAM API has been expanded to support more use cases for the SpotCAM+IR (thermal PTZ variant). This includes the following new endpoints:
SetIrColormap/GetIrColormap: Set/get the mapping between radiometric IR samples to color, for videoSetIrMeterOverlay: Set location for the "Spot Meter", which indicates temperature at a point in the thermal video stream.
The SpotCAM Power API now has an additional endpoint to cycle power for any of the components that could previously be toggled using SetPowerStatus. CyclePower can be used to help the PTZ recover from adverse behavior, such as incorrect auto-focus or poor motor behavior, which can sometimes happen as the result of a robot fall. CyclePower will wait the appropriate amount of time between turning components off and turning on again to make sure the power is cycled correctly without the client needing to know the correct interval.
Same as 2.3.0
Get image (updated) Support for the new pixel format of IR images.
Ricoh Theta (updated)
Improved parsing of timestamp information from the camera.
Correctly set the image proto format field.
Defaults to not capturing continuously. Flags --capture-continuously and --capture-when-requested can be used to specify the desired behavior.
Spot CAM (updated) Support for IR images and power cycling functionality.
One of the main features of the 2.3 release is control and support of Spot's arm and gripper. Arm and gripper commands are included in the SynchronizedCommand message, and can be commanded in addition to mobility commands. The RobotCommandBuilder in the SDK provides many new helpers for building new arm and gripper commands. The synchro command builder functions now have an optional build_on_command argument, which is used to build a mobility/arm/gripper command onto an existing command, merging them correctly.
The arm and gripper state are reported in the new manipulator_state field of the robot state. The Python SDK Robot class now has a has_arm() helper to determine if the robot has an arm or not.
For more information about controlling the arm, see the arm documentation.
Manipulation API (beta) This new API provides some high-level control options for walking to and picking up objects in the world.
Arm Surface Contact (beta) ArmSurfaceContactService lets you accurately move the robot's arm in the world while having some ability to perform force control. This mode is useful for drawing, wiping, and other similar behaviors.
Doors (beta) DoorService will automatically open and move through doors, once provided some information about handles and hinges.
An interface for integrating real-time image processing and machine learning for identifying objects and aiding grasping. For more information, see the network compute bridge documentation.
A new PayloadEstimationCommand is available to have Spot try to estimate the mass properties of a payload itself. After moving about to perform its estimation, the mass properties will be reported in the command feedback.
Some SpotCAMs now include an IR camera. There are additional cameras and screens available for those versions, and a new pixel format PIXEL_FORMAT_GREYSCALE_U16 used to represent those IR images. There are additional rpcs used to set colormaps and overlays of the IR images for live display.
Logpoint QUEUED status is now broken up further with the queue_status field, which differentiates between when the image has or has not been captured.
The new Choreographer executable now includes two new tracks, gripper and arm, and includes new dance moves which control the arm.
A new PREP_POSE_UNDOCK command option can be used to undock a docked robot. It will return the new STATUS_ERROR_NOT_DOCKED if the robot was not already docked. When successful the status will be STATUS_AT_PREP_POSE.
When localizing the robot using FIDUICIAL_INIT_SPECIFIC, if the target waypoint does not contain a good measurement of the desired fiducial, nearby waypoints may be used to infer the robot's location. This behavior can be disabled with the new restrict_fiducial_detections_to_target_waypoint field to only use the waypoint’s own data.
A new destination_waypoint_tform_body_goal is provided for the NavigateTo and NavigateRoute rpcs. This allows the user to specify a goal position that is offset from the destination waypoint, rather than exactly on the waypoint.
A new command_id field can be specified on the NavigateTo and NavigateRoute rpcs. This is used to continue a previous command without needing to re-specify all the data. An important difference between specifying the command_id versus sending a new command is that if the robot has reported itself stuck, continuing a command will result in a STATUS_STUCK error, rather than trying again. A new STATUS_UNRECOGNIZED_COMMAND will be returned if the command_id does not match the currently executing command.
The map representation now tracks the “source” of waypoints and edges. It is possible to override the cost of an edge used when planning paths and to disable the alternate route finding for a particular edge.
Leases now include client names alongside the sequence number for help in debugging. If you are writing a custom client, make sure to append your client name any time that you create a sub-lease.
ListLeases can optionally request to have the full lease information of the latest lease, rather than only the root lease information that was previously reported.
In the seconds following modifications to the robot directory to the robot directories existing clients may experience a one time request failure. This failure is transient and can be resolved by retrying the request. This has been an expected failure case and a new error (RetryableUnavailableError) has been put in to better reflect the failure.
SE3Pose and Quat math helpers have transform_vec3 members to simplify rotating vectors.
There is a new get_self_ip() helper in common.py for determining the ip address your client will use to talk to the robot. This is useful for determining the correct registration information for a service, particularly on a machine with multiple network interfaces. This is also available via the python command line program python3 -m bosdyn.client <robot host> self-ip.
When listing events from the python command line program, you can now filter by event level and by event type.
The python SDK now depends on the Deprecated package, which is used to mark functions and classes that are deprecated and provide warnings, so that users are made aware that features that they are using may be removed in the future.
The Deprecated package has been implemented across the SDK so that deprecated features will print out a warning when they are called. Documentation surrounding deprecated features has also been updated.
Spot Check no longer computes the foot_height_results or leg_pair_results fields.
All rpcs in the Python SDK have a default timeout of 30s. The global timeout can be changed by assigning a new value to bosdyn.client.common.DEFAULT_RPC_TIMEOUT, and individual rpc calls can still set their own timeout via a timeout=sec optional parameter at any call site.
When a network transport failure occurs, depending on the particular operating system and version of gRPC installed, the error from the python SDK may not always be the most specific error possible, such as UnknownDnsNameError. It may instead be raised as either a generic RpcError, or another generic failure type such as UnableToConnectToRobotError.
Spot CAM LED illumination levels are not currently recorded or played back in Autowalk missions.
When capturing both a PTZ and Panoramic image in the same action, there may occasionally be two PTZ images captured along with the Panoramic image, rather than just one.
If you write a custom data acquisition plugin or image service, do not change its DataAcquisitionCapability or ImageSource set once it is running and registered. New capabilities may not be detected, and old capabilities may still be listed as available in the Data Acquisition service. To change the capabilities of a service: unregister it from the directory, wait until its capabilities are no longer listed in the Data Acquisition service, and then re-register it. This waiting also applies to restarting a service if its capabilities will be different upon restart.
If you write a custom data acquisition plugin without using our helper class, its GetStatus() rpc is expected to complete immediately. If it takes too long to complete it can cause timeouts when requesting GetStatus() of the data acquisition service.
If you register a new service with the robot, calling robot.ensure_client() to create a client for that service may result in a UnregisteredServiceNameError.
- Workaround: call
robot.sync_with_directory()beforerobot.ensure_client()
SE2VelocityLimits require care. Correct usage of the SE2VelocityLimit message requires the user to fully fill out all the fields, setting unlimited values to a large number, say 1e6.
Arm and Mobility Command (new) Demonstrates how to issue both mobility and arm commands to the robot at the same time.
Arm Door (new) Demonstrates how to use the door service to have Spot autonomously open a door. It opens an image display and requires the same use input as when opening a door with the tablet.
Arm Force Control (new) Demonstrates how to create force controlled trajectories for the arm and gripper.
Arm Gaze (new) Shows how to command multiple different types of gaze requests.
Arm GCode (new) Uses the arm surface contact API to write GCode on the ground using sidewalk chalk.
Arm Grasp (new) Shows how to use the manipulation API to autonomously grasp an object based on the object’s image coordinates in pixel space. It opens an image view and lets a user select an object by clicking on the image, similar to grasping with the tablet.
Arm Joint Move (new) Shows how to create and command a joint move trajectory.
Arm Simple (new) A starter example which shows how to issue the robot command RPC with a basic arm command which moves the end effector to a couple different positions.
Arm Stow Unstow (new) Shows how to issue API commands to stow and unstow the arm.
Arm Surface Contact (new) Uses the arm surface contact API to request a end effector trajectory move which applies some force to the ground.
Arm Trajectory (new) Demonstrates how to create an arm command with a position-based trajectory.
Arm Walk to Object (new) This example shows how to use the manipulation api to command the robot to walk towards an object and prepare to grasp it. The example opens an image view and lets a user select an object by clicking in the image.
Arm With Body Follow (new) Shows how to issue arm commands that allow the body to move to a good position to achieve the desired arm command.
Comms Test (updated) The comms test example can now successfully be run with Docker.
Data Acquisition Service Plugins (updated) The directory structure has changed to create individual directories for each plugin (and the plugin’s Dockerfile and requirements files).
Data Service (updated) A new example script, delete_pages.py, has been added to remove log pages from robots.
Estop (updated) The estop no-gui example’s logging statements have been improved.
GraphNav Command Line (updated) Has commands to clear the map on the robot, and to manually close the loop in a map. Updated to properly return the lease when exiting the script. Optimized to only upload snapshots to the robot that are not already present.
Mission Recorder (updated) Fixed the localization node to use the nearest fiducial.
Network Compute Bridge (new) The example has a network compute bridge work service example, which runs a tensorflow model and registers the service with the robot. Additionally, the example contains a client-side example that queries the network compute bridge service to identify objects in the robot camera images using the server’s tensorflow model.
Replay Mission (updated) Optimized to only upload snapshots to the robot that are not already present. Has an option to disable alternate route finding when running a mission.
Ricoh Theta (updated) Fixes a missing import required to run the continuous capture thread.
Self Registration (updated) Updated to create a payload with more realistic sample values.
Spot CAM (updated) The WebRTC example now records audio. The compositor example now includes Spot CAM IR support.
Upload Choreographed Sequence (updated) Returns a clearer error message if being used with an incorrect license.
Web Cam Image Service (updated) The web cam example now has better support for Windows, and has a debug mode which will show a popup image window of the camera image.
Automated docking at charging stations is out of beta and available for enterprise customers. There have been a few updates to the protos regarding status reporting and handling "prep" poses.
Payloads that have been registered with the robot but have not yet been authorized will automatically have service faults raised on their behalf indicating their status. This will help prevent operators from forgetting to authorize payloads after attaching them to the robot.
Image Services Helper functions for creating image services that reduce the amount of boiler plate code required for creating an image service and ensure the necessary fields of the response RPCs will be populated by the service.
Data Acquisition Service
Helper functions for communicating with the on robot data acquisition service to acquire data, monitor the status of the acquisition, cancel requests, and download the data using the REST endpoint. These functions originally were in the data_acquisition_service example, but are now part of the bosdyn-client wheel.
Added new status STATUS_NEAR_GOAL as well as a new BodyMovementStatus to help differentiate between different kinds of states the robot can be in at the end of its trajectory.
The BosdynGraphNavLocalize node can now specify a full SetLocalizationRequest, rather than only localizing to the nearest fiducial.
When comparing blackboard values, there is a new HandleStaleness option to specify what the node should do if the blackboard value is stale.
is_estopped()helper for the estop client and robot.- Helper functions to create time ranges in the robot’s time.
- Downloader script for bddf log files.
Data Acquisition Data Acquisition Service on robots is now robust to port number changes. The previous work around to this problem was to always specify the same port when starting/restarting a service. Now, the port argument for external api services can use the default, which will choose an available ephemeral port.
Image Services
Robot Cameras image service will respond to GetImage requests with incorrect format (e.g requesting a depth image as format JPEG) using the STATUS_UNSUPPORTED_IMAGE_FORMAT_REQUESTED. Previously, this was returned as STATUS_IMAGE_DATA_ERROR.
The Ricoh Theta image service example improvements
- Automatically disables sleep mode when putting the ricoh theta into client mode (using
ricoh_client_mode.py). - By default, it now runs a background thread capturing images continuously to minimize the delays waiting for an image to appear when viewing from the camera.
- It will wait for the capture to be completely processed before returning an image. This fixes issues where a very old image would be displayed, since it would trigger a take picture, but just return the most recent processed image.
Command line client The "log" and "textmsg" commands now go through the DataBuffer service, and so can be read back by downloading bddf files from the robot.
EstopService timeout The maximum timeout on the EstopService (aka the motor cut authority) has been raised from 65 seconds to just over 18 hours and 10 minutes. The estop service also correctly reports an error if given an invalid timeout.
BDDF code has moved to the bosdyn-core package, so that it can be used separately from the client code. The new import location is bosdyn.bddf. The old import path via bosdyn.client.bddf is deprecated.
bosdyn-client now depends on the requests library for making http requests to download data acquisition results and bddf logs.
When a network transport failure occurs, depending on the particular operating system and version of gRPC installed, the error from the python SDK may not always be the most specific error possible, such as UnknownDnsNameError. It may instead be raised as either a generic RpcError, or another generic failure type such as UnableToConnectToRobotError.
Spot CAM LED illumination levels are not currently recorded or played back in Autowalk missions.
When capturing both a PTZ and Panoramic image in the same action, there may occasionally be two PTZ images captured along with the Panoramic image, rather than just one.
If you write a custom data acquisition plugin or image service, do not change its DataAcquisitionCapability or ImageSource set once it is running and registered. New capabilities may not be detected, and old capabilities may still be listed as available in the Data Acquisition service. To change the capabilities of a service: unregister it from the directory, wait until its capabilities are no longer listed in the Data Acquisition service, and then re-register it. This waiting also applies to restarting a service if its capabilities will be different upon restart.
If you write a custom data acquisition plugin without using our helper class, its GetStatus() rpc is expected to complete immediately. If it takes too long to complete it can cause timeouts when requesting GetStatus() of the data acquisition service.
If you register a new service with the robot, calling robot.ensure_client() to create a client for that service may result in a UnregisteredServiceNameError.
- Workaround: call
robot.sync_with_directory()beforerobot.ensure_client()
SE2VelocityLimits require care. Correct usage of the SE2VelocityLimit message requires the user to fully fill out all the fields, setting unlimited values to a large number, say 1e6.
Image service test program (new) A new tester program for image services is available to help with the development and debugging of new image service implementations.
Docking (new) Shows how to trigger the docking service to safely dock the robot on a charger.
Web Cam Image Service (updated) The web cam example now uses the new image service helpers.
Ricoh Theta Image Service (updated) Uses the new image service helpers. A few extra bug fixes as described above.
Data Service (updated) Added options to specify a time range, and automatically converts times to robot time.
Data acquisition (updated)
Uses the new data acquisition helpers. The data acquisition tester program has been moved to a common tester_programs directory.
Spot I/O: Data Acquisition
This release features a new system for acquiring, storing, and retrieving sensor data. It comprises several new services and their associated clients.
Data Acquisition Service: The coordinating service that will capture images, robot metadata, and delegate to plugins to capture custom sensor data.
Data Acquisition Plugins: User-implemented services that can capture data from sensors and save it into the store.
Data Acquisition Store: Interface for saving data and metadata to disk for later retrieval.
Image services: Existing interface used in a new way. User-implemented image services will now be displayed in the tablet for driving, and be automatically capturable by the Data Acquisition Service.
Stance: Allows precise placement of the feet of the robot, beyond just positioning the body.
Battery change pose: Rolls Spot over so that the battery is accessible removal and replacement.
Several changes have been made in preparation for the release of Spot’s arm. These represent new ways to accomplish the same control as before, but in a way that will be compatible with also controlling the robot’s arm in a future release.
Synchronized commands and feedback: A new synchronized_command for combining mobility control with arm and gripper control. This deprecates the mobility_command in the RobotCommand message. Additionally, the top-level command status has been moved into the individual full-body and mobility command feedback messages so that mobility and arm commands can individually report their state.
Stop: The existing full-body Stop command still exists, but there is an additional mobility-only Stop command that can be used to only stop the mobility without affecting any separate arm control.
To simplify the development of reliable services and report when problems arise, a new set of reportable faults has been added, usable by all services.
Fault Service: Used to report or clear faults pertaining to a service or payload. The Python SDK includes a client library for triggering and clearing faults through this service.
ServiceFaultState in RobotState: All reported service faults will be included in the RobotState message. Clearing active faults will move them into historical faults. All service faults will automatically be displayed in the tablet interface to inform users.
Directory and Payload Liveness faults: New options for directory and payload registration enable liveness monitoring. When this feature is implemented, alongside directory or payload keep-alives, service faults will be automatically raised when a service crashes or a payload disconnects.
Integrations: Boston Dynamics supported payloads incorporate service faults and liveness monitoring out of the box.
- Spot CORE will report service faults if it experiences issues during startup, fails to communicate with the robot, detects an invalid payload configuration, or fails to communicate to an expected LiDAR.
- Spot CAM will report service faults if it is disconnected from Spot or if any of its internal services crash.
- The
bosdyn.clientcommand line interface can show and monitor reported faults.
The robot now dedicates some internal storage space to user data and logging. In addition to the data acquisition system, the user can store messages, events, time-series data, or arbitrary binary blobs.
Data Buffer: New service interface for storing various kinds of data on the robot.
Data Service: Retrieval service that can be used to return the data stored in the data buffer.
BDDF: File format for large downloads of stored data, and tools for reading the file.
Download endpoints: HTTPS download of a zip file of data acquisition mission datasets or bddf-encoded data.
Point cloud service definitions are provided for retrieving point cloud data from LiDAR sensors, such as from the EAP payload.
Congestion control is now available for WebRTC streaming. External microphones supported, with control for selecting microphones and setting gain levels individually. Note: External microphone support only available on Spot CAM + IR.
The localization data now includes a transform to a "seed" frame, providing a consistent global frame for use across multiple runs on the same map.
Localization data can be requested relative to a particular waypoint, rather than only the waypoint that the robot is currently localized to.
Additional control for determining whether the robot will navigate through areas with poor quality features.
Additional mission nodes which support new functionality:
- Point the Spot CAM PTZ to a specified orientation.
- Dock the robot at a charging station.
- Capture data through the data acquisition service.
- Manipulate strings in the blackboard.
Play advanced choreographed routines for Spot. The choreography service requires a special license to use.
The new docking service provides a way to autonomously dock at a charging station. It is currently in beta, and requires a special license to use.
Graph Nav
- Added fiducial-related status errors in
SetLocalizationResponse, such as a fiducial being too far away or having poor data. - Edges now record mobility params that were set during record time, and use them when navigating those edges.
- “Stuck” detection has changed, and the robot will report much sooner when it has no way to make progress.
- Improved
StartRecordingResponseandCreateWaypointResponseto report errors about bad fiducials or point cloud data.
Fiducial Detection
- Fiducials now report a filtered pose in addition to the raw detected pose, to avoid jitter in individual detections.
- Fiducial detections include extra information, such as the detection covariance, camera frame, and status regarding ambiguity or error.
Mission Nodes
- The
BosdynGraphNavStatenode can specify the id of the waypoint to use for the reported localization.
Spot Check
- Added status field in
SpotCheckCommandResponse. - Improved the list of errors in
SpotCheckFeedbackResponsemessage. - Spot Check now checks and reports results on hip range of motion.
Python client
- Blocking “power on” and “power off” helpers report errors correctly, rather than always raising
CommandTimedOutErrorif the robot could not power on or off. - Added helper classes for registering and launching services.
- Added the ability to authenticate the robot instance from payload credentials.
- Printing the Spot SDK exceptions now provides more information.
- Increased default message size limit for receiving and sending messages to 100 MB
- Command line interface supports the new 2.1 functionality
- Payload commands.
- Payload registration commands.
- Fault commands.
- Data buffer commands.
- Data service commands.
- Data acquisition commands.
Image capture parameters
- Added exposure and gain parameters associated with an image capture.
License interface
- Added
GetFeatureEnabled()to theLicenseServiceto query for particular license features.
Robot Control
A behavior fault (CAUSE_LEASE_TIMEOUT) is raised when the usage of a lease times out, and must be cleared before the robot can be commanded again. This should have minimal effect on current clients, as this happens near the same time that the robot powers off from comms loss (which clears behavior faults).
Graph Nav
When GraphNav reports STATUS_STUCK while navigating, the robot will stop walking. It will need to be re-commanded to navigate in order to continue. Previous behavior was that the robot would continue walking when stuck until commanded to stop by a client.
Missions
Autowalk mission callback nodes only wait 10 seconds for a response. When a mission calls Tick() on a mission callback service, it expects a quick response. In 2.0 it would wait up to 60 seconds for a response before retrying. This has been reduced to 10 seconds in version 2.1. Callbacks that do any significant work should be written to return with STATUS_RUNNING quickly, and then continue to do their work on another thread rather than trying to fit in all of their work before returning a response. The service can then base their response to subsequent Tick() requests on the status of that thread.
When a network transport failure occurs, depending on the particular operating system and version of gRPC installed, the error from the python SDK may not always be the most specific error possible, such as UnknownDnsNameError. It may instead be raised as either a generic RpcError, or another generic failure type such as UnableToConnectToRobotError.
Spot CAM LED illumination levels are not currently recorded or played back in Autowalk missions.
When capturing both a PTZ and Panoramic image in the same action, there may occasionally be two PTZ images captured along with the Panoramic image, rather than just one.
If you write a custom data acquisition plugin or image service, do not change its DataAcquisitionCapability or ImageSource set once it is running and registered. New capabilities may not be detected, and old capabilities may still be listed as available in the Data Acquisition service. To change the capabilities of a service: unregister it from the directory, wait until its capabilities are no longer listed in the Data Acquisition service, and then re-register it. This waiting also applies to restarting a service if its capabilities will be different upon restart.
Furthermore, always specify the port that it should run on via the --port flag, and do not change it between restarts of your plugin or image service. If you must change the port, then you must reboot the robot.
If you write a custom data acquisition plugin without using our helper class, its GetStatus() rpc is expected to complete immediately. If it takes too long to complete it can cause timeouts when requesting GetStatus() of the data acquisition service.
If you configure the estop service with custom timeouts and set an invalid timeout, you will not receive an error, but the robot will set the timeout to something else. The maximum estop timeout is 60 seconds, and the maximum estop cut_power_timeout is 65 seconds.
If you register a new service with the robot, calling robot.ensure_client() to create a client for that service may result in a UnregisteredServiceNameError.
- Workaround: call
robot.sync_with_directory()beforerobot.ensure_client()
SE2VelocityLimits require care. Correct usage of the SE2VelocityLimit message requires the user to fully fill out all the fields, setting unlimited values to a large number, say 1e6.
The following services, fields, and functions will continue to work, but will be removed in a future version.
The LogAnnotationService is replaced with the DataBufferService, which allows user access to the logged data.
Mobility commands have been moved from RobotCommand, and into SynchronizedCommand within RobotCommand. When changing clients to use SynchronizedCommand, be aware that the feedback will be in the new SynchronizedCommand feedback. The top-level command status is also deprecated in favor of a status within individual feedback messages. Changing clients to use the new SynchronizedCommand will make them compatible with arm commands in a future release.
The representation of SE3Covariance has changed to a matrix. The individual element representation is deprecated.
In the map edge annotations, the ground_mu_hint and grated_floor fields have moved into the mobility_params message.
The helper functions in RobotCommandBuilder have new versions that use the new SynchronizedCommand.
sit_command() → synchro_sit_command()
stand_command() → synchro_stand_command()
velocity_command() → synchro_velocity_command()
trajectory_command() → synchro_se2_trajectory_point_command()
The non-synchro versions are deprecated, and will be removed at the time that the mobility commands are removed from RobotCommand.
- Example data acquisition plugin implementations.
- Examples for capturing and downloading data.
- Test program to validate a data acquisition plugin.
Comms Test (new) Demonstrates how to use the SDK to perform comms testing.
Data Service (new) Get comments and data index information from the robot.
Ricoh theta image service (new)
Create a standard Boston Dynamics API ImageService that communicates with the Ricoh Theta camera.
Service faults (new) Demonstrates raising service faults, clearing service faults, and implementation of directory liveness checks.
Spot detect and follow (new) Collects images from the two front Spot cameras and performs object detection on a specified class.
Stance (new) Exercises the stance function to reposition the robots feet.
Stitch front images Demonstrate how to stitch the front camera images together into a single image in an OpenGL shader.
Upload choreographed sequence (new) Shows how to use the Choreography service to upload an existing choreographed sequence to the robot, and have the robot execute that uploaded routine.
Velodyne client (new) Demonstrates how to use the Velodyne service to query for point clouds.
Web cam image service (new)
Implements the standard Boston Dynamics API ImageService and communicates to common web cameras using OpenCV.
World object with image coords (new) Demonstrates adding a world object that exists only in image coordinates, rather than having a full transform.
- Uses the new
SynchronizedCommandfor robot commands.
Frame trajectory command (updated)
- Uses the new
SynchronizedCommandfor robot commands.
- Added an option to auto-rotate images to be rightside-up.
- Added an option to retrieve images from user image services.
- Added support for more pixel formats.
GraphNav command-line (updated)
- Waypoints can be specified by either short codes or waypoint names.
- Waypoints sorted by creation time.
- Uses the new
SynchronizedCommandfor robot commands.
- Switched to use Data Buffer for logging instead of the deprecated
LogAnnotationService.
Mission question answerer (updated)
- Updated to prompt the user on the command line for an answer.
- Added support for navigating through feature-poor areas.
- Uses the new payload keep-alive.
Remote mission service (updated)
- Separated example_servicers.py into separate hello_world_mission_service.py and power_off_mission_service.py files.
- Added an option to skip the initial localization.
- Uses new helpers for registration.
- New option to delete all images from the USB drive.
- Support for the IR camera.
- Uses the new
SynchronizedCommandfor robot commands.
- Uses the new
SynchronizedCommandfor robot commands. - Supports battery change pose command.
- Uses the new
SynchronizedCommandfor robot commands. - Supports battery change pose command.
Ricoh Theta remote mission service (removed)
- This has been removed and replaced with the Ricoh Theta image service, which provides better integration for displaying and capturing data.
get_depth_plus_visual_image (removed)
- Example removed because all robot cameras include
depth_in_visual_framesources by default.
Spot check (removed)
- Users can run Spot Check from the tablet.
- Power Client detects errors during a power command right away and propagates them up to the application before the command timeout is reached.
Release 2.0.2 contains the same issues as release 2.0.1, listed below.
If you delete an object from the world object service, there is a chance that a ListWorldObjects call immediately afterwards may still include that object.
- Workaround: wait a short time before expecting the object to be gone.
If you register a new service with the robot, calling robot.ensure_client to create a client for that service may result in a UnregisteredServiceNameError.
- Workaround: call robot.sync_with_directory() before robot.ensure_client()
SE2VelocityLimits require care. The proto comment states that "if set, limits the min/max velocity," implying that one should not set values for any directions one does not want limited. However, if any of the numeric fields are not set in the message, they will be interpreted as 0. For example, if angular is not set but linear is, then the message will be incorrectly interpreted as having an angular limit of 0 and the robot will fail to rotate (obviously not the intent). Similarly, if the user only sets say the 'x' field of linear, then 'y' will be incorrectly limited to 0 as well.
- Workaround: Correct usage of the SE2VelocityLimit message requires the user to fully fill out all the fields, setting unlimited values to a large number, say 1e6.
LogAnnotationClient does not include async versions of its rpcs.
- Workaround: If you need to call these in an async manner, call them on a separate thread.
App tokens are no longer required to authorize applications. Instead, each robot itself will be licensed itself. From a programming perspective, this means that it is no longer necessary to load app tokens into the sdk object, or to fill them out in GetAuthTokenRequest.
If a client attempts to call a function for which the robot is not licensed, the robot will respond with an error related to the license issue. The PowerService and GraphNavService responses now include new error codes for license errors on certain actions.
There is a new LicenseClient which can be used to query the license information for a robot. License information can also be queried from the bosdyn.client command line utility.
- The robot previously accepted new commands when there were behavior faults, but did not execute them and would not provide feedback on them. The robot will now reject them with the new status
STATUS_BEHAVIOR_FAULT. - The python SDK will throw the exception
BehaviorFaultError. 2.0.0 clients will throw aResponseErrorin these cases.
- If the fiducials are not visible, the action will fail with
STATUS_MISSING_FIDUCIALS. When starting recording or creating a manual waypoint in the GraphNavRecordingService, the client can require certain fiducials to be visible. If the fiducials are not visible, the action will fail withSTATUS_MISSING_FIDUCIALS. - When recording a map, grated floor mode and ground friction hints that are set in the recording environment are now correctly recorded into the map and used during playback.
- Added an option to the Spot CAM MediaLogService to retrieve the raw (unstitched) images for a log point.
- When a payload is authorized, it is given full access to the services on the robot, rather than a limited set. For example, a payload could now operate Spot.
- Removed some obsolete or internal protobuf messages and service RPCs which were not in use in the SDK.
- Fixed an issue where the SDK would continuously try to request new tokens if it lost connection to the robot at the time when it tried to renew its current user token.
Release 2.0.1 contains the same issues as release 2.0.0, listed below.
If you delete an object from the world object service, there is a chance that a ListWorldObjects call immediately afterwards may still include that object.
- Workaround: wait a short time before expecting the object to be gone.
If you register a new service with the robot, calling robot.ensure_client to create a client for that service may result in a UnregisteredServiceNameError.
- Workaround: call robot.sync_with_directory() before robot.ensure_client()
SE2VelocityLimits require care. The proto comment states that "if set, limits the min/max velocity," implying that one should not set values for any directions one does not want limited. However, if any of the numeric fields are not set in the message, they will be interpreted as 0. For example, if angular is not set but linear is, then the message will be incorrectly interpreted as having an angular limit of 0 and the robot will fail to rotate (obviously not the intent). Similarly, if the user only sets say the 'x' field of linear, then 'y' will be incorrectly limited to 0 as well.
- Workaround: Correct usage of the SE2VelocityLimit message requires the user to fully fill out all the fields, setting unlimited values to a large number, say 1e6.
LogAnnotationClient does not include async versions of its rpcs.
- Workaround: If you need to call these in an async manner, call them on a separate thread.
- Example that utilizes the 360-degree Ricoh Theta camera during an Autowalk mission.
- Example that shows how to upload a file to a Google Cloud Platform (GCP) bucket or an Amazon Web Services (AWS) S3 bucket.
- Updated to account for the additional state metrics that are reported. Older versions of this example may fail when connecting to updated robots.
- Added support for viewing the WebRTC stream.
- The example script does not localize itself to any map, but assumes the robot is already localized or that the mission has a localization node in it.
- It verifies that an estop is properly connected before trying to run the mission.
- It contains an additional --timeout parameter that can be used to set an overall time limit on mission execution.
- Can add relocalization nodes to a mission.
- Fixed a UI crash on MacOS X.
The APIs used by Autowalk are now accessible to developers.
- Overall conceptual documents
- GraphNavService: Upload and download maps of the environment, update localizations to that map, and command the robot to autonomously navigate to a location in the map. Example usage can be found in
graph_nav_command_line.py. Examples of interpreting the map data can be found ingraph_nav_view_map.py - GraphNavRecordingService: Record maps while the robot walks around. Example usage found in
recording_command_line.py - MissionService: Load and play autonomous missions. Example mission creation is shown in
mission_recorder.pywith upload and playback usage shown inreplay_mission.py - RemoteMissionService: A new method for handling mission callbacks, where the mission can trigger user code via an rpc. For building your own callbacks, see the examples in remote_mission_service.
Control and query all hardware features of the Spot CAM. For examples of using each service, see the Spot CAM command line example.
- CompositorService and StreamQualityService: change the layout and quality of the webrtc stream.
- PtzService: Direct PTZ cameras to desired poses.
- LightingService: Control the individual brightness of the illuminator LEDs.
- MediaLogService: Save and retrieve high-resolution images to and from the internal USB drive for later processing.
- AudioService: Upload and play sounds over the Spot CAM speakers.
- NetworkService: Adjust networking settings.
- HealthService, VersionService, PowerService: Query the status of the hardware and software, and power components on and off.
Payloads with a compute component can self-register with Spot and API services
- DirectoryRegistrationService: Allows end users to register new gRPC services running on a payload into the robots service directory. This allows for communicating through the robot’s proxy to the service from off-robot, and for registering mission callbacks for integrations with Autowalk missions. See
directory_modification.pyfor example usage. - PayloadRegistrationService: Payloads can now register themselves with the robot, providing their properties and awaiting authorization from a robot administrator. See the self_registration and payloads examples for how to register your own payload.
Learn more about how Spot is perceiving the world around it.
- WorldObjectService: Request details of any objects that has been detected in the world, and add your own detections. Example usage can be found in
mutate_world_objects.py,fiducial_follow.py, andadd_image_coordinates.py. - LocalGridService: Request maps of the area around the robot, including terrain height and obstacle classification. Example usage shown by the bosdyn.client command line utility and the
basic_streaming_visualizer.pyexample. - depth_in_visual_frame image sources. These depth map images have the same dimension, extrinsics, and intrinsics as the grayscale image sources, which can help with pixel-depth correspondence issues.
- Python QuickStart has been revamped to streamline getting up and running on the SDK.
- Conceptual documentation has been added to explain key ideas on how to develop for Spot.
- Payload developers guide has been added.
- Generated documents of the API protocol have also been added.
- Reduced API request overhead by several hundred bytes/request.
- TimeSync estimator more resilient to outlier latencies and temporary network outages.
- PowerState: Overall charge percentage and estimated runtime.
- KinematicState: Body velocities are now available in KinematicState.
- RobotState: Foot contact state (in contact vs. not in contact).
- Can now disable various low-level locomotion defaults for special situations and terrain (stair tracking, pitch limiting, cliff avoidance).
- Body rotation can be specified as an offset to nominal or to horizontal.
- See more details in the Breaking Changes section.
- Downloading of depth images supported. Depth maps will be written to PGM files.
- Directory listing has improved formatting.
Version 2.0 contains several breaking changes. While some clients and programs written for the version 1.* SDK may still work, expect some updates to be necessary for most programs.
Documentation of frames on Spot:
- Documentation of frames on Spot (link):
- The Frame message (
geometry.proto) and FrameType have been deprecated, and the frame is now described as a string throughout the API. - When receiving data from the robot (robot state, images, grid maps, world objects, etc.), the data will come with a string describing the frame it is represented in, but also a FrameTreeSnapshot message which describes how to transform the data into other frames.
- Use the helpers in
frame_helpers.py(in particularget_a_tform_b) to compute appropriate transforms for your use case. Seeframe_trajectory_command.pyfor an example of using transforms to command the robot. - Code written for version 1 will need to update to the following new convention:
| Version 1 frame enum | Version 2 frame string | frame_helpers.py constant |
|---|---|---|
| FRAME_KO | “odom” | ODOM_FRAME_NAME |
| FRAME_VO | “vision” | VISION_FRAME_NAME |
| FRAME_BODY | “body” | BODY_FRAME_NAME |
New RpcError exceptions can be raised during rpc calls. If you were already catching RpcErrors, you will catch these. If you were catching individual subclasses, be aware of these new ones.
- PermissionDeniedError
- ResponseTooLargeError
- NotFoundError
- TransientFailureError
There are some new exceptions that can be thrown due to errors with the request before any rpc is made. They generally indicate programmer error, so depending on your use case it may be acceptable to not catch them to find bugs in your program. If it is important to catch all exceptions, be aware that these exist, and all inherit from bosdyn.client.Error
- TimeSyncRequired
- NoSuchLease
- LeaseNotOwnedByWallet
When creating clients or channels from a Robot object, a new class of exceptions inheriting from RobotError may be raised. NonexistentAuthorityError is no longer thrown, but other RpcErrors may be raised.
- UnregisteredServiceError
- UnregisteredServiceNameError
- UnregisteredServiceTypeError
Robot command client will throw a new error if a frame is specified that the robot does not recognize.
- UnknownFrameError
- Trajectories must now specify the frame name in the parent message instead of the trajectory itself.
- Trajectory commands can no longer be specified in a body frame since the output behavior can be ambiguous.
- Robot command messages were split into different proto files (basic_command, full_body_command), which will change import/include paths.
- ‘vel’ field in SE3TrajectoryPoint renamed to velocity (
trajectory.proto) - Updates in
Payload.proto- LabelPrefix field was changed from String to Repeated String
- body_T_payload renamed to body_tform_payload
- mount_T_payload renamed to mount_tform_payload
- All Frame messages have been replaced by frame strings where applicable.
- AddLogAnnotationResponse does not have a status field anymore, errors are encoded in the message header information
- ko_tform_body, vo_tform_body, and ground_plane_rt_ko in Kinematic state have been replaced with the transforms_snapshot.
- The SampleCommon message for image captures has been replaced by acquisition time and a FrameTreeSnapshot.
- bosdyn-client has added a dependency on numpy
- Autowalk missions and maps recorded with version 1.1 are not compatible with version 2.0
If you delete an object from the world object service, there is a chance that a ListWorldObjects call immediately afterwards may still include that object.
- Workaround: wait a short time before expecting the object to be gone.
If you register a new service with the robot, calling robot.ensure_client to create a client for that service may result in a UnregisteredServiceNameError.
- Workaround: call robot.sync_with_directory() before robot.ensure_client()
SE2VelocityLimits require care. The proto comment states that "if set, limits the min/max velocity," implying that one should not set values for any directions one does not want limited. However, if any of the numeric fields are not set in the message, they will be interpreted as 0. For example, if angular is not set but linear is, then the message will be incorrectly interpreted as having an angular limit of 0 and the robot will fail to rotate (obviously not the intent). Similarly, if the user only sets say the 'x' field of linear, then 'y' will be incorrectly limited to 0 as well.
- Workaround: Correct usage of the SE2VelocityLimit message requires the user to fully fill out all the fields, setting unlimited values to a large number, say 1e6.
LogAnnotationClient does not include async versions of its rpcs.
- Workaround: If you need to call these in an async manner, call them on a separate thread.
- Register, update, and unregister a service.
- Renamed from
get_payload. - Expanded to show payload version handling.
- Example showing how to set up a payload that registers itself with the robot, hosts a service, and registers its service with the robot.
add_image_coordinates_to_scene (Renamed to world_object_with_image_coordinates in 2.1.0)
- Example using the API demonstrating adding image coordinates to the world object service.
- New EstopNoGui as a command-line addition to the GUI version of the E-Stop example.
get_depth_plus_visual_image (Removed in 2.1.0)
- Example demonstrates how to use the new depth_in_visual_frame image sources to visualize depth in a fisheye image.
- Example program demonstrates how to retrieve information about the state of the currently-running mission.
- Example program shows how to retrieve Spot's location in both the visual and odometry frames. Using these frames, the program shows how to build and execute a command to move Spot to that location plus 1.0 in the x axis.
- Example demonstrates 3 different methods for working with Spot asynchronous functions.
- Example demonstrate how to use the world object service to list the objects Spot can detect, and filter these lists for specific objects or objects after a certain time stamp.
- Command line interface for graph nav with options to download/upload a map and to navigate a map.
- Example shows how to load and view a graph nav map.
- Example with an interface for operating Spot with your keyboard, recording a mission, and saving it.
- Run a gRPC server that implements the RemoteMissionService service definition.
- Connect a RemoteClient directly to that server.
- Build a mission that talks to that server.
- Example on how to replay a mission via the API.
- Examples to demonstrate how to interact with the Spot CAM.
- Example to visualize Spot's perception scene in a consistent coordinate frame.
- Examples to demonstrate how to use the world object service to add, change, and delete world objects.
- Added support for Windows driver.
-
Missions API Beta and Callbacks When an Autowalk Mission is created with a "Callback" event, a client can detect that change using a beta version of the Mission API, then tell the robot to continue or abort the Mission. Example uses include a sensor payload that detects Callback events and captures sensor information before advancing the mission, and a desktop UI which waits for the user to push a button before advancing the mission.
-
External Forces Beta. Mobility commands can specify how to handle external forces. Examples of external forces could include an object that Spot is towing, or an object Spot is pushing. The default behavior is to do nothing, but clients can specify whether Spot should estimate external forces and compensate for it, or explicitly specify what the external forces are.
-
Depth image extrinsics are fixed. In earlier 1.1.x releases, the extrinsics were incorrectly the same as the fisheye cameras.
-
App Token expiration logging.. The Python SDK object logs if the app token will expire in the next 30 days. New tokens can be requested at support@bostondynamics.com.
- mission_question_answerer demonstrates how to build a client which responds to Mission Callbacks.
1.1.1 has no SDK-related changes.
The 1.1.0 SDK software is published under a new software license which can be found in the LICENSE file at the top of the SDK directory.
-
ImageService exposes depth maps from on-board stereo cameras as additional image sources. Image Sources specify an ImageType to differentiate depth maps from grayscale images.
-
PayloadService is a new service which lists all known payloads on the robot.
-
SpotCheckService is a new service which runs actuator and camera calibration.
-
E-Stop soft timeouts. In prior software release, E-Stop endpoints which stopped checking in would result in the power to the robot's motors being cut immediately. Now the E-Stop endpoint can be configured so Spot will attempt to sit followed by cutting power. The timeout parameter for an E-Stop endpoint specifies when the sitting behavior starts, and the cut_power_timeout parameter specifies when the power will cut off.
-
TerrainParams can be added to MobilityParams to provide hints about the terrain that Spot will walk on. The coefficient of friction of the ground can be specified. Whether the terrain is grated metal can also be specified.
-
Log Annotations a new type of log: Blob for large binary data.
The sample code directory structure has changed to directory-per-example under python/examples. Each example includes a requirements.txt file for specifying dependencies.
-
estop is a desktop GUI which creates an E-Stop endpoint for a robot. This example demonstrates how to use the E-Stop endpoint system, and is a useful utility on its own.
-
follow_fiducial is an example where Spot will follow an AprilTag fiducial that it can see in its on-board cameras. This demonstrates how to use camera extrinsics and intrinsics to convert pixels to world coordinates, and how to use the trajectory commands.
-
get-image is a simple example to retrieve images from Spot and save them to disk. It shows how to use the basics of the image service.
-
get-payload is a simple example which lists all of the payloads on the robot. It shows how to use the payload service.
-
get_robot_state is a simple example to retrieve robot state.
-
hello_spot is carried over from prior SDK releases. It is an introductory tutorial showing basic use of the Spot SDK.
-
logging demonstrates how to add custom annotations to Spot’s log files.
-
spot_check demonstrates how to use SpotCheck - Spot’s in-the-field calibration behavior..
-
spot_light is a demo where Spot rotates its body while standing to try to face a flashlight seen in its front cameras.
-
spot_tensorflow_detector demonstrates how to integrate the Spot SDK with Tensorflow for object classification from images.
-
time_sync is a simple example demonstrating how to use the TimeSync service.
-
wasd is carried over from prior SDK releases. It is an interactive program which uses keyboard control for the robot, and demonstrates how to use a variety of commands.
-
xbox_controller demonstrates how to specify more advanced options for mobility commands.
-
Too many invalid login attempts will lock a user out from being able to authenticate for a temporary period to prevent brute-force attacks. GetAuthTokenResponse indicates this state with a STATUS_TEMPORARILY_LOCKED_OUT.
-
Elliptic Curve (ECDSA) cryptography used for user tokens - reducing the size of RPC requests by several hundred bytes.
-
gRPC exceptions are correctly handled in Python 3.
-
Command-line tool handles unicode robot nicknames correctly.
-
Command-line tool supports retrieving robot model information (URDF and object files)
-
Command-line tool supports retrieving multiple images at once.
-
“Strict Version” support for software version.
-
App Token paths which include “~” will automatically expand, rather than fail.
-
Mobility Commands which have MobilityParams.vel_limit with only a min or max velocity are correctly handled. In prior releases, these commands would result in no movement at all.
-
Mobility Commands which have BodyControlParams.base_offset_rt_footprint.reference_time in the past result in a STATUS_EXPIRED response rather than a STATUS_INVALID_REQUEST.
-
SE2VelocityCommands with unset slew_rate_limit are correctly handled. In prior releases, an unset slew_rate_limit would result in the robot walking in place.
-
Removed support for Python 2.7. Only Python 3.6+ is supported due to upcoming Python 2 End-of-Life. Windows 10, MacOS, and Ubuntu LTS are still supported.
-
The HINT_PACE LocomotionHint is no longer supported due to physical stability issues. Any commands which specify a HINT_PACE LocomotionHint will be treated like a HINT_JOG LocomotionHint is specified.
-
HINT_AUTO_TROT and HINT_AUTO_AMBLE are deprecated as names - use HINT_SPEED_SELECT_TROT and HINT_SPEED_SELECT_AMBLE respectively going forward.
-
Protocol Buffer locations changed to split services from messages. Any direct imports of protocol buffers by client applications will need to change to support the 1.1.0 version changes.
-
Improved documentation on SDK installation.
-
Clearer Python dependency requirements.
-
RobotId service exposes computer serial number in addition to robot serial number.
-
wasd image capture works in Python 3.
-
Fixed timing bugs in power service.
Initial release of the SDK.