Velocity Meter (ACT2535)

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

Description

Serial source for the Aichi ACT2535 non-contact optical velocity meter. Outputs 2D ground velocity as VelocityMeter and VehicleSpeed data for vehicular fusion pipelines.

Inputs / Outputs

Inputs: (none)
Outputs: VelocityMeter, VehicleSpeed

Config aliases

Act2535Source, act2535Source, act2535, velocitymeter

Properties

The following fields are exposed in the node’s Properties panel in the UI. Types map to UI widgets (e.g. string → text input, number → numeric, boolean → toggle, select → dropdown, json → JSON editor).

Key	Label	Type	Default	Description / Notes
`port`	Serial Port	`string`	`COM10`	Serial port the ACT2535 is connected to (e.g. COM10 or /dev/ttyUSB0).
`baudrate`	Baud Rate	`number`	`115200`	Serial baud rate; the ACT2535 uses 115200 by default.
`hwFlowControl`	HW Flow Control	`boolean`	`true`	Enable RTS/CTS hardware flow control on the serial link.

Example node definition

A full node definition in config.json looks like the block below. Paste it under the sources key of your config, keyed by the node’s instance name (any identifier; it doesn’t have to match the node ID).

{
  "sources": {
    "act2535": {
      "outEndpoint": "inproc://act2535_data",
      "settings": {
        "baudrate": 115200,
        "hwFlowControl": true,
        "port": "COM10"
      }
    }
  }
}

Field reference

Field	Purpose
`outEndpoint`	ZMQ / inproc endpoint this source binds to publish its output. The runtime auto-generates one if omitted.
`settings`	All user-configurable fields — see the Properties table above.

Connections can also be declared at the top-level connections array when settings.explicitConnections is true, as an alternative to filling inputEndpoints on each node.

Loading documentation…