Any Idea about this?
IMO, as loggers may use same local port, EB discard second access.
In “src/sensors/canbus/logger/README.md”, following description says that UDP port could be defined!
Could you let me know how to test it?
The connection to AurixCAN happens using UDP sockets. Additional arguments for the remote (`aport`) and
local (`bport`) UDP port can be specified if AurixCAN is working in a non-default configuration. By
default, on DRIVE PX2, AurixCAN is reachable over `aport=50000` and communicates with the Tegra over
`bport=60395`. On ACR however, AurixCAN is reachable over `aport=50000` and communicates with
the Tegra over `bport=50103`.
it’s because the sample_canbus_logger binary is being occupied by 1st process.
we will look into this, please have an alternative way to access two AURIX-CAN from TegraA and TegraB instead.
thanks
Regarding ‘I found bport should be only 60395 for bus A or B.
That is, the second command above you suggested does not work, terminated with some error messages.’, could you please upload the error messages on this topic? Thanks.
So, how can I use multi aurix can channel at a time? Whenever I turn on more than one channel, only the one turned on last works.
I have one channel set as
params.protocol = “can.aurix”;
params.parameters = “ip=10.42.0.146,bport=60395,bus=a,config-file=/usr/local/driveworks/data/samples/sensors/can/EasyCanConfigFile.conf”;
the other channel I set in this way:
params.protocol = “can.aurix”;
params.parameters = “ip=10.42.0.146,bport=60395,bus=b,config-file=/usr/local/driveworks/data/samples/sensors/can/EasyCanConfigFile.conf”;