Jump to content

Coy C

Members
  • Posts

    3
  • Joined

  • Last visited

Everything posted by Coy C

  1. I'm updating a legacy C# project using a USB2523 to use a USB2627. With the new driver for Win10 64bit, the board appears to continue to acquire data after being aborted in mid data acquisition. This prevents the system from starting data acquisition again because the board is busy and not available. Given some time, the board must time out as it once again becomes available and data acquisition can be started. The following call is being used to stop the board. _daqBoard[iBoard].StopBackground(MccDaq.FunctionType.DaqiFunction); Is this the correct way to stop the board during data acquisition? If so, do you have any suggestions about what I need to do to fix this issue? Also, can you point me to example projects written in C# and C++?
  2. Hello, I have been handed a legacy system that uses a USB-2523 and needs the software updated to use a USB-2627. Do you have any documentation on the changes required in the software? So far, I have found that the registry entries have changed. For example, the information stored at System\CurrentControlSet\Services\USBDAQLIB\Enum is now stored at System\CurrentControlSet\Services\mcusb\Enum. The issue I am struggling with at the moment is that when the software calls the DaqInScan() function, I get an exception. err = _DaqBoard[iBoard].DaqInScan(_chanArray, _chanTypeArray, _gainArray, ChanCount, ref _sampleRate, ref PretrigCount, ref Count, _memHandle[iBoard], _options); The values passed in are: _chanArray = 0 _chanTypeArray = Analog _gainArray = Bip10Volts ChanCount = 1 _sampleRate = 10000000 PretrigCount = 0 Count = 26214400 _memHandle[iBoard] = 701038592 _options = Ctr16Bit, Background, ExtClock, ExtTrigger The exception message is: Exception = BadBoardType Exception = This function can not be used with this board. Exception = False I have been all over your website but have not been able to find the info I need to solve this one. I could not find any example programs for the 2600 series here: https://mcc.download.ni.com/#downloads/example_programs/Product_Specific_Examples/ I downloaded the ULHelp files from the following link and the index displays correctly, but none of the actual text. https://www.mccdaq.com/pdfs/manuals/ULHelp.zip Any help sorting out what has changed in the software between USB-2523 and USB-2627 and specifically why the DaqInScan() call is throwing an exception with the 2627 but not with the 2523 would be greatly appreciated. Thanks, Coy
  3. I am working on bringing a legacy Win7-32bit system using an IOTech 3005USB board up to Win10-64bit. I am having problems interfacing with the IOTech 3005USB board and have some questions. 1) Is it possible to use the IOTech 3005USB board on a Win10-64 bit system using a 64bit application written in C#? 2) Do I need to use a different driver for 64 bit. I am currently using the drivers in the daqcom2setup.exe which has a version number of 2.11.15.0? 3) Can you send me a compiled application I can use to prove the hardware is working on Win10 64bit? At this point, this is what I have been able to do: * I can compile the example project at C:\Program Files (x86)\DaqCOM\VC7\DaqBoard3KUSB\Daq3KUSBAnalogInput in 32bit. When I run it, it appears to see the 3005USB and collect numbers from it. Is there a way to use this program to prove that the numbers are actually coming from the hardware. At this point, they just appear to be random small values. I have a signal generator if that would help. * If I try to recompile the above project in 64bit, it fails to run stating it "cannot register". * I can compile and run my own, simple C++ project in 32bit and find the board. This does not work if I try to compile in 64bit. Any help would be greatly appreciated, Coy
×
×
  • Create New...