Other Parts Discussed in Thread: IWR6843
I am having issues using the ROS driver with the IWR6843 ISK running mmWave SDK version 3.1. I would guess that these issues are caused by changes to the way data is packaged between previous versions of the SDK and 3.1, but I am not sure. Has this sensor been tested with ROS?
The error I am seeing is outlined below.
Sending chirp config...
mmwDemo:/>'
[ INFO] [1554322830.829399073]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1554322830.830229727]: mmWaveQuickConfig: Sending command: 'sensorStart'
[ INFO] [1554322830.841921667]: mmWaveCommSrv: Sending command to sensor: 'sensorStart'
[ INFO] [1554322830.860494031]: mmWaveCommSrv: Received response from sensor: 'sensorStart
Debug: Init Calibration Status = 0x1e
Done
mmwDemo:/>'
[ INFO] [1554322830.902677967]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1554322830.903663989]: mmWaveQuickConfig: Ignored blank or comment line: ''
[ INFO] [1554322830.904419522]: mmWaveQuickConfig: Ignored blank or comment line: ''
[ INFO] [1554322830.904481030]: mmWaveQuickConfig: mmWaveQuickConfig will now terminate. Done configuring mmWave device using config file: /home/radar/ROS_workspace/src/ti_mmwave_rospkg/cfg/6843_2d.#chirp config sent successfully
terminate called after throwing an instance of 'std::out_of_range'
what(): vector::_M_range_check: __n (which is 192) >= this->size() (which is 192)
[mmWaveQuickConfig-3] process has finished cleanly
log file: /home/radar/.ros/log/ebbddb64-564d-11e9-8429-08002702233a/mmWaveQuickConfig-3*.log #log file does not exist
[mmWave_Manager-2] process has died [pid 11219, exit code -6, cmd /home/$USER/$ROS_WORKSPACE/devel/lib/ti_mmwave_rospkg/ti_mmwave_rospkg __name:=mmWave_Manager __log:=/home/$USER/.ros/log/ebbddb64-564d-11e9-8429-08002702233a/mmWave_Manager-2.log].
log file: /home/$USER/.ros/log/ebbddb64-564d-11e9-8429-08002702233a/mmWave_Manager-2*.log
Thank you,
