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
| Field | Default | Description |
|---|---|---|
| Interface | can0 | The CAN interface name on the edge gateway (e.g., can0, vcan0) |
| Baud Rate | 500000 | Communication speed in bits per second |
Common baud rates
| Rate | Value | Use Case |
|---|---|---|
| 125 kbps | 125000 | Low-speed diagnostics |
| 250 kbps | 250000 | Standard industrial |
| 500 kbps | 500000 | Standard automotive and industrial |
| 1 Mbps | 1000000 | High-speed applications |
REST API
REST connectors enable data acquisition from HTTP-based APIs and web services.
Configuration
| Field | Description |
|---|---|
| Base URL | The root URL for API calls (e.g., https://api.example.com/v1) |
| Auth Type | Authentication method: None, Basic, Bearer token, or API key |
| Headers | Optional custom HTTP headers (key-value pairs) |
Authentication types
| Type | Description |
|---|---|
| None | No authentication required |
| Basic | HTTP Basic Authentication (username and password) |
| Bearer | OAuth 2.0 Bearer token in the Authorization header |
| API Key | API 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.