BioSemi.nl

Paul, my huge apologies! It seems like the sleep deprivation of being a new dad (less than 3 weeks now) is in fact affecting my code. I hope you didn't waste too much time on my query, but I thank you sincerely for trying. FYI, my modular arithmetic was fine, so I didn't lose synchronization. But wh...

Hi Paul, I too have been able to use ActiView to obtain uncontaminated data, so I was surprised by this error. However, it's worth noting that the DLL that I'm using, and the one that ActiView uses are different. That being said, I wish I could share my code, but unfortunately cannot (company restri...

I'm getting a strange bug when using the Labview_DLL.dll in my C++ program. I setup my program according to the instructions http://www.biosemi.com/faq/make_own_acquisition_software.htm, and I'm using the Labview_DLL.dll obtained from the current download of the "USB driver Windows (32bit)" from htt...

When I run that application, I do get the same results. To be specific, since this is important for the discussion and solution below, I'm talking about the application to which you referred, but obtained from a "USB driver Windows (64bit)" download I made on August 3, 2011. Please be aware that thi...

In fact, in my tests, I've found that all of the functions described http://www.biosemi.com/faq/make_own_acq ... ftware.htm always return true, regardless of whether the device is on/off or connected properly.

Forgive me for being completely naive, but you are talking about actually connecting the pins on the rear panel of the optical receiver/usb interface with wires, correct? If I'm understanding correctly, there isn't a software solution without this hardware tweak.

Sorry, but I guess I wasn't clear. These output trigger pulses don't seem to get saved to the data stream in the ringbuffer. Is there a way to write to the input trigger pulses which are recorded on the sync line? Or are these output trigger pulses recorded somewhere? I basically need to "time stamp...

So when sending data in the 2nd and 3rd byte, after USB_WRITE has been called to enable the handshake, should the first byte always be '\xFF'? This won't try to re-handshake, right?

I don't understand what data to send to USB_WRITE. [url=http://www.biosemi.com/faq/make_own_acquisition_software.htm]This link[/url] suggests a 64 byte array. But even with [url=http://www.biosemi.com/faq/trigger_signals.htm]this link[/url] I don't understand which byte of the 64 is recorded as the ...

I'm having this same problem, and the value returned from READ_POINTER does not seem to indicate whether acquisition is running, since it always returns true. Instead I get some output to the command line that says: GetOverlappedResult for buffer 0 returns 121 The semaphore timeout period has expire...

Thanks for the info Coen. Could you add my contact information to a list to be notified when you find a solution to the 10-packet limit, or simply reply to this thread (I'm subscribed). Thanks!

Thanks Coen! That seems like it'd be a great solution. Just one question. That page says about the latency "timing of the trigger inputs is accurate to the time period of a sample", but I understood USB communication to have inherent delays of up to 30 ms. Is this not the case with the USB_WRITE fun...

I've been creating a C++ based application (not LabView) using the LabView_DLL.dll, as described here (www. biosemi. com/faq/make_own_acquisition_software.htm). Now I need my program to send trigger pulses on the parallel port to synchronize with the BioSemi EEG collection (ActiveTwo Mk2), and I'm s...