Skip to main content


The template functionality makes it possible for a user to manage the configuration of a range of devices by setting up a template with the required functionality, and then applying that to a number of devices.

Temlates overview


A template can contain the following configurations.

Advanced Configuration#

Most advanced configuration settings are available to be specified for a template. Options that aren't available for templates have been removed because they are too specific for each device and it doesn't make sense to set in a template.

The table shows the settings currently associated to the template, and clicking the edit button will open the settings UI, with all available settings.

Modules (Custom Code)#

Modules are created the same way for templates as they are for normal devices; chose a type depending on what you need the module for, and when creating a custom module of type service, it will automatically create a custom service for you and associate that to the same template.


Read more here.

Creating Custom Services#

Creating a custom service does not not autocreate a custom module as of now, so if you want to create a custom service, you should instead go create a custom module of the type service, then a service will be automatically created.

Overriding Default Services#

To override a default engine, like the obd_manager from a template, you can simply create a new service which has the same name as the default service.

Triggers and Jobs#

Triggers and Jobs are created the same way for templates as they are for normal devices.

More info about Jobs and Triggers


Loggers are created similarly to how they are for regular devices. They are a little different since creating loggers on a template will create buses as well. A prerequisite to setting up Tempalted Loggers is to have already created some CAN Messages and CAN Signals or PIDs in the Library.

Templated CAN Loggers#

To create a templated CAN logger, find the Loggers tab in the template you would like to edit, click Create, and CAN. You will be presented with a window like this:

Create can logger

Here you will need to select the CAN signal you'd like to log, and set the bus configuration. In a guide on importing CAN messages and signals through DBC files we imported some signals related to the seat temperatures. Here we can see those:

Select logged signal

The first logger you create on a template will always create a bus that's associated to that template. More buses will be created when loggers are created with a protocol, which none of the existing buses are set to. Multiple buses with the same protocol are not supported. When you click on the Bus dropdown, you will see both the buses that are associated to the template, and the buses which are 'supported' by the message. If one of these buses is selected, it will prefil the Protocol and Baudrate fields (there are no association made between the selected bus and the newly created logger/bus/template).


The Message supported buses section refers to the Used by Vehicle(s) dropdown in the CAN Message edit window in the library.

Logger buses

Let's say this signal can be logged on a bus with protocol ID 6 and default baudrate. You'd set the parameter values, save, and the next logger you create for this template, you can choose to fill these fields using the bus that was just created.

Can logger buses with tempalte bus

Templated PIDs#

The process for creating templated PID loggers is very similar as for CAN loggers. Go to the template's Loggers tab, click Create, then PID. You'll be presented with a window similar to this:

Logger buses

Most of this is identical to what you'd see when creating PID loggers for devices, with the exception of Bus settings. Take a look at the templated CAN loggers section to get an idea of how they work. A notable difference here is that for PID loggers, the Bus is optional. If one's not specified, the PID will be logged using the vehicle's default bus.


To use the templates, the common usage is the following.

  1. Create a template with a descriptive name.
  2. Make some changes to the template - change configuration, add loggers, custom code, etc.
  3. Add some devices to the template by clicking the devices tab and then "Add Device(s)", find one or more devices to add, and click save.
  4. Now to actually apply any of the changes to the devices, you should click "apply" on the template to apply the template to all associated devices, or to apply it one by one, click apply on each device.

To ensure reproducible behavior, please make sure to keep the configuration on each device as "clean" as possible, as that will make it easier to manage, and try to keep manual changes to devices with a template applied, as few as possible to avoid any colissions between the changes made manual and the changes from the template.