No signal from g.USBamp anymore
Posted: Thu Nov 27, 2014 10:24 pm
Hello everyone,
we're currently facing problems with receiving a signal in OpenVibe and running out of ideas of how to solve them.
We use OpenVibe on two different computer systems (Windows 7 and Windows 8.1) and our acquisition device is g.USBamp (drivers: g.USBamp_Driver_3.12.00_Win32 and g.USBamp_Driver_3.12.00_Win64).
For several weeks we didn’t have any problems with displaying EEG signals in OpenVibe. Last week we had a minor issue with the 16-channel g.GAMMAbox, which was fixed simply through recalibration. Since then, however, the signal display in OpenVibe looks like this:
![Image](http://s28.postimg.org/xdaijsdf1/signal.jpg)
These are our settings for the acquisition server:
![Image](http://s3.postimg.org/be6za93f7/acser.jpg)
Which OpenVibe scenarios we use - be it signal monitoring for motor imagery (picture above) or the simplest case of "Acquisition client" connected to "Signal display" - makes no difference either. It's also not a matter of scaling: Best Fit vs. manual scaling changes nothing. Nor does auto-calibration help.
Further indicators that something is wrong are (1) that the device drift is higher than it was on the weeks before (when we had no problems with the signal), i.e., it now fluctuates between 0 and -4ms, and (2) that whenever the button "Disconnect" is pressed in the acquisition sever, the amplifier and gammabox have to be powered off and on before reconnection, otherwise the impedance check will show 0.00k ohms for all channels.
It doesn't seem to be a hardware problem because we've tried two functioning g.GAMMAboxes, and other signal display software (g.Recorder) shows a perfectly normal signal!
However, it also doesn't seem to be a software problem because we haven't changed anything in the software since when it was still working, and after trying various solutions in vain, we reinstalled and recompiled the entire OpenVibe platform on one computer as well as the g.USBamp driver, but this made no difference either.
Do you have any further ideas for getting a proper EEG signal?
Thanks,
Dominic
we're currently facing problems with receiving a signal in OpenVibe and running out of ideas of how to solve them.
We use OpenVibe on two different computer systems (Windows 7 and Windows 8.1) and our acquisition device is g.USBamp (drivers: g.USBamp_Driver_3.12.00_Win32 and g.USBamp_Driver_3.12.00_Win64).
For several weeks we didn’t have any problems with displaying EEG signals in OpenVibe. Last week we had a minor issue with the 16-channel g.GAMMAbox, which was fixed simply through recalibration. Since then, however, the signal display in OpenVibe looks like this:
![Image](http://s28.postimg.org/xdaijsdf1/signal.jpg)
These are our settings for the acquisition server:
![Image](http://s3.postimg.org/be6za93f7/acser.jpg)
Which OpenVibe scenarios we use - be it signal monitoring for motor imagery (picture above) or the simplest case of "Acquisition client" connected to "Signal display" - makes no difference either. It's also not a matter of scaling: Best Fit vs. manual scaling changes nothing. Nor does auto-calibration help.
Further indicators that something is wrong are (1) that the device drift is higher than it was on the weeks before (when we had no problems with the signal), i.e., it now fluctuates between 0 and -4ms, and (2) that whenever the button "Disconnect" is pressed in the acquisition sever, the amplifier and gammabox have to be powered off and on before reconnection, otherwise the impedance check will show 0.00k ohms for all channels.
It doesn't seem to be a hardware problem because we've tried two functioning g.GAMMAboxes, and other signal display software (g.Recorder) shows a perfectly normal signal!
However, it also doesn't seem to be a software problem because we haven't changed anything in the software since when it was still working, and after trying various solutions in vain, we reinstalled and recompiled the entire OpenVibe platform on one computer as well as the g.USBamp driver, but this made no difference either.
Do you have any further ideas for getting a proper EEG signal?
Thanks,
Dominic