Unable to run recorder-qtgui on Drive AGX Orin

[kevin.kal]

Please provide the following info (tick the boxes after creating this topic):
Software Version
DRIVE OS 6.0.8.1
[*] DRIVE OS 6.0.6
DRIVE OS 6.0.5
DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
other

Target Operating System
[*] Linux
QNX
other

Hardware Platform
[*] DRIVE AGX Orin Developer Kit (940-63710-0010-300)
DRIVE AGX Orin Developer Kit (940-63710-0010-200)
DRIVE AGX Orin Developer Kit (940-63710-0010-100)
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)
other

SDK Manager Version
1.9.3.10904
[*] other

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
other

Hello,

We are trying to use the Recorder tool feature to record some camera data from 2x Sekonix SF3325 GMSL Cameras.

However when I run the code I get the following error as shown in the screenshot:

Could you have a look and let us know how to fix this?

Thanks

[SivaRamaKrishnaNV]

Dear @kevin.kal,
There are few known issues when launching recorder-qtguiincluded in release notes.
Could you please check using recorder tool?

[kevin.kal]

Hello @SivaRamaKrishnaNV

Can you specify which recorder tool to use?

here is the screenshot to the recording tools I see. Which one should be in use?

[SivaRamaKrishnaNV]

Dear @kevin.kal,
Please check DriveWorks SDK Reference: Basic Recording Tool

[kevin.kal]

Hello @SivaRamaKrishnaNV,

I have tried to run that command with a rig file but I’m getting the following errors as shown in the screenshots below:

Below is the screenshots of the rig file to which I edited the original file of release.json and saved it as release_test.json. The only difference is I added 2 SF3325 cameras.

Please have a look and let us know what the issue is.

Thanks

[SivaRamaKrishnaNV]

Dear @kevin.kal,
Could you keep only camera sensors in rig file?
Also, always please use text messages to post logs/configs instead of pictures. This makes the topic to be searchable by others in community who hits similar issue.

[kevin.kal]

Hello @SivaRamaKrishnaNV,

Apologies, I will paste the text here going forward.

I have created a different rig file with just the camera sensor but I am still getting errors:

pomo@tegra-ubuntu://usr/local/driveworks-5.10/tools/capture$ sudo -s
[sudo] password for pomo:
root@tegra-ubuntu:/usr/local/driveworks-5.10/tools/capture# ./recorder //usr/local/driveworks-5.10/tools/capture/configs/rwd/hyperion7_1/hype_test.json
[07-08-2024 10:57:11] Platform: Detected Drive Orin P3710
[07-08-2024 10:57:11] TimeSource: monotonic epoch time offset is 1723015431745164
[07-08-2024 10:57:11] TimeSourceVibranteLinux: detect valid PTP interface mgbe2_0
[07-08-2024 10:57:11] TimeSource Nvpss : PTP ioctl returned error. Synchronized time will not be available from this timesource.
[07-08-2024 10:57:11] TimeSource: Could not detect valid PTP time source at nvpps. Fallback to mgbe2_0
[07-08-2024 10:57:11] PTP Time is available from Eth Driver
[07-08-2024 10:57:11] Platform: currently selected GPU device integrated ID 0
[07-08-2024 10:57:11] Context::mountResourceCandidateDataPath resource FAILED to mount from ‘./resources’: VirtualFileSystem: Failed to mount ‘./resources/resources.pak’
[07-08-2024 10:57:11] Context::mountResourceCandidateDataPath resource FAILED to mount from ‘/usr/local/driveworks-5.10/tools/capture/data’: VirtualFileSystem: Failed to mount ‘/usr/local/driveworks-5.10/tools/capture/data/resources.pak’
[07-08-2024 10:57:11] Context::mountResourceCandidateDataPath resource FAILED to mount from ‘/usr/local/driveworks-5.10/tools/capture/…/…/data’: VirtualFileSystem: Failed to mount ‘/usr/local/driveworks-5.10/tools/capture/…/…/data/resources.pak’
[07-08-2024 10:57:11] Context::mountResourceCandidateDataPath resource FAILED to mount from ‘/usr/local/driveworks-5.10/data’: VirtualFileSystem: Failed to mount ‘/usr/local/driveworks-5.10/data/resources.pak’
[07-08-2024 10:57:11] Context::findResourcesPackageInPathWalk: Could not find ./resources/resources.pak in upto 7 parent directories from /usr/local/driveworks-5.10/tools/capture/…/…/targets/aarch64-Linux/lib/libdw_base.so.5.10
[07-08-2024 10:57:11] Context::findResourcesPackageInPathWalk: Could not find ./resources/resources.pak in upto 7 parent directories from /usr/local/driveworks-5.10/targets/aarch64-Linux/lib/libdw_base.so.5.10
[07-08-2024 10:57:11] SDK: No resources(.pak) mounted, some modules will not function properly
[07-08-2024 10:57:11] egl::Display: found 1 EGL devices
[07-08-2024 10:57:11] egl::Display: use drm device: drm-nvdc
[07-08-2024 10:57:11] TimeSource: monotonic epoch time offset is 1723015431745164
[07-08-2024 10:57:11] TimeSourceVibranteLinux: detect valid PTP interface mgbe2_0
[07-08-2024 10:57:11] TimeSource Nvpss : PTP ioctl returned error. Synchronized time will not be available from this timesource.
[07-08-2024 10:57:11] TimeSource: Could not detect valid PTP time source at nvpps. Fallback to mgbe2_0
[07-08-2024 10:57:11] PTP Time is available from Eth Driver
[07-08-2024 10:57:11] Initialize DriveWorks SDK v5.10.87
[07-08-2024 10:57:11] Release build with GNU 9.3.0 from buildbrain-branch-0-g9a5b4670e12 against Drive PDK v6.0.6.0
[07-08-2024 10:57:11] Rig overlay directory does not exist: /storage/driveworks/data/vehicle_cfg
[07-08-2024 10:57:11] Platform: currently selected GPU device integrated ID 0
terminate called after throwing an instance of ‘dw::core::Exception’
what(): DW_FILE_NOT_FOUND: Rig::fromFile: cannot open file: //usr/local/driveworks-5.10/tools/capture/configs/rwd/hyperion7_1/hype_test.json
Aborted
root@tegra-ubuntu:/usr/local/driveworks-5.10/tools/capture#

Here is the code for the rig file: hype_test.json

{
    "name": "camera:front:center:60fov",
    "nominalSensor2Rig": {
        "quaternion": [
            -0.502444,
            0.507493,
            -0.497444,
            0.492494
        ],
        "t": [
            1.749,
            -0.1,
            1.47
        ]
    },
    "parameter": "camera-type=ar0231-rccb-bae-sf3325,camera-group=a,camera-count=1,format=h264,output-format=yuv",
    "properties": {
        "Model": "ftheta",
        "bw-poly": "0.0 0.000545421498827636 -1.6216719633103e-10 -4.64720492990289e-12 2.85224527762934e-16",
        "cx": "960",
        "cy": "604",
        "height": "1208",
        "width": "1920"
    },
    "protocol": "camera.gmsl",
    "sensor2Rig": {
        "quaternion": [
            -0.502444,
            0.507493,
            -0.497444,
            0.492494
        ],
        "t": [
            1.749,
            -0.1,
            1.47
        ]
    }
}

[SivaRamaKrishnaNV]

@kevin.kal

what(): DW_FILE_NOT_FOUND: Rig::fromFile: cannot open file: //usr/local/driveworks-5.10/tools/capture/configs/rwd/hyperion7_1/hype_test.json

Does the file exists in the path with read permission? Please see if removing additional / in the beginning of file helps?

[kevin.kal]

Managed to copy the file to my home directory and change the permissions however still the errors persist:

root@tegra-ubuntu:/usr/local/driveworks-5.10/tools/capture# ./recorder /home/pomo/release_test.json
[07-08-2024 11:37:56] Platform: Detected Drive Orin P3710
[07-08-2024 11:37:56] TimeSource: monotonic epoch time offset is 1723015431745165
[07-08-2024 11:37:56] TimeSourceVibranteLinux: detect valid PTP interface mgbe2_0
[07-08-2024 11:37:56] TimeSource Nvpss : PTP ioctl returned error. Synchronized time will not be available from this timesource.
[07-08-2024 11:37:56] TimeSource: Could not detect valid PTP time source at nvpps. Fallback to mgbe2_0
[07-08-2024 11:37:56] PTP Time is available from Eth Driver
[07-08-2024 11:37:56] Platform: currently selected GPU device integrated ID 0
[07-08-2024 11:37:56] Context::mountResourceCandidateDataPath resource FAILED to mount from './resources': VirtualFileSystem: Failed to mount './resources/resources.pak'
[07-08-2024 11:37:56] Context::mountResourceCandidateDataPath resource FAILED to mount from '/usr/local/driveworks-5.10/tools/capture/data': VirtualFileSystem: Failed to mount '/usr/local/driveworks-5.10/tools/capture/data/resources.pak'
[07-08-2024 11:37:56] Context::mountResourceCandidateDataPath resource FAILED to mount from '/usr/local/driveworks-5.10/tools/capture/../../data': VirtualFileSystem: Failed to mount '/usr/local/driveworks-5.10/tools/capture/../../data/resources.pak'
[07-08-2024 11:37:56] Context::mountResourceCandidateDataPath resource FAILED to mount from '/usr/local/driveworks-5.10/data': VirtualFileSystem: Failed to mount '/usr/local/driveworks-5.10/data/resources.pak'
[07-08-2024 11:37:56] Context::findResourcesPackageInPathWalk: Could not find ./resources/resources.pak in upto 7 parent directories from /usr/local/driveworks-5.10/tools/capture/../../targets/aarch64-Linux/lib/libdw_base.so.5.10
[07-08-2024 11:37:56] Context::findResourcesPackageInPathWalk: Could not find ./resources/resources.pak in upto 7 parent directories from /usr/local/driveworks-5.10/targets/aarch64-Linux/lib/libdw_base.so.5.10
[07-08-2024 11:37:56] SDK: No resources(.pak) mounted, some modules will not function properly
[07-08-2024 11:37:56] egl::Display: found 1 EGL devices
[07-08-2024 11:37:56] egl::Display: use drm device: drm-nvdc
[07-08-2024 11:37:56] TimeSource: monotonic epoch time offset is 1723015431745165
[07-08-2024 11:37:56] TimeSourceVibranteLinux: detect valid PTP interface mgbe2_0
[07-08-2024 11:37:56] TimeSource Nvpss : PTP ioctl returned error. Synchronized time will not be available from this timesource.
[07-08-2024 11:37:56] TimeSource: Could not detect valid PTP time source at nvpps. Fallback to mgbe2_0
[07-08-2024 11:37:56] PTP Time is available from Eth Driver
[07-08-2024 11:37:56] Initialize DriveWorks SDK v5.10.87
[07-08-2024 11:37:56] Release build with GNU 9.3.0 from buildbrain-branch-0-g9a5b4670e12 against Drive PDK v6.0.6.0
[07-08-2024 11:37:56] Rig overlay directory does not exist: /storage/driveworks/data/vehicle_cfg
[07-08-2024 11:37:56] Platform: currently selected GPU device integrated ID 0
[07-08-2024 11:37:56] rig::DatabaseOverlayer: Failed to open a file '/tmp/car_vin' - file likely does not exist - skipping overlay
[07-08-2024 11:37:56] RigConfiguration: loading dwGenericVehicle from a rig that does not contain the drive-by-wire second order dynamics. Ignoring the second-order dynamic values.
[07-08-2024 11:37:56] No valid data file found for camera:front:center:120fov in parameter string: camera-name=SF3325,interface=csi-a,link=0,output-format=raw+processed,fifo-size=1,warn-per-frame=0,skip-eeprom=1 (using configuration folder /home/pomo/)
[07-08-2024 11:37:56] No valid data file found for camera:front:center:60fov in parameter string: camera-name=SF3325,interface=csi-a,link=1,output-format=raw+processed,fifo-size=1,warn-per-frame=0,skip-eeprom=1 (using configuration folder /home/pomo/)
[07-08-2024 11:37:56] No valid data file found for can:vehicle in parameter string: device=can0 (using configuration folder /home/pomo/)
[07-08-2024 11:37:56] No valid data file found for gps:xsens in parameter string: device=/dev/ttyUSB0,baudrate=230400,stop-bits=1,slave=true,file-buffer-size=8192,index_table=off (using configuration folder /home/pomo/)
[07-08-2024 11:37:56] No valid data file found for imu:xsens in parameter string: device=/dev/ttyUSB0,baudrate=230400,stop-bits=1,slave=true,file-buffer-size=8192,index_table=off (using configuration folder /home/pomo/)
[07-08-2024 11:37:56] No valid data file found for radar:front:center in parameter string: device=CONTINENTAL_ARS430,ip=10.1.1.20,port=40000,multicast-ip=239.0.0.1,time-smoothing=false,slave=true,file-buffer-size=4194304 (using configuration folder /home/pomo/)
[07-08-2024 11:37:56] rig::DatabaseOverlayer: Failed to open a file '/tmp/car_vin' - file likely does not exist - skipping overlay
[07-08-2024 11:37:56] RigConfiguration: loading dwGenericVehicle from a rig that does not contain the drive-by-wire second order dynamics. Ignoring the second-order dynamic values.
[07-08-2024 11:37:56] SensorFactory::createSensor() -> time.nvpps, nvpps-device=/dev/nvpps0
[07-08-2024 11:37:56] TimeSensor: failed to set NVPPS parameters.  Error: Invalid argument
[07-08-2024 11:37:56] This platform does not support NVPPS GPIO mode. Fallback to timer mode
[07-08-2024 11:37:56] TimeSensor: initialized with no UTC time reference.
[07-08-2024 11:37:56] EndpointNVPPS: started on /dev/nvpps0
[07-08-2024 11:37:56] SensorFactory::createSensor() -> camera.gmsl, camera-name=SF3325,interface=csi-a,link=0,output-format=raw+processed,fifo-size=1,warn-per-frame=0,skip-eeprom=1
[07-08-2024 11:37:56] SensorFactory::createSensor() -> camera.gmsl.master, 
[07-08-2024 11:37:56] CameraMaster::parseDevBlock Getting device info list.
[07-08-2024 11:37:56] devBlock: 0 Slave = 0 Interface = csi-a Camera_name = SF3325 Link = 0 GroupInit = 0 RecCfg = 1
[07-08-2024 11:37:56] Camera Match Name: SF3325 Description: Sekonix SF3325 module - 60-deg FOV, DVP AR0231-RCCB, MAX96705 linkIndex: 4294967295 serInfo.Name: MAX96705
[07-08-2024 11:37:56] Client, Setting up information for camera ID 0
[07-08-2024 11:37:56] Client, successfully found info for camera ID 0 bound to id 0
[07-08-2024 11:37:56] CameraClient: using NITO found at /usr/share/camera/SF3325.nito
[07-08-2024 11:37:56] SensorFactory::createSensor() -> camera.gmsl, camera-name=SF3325,interface=csi-a,link=1,output-format=raw+processed,fifo-size=1,warn-per-frame=0,skip-eeprom=1
[07-08-2024 11:37:56] devBlock: 0 Slave = 0 Interface = csi-a Camera_name = SF3325 Link = 1 GroupInit = 0 RecCfg = 1
[07-08-2024 11:37:56] Camera Match Name: SF3325 Description: Sekonix SF3325 module - 60-deg FOV, DVP AR0231-RCCB, MAX96705 linkIndex: 4294967295 serInfo.Name: MAX96705
[07-08-2024 11:37:56] Client, Setting up information for camera ID 1
[07-08-2024 11:37:56] Client, successfully found info for camera ID 1 bound to id 1
[07-08-2024 11:37:56] CameraClient: using NITO found at /usr/share/camera/SF3325.nito
[07-08-2024 11:37:56] SensorFactory::createSensor() -> can.socket, device=can0
[07-08-2024 11:37:56] CANSocket: cannot connect to CAN, network is down
[07-08-2024 11:37:56] SensorManager::addSensor DW_HAL_CANNOT_OPEN_CHANNEL: CANSocket: socket error 100
[07-08-2024 11:37:56] SensorManager::addSensorsFromRig() failed to add sensor from rig: can.socket device=can0 (Error: DW_HAL_CANNOT_OPEN_CHANNEL)
[07-08-2024 11:37:58] CameraClient: Stopping client
terminate called after throwing an instance of 'dw::core::Exception'
  what():  DW_HAL_CANNOT_OPEN_CHANNEL: SensorManager::SensorManager() Failed to add sensors from rig
Aborted
root@tegra-ubuntu:/usr/local/driveworks-5.10/tools/capture#

[SivaRamaKrishnaNV]

@kevin.kal

CANSocket: socket error 100
[07-08-2024 11:37:56] SensorManager::addSensorsFromRig() failed to add sensor from rig: can.socket device=can0 (Error: DW_HAL_CANNOT_OPEN_CHANNEL)
[07-08-2024 11:37:58] CameraClient: Stopping client

It indicates rig file has CAN sensor. Do you want to record CAN sensor as well? If not, please remove it.

[kevin.kal]

But I don’t think I added the CAN sensor in the rig file, just the camera. here is the code of hype_test.json.

{
    "name": "camera:front:center:60fov",
    "nominalSensor2Rig": {
        "quaternion": [
            -0.502444,
            0.507493,
            -0.497444,
            0.492494
        ],
        "t": [
            1.749,
            -0.1,
            1.47
        ]
    },
    "parameter": "camera-type=ar0231-rccb-bae-sf3325,camera-group=a,camera-count=1,format=h264,output-format=yuv",
    "properties": {
        "Model": "ftheta",
        "bw-poly": "0.0 0.000545421498827636 -1.6216719633103e-10 -4.64720492990289e-12 2.85224527762934e-16",
        "cx": "960",
        "cy": "604",
        "height": "1208",
        "width": "1920"
    },
    "protocol": "camera.gmsl",
    "sensor2Rig": {
        "quaternion": [
            -0.502444,
            0.507493,
            -0.497444,
            0.492494
        ],
        "t": [
            1.749,
            -0.1,
            1.47
        ]
    }
}

[SivaRamaKrishnaNV]

@kevin.kal

No valid data file found for camera:front:center:120fov in parameter string: camera-name=SF3325,interface=csi-a,link=0,output-format=raw+processed,fifo-size=1,warn-per-frame=0,skip-eeprom=1 (using configuration folder /home/pomo/)
[07-08-2024 11:37:56] No valid data file found for camera:front:center:60fov in parameter string: camera-name=SF3325,interface=csi-a,link=1,output-format=raw+processed,fifo-size=1,warn-per-frame=0,skip-eeprom=1 (using configuration folder /home/pomo/)
[07-08-2024 11:37:56] No valid data file found for can:vehicle in parameter string: device=can0 (using configuration folder /home/pomo/)
[07-08-2024 11:37:56] No valid data file found for gps:xsens in parameter string: device=/dev/ttyUSB0,baudrate=230400,stop-bits=1,slave=true,file-buffer-size=8192,index_table=off (using configuration folder /home/pomo/)
[07-08-2024 11:37:56] No valid data file found for imu:xsens in parameter string: device=/dev/ttyUSB0,baudrate=230400,stop-bits=1,slave=true,file-buffer-size=8192,index_table=off (using configuration folder /home/pomo/)
[07-08-2024 11:37:56] No valid data file found for radar:front:center in parameter string: device=CONTINENTAL_ARS430,ip=10.1.1.20,port=40000,multicast-ip=239.0.0.1,time-smoothing=false,slave=true,file-buffer-size=4194304 (using configuration folder /home/pomo/)
[07-08-2024 11:37:56] rig::DatabaseOverlayer: Failed to open a file '/tmp/car_vin' - file likely does not exist - skipping overlay
[07-08-2024 11:37:56] RigConfiguration: loading dwGenericVehicle from a rig that 

The log indicates you have all these sensors present on rig file used by application. Please make sure you are passing correct rig file path

[kevin.kal]

Apologies for that again. I did use the wrong rig file, I have now corrected this. However errors still shows:

root@tegra-ubuntu:/usr/local/driveworks-5.10/tools/capture# ./recorder /home/pomo/hype_test.json
[07-08-2024 15:02:56] Platform: Detected Drive Orin P3710
[07-08-2024 15:02:56] TimeSource: monotonic epoch time offset is 1723015431745165
[07-08-2024 15:02:56] TimeSourceVibranteLinux: detect valid PTP interface mgbe2_0
[07-08-2024 15:02:56] TimeSource Nvpss : PTP ioctl returned error. Synchronized time will not be available from this timesource.
[07-08-2024 15:02:56] TimeSource: Could not detect valid PTP time source at nvpps. Fallback to mgbe2_0
[07-08-2024 15:02:56] PTP Time is available from Eth Driver
[07-08-2024 15:02:56] Platform: currently selected GPU device integrated ID 0
[07-08-2024 15:02:56] Context::mountResourceCandidateDataPath resource FAILED to mount from './resources': VirtualFileSystem: Failed to mount './resources/resources.pak'
[07-08-2024 15:02:56] Context::mountResourceCandidateDataPath resource FAILED to mount from '/usr/local/driveworks-5.10/tools/capture/data': VirtualFileSystem: Failed to mount '/usr/local/driveworks-5.10/tools/capture/data/resources.pak'
[07-08-2024 15:02:56] Context::mountResourceCandidateDataPath resource FAILED to mount from '/usr/local/driveworks-5.10/tools/capture/../../data': VirtualFileSystem: Failed to mount '/usr/local/driveworks-5.10/tools/capture/../../data/resources.pak'
[07-08-2024 15:02:56] Context::mountResourceCandidateDataPath resource FAILED to mount from '/usr/local/driveworks-5.10/data': VirtualFileSystem: Failed to mount '/usr/local/driveworks-5.10/data/resources.pak'
[07-08-2024 15:02:56] Context::findResourcesPackageInPathWalk: Could not find ./resources/resources.pak in upto 7 parent directories from /usr/local/driveworks-5.10/tools/capture/../../targets/aarch64-Linux/lib/libdw_base.so.5.10
[07-08-2024 15:02:56] Context::findResourcesPackageInPathWalk: Could not find ./resources/resources.pak in upto 7 parent directories from /usr/local/driveworks-5.10/targets/aarch64-Linux/lib/libdw_base.so.5.10
[07-08-2024 15:02:56] SDK: No resources(.pak) mounted, some modules will not function properly
[07-08-2024 15:02:56] egl::Display: found 1 EGL devices
[07-08-2024 15:02:56] egl::Display: use drm device: drm-nvdc
[07-08-2024 15:02:56] TimeSource: monotonic epoch time offset is 1723015431745165
[07-08-2024 15:02:56] TimeSourceVibranteLinux: detect valid PTP interface mgbe2_0
[07-08-2024 15:02:56] TimeSource Nvpss : PTP ioctl returned error. Synchronized time will not be available from this timesource.
[07-08-2024 15:02:56] TimeSource: Could not detect valid PTP time source at nvpps. Fallback to mgbe2_0
[07-08-2024 15:02:56] PTP Time is available from Eth Driver
[07-08-2024 15:02:56] Initialize DriveWorks SDK v5.10.87
[07-08-2024 15:02:56] Release build with GNU 9.3.0 from buildbrain-branch-0-g9a5b4670e12 against Drive PDK v6.0.6.0
[07-08-2024 15:02:56] Rig overlay directory does not exist: /storage/driveworks/data/vehicle_cfg
[07-08-2024 15:02:56] Platform: currently selected GPU device integrated ID 0
[07-08-2024 15:02:56] rig::DatabaseOverlayer: Failed to open a file '/tmp/car_vin' - file likely does not exist - skipping overlay
terminate called after throwing an instance of 'dw::core::Exception'
  what():  DW_FILE_INVALID: Rig:fromArchive - cannot load files of version 0 because they are missing 'steeringCoefficient'
Aborted
root@tegra-ubuntu:/usr/local/driveworks-5.10/tools/capture# 

hype_test.json code:

{
    "name": "camera:front:center:60fov",
    "nominalSensor2Rig": {
        "quaternion": [
            -0.502444,
            0.507493,
            -0.497444,
            0.492494
        ],
        "t": [
            1.749,
            -0.1,
            1.47
        ]
    },
    "parameter": "camera-type=ar0231-rccb-bae-sf3325,camera-group=a,camera-count=1,format=h264,output-format=yuv",
    "properties": {
        "Model": "ftheta",
        "bw-poly": "0.0 0.000545421498827636 -1.6216719633103e-10 -4.64720492990289e-12 2.85224527762934e-16",
        "cx": "960",
        "cy": "604",
        "height": "1208",
        "width": "1920"
    },
    "protocol": "camera.gmsl",
    "sensor2Rig": {
        "quaternion": [
            -0.502444,
            0.507493,
            -0.497444,
            0.492494
        ],
        "t": [
            1.749,
            -0.1,
            1.47
        ]
    }
}

[kevin.kal]

Hello @SivaRamaKrishnaNV

Can you give us an update with this please?

[SivaRamaKrishnaNV]

Hi @kevin.kal ,

@kevin.kal

"parameter": "camera-type=ar0231-rccb-bae-sf3325,camera-group=a,camera-count=1,format=h264,output-format=yuv",

I notice you could run sample_camera from Unable to use ./sample_camera for Sekonix SF3325-100 GMSL Camera on Drive AGX Orin OS 6.0.6 - #14 by kevin.kal. Can you use camera-type=SF3325, link=0. Remove camera-count . Please share the logs in case of any issue.

[kevin.kal]

@SivaRamaKrishnaNV

I’ve changed the line inside the .json file, I created a new file. I tried to run ./recorder I am getting different errors.

root@tegra-ubuntu://usr/local/driveworks-5.10/tools/capture# ./recorder //usr/local/driveworks-5.10/tools/capture/configs/rwd/hyperion7_1/hype_rig_test.json
bash: ./recorder: cannot execute binary file: Exec format error
root@tegra-ubuntu://usr/local/driveworks-5.10/tools/capture# ./recorder
bash: ./recorder: cannot execute binary file: Exec format error
root@tegra-ubuntu://usr/local/driveworks-5.10/tools/capture#

.json file:

  GNU nano 4.8                                                                                    hype_rig_test.json                                                                                               
{
    "name": "camera:front:center:60fov",
    "nominalSensor2Rig": {
        "quaternion": [
            -0.502444,
            0.507493,
            -0.497444,
            0.492494
        ],
        "t": [
            1.749,
            -0.1,
            1.47
        ]
    },
    "parameter": "camera-type=SF3325,link=0,camera-group=a,format=h264,output-format=yuv",
    "properties": {
        "Model": "ftheta",
        "bw-poly": "0.0 0.000545421498827636 -1.6216719633103e-10 -4.64720492990289e-12 2.85224527762934e-16",
        "cx": "960",
        "cy": "604",
        "height": "1208",
        "width": "1920"
    },
    "protocol": "camera.gmsl",
    "sensor2Rig": {
        "quaternion": [
            -0.502444,
            0.507493,
            -0.497444,
            0.492494
        ],
        "t": [
            1.749,
            -0.1,
            1.47
        ]
    }
}

I am not sure why the ./recorder code doesn’t work.

[SivaRamaKrishnaNV]

Dear @kevin.kal,
Could you check the file type of recorder using file <recorder tool path>

[kevin.kal]

Hello @SivaRamaKrishnaNV

here is the log:

root@tegra-ubuntu:/usr/local/driveworks-5.10/tools/capture# file ./recorder
./recorder: ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=94375d0751f87cdf957adb50f61b9463e16ef55d, for GNU/Linux 3.2.0, not stripped
root@tegra-ubuntu:/usr/local/driveworks-5.10/tools/capture#

[SivaRamaKrishnaNV]

Dear @kevin.kal
Did you copy recorder tool to target from host or docker? The log indicates it is x86 based tool.

[kevin.kal]

@SivaRamaKrishnaNV I did not copy the ./recorder program from anywhere. It was already there since I flashed DRIVE OS 6.0.6

I am not sure how the ./recorder program is using x86 based tool when it partially working couple of days back as you can see the previous comments