This tool is available on the x86 Host System and NVIDIA DRIVE™ OS Linux.
This is a front-end for the Basic Recording Tool, and provides the following additional features:
Run this tool by executing:
cd /usr/local/driveworks/tools/capture ./recorder-tui <rig file> OR <rig_directory> [--bbr] `bbr` starts the recorder in black box recording (bbr) mode.
After initialization, the tool supports the following commands:
Command | Action |
---|---|
s <Enter> | toggle recording |
q <Enter> | quit |
start <Enter> | start recording |
stop <Enter> | stop recording |
bbr <Enter> | bbr recording mode |
continuous <Enter> | continuous recording mode |
h264 <Enter> | record camera in h264 |
lraw <Enter> | record camera in lraw |
bbr
, continuous
, h264
and lraw
switch is supported only when the recorder is in stopped state.
The textual interface of the tool is illustrated in the screenshot below:
This tool can discover SSD/eSATA disks that are mounted on the target and meet the following criteria:
ext4
filesystem format> 5GB
free space available/proc/mounts
This tool automatically selects the first available disk for recording. Once a disk becomes full (free space < 5GB), output files will be put into the next available disk automatically.
If automatic disk selection is not convenient, one can manually specify the recording directory in the rig configuration file using the "recorder_storage_paths":
{ "rig": { "recorder_storage_map": { "<sensor_name_1>": "1", "<sensor_name_2>": "0", "<sensor_name_3>": "0", <...> }, "recorder_storage_paths": [ "<your_storage_path_1>", "<your_storage_path_2>", <...> ], <...> }, <...> }
"recorder_storage_map" is used to map the sensor to the index of "recorder_storage_paths" list. Example: "sensor_name_1" is mapped to index "1" which is "your_storage_path_2". If the sensor map is not provided, then the default value of the storage index "0" will be selected.
ext4
filesystem and have > 5GB
in free space.This tool measures sensor statistics (at disk sink).
The Manual Storage Selection feature can be used to perform multi-SSD recording on a single Xavier device.
To achieve this, a user must create multiple rig files, each with their specified storage path and subset of sensors, and place them inside a <rig_directory>
.
The tool can then be launched as below:
./recorder-tui <rig_directory> --bbr
Black Box Recorder (BBR) records sensor data clips around a vehicle disengagement trigger event. BBR automatically deletes the recording folders of current recording session expect the last three. If a lateral or longitudinal disengagement occurs, BBR preserves the 30 seconds before and after the point of disengagement. The disengagement folder will have two or three recording folders depending on the exact time of the disengagement. BBR internally uses recorder-tui, so the recording data format and directory structure will be identical to the normal recording case.
When using recorder-tui to record a session, it can be useful to be able to tag these sessions. With recorder-tui you can pass in --tag <tag-name>
to set a tag for the recorded session which will appear in the aux_info file. The valid values for this tag will need to be specified under the tags.txt
file which should appear under your configuration directory that you pass to recorder-tui.