Control your generic component with the generic API

The generic API allows you to give commands to your generic components for running model-specific commands using DoCommand.

The generic component supports the following method:

Method NameDescriptionviam-micro-server Support
DoCommandExecute model-specific commands.

GetResourceNameGet the ResourceName for this generic component with the given name.

CloseSafely shut down the resource and prevent further use.

Establish a connection

To get started using Viam’s SDKs to connect to and control your generic component and the rest of your machine, go to your machine’s page on the Viam app, Navigate to the CONNECT tab’s Code sample page, select your preferred programming language, and copy the sample code.

To show your machine’s API key in the sample code, toggle Include API key.

When executed, this sample code will create a connection to your machine as a client. Then control your machine programmatically by getting your generic component from the machine with FromRobot and adding API method calls, as shown in the following examples.

The following examples assume you have a board called “my_board” configured as a component of your machine. If your board has a different name, change the name in the code.

Import the generic component package for the SDK you are using:

from viam.components.generic import Generic
import (
  "go.viam.com/rdk/components/generic"
)
#include <viam/sdk/components/generic/generic.hpp>

API

DoCommand

Execute model-specific commands. If you are implementing your own generic component and add features that have no built-in API method, you can access them with DoCommand. Supported by viam-micro-server.

Parameters:

  • command (Mapping[str, ValueTypes]) (required): The command to execute.
  • timeout (float) (optional): An option to set how long to wait (in seconds) before calling a time-out and closing the underlying RPC call.

Returns:

  • (Mapping[str, Any]): Result of the executed command.

Raises:

  • (NotImplementedError): Raised if the Resource does not support arbitrary commands.

Example:

my_generic_component = Generic.from_robot(robot=machine, name="my_generic_component")
command = {"cmd": "test", "data1": 500}
result = await my_generic_component.do_command(command)

For more information, see the Python SDK Docs.

Parameters:

Returns:

Example:

myGenericComponent, err := generic.FromRobot(machine, "my_generic_component")

command := map[string]interface{}{"cmd": "test", "data1": 500}
result, err := myGenericComponent.DoCommand(context.Background(), command)

For more information, see the Go SDK Docs.

Parameters:

Returns:

Example:

// Example using doCommand with an arm component
const command = {'cmd': 'test', 'data1': 500};
var result = myArm.doCommand(command);

For more information, see the Flutter SDK Docs.

GetResourceName

Get the ResourceName for this generic component with the given name.

Parameters:

  • name (str) (required): The name of the Resource.

Returns:

Example:

my_generic_component_name = Generic.get_resource_name("my_generic_component")

For more information, see the Python SDK Docs.

Parameters:

Returns:

For more information, see the Flutter SDK Docs.

Close

Safely shut down the resource and prevent further use.

Parameters:

  • None.

Returns:

  • None.

Example:

my_generic_component = Generic.from_robot(robot=machine, name="my_generic_component")
await my_generic_component.close()

For more information, see the Python SDK Docs.

There is no need to explicitly close a generic component’s resource in C++, as resource destruction is handled automatically by the generic component’s class destructor when variables exit scope.

Have questions, or want to meet other people working on robots? Join our Community Discord.

If you notice any issues with the documentation, feel free to file an issue or edit this file.