Please provide the following info (tick the boxes after creating this topic): Software Version
DRIVE OS 6.0.6
DRIVE OS 6.0.5
DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
Target Operating System
DRIVE AGX Orin Developer Kit (940-63710-0010-D00)
DRIVE AGX Orin Developer Kit (940-63710-0010-C00)
DRIVE AGX Orin Developer Kit (not sure its number)
SDK Manager Version
Host Machine Version
native Ubuntu Linux 20.04 Host installed with SDK Manager
native Ubuntu Linux 20.04 Host installed with DRIVE OS Docker Containers
native Ubuntu Linux 18.04 Host installed with DRIVE OS Docker Containers
I’m trying to use DriveWorks SensorSerializer module to switch the output file while recording, but the following method becomes an error and cannot be executed. When I call dwSensorSerializer_initialize() again, the process terminate.
Anyway, I would be happy if there is a way to change the output file during recording without frame drops.
I’m not sure if running dwSensorSerializer_initialize() again is the correct way.
It would be very helpful if there is a sample code available.
What I’m looking for is similar to the “Automatic Storage Selection” feature in the sample recording app “recorder-tui,” but since the source code is not provided, it is impossible to analyze.
Also, if possible, I would like to generate split files in the same directory of the same disk instead of switching disks.
The following is described in the Automatic Storage Selection section of the DriveWorks Reference Text UI Recording Tool documentation:
“Once a disk becomes full (free space < 5GB), output files will be put into the next available disk automatically.”
Is the following behavior correct?
The type parameter of dwSerializerParams in dwSensorSerializer_initialize() is set to “user”, and the df command is executed in the onData function defined by the user to check for a Storage with free space of 5GB or more, and the output files are saved there.