tagging does not work with our equipment
Posted: Wed Oct 14, 2020 12:17 pm
Hi, glad to find here and urgent to ask one question.
We have developed an EEG amplifier---in its primitive stage though.
It works fine with the Modular EEG P2 driver because we used their proxy.
And if we send 6 channels of ideal sin waves to test, the perfect waves could be received via the serial port and displayed on openvibe.
When we run the motor-imagery-bci-1-acquisition xml, the tagging just looked very dense and weird, almost ten times one second.
But if we changed the acquisition server to general oscillator or general time signal whatever built-in signal generators, the tagging was fine.
BTW, we also recorded the signal and stimuli tagging together into CSV files, the built in signal generator files have very few tagging in the CSV file,
however the ov file can be correctly read out with the General file reader, including the tagging. It can also be correctly transferred with the ov2mat function into mat files.
Our amplifier produced CSV file has a lot tagging in the CSV file, but cannot be read out by the ov2mat function. This ov2mat could not seperate the stimuli information.
I am very very confused.
Thanks a lot !
We have developed an EEG amplifier---in its primitive stage though.
It works fine with the Modular EEG P2 driver because we used their proxy.
And if we send 6 channels of ideal sin waves to test, the perfect waves could be received via the serial port and displayed on openvibe.
When we run the motor-imagery-bci-1-acquisition xml, the tagging just looked very dense and weird, almost ten times one second.
But if we changed the acquisition server to general oscillator or general time signal whatever built-in signal generators, the tagging was fine.
BTW, we also recorded the signal and stimuli tagging together into CSV files, the built in signal generator files have very few tagging in the CSV file,
however the ov file can be correctly read out with the General file reader, including the tagging. It can also be correctly transferred with the ov2mat function into mat files.
Our amplifier produced CSV file has a lot tagging in the CSV file, but cannot be read out by the ov2mat function. This ov2mat could not seperate the stimuli information.
I am very very confused.
Thanks a lot !