CAN Source

Node ID: can · Role: Source · Realtime config: no

Description

CAN bus vehicle data source. Subtypes: Vector CAN, PEAK CAN. Reads wheel speeds, steering angles, and other vehicle signals. Outputs VehicleSpeed and CANData.

Inputs / Outputs

Inputs: (none)
Outputs: Can

Config aliases

CanDataSource, canDataSource, can

Properties

No user-facing properties.

Subtypes

Value	Display name	Extra properties
`vector`	Vector CAN	3 field(s)
`peak_can`	PEAK CAN	3 field(s)

Subtype: `vector` — Vector CAN

Property	Type	Default	Description
Channel Index `channel`	number	`0`
Baudrate `baudrate`	select	`500000`	Options: `125000`, `250000`, `500000`, `800000`, `1000000`.
Sender ID `senderId`	string	`can`

Subtype: `peak_can` — PEAK CAN

Property	Type	Default	Description
PCAN Channel `channel`	select	`PCAN_USBBUS1`	Options: `PCAN_USBBUS1`, `PCAN_USBBUS2`, `PCAN_USBBUS3`, `PCAN_USBBUS4`.
Baudrate `baudrate`	select	`500000`	Options: `125000`, `250000`, `500000`, `800000`, `1000000`.
Sender ID `senderId`	string	`can`

Example node definition

A minimal entry in config.json looks like the block below. Paste it under the sources key, keyed by an instance name of your choice. All settings are optional: anything not listed under settings uses the default from the Properties table above. See The configuration file for how the sections and endpoint wiring work.

{
  "sources": {
    "can": {
      "outEndpoint": "inproc://can_data",
      "type": "vector",
      "settings": {}
    }
  }
}

Loading documentation…