Automotive and Embedded Networks

cancel
Showing results for 
Search instead for 
Did you mean: 

[NI-ADCS] ndOpenDiagnosticsOnCANFD takes a long time to execute

Hello,

 

I'm turning to the community because i'm facing a problem and honestly don't know how to solve it.

 

Context : I'm using the C API for XNET and ADCS with Labwindows/CVI. I use XNET 19.0 and ADCS 19.0.

Hardware : NI PXI-8510 with CAN Transceiver TRC-8542

 

During the program execution, I have to open and close multiple diagnostics sessions. For this I use ndOpenDiagnosticsOnCANFD.

 

When starting the program, the first call of ndOpenDiagnosticsOnCANFD will always take a long time (~30-35s). I want to insist that it happens only on the first time the function is called and it will happen at every start of the program.

 

During this time, the CAN transceiver stays off (no LED on). I also tried to log the API calls through NI I/O Trace but the recordings start once the interface is active (so on ndOpenDiagnosticsOnCANFD call is finished).

 

Hoping somebody can help me on this issue 🙂

 

EDIT : I already checked this issue but as it is quite old, it wasn't very helpful : previous issue 

0 Kudos
Message 1 of 2
(1,390 Views)

Hi,

 

normally the first call (or the loading of the ADCS library, to be more precise) may take up to a second or so, while the library loads various needed components, but 30 seconds seems way too long.

For example, I just tried starting one of the CVI examples and it starts and connects basically instantaneous

(via XNET to the Demo ECU application).

 

Have you tried if upgrading ADCS to the latest released version helps, and optionally XNET too?

0 Kudos
Message 2 of 2
(1,364 Views)