Skip to content

Log / replay CAN bus messages

Profinity can log and replay messages from your Controller Area Network (CAN) bus network, and can also log CAN bus data to timeseries databases such as InfluxDB and Prometheus.

To log a set of CAN bus messages, first add a CAN bus adapter to your profile, then connect to the adapter. Refer to How to connect to CAN bus for step-by-step guidance. Before logging, check that Profinity is receiving CAN bus messages in the SEND & RECEIVED CAN window (refer to Send / receive CAN bus messages). Once CAN bus messages are coming in to Profinity, you are ready to log.

Logging CAN bus messages

Profinity has two kinds of logger:

You configure all loggers in the same way, by adding the logger to the profile as a component.

The CAN File Logger and the CAN SFTP Logger record native CAN bus messages. The CAN SFTP Logger sends the files to a remote server over the Secure Shell (SSH) File Transfer Protocol (SFTP). The TAG File Logger and the TAG SFTP Logger instead record the values of the tags in selected tag collections.

The MQTT Publisher and the Webhook Publisher publish CAN-derived tag data to a Message Queuing Telemetry Transport (MQTT) broker or a webhook. You add them from the Publishers & Subscribers category in the same way.

CAN data log replayer

The CAN Data Log Replayer replays log files that were recorded earlier in Profinity. The replayer cannot replay InfluxDB or Prometheus data. It replays only a file log of CAN messages recorded by a File or SFTP logger. Profinity processes replayed messages as if it had received them from the bus, so they mix with any live traffic. How to replay CAN bus logs gives the procedure, the Replay CAN logs permission, the replay controls, and the warning about live traffic.

To log tag values instead, refer to Log tags to a file. To send packets to the bus, refer to Send / receive CAN bus messages.