Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

Expected DAQmxResetDevice() time on a USB-6218 (or similar)?

- driver: NIDAQmx 19.6

- hardware: USB-6218

 

Hello,

 

I'm using the DAQmx C API to interface a USB-6218. On selecting the device for my purposes in my program, the call to DAQmxResetDevice() takes around 2200 ms on my system. Is this an expected time.

 

I wonder because the NI DAQ help states: This function does not wait for the device to reset before continuing execution.

 

The call itself returns with success. The call itself has been isolated to take the time, no enumeration calls or any other NI DAQ calls take place.


BR,

Paul

0 Kudos
Message 1 of 3
(78 Views)

That is rather interesting, though I have not worked with 6218 but other DAQs does return before actual reset completes and I had to work around by querying to see if the reset completed.

 

Anyone with the hardware should be able to test this out with other programming language because all still use the core C DLL.

Santhosh
Soliton Technologies

New to the forum? Please read community guidelines and how to ask smart questions

Only two ways to appreciate someone who spent their free time to reply/answer your question - give them Kudos or mark their reply as the answer/solution.

Finding it hard to source NI hardware? Try NI Trading Post
Message 2 of 3
(49 Views)

It would be interesting to get some measurement from other users.

I could provide the C++ code to enumerate and measure the time, if requierd.

0 Kudos
Message 3 of 3
(26 Views)