Jeffrey

Per the User's manual, https://www.mccdaq.com/pdfs/manuals/USB-205.pdf, page 16, Trigger latency spec states: 1 µs + 1 pacer clock cycle max Correct.

Scan set up time is between 20 mS and 80 mS. the setup time is PC dependent, depending on how long it takes to setup an interrupt, etc. I don't have better hard data than that. you request a sample rate and the device driver tells you what it can really do. This is due to the divider circuit built into the USB-205. Most requested values it can achieve, but sometimes it can only get close. DAQami is just reporting back what the driver tells it.

In your VB6 deployment wizard, there is probably where CBW32.DLL is picked up. Remove it and you won't see this problem on the next install. Happy Thanksgiving! Jeff

message sent to you via private messaging.

So there is a module named "Delay08" perhaps best at this point to send me the worksheet.

26 characters long, all alpha except the last set are all numbers, and yes there are "-" you do not need to uninstall, just run the configurator and enter the key. Then open the worksheet, if you get the error click ok or continue of whatever it states, so you can open the worksheet and see the module.

The key used on the development system (the one that doesn't show the error)

did you install your DASYLab 13 key on the computer showing the error?

Hello @Atanas You are correct, DAQami does not include the external clock option. The device is capable of using AICKI for external clock but as stated, that feature is not included in DAQami. it can be implemented using the Universal Library in Python (or any other supported IDE). See example ULAI12, it features ExtClock mode (external clock). The USB-205 has only one A/D converter, so when you set up a scan for 1 channel, you get 1 sample for each external clock pulse. but when you scan more than 1 channel, each external clock pulse will acquire one sample from one channel, but with each clock pulse, the multiplexer will index through your channels. in short, you need 2 clock pulses to sample from 2 channels. This is how the USB-205 operates. Other devices include 1 A/D per channel such as the USB-1808, USB-1608FS-PLUS, or the USB-2020. Many other devices have a scan option called BURSTMODE where for each external clock pulse provided, the device scans through ALL the channels you've selected in the AInScan function. This minimizes skew time. But as stated, the USB-205 does not include either of these options.

normally it would be here... But you truncated it. :-O As stated in a previous response I sent....

is there a pop up message stating which module is missing? go on the original development system and find out which one it is. That will help to determine why it is not on your target system

Hello @Jon Morris When InstaCal finds your board as board 0 and has no problems accessing yet your VB6 program does, the most likely reason is because you have multiple copies of cbw32.DLL on your system, and they are not all the same rev number. Easy fix though, starting at C:\ have your system search for cbw32.dll. I'm sure you'll find more than one. The only one that needs to be there is the one installed in C:\Program files (x86)\Measurement Computing\DAQ. note if you are running 32 bit Windows 7 the path is C:\Program files\Measurement Computing\DAQ. If you find any others, delete them. if you are not comfortable with that, at least rename them such as cbw32.old

I would try a different computer.

it does not. I would search the entire hard drive (starting at c:\" for cbw32.dll and cbw64.dll. There should not be any copies left on the system. If there are, I recommend you delete them. re the Registry, assuming you have removed all MCC and DASYLab software, I would search the registry for any DASYLab, InstaCal, Measurement Computing residual keys. and delete them all. There is no easier way to accomplish this.

responded via private message...

The 26 character key is what sets the features for the various versions of DASYLab (Lite, Basic, Full, Pro, or Runtime). certainly. this folder: https://mcc.download.ni.com/#Archive/DASYLab/DASYLabV13/ this is the download I recommend: https://mcc.download.ni.com/Archive/DASYLab/DASYLabV13/DASYLab 13_0_0a.exe Depending on the MCC driver you used (check your development computer, DASYLab 13 configurator, installed drivers): https://mcc.download.ni.com/#Archive/DASYLab/DASYLabV13/MCC-DRV all V13/MCC-DRV_13_4/ or https://mcc.download.ni.com/Archive/DASYLab/DASYLabV13/MCCDAQ-Classic Driver/mcc-classic.13.0.0.632.en.dlp to be clear, to make the runtime run like the original, use the MCC DASYLab driver used on the DASYLab 13 installation. Easy way to tell is to run DASYLab 13, go to the modules >> inputs/outputs. If the folder name is MCC-DRV use https://mcc.download.ni.com/#Archive/DASYLab/DASYLabV13/MCC-DRV all V13/MCC-DRV_13_4/ if the folder name is MCCDAQ (or similar) use https://mcc.download.ni.com/Archive/DASYLab/DASYLabV13/MCCDAQ-Classic Driver/mcc-classic.13.0.0.632.en.dlp still not sure? Send me a picture of the configurator, Packages tab with Data acquisition tree expanded so I can see the list of drivers you have installed and their rev numbers.

responded via private message....

Hello @Joerg Hampel I suggest you have your customer run the LV-link3 examples: DtAinSingle.vi and/or DtAinMultichannelSingleU32.vi or similar example. I ran these two example more than 20 times each, there were no errors.

There has to be something different between the 2 systems. What are the differences? You stated one computer it running DASYLab 13 development and the other is running DASYLab 2022 (V16) runtime. I would uninstall DASYLab 2022 and install DASYLab 13. Until you get the problem resolved, for a limited amount of time (for the purposes of trouble shooting), you may install your DASYLab 13 license on the previously installed DASYLab 2022 system. Get it working, and then change the key to your runtime. Note you do not have to reinstall DASYLab 2022 at that point, just use the DASYLab 2022 runtime key on the DASYLab 2013 runtime install.

Until you can get InstaCal to operate properly and see that InstaCal recognizes the USB-2408, I would not give any further thought to DASYLab. There is something wrong with your Windows OS installation. Recommendations: Run Windows update, Run a virus scan, Set to an earlier restore point. You might also get in touch with your IT folks, perhaps they know of some change to your OS that you don't. For the sake of a test and to gain some confidence in the components, try installing InstaCal and your USB-2408 on another computer.

What is your device make and model on both the development computer vs the one you installed the runtime? You'll need to change the settings to match those of the working computer.

Hello @Jennifer3798 as requested... 153862B.STEP

Hello @jrayeske no, there is no ul.get_daq_device_inventory(InterfaceType.USB) for LabVIEW. The device must be present in InstaCal. Direct access to the DLLs is not supported. Case in point, you don't ever access devices via DaqDevInfo.dll. As stated, it is not supported, but if you really, REALLY want to, then you would use cbw32.DLL for 32 bit LabVIEW or cbw64 on 64 bit LabVIEW. header file? go to C:\Users\Public\Documents\Measurement Computing\DAQ\C for cbw.h. Documentation on all function calls is found in https://www.mccdaq.com/pdfs/manuals/Mcculw_WebHelp/ULStart.htm This is assuming you want to take this on, but as stated, Measurement Computing does not offer support for using our DLLs in LabVIEW. MCC offers the ULx for NI LabVIEW, that we do support. I just want to be clear on that.

Hello @ee.engineer That error indicates there is a missing module on the target (newly configured) system. Best guess: Run the DASYLab Configurator, and verify the Measurement Computing driver is enabled. if it is not enabled, enable it. click 'OK' at the bottom, follow the onscreen prompts, and try running the work sheet again. if it is enabled, disable it, click OK at the bottom and follow the onscreen prompts. Then run the DASYLab configurator a second time, and this time, enable it. click 'OK' at the bottom, follow the onscreen prompts, and try running the work sheet again. -sometimes the first time the MCC-DRV driver is enabled doesn't quite work right and needs disable/enable cycle.

There is something wrong with your InstaCal installation. As a test, I would unplug the USB-2408 from the computer, and then run InstaCal. if it launches and then shows you normal operation (shows you the board list), then perhaps there is a problem with your USB-2408. Normal view of InstaCal with no boards showing: if you see the same behavior (shows the splash screen then exits), then you will need to uninstall/reinstall InstaCal I read you don't want to do an uninstall/reinstall, but I see no other option when you can run InstaCal.