Mitsar 201 with OpenViBE?
-
- Posts: 2
- Joined: Sat Jan 22, 2011 8:48 pm
Mitsar 201 with OpenViBE?
I noticed that a driver was recently provided for the Mitsar 202 amp. Can anyone tell me if this driver should also work for a Mitsar 201 amp (which has fewer channels than the 202)? Thanks, Jordan
Re: Mitsar 201 with OpenViBE?
Hi folks,
I have the same question as Jordan. I would really like to use OpenViBE for independent component neurofeedback using the facility to apply a spatial filter to the signal. I know that this is possible, in general, but I don't know if it can be done with my Mitsar 201. I have tried using the Mitsar 202 driver kindly supplied by the OpenViBE community (the 202 has more channels than the 201).
Using the Mitsar 202 driver when I connect using the Acquisition Server it tells me I have succeeded. Since I do not get this success message when I try to connect to other amps which I do not have, I take it that this is a real sign that the software is recognising my amplifier. However when I press play, the message 'DLL start WRONG' and then 'ERROR Starting failed!'
I can't see how to go forward from here. Can anyone offer any suggestions? Am I missing something, or do you think that this is a problem with amplifier
compatibility? If so, is there any chance that the 202 driver could be modified for use with the 19-channel model 201?
Thank you for reading this.
Russell
I have the same question as Jordan. I would really like to use OpenViBE for independent component neurofeedback using the facility to apply a spatial filter to the signal. I know that this is possible, in general, but I don't know if it can be done with my Mitsar 201. I have tried using the Mitsar 202 driver kindly supplied by the OpenViBE community (the 202 has more channels than the 201).
Using the Mitsar 202 driver when I connect using the Acquisition Server it tells me I have succeeded. Since I do not get this success message when I try to connect to other amps which I do not have, I take it that this is a real sign that the software is recognising my amplifier. However when I press play, the message 'DLL start WRONG' and then 'ERROR Starting failed!'
I can't see how to go forward from here. Can anyone offer any suggestions? Am I missing something, or do you think that this is a problem with amplifier
compatibility? If so, is there any chance that the 202 driver could be modified for use with the 19-channel model 201?
Thank you for reading this.
Russell
Re: Mitsar 201 with OpenViBE?
Hi again,
Further to my previous message, here are some more details.
When the Acquisition Server fails, I get the following lines of error code in separate, consecutively opening dialogue boxes :
Mitsardll: HAL error: sending code -1 for 10
Mitsardll: HAL error: sending code -1 for 11
Mitsardll: HAL error: sending code -1 for 152
Mitsardll: HAL error: sending code -1 for 153
Mitsardll: HAL error: sending code -1 for 154
Mitsardll: HAL error: sending code -1 for 155
Mitsardll: HAL error: sending code -1 for 156
Mitsardll: HAL error: sending code -1 for 157
Mitsardll: HAL error: sending code -1 for 158
Mitsardll: HAL error: sending code -1 for 159
Mitsardll: HAL error: sending code -1 for 160
Mitsardll: HAL error: sending code -1 for 161
MD: Error Start failed
I also have the following messages prior to the failure:
[ INF ] Created kernel loader, trying to load kernel module
[ INF ] Kernel module loaded, trying to get kernel descriptor
[ INF ] Got kernel descriptor, trying to create kernel
[ INF ] Adding [../bin/OpenViBE-plugins-*.dll]
[ INF ] Added 2 plugin object descriptor(s) from [../bin/OpenViBE-plugins-acqu
isition-dynamic.dll]
[ INF ] Added 6 plugin object descriptor(s) from [../bin/OpenViBE-plugins-clas
sification-dynamic.dll]
[ INF ] Added 1 plugin object descriptor(s) from [../bin/OpenViBE-plugins-clas
sification-gpl-dynamic.dll]
[ INF ] Added 1 plugin object descriptor(s) from [../bin/OpenViBE-plugins-feat
ure-extraction-dynamic.dll]
[ INF ] Added 17 plugin object descriptor(s) from [../bin/OpenViBE-plugins-fil
e-io-dynamic.dll]
[ INF ] Added 2 plugin object descriptor(s) from [../bin/OpenViBE-plugins-matl
ab-dynamic.dll]
[WARNING] No 'plugin object descriptor' found from [../bin/OpenViBE-plugins-pyth
on-dynamic.dll] even if it looked like a plugin module
[ INF ] Added 9 plugin object descriptor(s) from [../bin/OpenViBE-plugins-samp
les-dynamic.dll]
[ INF ] Added 29 plugin object descriptor(s) from [../bin/OpenViBE-plugins-sig
nal-processing-dynamic.dll]
[ INF ] Added 22 plugin object descriptor(s) from [../bin/OpenViBE-plugins-sig
nal-processing-gpl-dynamic.dll]
[ INF ] Added 17 plugin object descriptor(s) from [../bin/OpenViBE-plugins-sim
ple-visualisation-dynamic.dll]
[ INF ] Added 12 plugin object descriptor(s) from [../bin/OpenViBE-plugins-sti
mulation-dynamic.dll]
[ INF ] Added 19 plugin object descriptor(s) from [../bin/OpenViBE-plugins-str
eam-codecs-dynamic.dll]
[ INF ] Added 3 plugin object descriptor(s) from [../bin/OpenViBE-plugins-stre
aming-dynamic.dll]
[ INF ] Added 4 plugin object descriptor(s) from [../bin/OpenViBE-plugins-tool
s-dynamic.dll]
[ INF ] Added 4 plugin object descriptor(s) from [../bin/OpenViBE-plugins-vrpn
-dynamic.dll]
[WARNING] Registery key Software\VB and VBA Program Settings\Brain Quick - Syste
m 98\EEG_Settings is not initialized
[ INF ] Connecting to device [Mitsar EEG 202 - A]...
[ INF ] Connection succeeded !
Is there anything I can do to use this driver? If not, can anyone see how it could be modified to work with the 201?
This model is widely used here in Australia, so if a driver could be made to work, it would potentially benefit many people, especially since there are many applications for which OpenViBE appears to have considerable advantages, for example, independent component neurofeedback.
Please help if you can. Thank you. -- Russell
Further to my previous message, here are some more details.
When the Acquisition Server fails, I get the following lines of error code in separate, consecutively opening dialogue boxes :
Mitsardll: HAL error: sending code -1 for 10
Mitsardll: HAL error: sending code -1 for 11
Mitsardll: HAL error: sending code -1 for 152
Mitsardll: HAL error: sending code -1 for 153
Mitsardll: HAL error: sending code -1 for 154
Mitsardll: HAL error: sending code -1 for 155
Mitsardll: HAL error: sending code -1 for 156
Mitsardll: HAL error: sending code -1 for 157
Mitsardll: HAL error: sending code -1 for 158
Mitsardll: HAL error: sending code -1 for 159
Mitsardll: HAL error: sending code -1 for 160
Mitsardll: HAL error: sending code -1 for 161
MD: Error Start failed
I also have the following messages prior to the failure:
[ INF ] Created kernel loader, trying to load kernel module
[ INF ] Kernel module loaded, trying to get kernel descriptor
[ INF ] Got kernel descriptor, trying to create kernel
[ INF ] Adding [../bin/OpenViBE-plugins-*.dll]
[ INF ] Added 2 plugin object descriptor(s) from [../bin/OpenViBE-plugins-acqu
isition-dynamic.dll]
[ INF ] Added 6 plugin object descriptor(s) from [../bin/OpenViBE-plugins-clas
sification-dynamic.dll]
[ INF ] Added 1 plugin object descriptor(s) from [../bin/OpenViBE-plugins-clas
sification-gpl-dynamic.dll]
[ INF ] Added 1 plugin object descriptor(s) from [../bin/OpenViBE-plugins-feat
ure-extraction-dynamic.dll]
[ INF ] Added 17 plugin object descriptor(s) from [../bin/OpenViBE-plugins-fil
e-io-dynamic.dll]
[ INF ] Added 2 plugin object descriptor(s) from [../bin/OpenViBE-plugins-matl
ab-dynamic.dll]
[WARNING] No 'plugin object descriptor' found from [../bin/OpenViBE-plugins-pyth
on-dynamic.dll] even if it looked like a plugin module
[ INF ] Added 9 plugin object descriptor(s) from [../bin/OpenViBE-plugins-samp
les-dynamic.dll]
[ INF ] Added 29 plugin object descriptor(s) from [../bin/OpenViBE-plugins-sig
nal-processing-dynamic.dll]
[ INF ] Added 22 plugin object descriptor(s) from [../bin/OpenViBE-plugins-sig
nal-processing-gpl-dynamic.dll]
[ INF ] Added 17 plugin object descriptor(s) from [../bin/OpenViBE-plugins-sim
ple-visualisation-dynamic.dll]
[ INF ] Added 12 plugin object descriptor(s) from [../bin/OpenViBE-plugins-sti
mulation-dynamic.dll]
[ INF ] Added 19 plugin object descriptor(s) from [../bin/OpenViBE-plugins-str
eam-codecs-dynamic.dll]
[ INF ] Added 3 plugin object descriptor(s) from [../bin/OpenViBE-plugins-stre
aming-dynamic.dll]
[ INF ] Added 4 plugin object descriptor(s) from [../bin/OpenViBE-plugins-tool
s-dynamic.dll]
[ INF ] Added 4 plugin object descriptor(s) from [../bin/OpenViBE-plugins-vrpn
-dynamic.dll]
[WARNING] Registery key Software\VB and VBA Program Settings\Brain Quick - Syste
m 98\EEG_Settings is not initialized
[ INF ] Connecting to device [Mitsar EEG 202 - A]...
[ INF ] Connection succeeded !
Is there anything I can do to use this driver? If not, can anyone see how it could be modified to work with the 201?
This model is widely used here in Australia, so if a driver could be made to work, it would potentially benefit many people, especially since there are many applications for which OpenViBE appears to have considerable advantages, for example, independent component neurofeedback.
Please help if you can. Thank you. -- Russell
Re: Mitsar 201 with OpenViBE?
Hello Russell,
not having the device or the SDK there is not much we can do here. Would it be possible for you to find somebody having the device and the means to write the driver for openvibe? We would gladly include it in our distribution after that.
Regards
Jozef
not having the device or the SDK there is not much we can do here. Would it be possible for you to find somebody having the device and the means to write the driver for openvibe? We would gladly include it in our distribution after that.
Regards
Jozef
-
- Posts: 775
- Joined: Tue Dec 04, 2012 3:53 pm
- Location: INRIA Rennes, FRANCE
Re: Mitsar 201 with OpenViBE?
There is Mitsar EEG 202 driver integrated to 0.17.1. As the OpenViBE core team does not have the device, I cannot confirm that it works. If the driver is to be extended for 201, this coding effort should be done by someone who has access to both the device and the SDK.
Happy hacking,
Jussi
Happy hacking,
Jussi