Error recording camera h264 (Solved)

Hello,

I’m trying to record my camera in order to calibrate them. To do so i tried to use the tool recorder but it needs a configuration file and the example given in the development guide isn’t working:

{
    "name": "camera:front:center:60fov",
    "nominalSensor2Rig": {
        "quaternion": [
            0.0,
            0.0,
            0.0,
            1.0
        ],
        "t": [
            0.0,
            0.0,
            0.0
        ]
    },
    "parameter": "camera-type=ar0231-rccb-bae-sf3325,camera-group=a,camera-count=1,camera-mask=0001,siblingIndex=0,output-format=raw+yuv,fifo-size=1,warn-per-frame=0",
    "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.0,
            0.0,
            0.0,
            1.0
        ],
        "t": [
            0.0,
            0.0,
            0.0
        ]
    }
}

I also tried to do it with the information given when i launch the sample_camera_gmsl:

{
    "rig": {
        "sensors": [
            {
                "name": "CAM_120deg",
                "nominalSensor2Rig": {
                    "quaternion": [
                        -0.49579393863678,
                        0.496242880821228,
                        -0.503722012042999,
                        0.504178106784821
                    ],
                    "t": [
                        3.92000007629395,
                        0.0,
                        0.575314044952393
                    ]
                },
                "parameter": "output-format=h264,fifo-size=3,camera-count=1,camera-type=ar0231-rccb-bae-sf3324,csi-port=a,slave=0,camera-mask=0001",
                "properties": {
                    "Model": "pinhole",
                    "cx": "990.305075",
                    "cy": "621.326973",
                    "distortion": "-3.23600093e-01 2.62953390e-01",
                    "fx": "1839.62298",
                    "fy": "1841.51169",
                    "height": "1920",
                    "width": "1208",
                    "params": ""
                },
                "protocol": "camera.gmsl",
                "sensor2Rig": {
                    "quaternion": [
                        -0.49579393863678,
                        0.496242880821228,
                        -0.503722012042999,
                        0.504178106784821
                    ],
                    "t": [
                        3.92000007629395,
                        0.0,
                        0.575314044952393
                    ]
                }
            }
        ],
        "vehicle": {
            "valid": true,
            "value": {
                "axlebaseFront": 1.62699997425079,
                "axlebaseRear": 1.61800003051758,
                "bumperFront": 0.912000000476837,
                "bumperRear": 1.10909998416901,
                "centerOfMassToRearAxle": 1.56449997425079,
                "frontCorneringStiffness": 30654.0,
                "height": 1.45500004291534,
                "inertia": 1780.80004882812,
                "length": 4.91499996185303,
                "mass": 1779.40002441406,
                "rearCorneringStiffness": 36407.0,
                "steeringCoefficient": 1.0,
                "wheelDiameter": 0.680000007152557,
                "wheelbase": 2.91199994087219,
                "width": 1.87399995326996,
                "widthWithMirrors": 0.0
            }
        }
    },
    "version": 2
}

The error given is “CameraGMSL: default IPP event callback function set terminate called after throwind an instance of ‘dw::core::exeption’ what(): DW_INVALID_ARGUMENT: CameraGMSL: DW_CAMERA_PROCESSED_IMAGE not enabled”

I also had another issue: when camera-mask=0010 it says that it’s not compatible with camera-cout=1, camera-mask is a binary number right?

Thanks in advance,
Adrien

Dear Adrien,
Can you please share the camera details and connection details(which port have you connected).

Dear SivaRamaKrishna,

I have two camera Sekonix SF3325-100 (60deg) and SF3324-100 (120deg) RCCB, the setting on the previous DW version was the same: type=ar0231-rccb connected to port A0 and A1. The strange thing it that i literally copied/pasted the arguments of sensor factory used by the sample_camera_gmsl.

Thanks

Dear Adrien,
Are you able to run single/muitple camera using sample_camera_gsml/sample_camera_multiple_gsml? Could you please check that first and paste the command here.

Dear SivaRamaKrishna,

I’m able to see both of my cameras with sample_camera_multiple_gsml --selector-mask=00110000

I have to say that the colors are a bit strange, but maybe because of the frequency of my office’s lights. please find attached a screenshot of what i can see.

PS: My desk is white/grey

Dear AdrienBonefons,

We usually see this type of image when there is a flicker light.
Because we are using the sensor with a fix exposure and it is a HDR sensor we have no prevention on flicker. Thanks.

Dear AdrienBonefons,

Could you please try to record with below configuration for your topic? Thanks.

{
    "rig": {
        "sensors": [
            {
                "name": "camera_capture_test",
                "nominalSensor2Rig": {
                    "quaternion": [
                        0.5,
                        -0.5,
                        0.5,
                        -0.5
                    ],
                    "t": [
                        1.77,
                        0.0,
                        1.47
                    ]
                },
                "parameter": "camera-type=ar0231-rccb-bae-sf3324,csi-port=a,camera-count=1,camera-mask=0001,format=h264,output-format=yuv,fifo-size=30,file-buffer-size=4194304",
                "properties": {
                    "Model": "ftheta",
                    "bw-poly": "0.0 0.00102669443003833 3.77865596590254e-08 -2.1812513600894e-11 4.76916107246175e-14",
                    "cx": "960",
                    "cy": "604",
                    "height": "1208",
                    "width": "1920"
                },
                "protocol": "camera.gmsl",
                "sensor2Rig": {
                    "quaternion": [
                        0.5,
                        -0.5,
                        0.5,
                        -0.5
                    ],
                    "t": [
                        1.77,
                        0.0,
                        1.47
                    ]
                }
            }

        ],
        "vehicle": {
            "valid": true,
            "value": {
                "COMMENT": "steeringCoefficient is not validated",
                "axlebaseFront": 1.582,
                "axlebaseRear": 1.575,
                "bumperFront": 0.912,
                "bumperRear": 1.109,
                "centerOfMassToRearAxle": 1.564,
                "frontCorneringStiffness": 30654.0,
                "height": 1.473,
                "inertia": 1780.8,
                "length": 4.872,
                "mass": 1779.4,
                "rearCorneringStiffness": 36407.0,
                "steeringCoefficient": 14.8,
                "wheelDiameter": 0.673,
                "wheelbase": 2.85,
                "width": 1.852,
                "widthWithMirrors": 2.121
            }
        }
    },
    "version": 2
}

Trying with your configuration gives me the same issue, but isn’t the output-format supposed to be h264?

Thanks

Dear AdrienBonefons,

Could you refer to below link for configuration reference on DPX2?
/usr/local/driveworks-1.2/doc/nvdwx_html/dwx_config_ref.html

Could you please try to run recorder-tui application?
./recorder-tui config/hyperion7_1/release.json

Dear Steve,

I already followed the instructions of the devguide but i’m still not able to make it work! Even with ./recorder-tui config/hyperion7_1/release.json the application crashes writing

Recorder @ release: 
Last output: Rig: release.json recorder-tui: starte

Last error: Aborted (code dumped)

Hope this issue will be fixed soon,

Regards

Dear AdrienBonefons,

Please check if the USB storage device is properly detected.
In my case, lsusb
Bus 002 Device 007: ID 067b:2773 Prolific Technology, Inc. PL2773 SATAII bridge controller

This my release.json file

{
    "rig": {
        "sensors": [
            {
                "name": "camera_capture_test",
                "nominalSensor2Rig": {
                    "quaternion": [
                        0.5,
                        -0.5,
                        0.5,
                        -0.5
                    ],
                    "t": [
                        1.77,
                        0.0,
                        1.47
                    ]
                },
                "parameter": "camera-type=ar0231-rccb-bae-sf3324,csi-port=a,camera-count=1,camera-mask=0001,format=h264,output-format=yuv,fifo-size=30",
                "properties": {
                    "Model": "ftheta",
                    "bw-poly": "0.0 0.00102669443003833 3.77865596590254e-08 -2.1812513600894e-11 4.76916107246175e-14",
                    "cx": "960",
                    "cy": "604",
                    "height": "1208",
                    "width": "1920"
                },
                "protocol": "camera.gmsl",
                "sensor2Rig": {
                    "quaternion": [
                        0.5,
                        -0.5,
                        0.5,
                        -0.5
                    ],
                    "t": [
                        1.77,
                        0.0,
                        1.47
                    ]
                }
            }

        ],
        "vehicle": {
            "valid": true,
            "value": {
                "COMMENT": "steeringCoefficient is not validated",
                "axlebaseFront": 1.582,
                "axlebaseRear": 1.575,
                "bumperFront": 0.912,
                "bumperRear": 1.109,
                "centerOfMassToRearAxle": 1.564,
                "frontCorneringStiffness": 30654.0,
                "height": 1.473,
                "inertia": 1780.8,
                "length": 4.872,
                "mass": 1779.4,
                "rearCorneringStiffness": 36407.0,
                "steeringCoefficient": 14.8,
                "wheelDiameter": 0.673,
                "wheelbase": 2.85,
                "width": 1.852,
                "widthWithMirrors": 2.121
            }
        }
    },
    "version": 2
}

Dear Steve,

After some more tries it’s working with recorder and recorder-tui, thanks! Concerning the recorder-qtgui i’m not using it but i have to say that it’s not working.

Is there a way to see in direct what we record like in the previous version?

Thanks again!

Dear AdrienBonefons,

Could you please upload the error message you encountered?

>Is there a way to see in direct what we record like in the previous version?
Are you asking if you can play the files that were recorded from the previous version? Thanks.

Deat Steve,

Yes of course: Its written Disk Full//No Disk on the app and nothing special in the command.

On the previous version it was possible to see the camera output and record it at the same time if my memory is right. It permit me to see what i’m recording in real time so i can move the camera if needed.

Thanks

Hello,

I am trying to use ./recorder-tui tool for recordings. However, it is giving me error and it is getting crashed.

Error:

No CUDA context available: DW_CUDA_ERROR

Anyone faced similar issue ?

However, ./recorder application is running fine with my setup.
THanks