Confusion with Acquisition server receiving both Data stream and Tags

Obtaining data from various hardware devices
Post Reply
edwaldt20
Posts: 2
Joined: Mon Dec 06, 2021 2:47 pm

Confusion with Acquisition server receiving both Data stream and Tags

Post by edwaldt20 »

We have set up the Acq.Server (AS) to receive EEG data as a stream of bytes.
The data stream provider is a python script that acts as a Server for the AS.
This works fine.
It is confusing that the python script is a Server for AS, (with 'bind' and 'accept'), and AS acts as its Client, but it works.

One of the channels of the EEG stream is not EEG data, but in fact event markers.
Now we'd like to add the ability to feed Tags, created from this last channel, from
the same python script to the AS, using the tag mechanism.

This mechanism is described in the documentation as a client, which writes 24byte tags
to the Tag-port on the AS. However, we find the AS constantly refuses the connection from
the python script, which is already acting as a Server for the data stream and providing data.

Does anyone here know of a complete example of this actually working? Preferably with Python?
Are we misunderstanding the communications - will this not work with the same script providing
both data and Tags ?

Thanks for any hints,

Thomas
Posts: 210
Joined: Wed Mar 04, 2020 3:38 pm

Re: Confusion with Acquisition server receiving both Data stream and Tags

Post by Thomas »

Hi,

Sorry for the late reply!

There is an example of TCP tagging client written in python in the code base: https://gitlab.inria.fr/openvibe/extras ... -client.py

Hope this helps,

Thomas

Post Reply