Performance issue using Veristand and RT system for CAN communication uing custom device

[NI_Follower]

Hello I am facing an issue related with CAN restbus simulation using veristand and custom device to update counter and CRC.

I am using veristand 2016 and Xnet driver to send CAN messages.

There is a custom device which has a lookup table to generate the CRC based on the counter value.

Controller configuration is as below

At the begininng of the test the signal values, crc and counter ae generated as expected. But after 3 to 4 hours of continous run, the values updated are unstable sa below. But the cycle time of the message stay as exected.ie, 100 Hz

The CPU and memory consumption remains stable while checking from the console viewer

I have other signals, which has less frequency, e, 10 Hz which is working as expected always.

Here is the logic inside the custom device

Please help me to fix this issue

[Darin_G]

I'm not sure how to help you with this, which may be an old XNET driver bug.

When older VeriStand users need more than what the native XNET CRC offer today, those customers have switched to using this CD:
https://github.com/NIVeriStandAdd-Ons/CAN-Frame-Protection-Custom-Device/
which calculates CRC in software, instead of using the native XNET CRC checks built into the XNET driver.

For more recent versions of VeriStand, I advise you to look at our new NI Vehicle Communications toolkit
https://www.ni.com/cs-cz/shop/software/products/vehicle-communication-toolkit.html

which offers a lot more capabilities such as Automotive Ethernet, AUTOSAR support, RESTbus simulation.

[NI_Follower · Accepted solution]

i have solved it by a manual core allocation. i have 8 test sockets and my controller has 8 cores. so each custom devices are assigned to each cores manually.. now it looks better,