📄️ ADS
With ads, we support most of the datatypes, also nested structs and arrays. The mapping we need to specify is the symbol name of the variable, struct, tcCOM object,... Ads is notification based and the max sample freq is 1000 Hz. Default, the cycle time of on change is 2 ms, if you want to have a faster or slower cycle time (slower cycle time results in a lower system load) you can specify the cycle time in the timer field of the variable. This will override the 2ms default cycle time. e.g.
📄️ 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.
📄️ GPS
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:
📄️ MQTT
MQTT is subscription based, we receive a notification when something is published on the topic. We receive the payloads as a string and are able to convert them automatically to the following datatypes:
📄️ Modbus
Supported datatypes
📄️ OPC UA
Authentication & advanced configs
📄️ Prometheus
With the Prometheus connection you can use the Capture collector as a Prometheus remote write destination. This way, you can send data collected by Prometheus to Capture.
📄️ 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:
📄️ 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.
📄️ Redis
With Redis you can use Pub/Sub to subscribe on a specific channel, or Key/Value to get the value assigned to a key.