I have two questions for today:
- Is there an intended/preferred usage of the functions outlined in RadarDecoder.h from the NVIDIA side? We are trying to decide how to implement the functions with our radar data output format but are unsure how much flexibility we have since it is unclear how these functions will be used in the API. Are certain functions meant to only be called from within the decoder?
We have read through the documentation for RadarDecoder in the DriveWorks SDK Reference and are looking for more clarification.
- Is it possible to get access to the Radar.cpp file? We are finding it very difficult to integrate into the ‘black box’. Specifically the dwSensorRadar_processRawData and dwSensor_readRawData functions.
2A. Does the dwSensorRadar_processRawData function call the decoder’s dwRadarDecoder_decodePacket function?
2B. What is the expected format of the ‘data’ parameter in the dwSensor_readRawData function?
Dear lord_duckfoot,
Could you please help to check “Integrating with Custom Sensors” part in /usr/local/driveworks-0.6/doc/nvdwx_html/NVIDIA_DriveWorks_DevGuide.pdf?
If not enough, could you file a bug for your topic with “Adding feature request”? We will look into it.
Please login to https://developer.nvidia.com/drive with your credentials. Please check MyAccount->MyBugs->Submit a new bug to file bug.
Please share ID here to follow up. Thanks.
hello jgs2185,
according to Bug 2158499.
you should be able to access the documentation via DriveSDK/drive-t186ref-foundation/utils/scripts/DPX2-P2379-EB-V4.02.02_release.zip
please refer to the [EB-DrivePX_Software_User_Guide_DPX2_P2379.pdf], there’s [Data protocol of Easy CAN Frames] for your reference,
moreover,
we had support two socket types by default, UDP (SOCK_DGRAM) and TCP (SOCK_STREAM)
if you would implement your own radar device, you should also specify the protocol.
for exmaple,
./sample_radar_replay --protocol=radar.socket --params=ip=10.0.0.101,port=1234,device=CUSTOM,protocol=udp,decoder=libradardecoder.so