Connectors

Other Protocols

Configure CAN bus, REST API, Edge Device, and custom protocol connectors.

In addition to OPC UA and Modbus TCP, Fleetera supports several other communication protocols.

CAN Bus

Controller Area Network (CAN) is a serial communication protocol used in vehicles, industrial machinery, and embedded systems.

Configuration

FieldDefaultDescription
Interfacecan0The CAN interface name on the edge gateway (e.g., can0, vcan0)
Baud Rate500000Communication speed in bits per second

Common baud rates

RateValueUse Case
125 kbps125000Low-speed diagnostics
250 kbps250000Standard industrial
500 kbps500000Standard automotive and industrial
1 Mbps1000000High-speed applications

REST API

REST connectors enable data acquisition from HTTP-based APIs and web services.

Configuration

FieldDescription
Base URLThe root URL for API calls (e.g., https://api.example.com/v1)
Auth TypeAuthentication method: None, Basic, Bearer token, or API key
HeadersOptional custom HTTP headers (key-value pairs)

Authentication types

TypeDescription
NoneNo authentication required
BasicHTTP Basic Authentication (username and password)
BearerOAuth 2.0 Bearer token in the Authorization header
API KeyAPI key sent as a custom header

Edge Device

Edge Device connectors reference devices that are managed directly by Fleetera Edge on the edge gateway. Use this when the edge device service is already configured outside of the Fleetera platform.

This protocol type accepts a generic JSON configuration object. No specific fields are required.

Custom Protocol

Custom connectors allow you to define connections to proprietary protocols or data sources that are not covered by the standard protocol types.

The configuration accepts any valid JSON object. Use this for custom integrations where you control both the edge device service and the data format.

CAN bus, REST API, and custom protocol support is available for connector configuration. Full end-to-end data acquisition for these protocols depends on the corresponding edge device services being deployed on the edge gateway.

On this page