BioSemi.nl

Hi Erfan,

Have a look at this BioSemi forum thread:

viewtopic.php?t=400&highlight=gsr

Also, try the Search function at the top of this forum page, for example try the search string: gsr

Regards,
Paul

Hi Erfan,

1. Quoting the BioSemi web page mentioned previously:

"The receiver converts every 24-bit word from the AD-box into a 32-bit Signed Integer, by adding an extra zero Least Significant Byte to the ADC data.
The 24-bit ADC output has an LSB value of 1/32th uV.
The 32-bit Integer received ...

Erfan,

The code in my last post was mangled a bit by the posting process!!!

These 2 line are nonsense:

for (int ii=0; ii<newSamps>newSamps)
break; // not a complete packet

The problem seems to be caused by angle brackets. Let me write it correctly using Fortran operators, i.e. .lt. for "less ...

Hi Erfan,

Try the code below. I haven't actually tried it myself because I'm not near my development machines today.

I use your previously referenced variables: driver, ringbuffer, ringBuffersize

Sorry, posting seems to remove program indentation.

Paul ...

Hi Erfan,

Your numbers from READ_POINTER look right!

The frontend sample rate is set manually by the mode switch. Mode 4 is usually 2048 samples/second/channel.
Other possible mode settings are shown in a table at the bottom of this page:
http://www.biosemi.com/faq/make_own_acquisition_software ...

Hi Erfan,

You are getting close.

Your "readdata" argument for READ_POINTER is usually the address of a simple 4 byte integer, not an array.
READ_POINTER will store the current value of its internal "next sample index" in that integer so you can know
where the seam between new samples and old ...

Hi Erfan,

You define a ring buffer to hold your samples in your call to READ_MULTIPLE_SWEEPS.

Then READ_POINTER returns, in its integer argument, the position (an index) in this ring buffer where the next sample will be stored.

This index value will be between 0 and the size of the ring buffer ...

Hi Tom,

A long shot perhaps but something else to check ...

Some new computers are coming with USB3, which Microsoft does not yet support!

Apparently these machines usually have USB2 installed as well.

Make sure that you are using a USB2 interface.

Paul

Hi Maarcc,

Also, from the answer to another problem:

"When the acquisition is running READ_POINTER returns TRUE and when it's not running it returns FALSE."

To illustrate, in January 2010 Labview_DLL_Synctest.cpp was changed to test this returned value.

Paul

For the record, the problem has been resolved.

The trouble was caused, in part, by a difference between the two Labview_DLL.dll versions, in the way the READ_MULTIPLE_SWEEPS API is implemented.

Hans was calling READ_MULTIPLE_SWEEPS once and then using USB_WRITE calls to repeatedly start and stop ...

Hi Hans,

First lets try the following.

Create a text file called "labview_dll.ini" in the directory that contains your .exe. Put a line in this file that contains just the word "log". If this file already exists in your directory, add the line to that file. Then retry your program. You should get ...

Hi Tast,

File 'WUDFUpdata_01009.dll' is included in the BioSemi driver install package in the x86 subdirectory for 32 bit Windows and in amd64 for 64 bit Windows.

I'd suggest that you follow the instructions in "Driver Install Readme.txt" to first delete any existing BioSemi driver and then do a ...

For C, you can lift some code from the test program labview_dll_synctest.cpp in the C-code subdirectory of the BioSemi driver package.

There was this recent discussion:
http://www.biosemi.nl/forum/viewtopic.php?t=452

Or consider something built on:
http://www.biosemi.com/download/ActiView604-Light ...

According to the following Microsoft page, the Express edition is 32 bits only:

http://msdn.microsoft.com/en-us/library/hs24szh9(VS.90).aspx

You can use 32 bit applications on 64 bit Windows but be careful ...
install the 64 bit driver package from BioSemi to get the correct WinUsb driver ...

Happ,

I just did it all again as a new project and it worked!

Did you do this additional step that I posted somewhat later on Thursday:

"Add Labview_DLL.lib to the project's Source Files as an Existing Item. "

What error message(s) are you getting?

Paul

Oh, I think I had to do one more thing,

Add Labview_DLL.lib to the project's Source Files as an Existing Item.

Paul

Correction 2:

For some unknown reason the ".h" is being removed in my previous posts!!!

Paul

Correction:

I added a ".h" to each of the standard include lines in main.cpp so for instance,
#include <stdio> becomes #include <stdio>

Paul

Hi Happ,

I downloaded Visual C++ 2008 and created a new project.

I added your above code as source file "main.cpp".

In Project->Properties->Configuration Properties->C/C++->General, item "Additional Include Directories"
I added: c:\...\developers kit\c-code (... is whatever is needed on your ...

Happ,

I don't often use Visual Studio.

Have you tried something like this:

http://www.learncpp.com/cpp-tutorial/a2 ... 5-express/

Paul

Happ,

It looks like the linker doesn't have the labview_dll.dll file.
Do you include it explicitly as a library to be searched?

Paul

Hi,

The error codes are defined here:

http://msdn.microsoft.com/en-us/library/ms681381%28VS.85%29.aspx

Error 6 is "invalid handle".

In your code you don't check the returned value from the "opendriver" call.
usbHandle may be NULL at this point.

To verify the success of the driver install,
does ...

There are labview_dll.h and labview_dll.lib files in the driver download package.

If you link with the .dll file you don't need to use the LoadLibrary and
GetProcAddress calls.

Otherwise everything looks OK.

Paul

Tomek,

Let's try to determine how your USB interface differs from what we've been
testing on.

I'll send you some instructions in a private message.

Paul

Tomek,

I think your software has been installed correctly.

There is something different about your USB interface.

In Settings->Control Panel->System->Hardware->Device Manager,
when you expand the "Universal Serial Bus Controllers", does it
mention "USB 2.0"?

Paul

Hi Marialaura,

Great detective work!

The new BioSemi software uses MS's WinUsb driver and must be used with the 42 KB Labview_DLL.dll file which would be dated 2009 or 2010.

My guess is that you were mixing this new MS WinUsb driver with an older
ActiView that included the 49 KB Labview_DLL.dll ...

Hi Marialaura,

>I did this as it was suggested. Nothing happend. The program neither run >neither give error message.

Nothing! Did it just hang? And you had to Ctrl-C to abort it?

>Could be the problem a virtual USB port installed? I mean to create the .parallel port on my laptop I used a USB ...

Hi Marialaura

> But what is strange is that Biosemi is not under USB controller tab but is mentioned as 'MS WinUsb2'.

It is for me too so this is OK.

Could you try the following ...

Open a "Command Prompt" window.

"cd" to the directory containing the driver download package.

Type: cd ...

Hi Marialaura

The "MS WinUsb2 Driver" means that you've loaded the latest BioSemi driver software.

1. When you say you have the same problem is it,

a) error 5000 in ActiView

b) This error in Labview_DLL_SyncTest:

IN PipeType (3) not bulk (2)!
*** bsif_usb_write: acquisition thread not running ...

Hi Benoît,

Did some previous version of the software work on this computer?

In Settings->Control Panel->System->Hardware->Device Manager,
do you see "MS WinUsb2 Driver"?

When you expand the "Universal Serial Bus Controllers", does it
mention "USB 2.0"?

Paul