DRIVE OS Version: 7.0.3
What is the meaning of the following warning on NVIDIA Drive HW and is it safe to ignore:
TimeSensor::addData() Buffer full, draining data
Note the warning happens almost every 2 minutes.
Correction, once the Buffer full is triggered which takes about 2 minutes to reach this state the warning is issued every 2 seconds.
Notably, I see in the logs the following message being thrown:
SensorFactory: Override default timeSensor with the user passed one
I am reading more about it but it could likely offer some leads into the issue.
Dear @ussama.naal ,
Could you share full application log?
Absolutely,
[DW][INFO] ProgramArguments: Missing argument 'dwTracePath' requested
[DW][INFO] Starting my sample application...
[08-02-2026 07:57:41] Adding variable DW_Base:DW_Version
[08-02-2026 07:57:41] Added variable DW_Base:DW_Version
[08-02-2026 07:57:41] Platform: number of GPU devices detected 1
[08-02-2026 07:57:41] Platform: currently selected GPU device 0, Resource Data Dir: trt_10_08_10_05, Arch: ga10b
[08-02-2026 07:57:41] Platform: currently selected GPU device integrated ID 0
[08-02-2026 07:57:41] Context::mountResourceCandidateDataPath resource FAILED to mount from './resources': VirtualFileSystem: Failed to mount './resources/resources.pak'
[08-02-2026 07:57:41] Context::mountResourceCandidateDataPath resource FAILED to mount from '/home/xxxx/data': VirtualFileSystem: Failed to mount '/home/xxxx/data/resources.pak'
[08-02-2026 07:57:41] Context::findDataRootInPathWalk: Could not find ./data/DATA_ROOT in upto 7 parent directories from /usr/local/driveworks/targets/aarch64-Linux/lib/libdw_base.so.7.0
[08-02-2026 07:57:41] Context::findDataRootInPathWalk: Could not find ./data/DATA_ROOT in upto 7 parent directories from /usr/local/driveworks/targets/aarch64-Linux/lib/libdw_base.so.7.0
[08-02-2026 07:57:41] Context::findResourcesPackageInPathWalk: Could not find ./resources/resources.pak in upto 7 parent directories from /usr/local/driveworks/targets/aarch64-Linux/lib/libdw_base.so.7.0
[08-02-2026 07:57:41] Context::findResourcesPackageInPathWalk: Could not find ./resources/resources.pak in upto 7 parent directories from /usr/local/driveworks/targets/aarch64-Linux/lib/libdw_base.so.7.0
[08-02-2026 07:57:41] SDK: No resources(.pak) mounted, some modules will not function properly
[08-02-2026 07:57:41] [08-02-2026 07:57:41] Initialize DriveWorks SDK v7.0.3
[08-02-2026 07:57:41] [08-02-2026 07:57:41] Release build with GNU 13.2.0 from against Drive PDK v7.0.3.0
[08-02-2026 07:57:41] SensorFactory::createSensor() -> time.nvpps, nvpps-device=/dev/nvpps0
[08-02-2026 07:57:41] Found driver: time.nvpps
[08-02-2026 07:57:41] TimeSensorNVPPS: initialized with no UTC time reference.
[08-02-2026 07:57:41] output-timestamp parameter is deprecated and will be removed in next release
[08-02-2026 07:57:41] SensorFactory: Override default timeSensor with the user passed one
[08-02-2026 07:57:41] EndpointNVPPS: started on /dev/nvpps0
[08-02-2026 07:57:41] SensorFactory::loadPluginLibraryHelper:Succeed to load dynamic lib - /usr/local/driveworks/targets/aarch64-Linux/lib/libsensor_plugin_public_radar.so
[08-02-2026 07:57:41] SensorFactory::createSensor() -> lidar.custom, device=CUSTOM_EX,log_level=INFO,decoder-path=/home/xxxx/arm/libxxxx_lidar_plugin_arm.so,ip=10.0.0.4
[08-02-2026 07:57:41] Found driver: lidar.custom
[08-02-2026 07:57:41] output-timestamp parameter is deprecated and will be removed in next release
[08-02-2026 07:57:41] output-timestamp parameter is deprecated and will be removed in next release
[08-02-2026 07:57:56] output-timestamp parameter is deprecated and will be removed in next release
[DW][INFO] Init Successfully.
[08-02-2026 07:59:57] TimeSensor::addData() Buffer full, draining data
[08-02-2026 07:59:59] TimeSensor::addData() Buffer full, draining data
[08-02-2026 08:00:01] TimeSensor::addData() Buffer full, draining data
[08-02-2026 08:00:03] TimeSensor::addData() Buffer full, draining data
[08-02-2026 08:00:05] TimeSensor::addData() Buffer full, draining data
[DW][INFO] Process Successfully.
[DW][INFO] Timing results:
Thread main:
-onProcess CPU: 198967us, std=1346 | GPU: 199386us, std=1391 | samples=646
-onRender CPU: 150us, std= 605 | GPU: 3us, std= 610 | samples=646
[08-02-2026 08:00:07] TimeSensor::addData() Buffer full, draining data
[DW][INFO] Release Successfully.
Dear @ussama.naal ,
Is it with lidar plugin sample?
Yes, this happens when using the sample_lidar_replay on the Drive HW.
Ok, it turns out that this problem is caused by the sample_lidar_replay application which blocks the DriveWorks the onProcess call until a frame is fully assembled. A full frame spin could take up between 50-200 ms to complete which means this process only sample yields to the DriveWorks 5-20 times per seconds .. which is not sufficient for the DriveWorks to keep up with the TimeSensor throughput.
The sample_lidar_replay will need to be modified to avoid this trap.
On a 2nd though it appears that the sample_lidar_replay isn’t consuming the TimeSensor which seems to be what’s causing the buffer full warning.