Set the Driver List
Written by Sean Withers
Updated at November 24th, 2025
Table of Contents
Support Documentation:
These calls allow us to send a list of valid Driver ID codes down to the device.
The list is checked by the device when a Driver ID tag/code is presented. The device can optionally be configured to buzz until a valid tag is scanned - or only toggle it's output (to mobilize the asset) on valid tag scan.
This can alternatively be done via CSV import in the Device Manager UI (Device Operations -> Set Drivers)
Responds true if the input is valid.
Required fields:
- ID Type (1=DMRFID, 2=iButton, 7=Wiegand)
- IdData
- Flags
- Layout
The IdData field should be in the below formats:
1=DMRFID serial should contain 5 bytes (10 HEX Characters)
2=iButton serial should contain 5-6 byes (12 HEX Characters)
7=Wiegand serial should contain bit length as first byte
Example cURL
curl -X POST 'https://api.oemserver.com/v1.0/driverlist/set/310056' -H 'Authorization: Basic user/pass' -H 'Content-Type: application/json' --data-raw '{"Drivers": [{"IdType": 7, "IdData": "FBI0UA==", "Flags": "01"},{"IdType":1,"IdData":"001CB70A7B","Flags":"01"}], "Layout": 0}'
Driver List Memory Allocation and Limits
Maximum Number of Drivers per Layout
All Digital Matter devices allocate a fixed 128 kB (131,072 bytes) partition for storing the Driver List.
Depending on the selected Driver List Layout, the maximum number of drivers that can be stored varies:
| Layout | Bytes per Entry | Max Drivers |
|---|---|---|
| Short | 8 bytes | 16,375 |
| Long | 32 bytes | 4,093 |
| Short + Name | 40 bytes | 3,275 |
Note: Driver list impact on device Memory
The number of drivers stored in the Driver List does not affect how many GPS records a device can store when it goes out of coverage.
Each Digital Matter device allocates separate, fixed memory partitions for different types of data — one for the Driver List and another for GPS log data. Because these partitions are independent, adding or removing drivers has no impact on the space reserved for GPS records or trip history between uploads.
When the Driver List Partition Is Full
If the Driver List reaches its maximum capacity:
- Any additional drivers beyond the allocated partition size will not be saved.
- Write attempts that exceed the partition boundary are ignored automatically by the device.
- As a result, the list will effectively be truncated once it reaches its defined storage limit.
