Introduction #

V-Link introduced profiles with version 3.1.0 to make it easier adding new configurations and making it compatible with a wider range of cars.

Currently we have 2 types of profiles:

• Vehicle Profiles– Used for car specific CAN messages etc.
• Interface Profiles– Used for additional interfaces like the ADC

The vehicle profile is what you choose when you start the application for the first time. When you selected a profile, the application will copy the default JSON files from the backend.

Vehicle Profiles #

The vehicle profiles are used to configure the interfaces and messages for CAN-Bus, RTI and the steering wheel controls. Currently we have three JSON files making up a profile:

• can.json
• rti.json
• swc.json

The preconfigured profiles can be found in this location:

~/v-link/backend/config/profiles/{platform}/{engine}

Interface Profiles #

Currently we have one interface profile,“adc.json”. The default file can be found in this location:

/v-link/backend/config/adc.json

This profile is used to configure the analog to digital interface.

Custom Profiles #

If your car isn’t listed, or if you’d like to modify an existing profile, the process is simple. You can either copy the files from the locations above or download the templates provided on this website.

If you only need CAN-Bus setup and don’t require RTI or steering wheel controls, that’s also possible—the app does not depend on any specific profile.

However, it’s essential to follow the same JSON structure used in the default profiles. Otherwise, your changes will not work.