cjanand

As an additional note, this PCI-DIO48H is connected and application run on a WIN 1 machine. The project folder (developed on Visual Studio) has the cbw32.dll and Instalcal installed in the system recognizes the PCI-DIO48H card. The exact error message is "CBUL32.SYS driver device driver is not installed" Please advise. Thanks.

We moved over from the USB-DIO96H setup to a PCI-DIO48H set up on a different machine Instacal recognizes the PCI card, assigns it Board 0 designation. When we run the code though it throws up the following two: 1) CBUL32.sys device driver not installed (we thought this was not needed for PCI cards). 2) When we click OK on the above message it comes up with the PCI card type b not recognized. Queries: 1) Is CBUL32.DLL/sys needed, and if so, where do we get them? 2) The CB.cfg file is attached, and it does indicate board type as b. Additionally in the code we use a base address as 0x300 while the cb.cfg indicates it differently. Are we permitted to change the address in the file? 3) Additionally, any other advice to get over this issue would be great. Thanks, Anand C J CB.CFG.txt

Great support work, John. Got your code to compile as promised. Will continue on my journey. Thanks, Anand c J

John, Pardon me for being a bother. But I certainly don't seem to have divined the way to compile the code. I tried several methods including the suggestions given by you but I run into project configuration issues giving rise to a large list of errors. I am attaching the zip of the project using Visual Studio COmmunity Edition 2019. I have also attached the outputs, error and warnings that show up while compiling. Enlighten me on where exactly I am goofing - I still think it is a slew of project configuration / settings issues. Thnaks, Anand C J MccDaqPrj.zip MyBuildOutputs.txt

Thanks John. Will try your suggestions and keep you posted. Anand C J

Hi, Using an USB DIO96H unit with A win 11 machine. Have installed all the software from your site. Coded a simple cbFlashLED() test. Code is attached. cbw.h, cbw32.dll and cbw64.dll are all in the same folder. Visual studio 2019 used with preporcessor settings to WIN32, _DEBUG, _CONSOLE Get the following errors: Severity Code Description Project File Line Suppression State Error LNK2019 unresolved external symbol _cbFlashLED referenced in function _main CnvrtrClbrtrMain.c

Hi, We use both the USB DAQ and PCI DAQ cards. Trying to compile the example ULDO01.c in the Visual Studio 2019 IDE. Seem to be running in to namespace errors like: Identifier "using" undefined from file cstdint Identifier "namespace" undefined from file cstdio etc. Suspect that I am having a compiler/linker setup issue. Could you please indicate a solution? Thanks, Anand C J

Hi, So we found the USB-DIO96H too slow for our application. We are reverting to PCIe 48 pin I/O card - though we are getting them off some other suppliers These are still your cards which you do not sell now. Reverting, meaning, we were able to successfully run one of this on a WIN7 machine with your old libraries. The question now is when we move to a Win10 machine, do we continue to use the old libraries or do we go for the new Instacal libraries for the PICe card? A quick reply would be great. Thanks, Anand C J.

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, 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

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

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

Hi, We are looking for a programmer's manual for the USB-DIO96H. While we have worked out the application from the WIn11 machine, we need to program device itself. We already have the user's manual for the USB-DIO96H and a programmer's manual for the PCI-DIO48. We are looking forward to a programmer's manual for teh USB-DIO96H. A quick action will be greatly appreciated. Thanks, Anand C J

HI, We developed s/w to access the USB-DIO96H using the function calls given inyour example code libraries. The system OS is Win 10 and 11. The complete system runs extremely slow. We tried getting into the debug mode and when stepping through the function calls (like configuring the board, setting up base address etc) for the debugger to go from one lilne of code to the next it take about 6 to 7 minutes each step. We are trying to set up s/w timers to step into the code to check what is delaying the calls. But we thought it would be wise to check with you if there is something we are not doing right, than reinvent schemes here. A quick guidance or set of suggestions to fixthis would be greatly appreciated. Thanks, Anand C J

Hi, We could not locate where exactly the master cb.cfg or the cfg pertinent to the newly added board exists. Need the WIndows path please. Secondly, are there any docs on editing this file and the need for such operations. Lastly any specific guidance on how a base address for DIO96H should be assigned - can it be absolutely random? Thanks, Anand C J