Generic Component

The generic component subtype enables you to add support for unique types of hardware that do not already have an appropriate API defined for them.

For example, when using an arm component, it makes sense to use the arm API, which provides specific functionality an arm component needs, such as moving to position or stopping movement. If you want to use an LED display, you need very different functionality that isn’t currently exposed in any API. Instead, you can use the generic component API to add support for your unique type of hardware, like LED displays, to your machine.

There are no built-in generic component models (other than fake). Use generic for a modular resource model that represents a unique type of hardware.

Supported Models

Before creating a new generic component, check whether one of the following modular resources supports your component.

Built-in models

For configuration information, click on the model name:

Modular Resources

Search for additional generic models that you can add from the Viam Registry:

For configuration information, click on the model name:

Control your board with Viam’s client SDK libraries

To get started using Viam’s SDKs to connect to and control your robot, go to your robot’s page on the Viam app, navigate to the Code sample tab, select your preferred programming language, and copy the sample code generated.

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

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

Be sure to import the generic package for the SDK you are using:

from viam.components.generic import Generic

import (
  "go.viam.com/rdk/components/generic"
)

API

The generic component supports the following method:

GetGeometries

Get all the geometries associated with the generic component in its current configuration, in the frame of the generic component. The motion and navigation services use the relative position of inherent geometries to configured geometries representing obstacles for collision detection and obstacle avoidance while motion planning.

my_generic = Generic.from_robot(robot=robot, name="my_generic_component")

geometries = await my_generic.get_geometries()

if geometries:
    # Get the center of the first geometry
    print(f"Pose of the first geometry's centerpoint: {geometries[0].center}")

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.

my_generic = Generic.from_robot(robot=robot, name="my_generic_component")

raw_dict = {
  "command": "raw",
  "raw_input": "home"
}
await my_generic.do_command(raw_dict)

myGeneric, err := generic.FromRobot(robot, "my_generic_component")

resp, err := myGeneric.DoCommand(ctx, map[string]interface{}{"command": "example"})

Close

Safely shut down the resource and prevent further use.

my_generic = Generic.from_robot(robot, "my_generic")

await my_generic.close()

myGeneric, err := generic.FromRobot(robot, "my_generic")

err := myGeneric.Close(ctx)

Troubleshooting

You can find additional assistance in the Troubleshooting section.

You can also ask questions in the Community Discord and we will be happy to help.