Connection Types

📄️ CAN

CAN mappings can be auto generated from a DBC file. We created a tool to convert the dbc file to a capture config, if needed, ask us for more info.

For GPS logging, the address needs to be ttyUSB1, ttyUSB2 or ttyUSB3. There are also only a select few measurements allowed. The measurement names must be the following GNGNS, GPGGA and/or GPRMC. Under each measurements these variables are possible:

📄️ Modbus

Supported datatypes

📄️ S7

S7 is a polling based protocol over tcp. This is not ideal for high resolution logging, as it takes a certain time to complete a read request. These are the datatypes we support:

📄️ OPC UA

Collect data from OPC UA servers using subscription-based monitoring.

📄️ MQTT

The MQTT connection collects data by subscribing to one or more MQTT topics. Whenever a message is published on a subscribed topic, Capture receives the payload, parses it (string-based), and converts it into one or more datapoints.

📄️ Kafka

📄️ gRPC

Capture can collect data from a gRPC server by acting as a client. Capture uses server reflection to discover available RPC methods and then calls methods based on your variable mappings.

🗃️ Redis

3 items

🗃️ Prometheus

2 items

📄️ HTTP

With the HTTP connection you can poll an API endpoint. It is also supported to define one or more JSON paths to extract specific values or objects from a JSON response.

📄️ System Metrics

The System Metrics connection is a connection that is automatically added (for Edge versions starting from 2.2.1).