Error 1074384878

[DL48114]

Does anyone have any suggestion on how to fix this issue?

Attached is the VI which is called within a sequence in Teststand that is looped for 2700 times.

In the VI I am stopping the session, flush, clear, and close the system after sending a single CAN frame. I am not sure how to get around this error.

Thanks.

[JefeL]

Depending on what version of XNET you are using this error description could be misleading. There is a static limit of 500 frames per interface. When attempting to open a session with more frames that that you get an error. The wording for this error in earlier versions of XNET was misleading and I want to say identical to the error you have shown. I believe we changed the error description in XNET 17.0 to be more helpful.

[DL48114]

Hi,

I am using NI-XNET 17.0.

Please help me understand what you mean by session with more frames.

I have a sequence in Teststand which loop through 2700 times. Each time, it will call this VI. In the VI, it creates a new session which sends one frame and close it out. Why would it reach the static limit of 500 frames?

Thanks for your help.

[JefeL · Accepted solution]

The picture of your code shows that you are using a Frame Output Single Point session which accepts an array of frames as input. XNET only allows 500 frames per interface so if you assign more than that to a single session it will error. You can have multiple sessions with varying numbers of frames on each interface but the total number must be 500 or less. Obviously if there is only a single element in your input array this would not apply.

In your TestStand sequence, does the error always occur on a specific iteration? If so, what iteration?

Does adding a small delay between iterations have an impact on the error?

[DL48114]

Thanks for the quick response. There is only one single element in the input array. I have updated the GIF to change the input into constant instead of user input.

The error occurs randomly at different iteration but it is always at this step. I do have a 3 second wait before and after this VI.

[JefeL]

Unfortunately the updated picture does not indicate how many frames are assigned to the session. Add code like this to verify that the frame count is always 500 or less: