labstreaminglayer / app-biosemi

Quick Start

The lab streaming layer (LSL) is a system for the unified collection of measurement time series in research experiments that handles both the networking, time-synchronization, (near-) real-time access as well as optionally the centralized collection, viewing and disk recording of the data.

The most up-to-date version of this document can always be found in the main repository README and the online documentation.

The most common way to use LSL is to use one or more applications with integrated LSL functionality to stream data from one or more devices (e.g., EEG and Eye Tracker) and from a task application (NBS Presentation, psychopy, etc.) over the local network and record the with the LabRecorder.

Most LSL Applications will come bundled with its own copy of the LSL library (i.e., lsl.dll for a Windows application). However, many applications and interfaces (e.g., like pylsl) do not ship with liblsl.dylib or liblsl.so on Mac or Linux, respectively. In those cases, it is necessary to install liblsl separately and make it available to the application or interface. See the liblsl repo for more info.

• Take a look at the list of supported devices and follow the instructions to start streaming data from your device. If your device is not in the list then see the Getting Help section below.
• Download LabRecorder from its release page. (Note that LabRecorder saves data to Extensible Data Format (xdf) which has its own set of tools for loading data after finishing recording.)
• Go through the Tutorials.
• Use LSL from your scientific computing environment. LSL has many language interfaces, including Python and Matlab.
  • Python users need to pip install pylsl then try some of the provided examples.
  • The Matlab interface is also popular but requires a little more work to get started; please see its README for more info.

If you are not sure what you are looking for then try browsing through the code which has submodule links to different repositories for tools and devices (Apps) and language interfaces (LSL). When you land in a new repository then be sure to read its README and look at its Releases page.

Getting Help

If you are having trouble with LSL then there are few things you can do to get help.

• Read the docs
• Search GitHub issues in the main repository, in the old archived repository, and in the submodule for your App or language interface of interest.
• Create a new GitHub issue. Please use the repository specific to the item you are having difficulty with. e.g. if you are having trouble with LabRecorder then open a new issue in its repository. If you don't know which repository is best then you can use the parent sccn/labstreaminglayer repository.
• Join the LabStreamingLayer #users channel on Slack. Invite Link. Someone there may be able to get to the bottom of your problem through conversation.
• You may also wish to try the very new labstreaminglayer.org forum

app-biosemi's Issues

No support for the new speed modes for the BioSemi Mark 2 high speed amp (MK2HS)

When trying to link with the new speed modes for MK2HS amp (speed modes 0-3 on the box) we get an error indicating speed modes above 8 are not supported. (biosemi_io.cpp line 164) I believe this is because the MK2HS amp sends out codes 10-13 for speed modes (0-3), and configurations for those modes have not been added yet. (See here: https://www.biosemi.com/faq/adjust_samplerate.htm).

I assume biosemi_io.cpp will need to be updated, but I am unsure if additional updates are needed

I see more thant 32 channels when selecting the "32, no AUX" option

Hi,

I use App-BioSemi and selecte the "32, no AUX" option (with "BioSemi-ABC" fro Cap Design). I expect to see 32-channel data but actually see 41-channel data when receiving the data with the pylsl package in Python. Which channels correspond to the actuall EEG channels? From 0 to 31 (in Python)? From 1 to 32? Or some other channels? And what is the order of the 32 channels same as the one shown below (which I got from https://www.biosemi.com/headcap.htm)?

Fp1
AF3
F7
F3
FC1
FC5
T7 (T3)
C3
CP1
CP5
P7
P3
Pz
PO3
O1
Oz
O2
PO4
P4
P8
CP6
CP2
C4
T8 (T4)
FC6
FC2
F4
F8
AF4
Fp2
Fz
Cz

And what are the other 9 channels for?

Signal delays in analog input box w.r.t. digital trigger

I'm currently investigating a timing issue where a square wave is 2-3 frames delayed (2048 Hz, approx. 1 - 1.4 ms) when recorded via the analog input box and compared against the digital trigger. I replicated the experiment (and used EEGLAB for data processing) on a .bdf file from ActiView, and the square waves from both the analog and digital signals are exactly aligned.

Can' access the download page

I'm trying to send biosemi data to LSL and tried to download this app. But there's no release and the link comes out blank.
waiting for your reply.

Unable to change channel names/labels (biosemi plugin)

Good afternoon,
I've been trying a lot of different ways to get the Matlab to change the channels A1-B32 to Fp1,Fp2 Etc. But non of the changes seem to actually make a difference when I am seeing the data in matlab.
When I use Bio-Semi's Actiview, I can change the channels by using a different configuration file.

Aux channels?

App-BioSemi/biosemi_io.cpp

Line 187 in 9da597f

// multiplexed, have 128ch EEG each and 8ch EXG each, plus 16 extra channels each (howdy!)

Are the Aux channels implemented properly? The comment above is a little disconcerting, even though these extra channels are eventually assigned "Aux" prefixes. I'm testing GSR, Plethysmography, Temperature, and Respiration. These signals appear in unexpected ways in the 16 recorded Aux channels. e.g. GSR is in Aux1 & Aux 2, Respiration is in Aux 9 and inverted in Aux 10, etc.

Error 5002 not being reported in LabRecorder or BioSemi app

The BioSemi amplifier can lose connection to the computer due to physical problems with the hardware. Once such error is the Error 5002 that is shown using the ActiView software as

Possible reasons: unsupported speedmode.
OR
Intermittent data loss (optical cable)
OR
USB driver not closed properly.

When you use the BioSemi LSL app however, this error is not reported. I am not sure if it is a general problem for more errors, but it would be very valuable if the biosemi App throws this error to the end user so they know that data is not being recorded. As it is now, nothing is shown in the LabRecorder terminal. I am using the Windows version of the BioSemi app.

If you are using the ActiView software it is reported and you can react accordingly.

CMake build not working

Hi @mgrivich ,

On Slack, Kana Okano is trying to get a LSL system up and running including Unity, python events, and BioSemi. I tried building the BioSemi app because we don't have one on the release page, but I can't get the cmake build to work (VS2017, using in-app cmake settings).

The first error I'm encountering is that it "cannot open include file ioctls.h". A very quick google suggests this is used in mingw builds. Is that what's going on here?