DecoderDelphi: invalid scan type received

Autonomous Vehicles DRIVE PX 2 DriveWorks
1

sample_radar_replay sample in DriveWorks 1.2 has an below error
could you have a solution for this?

nvidia@tegra-ubuntu:/usr/local/driveworks/bin$ ./sample_radar_replay --protocol=radar.socket --params=device=DELPHI_ESR2_5,ip=169.254.145.71,port=5555
[23-10-2018 20:41:32] Initialize DriveWorks SDK v1.2.400
[23-10-2018 20:41:32] Release build with GNU 4.9.4 from v1.2.0-rc11-0-ga7f5475 against Vibrante PDK v5.0.10.3
[23-10-2018 20:41:32] Platform: Detected Drive PX2 - Tegra A
[23-10-2018 20:41:32] TimeSource: monotonic epoch time offset is 1540006658047648
[23-10-2018 20:41:32] TimeSource: PTP ioctl returned error. Synchronized time will not be available.
[23-10-2018 20:41:32] TimeSource: Could not detect valid PTP time source at ‘eth0’. Fallback to CLOCK_MONOTONIC.
[23-10-2018 20:41:32] Platform: number of GPU devices detected 1
[23-10-2018 20:41:32] Platform: currently selected GPU device integrated ID 0
[23-10-2018 20:41:32] SDK: Resources mounted from …/./data/resources
[23-10-2018 20:41:32] SDK: Create NvMediaDevice
[23-10-2018 20:41:32] SDK: Create NvMediaIPPManager
[23-10-2018 20:41:32] SDK: use EGL display as provided
[23-10-2018 20:41:32] SensorFactory::createSensor() → radar.socket, device=DELPHI_ESR2_5,ip=169.254.145.71,port=5555
[23-10-2018 20:41:32] RadarSocket::RadarSocket, connected to 169.254.145.71:5555
[23-10-2018 20:41:32] DecoderDelphi: invalid scan type received

[23-10-2018 20:41:33] DecoderDelphi: invalid scan type received

Segmentation fault (core dumped)

2

Dear skkim,

According to the log, DecoderDelphi: invalid scan type received
Could you help to check if your radar is a Delphi product?
And were there any problems in DriveWorks 0.6?

3

Dear SteveNV

I’m using Delphi ESR2.5 12V radar.
in sample_radar_replay works but rendered data seems to invalid.
replay screen is not represent the moving object.

Thanks.

4

Dear skkim,

Could you upload the issued screen on the topic?

5

Dear SteveNV

I found the cause and solve that.

Thanks.

6

Dear SteveNV,

I’m using Delphi ESR2.5(24V), but not work…
The commands and results are below.

The view is displayed, but not ploted and “Packets” displayed in the view is zero.

./sample_radar_replay --protocol=radar.socket --params=ip=192.168.1.11,port=5555,device=DELPHI_ESR2_5

[29-10-2018 23:3:37] Initialize DriveWorks SDK v1.2.400
[29-10-2018 23:3:37] Release build with GNU 4.9.4 from v1.2.0-rc11-0-ga7f5475 against Vibrante PDK v5.0.10.3
[29-10-2018 23:3:37] Platform: Detected Drive PX2 - Tegra A
[29-10-2018 23:3:37] TimeSource: monotonic epoch time offset is 1540876231301103
[29-10-2018 23:3:37] TimeSource: PTP ioctl returned error. Synchronized time will not be available.
[29-10-2018 23:3:37] TimeSource: Could not detect valid PTP time source at 'eth0'. Fallback to CLOCK_MONOTONIC.
[29-10-2018 23:3:37] Platform: number of GPU devices detected 1
[29-10-2018 23:3:37] Platform: currently selected GPU device integrated ID 0
[29-10-2018 23:3:37] SDK: Resources mounted from .././data/resources
[29-10-2018 23:3:37] SDK: Create NvMediaDevice
[29-10-2018 23:3:37] SDK: Create NvMediaIPPManager
[29-10-2018 23:3:37] SDK: use EGL display as provided
[29-10-2018 23:3:37] SensorFactory::createSensor() -> radar.socket, ip=192.168.1.11,port=5555,device=DELPHI_ESR2_5
[29-10-2018 23:3:37] RadarSocket::RadarSocket, connected to 192.168.1.11:5555

Do you know what causes this error and how to fix it?
Thanks.

7

Dear atsutaka,

Could you please try to re-run with below command? Thanks.

./sample_radar_replay --protocol=radar.socket --params=device=DELPHI_ESR2_5,ip=192.168.1.11,port=5555

8

Dear SteveNV,

There is no change in the result…

I would be grateful if you could tell about any information we should check.
Any information would greatly help.

9

Dear atsutaka,

Could you try to run only “./sample_radar_replay” if the sample works or not? Thanks.

10

Dear SteveNV,

“./sample_radar_replay”(no argument) is working fine.

11

Dear atsutaka,

Thank you for your update. We will check it and update. Thanks.

12

Dear SteveNV,

Any update about this issue?

13

Any update?

Thanks.

14

Dear atsutaka,

Sorry for late reply. Unfortunately, DW does not support the ESR 2.5 24VDC. We only support the 12VDC.

15

Is there any plan for future releases of DW to support the ESR 2.5 24VDC radars?

16

Dear jkbell,

We have no plan to support the ESR 2.5 24VDC radars. Thanks.

17

Thank you for your response, Can you clarify if the Delphi ESR 2.5 12 VDC Radars will work with DW? Does the Continental ARS408 radar work with DW. We are using the Nvidia PX2 and were told from Autonomousstuff that the ESR 2.5 24VDC worked with this system so no we are back tracking to see what sensors actually work since we were steered in the wrong direction initially.

18

Dear jkbell,

Please refer to “Supported Sensors” in DriveWorks doc.
DriveWorks SDK Reference → Development Guide → Sensor Abstraction Layer → Sensors.

Supported Sensors
The following list shows the sensors that DriveWorks supports. For the most up-to-date information on supported sensors, see the Release Notes.

GMSL Cameras (NVIDIA DRIVE™ platform only)
Omnivision OV10635
Omnivision OV10640
Sekonix AR0231 (RGGB, RCCB sensors)
USB Camera
Any Video4Linux supported devices
PointGrey USB Cameras
Chameleon CM3-U3-31S4C-CS (Color sensor)
Chameleon CM3-U3-50S5M-CS (Mono sensor)
Grasshopper GS3-U3-50S5C-C (Color sensor)
Stereo Camera
ZED
CAN Bus
SocketCAN
Aurix Easy CAN
GPS
Any NMEA-compatible sensor using a serial UART
Xsens MTi-G-700 (serial based NMEA protocol + USB proprietary)
Garmin 18x
NovAtel dGPS
Lidar
Quanergy M8
IBEO Lux
Velodyne (VPL16, HDL32E, HDL 64-S3)
Radar
Continental ARS430 ethernet protocol
Continetal ARS430 CAN protocol
Delphi_ESR_2.5
IMU
Xsens MTi-G-700 (serial based NMEA Protocol + USB proprietary)