User Reference:SignalSharing: Difference between revisions
| Line 1: | Line 1: | ||
==Synopsis== | ==Synopsis== | ||
SignalSharing allows to tap into BCI2000 processing by receiving any filter output signal through a combination of a TCP connection, and shared memory. | ''SignalSharing'' allows to tap into BCI2000 processing by receiving any filter output signal through a combination of a TCP connection, and shared memory. | ||
==Function== | ==Function== | ||
Revision as of 13:44, 2 August 2024
Synopsis
SignalSharing allows to tap into BCI2000 processing by receiving any filter output signal through a combination of a TCP connection, and shared memory.
Function
The SignalSharing component in BCI2000 shares its input signal through a GenericSignal object which has been linked to a shared memory block using GenericSignal::ShareAcrossModules(). A dedicated thread waits for signal updates, and sends signal data out to a separate application waiting on a TCP/IP connection.
When the client application is running on a separate machine, full signal data are sent over the network. When the client is running on the same machine, only a reference to a shared memory block is sent. On the client side, a flag in the signal data block indicates whether full signal data is transmitted, or just the name of a shared memory block to which the client may connect in order to read data.