Closed pierreluctg closed 4 years ago
Hi @drebbe-intrepid, please have a look.
I will also post a PR with a fix.
Please see PR #85
This has been merged into v900 branch, needs to be pulled into other branches. I'll leave open for now with tags.
I still need to test this but I don't foresee any issues here.
PR #86
Thank you @drebbe-intrepid. Can you also push to v901 and master branch?
Can we also have a new release of the v900 (4.x) branch with this fix? Or a first release from v901 (5.x) with this fix in?
@pierreluctg I'll push it to all new branches and I'll make a new release for v900 (4.x) branch. I just want to test this a bit more before releasing this one.
Hi, we are observing a very large delay between Tx and Rx (of that same Tx message) on Linux when using libicsneo legacy API.
I have attached a code example showing the issue. On windows this is results in a tx+rx delay mean time of about 0.0025 sec. on Linux we get about 1 sec.
This means that on Linux sending a message (CAN in our case) and receiving that same message on the same CAN adapter and same network takes about 1 seconds. This is, as you know a eternity.
The code attached basically send a message with the current time in the data portion, then receive that same message and compare the time stored in data (Tx time) and the current time (Rx time).
Can you please have a look.
Let me know if you need any additional information.