VeriStand

cancel
Showing results for 
Search instead for 
Did you mean: 

CAN counter and CRC update failed in Long run - Veristand 2016 and XNET

Hello ,

 

I am trying to fix an issue with veristand custom device. 

 

Requirement:

 

Need to update 2 signals , CRC and Counter in a CAN frame with values from a lookup table.

 

Implementation

 

NI_Follower_2-1651066434596.png

Controller is configured like this

 

Used veristand 2016 and PXI CAN port to generate the frames

Added a custom device, which has the lookup table to send the crc value corresponds to a counter value

 

NI_Follower_0-1651066103990.png

 

 

Issue

 

This implementaion is working for a parallet execution for some duration , approx 4 hours, After that the values are unstable. But the cycle time of the message is as expected. 100 Hz

 

Like this 

NI_Follower_5-1651066919041.png

 

 

 

At the begining till 4 hours it worked well , counter values updated from 0 to 15 and associated crc also sent. 

 

Dont know the reason for this instability after a long run. 

CPU and Memory usages seems in range and not increasing,

 

Any idea to fix this?

 

 

My observation is, this happens to the signals, which have a rate of 100 HZ, for the lower frequency signals its stable. For 50 Hz and 1 Hz, it worked as expected.

NI_Follower_4-1651066814817.png

 

 

0 Kudos
Message 1 of 2
(848 Views)

This is a duplicate of
https://forums.ni.com/t5/NI-VeriStand/Performance-issue-using-Veristand-and-RT-system-for-CAN/td-p/4...

Darin Gillis
NI - Chief Product Owner - VeriStand
0 Kudos
Message 2 of 2
(815 Views)