You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ The official Spot SDK documentation also contains information relevant to the C+
21
21
-[Payload developer documentation](https://dev.bostondynamics.com/docs/payload/readme). Payloads add additional sensing, communication, and control capabilities beyond what the base platform provides. The Payload ICD covers the mechanical, electrical, and software interfaces that Spot supports.
22
22
-[Spot API protocol definition](https://dev.bostondynamics.com/docs/protos/readme). This reference guide covers the details of the protocol applications used to communicate to Spot. Application developers who wish to use a language other than Python can implement clients that speak the protocol.
23
23
24
-
This is version 4.1.0 of the C++ SDK. Please review the [Release Notes](docs/cpp_release_notes.md) to see what has changed.
24
+
This is version 4.1.1 of the C++ SDK. Please review the [Release Notes](docs/cpp_release_notes.md) to see what has changed.
The main classes contained in this folder are ClientSdk and Robot.
17
-
***ClientSdk**: Class for settings typically common to a single developer and/or robot fleet.
18
-
***Robot**: Class for settings common to one user's access to one robot. This is the main point
19
-
of access to all client functionality.
20
18
21
-
For example, to list the robot image sources using the Image client, simply create an Sdk object,
22
-
create a Robot object, authenticate, create the client and call the
19
+
-**ClientSdk**: Class for settings typically common to a single developer and/or robot fleet.
20
+
-**Robot**: Class for settings common to one user's access to one robot. This is the main point
21
+
of access to all client functionality.
22
+
23
+
For example, to list the robot image sources using the Image client, simply create an Sdk object,
24
+
create a Robot object, authenticate, create the client and call the
23
25
corresponding method, as shown below. It is that simple!
26
+
24
27
```
25
28
auto client_sdk = ::bosdyn::client::CreateStandardSDK("hello_spot");
26
29
auto robot = client_sdk->CreateRobot("10.0.0.3").move();
@@ -29,5 +32,5 @@ auto image_client = robot->EnsureServiceClient<::bosdyn::client::ImageClient>().
29
32
auto result = image_client->ListImageSources().move();
30
33
```
31
34
32
-
Clients that trigger robot movement also need to set up the TimeSync, Lease and E-Stop clients. Our
33
-
[Python examples](https://github.com/boston-dynamics/spot-sdk/tree/master/python/examples) repository contains many tutorials on how to use the clients. The API for the Spot Python SDK is very similar to the API for the Spot C++ SDK, and most Python examples can be used as reference on how to implement C++ applications. The Spot C++ SDK contains examples as well, listed [here](../../examples/README.md).
35
+
Clients that trigger robot movement also need to set up the TimeSync, Lease and E-Stop clients. Our
36
+
[Python examples](https://github.com/boston-dynamics/spot-sdk/tree/master/python/examples) repository contains many tutorials on how to use the clients. The API for the Spot Python SDK is very similar to the API for the Spot C++ SDK, and most Python examples can be used as reference on how to implement C++ applications. The Spot C++ SDK contains examples as well, listed [here](../../examples/README.md).
0 commit comments