LEMON Manuals: Even more car manuals for everyone: 1960-2025
Home >> Mercedes Benz >> 2019 >> Sprinter 2500 Van Cargo, 3.0L Eng, 4WD >> Repair and Diagnosis >> TMC Recommended Practices >> Onboard Vehicle Electronics >> RP 1227 - Mobile Device Communication API >> RP 1227 - Mobile Device Communication API >> 6. Functional Specification >> 6.2 API File Naming Conventions
April 5, 2026: LEMON Manuals is launched! Read the announcement.

6.2 API File Naming Conventions

Each vendor will provide a different name implementation of the API as a number of these implementations could simultaneously reside on the same mobile device. No vendor shall name its implementation "RP121032".  Each vendor will have a name of at least 4 characters for the filename prefixes listed below. Although long file names are supported by all of the operating systems mentioned herein, an API DLL shall still be named in accordance with the file allocation table (FAT) file system naming convention (up to eight characters for the file name and three characters for the extension).

Implementations will follow the following format (using VENDRX for a vendor name):

File Type Install Directory Resultant File Name
INI File Application defined location VENDRX.ini
Library File Application defined location VENDRX.so (if applicable)

Application developer may be using DLA drivers from multiple vendors and if that is the case the rp121032.ini  needs to updated accordingly and that would be the responsibility of the application developer. On some platforms the library file is a static library and is therefore linked into the application provider's executable.