@wandelbots/nova-js

This library provides an idiomatic TypeScript client for working with the Wandelbots NOVA robotics software platform API.

npm install @wandelbots/nova-js

If you develop a React application we also provide a set of React components. It includes a Robot Jogging Panel, a Robot Visualization and other useful UI widgets.

Basic usage

The core of this package is the NovaClient, which represents a connection to a configured robot cell on a given NOVA instance:

import { NovaClient } from "@wandelbots/nova-js/v2"

const nova = new NovaClient({
  instanceUrl: "https://example.instance.wandelbots.io",
  cellId: "cell",
  // Access token is given in the developer portal UI when you create an instance
  accessToken: "...",
})

API calls

You can make calls to the REST API via nova.api, which contains a bunch of namespaced methods for each endpoint generated from the OpenAPI spec and documentation.

For example, to list the controllers configured in your cell:

const controllerIds = await nova.api.controller.listRobotControllers()
// -> e.g. ["ur5e", ...]

Documentation for the various API endpoints is available on your Nova instance at /api/v2/ui or on portal.wandelbots.io

Opening websockets

NovaClient has various convenience features for websocket handling in general. Use openReconnectingWebsocket to get a persistent socket for a given Nova streaming endpoint that will handle unexpected closes with exponential backoff:

const programStateSocket = nova.openReconnectingWebsocket(`/programs/state`)

this.programStateSocket.addEventListener("message", (ev) => {
  console.log(ev.data)
})

Websockets on a given NOVA client are deduplicated by path, so if you call openReconnectingWebsocket twice with the same path you'll get the same object. The exception is if you called dispose, which you may do to permanently clean up a reconnecting websocket and free its resources:

programStateSocket.dispose()

The reconnecting websocket interface is fairly low-level and you won't get type safety on the messages. So when available, you'll likely want to use one of the following endpoint-specific abstractions instead which are built on top!

Contributing

If you would like to contribute a change to this repository, see CONTRIBUTING.md.