ERROR DW_NOT_AVAILABLEEndpointUDP: stopped

We can run /usr/local/driveworks/bin/sample_canbus_logger --driver=can.aurix --params=ip=10.42.0.146,bus=a

and we get a stream of CAN messages from the device connected to CAN1 on the harness.

But running /usr/local/driveworks/bin/sample_canbus_logger --driver=can.aurix --params=ip=10.42.0.146,bus=b

the process terminates without showing any CAN messages.

for bus=b, we get the following error.

104828400 ERROR DW_NOT_AVAILABLEEndpointUDP: stopped

whereas we get “EndpointUDP: started 10.42.0.146:50000” for bus=a (CAN1 on harness)

We confirmed there are continuous CAN messages from the device on CAN2 using a CAN/USB device.

The data rate is 500kb/s

We need to view the CAN data on the PX2

When I switch the device to CAN1 on the harness, I get the following error.

AurixCAN: lost clock sync between Aurix and Tegra clock. Tegra clock is ahead of Aurix clock by at least 908877672 msec

Dear cimig,

For time sync between Aurix and Tegra clock, please refer to the following link.
https://devtalk.nvidia.com/default/topic/1031778/faq/drive-px2-time-sync-guide/

And then please try to run the app again.
I could run the app w/o any error like below. Thanks.

nvidia@nvidia:/usr/local/driveworks/bin$ sudo ./sample_canbus_logger --driver=can.aurix --params=ip=10.42.0.83,bus=b
[sudo] password for nvidia:
Program Arguments:
–driver=can.aurix
–filter=000:000
–hwtime=1
–params=ip=10.42.0.83,bus=b
–send_i_understand_implications=0
–send_id=6FF

Initialize DriveWorks SDK v0.6.67
Release build with GNU 4.9.2 from v0.6.0-rc7-0-g51bd3aa against Vibrante PDK v5.0.5.0
TimeSource: monotonic epoch time offset is 1484388267289061
SDK: Resources mounted from /usr/local/driveworks-0.6/data/resources
nvrm_gpu: Bug 200215060 workaround enabled.
SDK: Create NvMediaDevice
egl::Display: found 2 EGL devices
egl::Display: use drm device: drm-nvdc
SDK: number of GPU devices detected 2
SDK: currently selected GPU device discrete ID 0
SAL: identified board as DrivePX2-TegraA
SensorFactory::createSensor() -> can.aurix, ip=10.42.0.83,bus=b
Cannot setup CAN message filters: DW_NOT_IMPLEMENTED
EndpointUDP: started 10.42.0.83:50000
^CEndpointUDP: stopped 10.42.0.83:50000
SDK: Release NvMediaDevice
Driveworks SDK released
nvidia@nvidia:/usr/local/driveworks/bin$ sudo ./sample_canbus_logger --driver=can.aurix --params=ip=10.42.0.83,bus=a
Program Arguments:
–driver=can.aurix
–filter=000:000
–hwtime=1
–params=ip=10.42.0.83,bus=a
–send_i_understand_implications=0
–send_id=6FF

Initialize DriveWorks SDK v0.6.67
Release build with GNU 4.9.2 from v0.6.0-rc7-0-g51bd3aa against Vibrante PDK v5.0.5.0
TimeSource: monotonic epoch time offset is 1484388267289061
SDK: Resources mounted from /usr/local/driveworks-0.6/data/resources
nvrm_gpu: Bug 200215060 workaround enabled.
SDK: Create NvMediaDevice
egl::Display: found 2 EGL devices
egl::Display: use drm device: drm-nvdc
SDK: number of GPU devices detected 2
SDK: currently selected GPU device discrete ID 0
SAL: identified board as DrivePX2-TegraA
SensorFactory::createSensor() -> can.aurix, ip=10.42.0.83,bus=a
Cannot setup CAN message filters: DW_NOT_IMPLEMENTED
EndpointUDP: started 10.42.0.83:50000
^CEndpointUDP: stopped 10.42.0.83:50000
SDK: Release NvMediaDevice
Driveworks SDK released