Hello,
First time on this board and I have a question pertaining to USB communication with DAQPad 6507.
First a little background information.
We have test suites which uses several communication media such as GPIB, RS232, TCP/IP, UDP, CAN, USB communicating with instruments through C++ libraries which interface with Python. We have 6 DAQPad 6507 units attatched to three different PC's built in with many other devices in 19-inch equipment racks.
For a little more than a year we have successfully used NIDAQ to interface with the DAQPad's. However, we are interested in using raw USB for the communication. The communication with NIDAQ is adequate. Nonethless, using raw USB would significantly simplify our installation software and development environment as well as lead to further optimization of our libraries. We use C++ in combination with the Win32-API.
We would like to investigate raw USB with DAQPad 6507.
Finally the questions:
1) We use GUID {7C797140-F6D8-11CF-9FD6-00A024178A17} to successfully enumerate the device DAQPad 6507 and open the driver file in the 'normal' fashion. The drive name is very long. However, we can not read the attributes from the device. The Win32-API returns Error 31, device not running or something like that, even though the device is properly hooked up and installed. Is the GUID correct? Is there some additional step needed to access the device?
2) How complicated is the language of DAQPad 6507? Is there a protocol description available or would we need to reverse engineer it?
Again, this is a development option and we will not spend endless amounts of time on the possible optimization. Nevertheless I would appreciate any help you could provide for this investigation.
Thank you. Sincerely, Chris. Software Development Manager, Automotive.