CAN Bus

CAN Bus

ID: uniflow.plugin.canbus  •  Category: Hardware Protocol  •  Version: v1.0.2

CAN Bus Plugin Reference Manual

1. Overview

Plugin Name: CAN Bus

Type: Hardware Protocol

Identifier: uniflow.plugin.canbus

Description

Receive and transmit data from vehicle networks and industrial CAN buses.


2. Configuration Parameters

The following configuration fields are available in the User Interface for this plugin:

Configuration SettingDescription
Adapter TypeSpecifies the adapter type.
Device Handle / COM PortNumeric value specifying the device handle / com port.
Bitrate (Kbps)Specifies the bitrate (kbps).
OBD2 Polling Interval (ms)Numeric value specifying the obd2 polling interval (ms).
Reconnect Delay (ms)Specifies the reconnect delay (ms).

3. Exposed Routes & Data Types

The following routes are available in the Uniflow catalog for this plugin:

Display NameRoute IDKindCategoryAccessData Type
Connection StatusMetaConnectedItemIdValue?ReadBool
Send Raw CAN FrameCmdSendRawIdCommand?ExecuteVariant
Send SignalCmdSendSignalIdCommand?ExecuteVariant

Route Parameters: Send Raw CAN Frame

This route requires the following parameters when executing commands or writes.

Parameter NameDisplay NameTypeRequired

Route Parameters: Send Signal

This route requires the following parameters when executing commands or writes.

Parameter NameDisplay NameTypeRequired

4. Usage Examples

Scenario A: Reading/Monitoring Data

To monitor data from CAN Bus, add the corresponding Input Node in the Rule Editor and select the desired property from the catalog. Link its output to any logical comparison or directly to an Action Node.

Scenario B: Triggering Actions

If the plugin supports writable properties or actions, use an Action Node in the Rule Editor. Configure the Target property to point to the CAN Bus action, and supply any required parameters mapping from your rule's logic.