Search found 4 matches
- Fri May 26, 2017 6:10 pm
- Forum: BioSemi all other topics
- Topic: User written acquisition software problem
- Replies: 6
- Views: 31176
Re: User written acquisition software problem
Hi Paul, I found the problem. I ran my program in the Valgrind memory checker and found this error: ==15369== Syscall param ioctl(USBDEVFS_SUBMITURB).buffer points to unaddressable byte(s) ==15369== at 0x7870507: ioctl (in /usr/lib64/libc-2.17.so) ==15369== by 0x7B49B7E: submit_bulk_transfer (linux_...
- Thu May 25, 2017 6:25 pm
- Forum: BioSemi all other topics
- Topic: User written acquisition software problem
- Replies: 6
- Views: 31176
Re: User written acquisition software problem
Hi Paul, In labview_dll.h (#included by Labview_DLL_Synctest) 'CHAR' is #defined as 'char'. So they're the same thing. 'char' casts -1 to byte size all 1's. And I've checked _controlBuffer[0] to verify that. That's why I'm mystified by this problem. If you could offer any debugging suggestions I'd b...
- Wed May 24, 2017 3:02 pm
- Forum: BioSemi all other topics
- Topic: User written acquisition software problem
- Replies: 6
- Views: 31176
Re: User written acquisition software problem
You are right, apparently I needed to click 'Disable BBCode', the brackets were stripped. The ctor code actually is this: SubSysBS::SubSysBS() { // init _controlBuffer for (int i=0; i<64; i++) _controlBuffer[i] = 0; ... Any suggestions on debugging the main USB_WRITE error problem will be greatly ap...
- Tue May 23, 2017 5:44 pm
- Forum: BioSemi all other topics
- Topic: User written acquisition software problem
- Replies: 6
- Views: 31176
User written acquisition software problem
Hello, I'm attempting to write a module for our current data acquisition system to use our BioSemi Mk2 system. It's set in mode 4 (282 chan). I'm using Linux. I got the Labview_DLL_Synctest example program to work (after adjusting for 282 chan). My program and Synctest both link with liblabview_dll....