Components

A component connects Profinity to a device, a protocol or a destination for data, and you add each one to a profile. This section covers every component Profinity ships, grouped by what it connects to. To add one, refer to How to add a component to your profile.

Connect to devices and buses

• CAN bus adapters: connect Profinity to a CAN bus with a bridge, Peak USB, SocketCAN, SocketCANd, CANdapter, or the virtual adapter.
• Industrial protocols: poll BACnet, EtherNet/IP, Modbus, Open Platform Communications Unified Architecture (OPC UA) or S7 devices into tags, or expose tags as an OPC UA server.
• Battery management systems: add a Prohelion Battery Management Unit (BMU), read its dashboard and update its firmware.
• Chargers and power supplies: add a TDK, Siglent, or Elcon charger, set its limits and start a charge.
• Motor controllers: add a WaveSculptor, read its dashboard and update its configuration and firmware.
• Elmar Solar MPPT: monitor an Elmar Solar maximum power point tracker.

Store, send and share data

• Loggers: write tag collections or CAN messages to files, a Secure Shell (SSH) File Transfer Protocol (SFTP) server, InfluxDB v1 or Prometheus.
• Historians: store tag history in InfluxDB v2, InfluxDB v3 or a SQL database.
• Publishers and Subscribers: move tag values to and from Message Queuing Telemetry Transport (MQTT) brokers and web services.
• Tag Relays: share live tags between Profinity instances.
• Prohelion Cloud Dashboard: send tag values to the Prohelion Cloud platform.

Display and extend

• Dashboard Component: show a YAML dashboard bound to existing tags.
• Using a Custom Component: add a custom component to a profile.
• Pack a Custom Component: pack a working component so another installation can add it.

Behaviour shared by components

• Connections and reconnecting: how components that connect start, show a problem and recover.
• Logging modes: what the Snapshot, On Change and Everything modes send.