User Destinations

The User Destinations section provides the WiCAN Pro with the ability to route specific telemetry data to multiple endpoints simultaneously. This is useful for users who want to send battery data to one service (like ABRP) while sending performance data to a private logging server or an MQTT broker. For the MQTT service, a better approach is to use the MQTT Group setting in each PID parameter, that way you only receive valid PID data, not stale data. Or, another approach is to specify the MQTT dest in every PID parameter. See Vehicle Group section for more info.

The WiCAN Pro supports up to 6 unique destinations.

1. Destination Types

Each destination slot can be configured as one of the following:

  • HTTP / HTTPS: A standard POST request. Use this for custom web servers or generic cloud APIs.
  • ABRP (A Better Routeplanner): A specialized preset. When selected, the WiCAN automatically formats the JSON payload to match the ABRP Telemetry API requirements. You simply provide your User Token.
  • MQTT_Topic: Instead of using the global MQTT settings, this allows you to publish a specific subset of data to a unique topic on your broker.

2. Timing and Logic

Unlike the global WebHook, which is purely interval-based, User Destinations offer more granular control over when data is sent:

  • Cycle (ms): The transmission frequency in milliseconds.
    • Value > 0: Data is sent on a fixed timer (e.g., 5000 for every 5 seconds).
    • Value = 0 (Event Driven): Data is sent instantly the moment a PID value changes. This is ideal for time-sensitive data like "Brake Pedal Status" or "Gear Position."
  • Batching: If multiple PIDs are assigned to the same destination, the WiCAN will bundle them into a single packet to conserve bandwidth.

3. Security and Authentication

For secure integrations, the WiCAN Pro supports several authentication methods per destination:

  • Auth / API Token: * Bearer Token: Standard for modern web APIs.
    • API Key (Header): Injects the key into the HTTP Header.
    • API Key (Query): Appends the key to the URL string.
    • Basic Auth: Username and Password encoding.
  • Cert Set: If using an HTTPS destination, you must select the corresponding Certificate Set (1-4) that you uploaded in the System tab. This ensures the WiCAN can verify the identity of the server before sending data.

4. Mapping Data to Destinations

Creating a destination is only the first half of the process. To actually send data there:

  1. Go to your Custom PIDs or Standard PIDs tabs.
  2. Edit a PID.
  3. Locate the Destination Dropdown.
  4. Select the Slot Number (1-6) you configured in this section.

5. Status Monitoring

Each destination includes a small status indicator:

  • Green: Last transmission was successful.
  • Red: Last transmission failed (Check your URL or Auth Token).
  • Gray: Destination is disabled or has not yet attempted to send data.
Table of Contents