Execution times using USB-DIO96H

[cjanand]

HI,

As you know we use the USB-DIO96H with the latest Instacal 6.73 libraries. The application was developed using C++ and the related libraries. We found that the application is fairly slow in its execution.

These are the values we got after profiling as a 32bit application running on Win11.

cbDOut using cbw32.dll        
Number of times called: 78,193    
Execution time per call: 2.99 ms
Total time elapsed for the full run of the app: 3.896617833 mins

cbDIn  using cbw32.dll
Number of times called: 24,829    
Execution time per call: 3.01ms
Total time elapsed for the full run of the app: 1.245588167 mins

The total duration for running the app from start to finish is short of 6 mins and the above two calls consume 5.14 minutes

Is this the expected speed of operation of the I/O access for this DAQ?

Is there something we are missing by which we can speed this up?

A quick reply with suitable suggestions would be great.

Thanks,

Anand C J

[JRys]

The USB-DIO96H is not a speedy device, and my test indicates that a single 8-bit port can be updated about 2600 times per second.  I used a 32-bit C program with a while loop to write ones & zeros continuously for my test. To determine the update rate, I measured the output square wave which was about 1300 Hz (2600 updates).

[cjanand]

Continuing on this, how fact it the PCI/PCIe DIO96 compared to the USB-DIO96? Just need a ball park comparison. Thanks.

[JRys]

I have yet to have the opportunity to test the PCI or PCIe boards, but I have heard that they are 10-20 times faster.

[cjanand]

JRys,

So is there a new product for PCIe 96 channel.

The ones on the website says "Not recommended for new designs".

A quick reply would be great.

- Anand C J

[JRys]

We are not designing any new PCI or PCIe boards.

You should check with National Instruments. They may have a product more suited to your application.

[cjanand]

JRys,

Question 1: Do the National Instrument PCI/e DAQ's use the same libraries as the Instacal?

Question 2: We profiled the f/w running the PCI and the UDB DAQ units. We seem to get PCI transactions under 10uS while the USB accesses seem to be around 2.9 ms? Could your libraries be using wait times on USB calls that account for such dergadation?

- Anand C J

[JRys]

National Instruments DAQ's are not compatible with InstaCal. Instead, they use Measurement & Automation Explorer.

We did not add artificial delays to the USB-DIO96H communication process.