BioSemi.nl

Hi Rivasd,

The usual approach, in any computer language, to read sockets efficiently is usually
something like this:

1. create a very large input buffer;

2. call 'recv' using that buffer and its dimensioned size;

3. 'recv' fills the buffer with what is immediately available, up to that ...

Hi Barry,

You're right, it doesn't seem to make sense. Perhaps you've stumbled on some subtle difference between
C and C++.

My suggestion ...

You have a C program that works - synctest. Try building your program from that, by first
stripping out what you don't need, testing at various stages that ...

Hi Barry,

As I understand things, here USB_WRITE expects as its 2nd argument the address of a 64 byte array
with all bits on in the first byte and the following 63 bytes all zeros.

The Synctest program is written in C and uses a "cast" to CHAR to set this first byte:

controlBuffer[0] = (CHAR)(-1 ...

Hi Barry,

This does not look right:

// init _controlBuffer
for (int i=0; i<64; i++)
_controlBuffer = 0;


Isn't there a subscript missing?

Paul

Can you roll Win 10 back to a pre driver install restore point?

Paul

Hi Nikolay,

Before 2009 BioSemi distributed a Windows kernel-mode driver only. Since 2009 BioSemi has been also
distributing a Windows user-mode driver. Most users now install only this user-mode driver.
The kernel-mode driver actually won't install on many newer versions of Windows, for example ...

The BioSemi download package for Windows doesn't contain everything needed to re-build LabView_DLL.dll.
No one has ever wanted to.

Routines BSIF_GET_STRIDE(), BSIF_GET_SYNC() and BSIF_GET_BYTES_PER_MSEC() are all entry points into the
USB ring buffer control routine bsif_winusb.cpp. You would need ...

Hunkeelin,

For includes, have a look at the code file "labview_dll_synctest.cpp" in the
BioSemi Linux driver download package. I think you need to include only "labview_dll.h",
which is in the download.

For linking, look at what is done for "Labview_DLL_SyncTest" in "Makefile", also in
the ...

Lloyd:

1. You can see a C language initialization sequence that works in the source code for the test program Labview_DLL_SyncTest
that comes in the driver download package. The source code is in file labview_dll_synctest.cpp.

2. With regard to putting the READ_MULTIPLE_SWEEPS call in the class ...

Hi Ben,

I was trying to rule out software - Windows Update was a long shot.

The semaphore timout occurring on the first input buffer means that
there's little or nothing coming in through the USB.

Paul

Hi Ben,

Some other things to check:

1. Is this Windows? Are System updates applied automatically? Were there any applied overnight Thursday/Friday?
If yes, can you restore to the prior state using Windows Restore?

2. Try running the test program "Labview_DLL_SyncTest" that comes in the driver ...

Hi Alex,

MISINFORMATION ALERT!!!

In yesterday's post I said that the first buffer returned by READ_POINTER is at least
262144 bytes in size.

This should have been the half of that: 131072. I have to learn to check the code
BEFORE posting rather than AFTER!!! This value changed several times ...

Hi Alex,

The new sync detection logic used to determine the number of channels (size of a
single packet of samples) in the latest version of the synctest program (to
avoid attaching meaning to the speed mode setting) is as follows:

When sampling starts the first two words dropped into the ring ...

Hi Alex,

A delayed reply - I was away from the internet last week.

My understanding of the situation is this:
A set of samples from one sweep of all channels is always preceeded by a sync word and a
status word. The sync word has the hexidecimal value ffffff00 and the status word contains,
among ...

Alex,

The modified labview_dll_synctest.cpp is needed only if you have the newest
Biosemi hardware. Again, it hasn't been tested with the new hardware but it
does still work with the older hardware. The program can be used on Windows,
Linux or Mac, in place of the version included in official ...

Alex,

1. My guess is that you have the environment variable "PKG_CONFIG_PATH" defined and
that is causing the mixing of the 32 and 64 bit objects. You may have defined this variable
if you built the 64 bit software in the same login session that you are using to build the
32 bit software. Try ...

Alex,

Are you still having trouble with the library?

Paul

Alex,

Perhaps this is what you need to install: glibc-devel.i686

Taken from: http://stackoverflow.com/questions/7412 ... -directory

Paul

Alex,

Your problem seems to be that your version of RedHat 64 doesn't have the 32 bit libraries and development support packages installed.
To compile and/or run 32 software you will need them. They can probably by added using "yum". It could be tedious adding what you
need one-by-one. Perhaps ...

Alex,

1. A disclaimer: I have never used Matlab.

2. "liblabview_dll.so" is a link to the real file which is "liblabview_dll.so.0.0.1". Your loadlibrary may not be
smart enough to follow the link. Try using the actual filename rather than the link name.

3. There is a line missing in the INSTALL ...

Sandeep,

On a 64 bit system install the 64 bit drivers, even if your programs are 32 bits.

Paul

If you are running 64 bit Linux and need 32 bit versions of the libraries liblabview_dll and libusb
(for instance, to run 32 bit Labview and Actiview), use the following procedure to generate them:

1. In the Biosemi driver download package for Linux, use the Linux32 directory.

2. In the INSTALL ...

To update this story ... the problem has been resolved.

It was not an OSX10.5 --> OSX10.6 problem nor was it a Labview 8.6 --> 2010 problem.

There was a flaw in the procedure used to create the Mac driver download zip file. The fault was apparently tolerated by Labview 10.6 but not by 2010.

A ...

Matthew,

I send the step-by-step procedure that I use on OSX 10.5 in a private
e-mail.

Please tell me where your procedure differs.

Paul

Hi Matthew,

This output is as expected which means that the OSX 10.5 libraries do work on 10.6.

The problem is therefore with the "BioSemi-Labview_DLL.framework" structure -
either Labview can't find it or its format has changed.

Please try the following.

When you start ActiView700-Mac-Rev15.vi ...

Matthew,

1. Open a Terminal window.

2. Go to the directory that contains the Labview_DLL_SyncTest program by using something like this:

cd ~/Downloads/USB\ drivers\ Mac/OSX-10.5-32/bin

3. Fix a permissions problem by using this command:

chmod u+x Labview_DLL_SyncTest

4. Start the program using ...

Hi Michael,

The DLL with Actiview and the DLL in the driver package should be interchangable - I believe the Actiview download package has been
updated since you reported the different versions.

You might try replacing your Actiview's DLL with the one you are using for development to build some ...

Hi Michael,

Since Actiview, by default, uses a 33554432 byte buffer and seems to be working for many users, I would doubt that there's a problem with
this size.

With buffer size 33554432 and speed mode 4 the buffer holds 29746 packets of 282 words plus 236 words of the 29747th packet. The I/O ...

Hi Michael,

This TRUE/FALSE from READ_POINTER was fixed in Jan 2010 so any Labview_DLL.dll created after date that should be OK.

The dll file packaged with Actiview must be from before that date. I will bring this to Coen's attention.

As you have discovered, you must download and install the ...

Hi Michael,

Try this:

Open a command prompt window and cd to the directory where you unzipped the BioSemi driver download package.

Then cd to USB_drivers_Windows_32bit (or 64bit), Developers_kit, C-code.

Run this: Labview_DLL_SyncTest 5

This will run for 5 seconds. Hit any key to exit.

Now ...