Acquire 4.5

[azurex]

Where do I start the acquire server? Is that just the principal acquire application or is there something else I should be running?

[azurex]

Answered my own question

Cliking on the S in the upper right hand corner

[azurex]

Ok now for a real question. I got the param file, but I can't seem to get BCI2000 to sync with the acquire server. I've tested both 4.5 and 4.4, but both versions give me the same error, namely can't connect to driver check dongle. Additionally I get errors about the transmitted channels not being valid channel specification, but I assume this is related to the original failure.

Here are the possibilities:
A) I'm running the NuAmps device dry, so the communication doesn't work with zeroed channels
B) NuAmp is not the same thing as SynAmps2 so the selected device isn't even compatible and I'll have to switch to the wireless version
C) neuroscan.exe is only compatible with 4.3.1 which isn't available on the public ftp anymore
D) I'm doing something wrong, it happens

Any thoughts?

[mellinger]

Hi,

when Acquire reports "cannot connect to driver", this is unrelated to BCI2000. Once you can see EEG data from your device in the Acquire window, you can work on connecting to BCI2000 as described on the wiki:
http://www.bci2000.org/wiki/index.php/C ... uroscanADC

HTH,
Juergen

[azurex]

I have been able to read EEG data from Acquire, however the error produced in BCI2000 is the same error that appears when Acquire is closed and no device is attached. Therefore I think that this particular message is related to the neuroscan.exe not behaving/communicating properly. When I do run acquire I am using port 3999, but the same error is still reported.

[mellinger]

So, what error does BCI2000 display then? Is it: "Could not connect to server at the provided address. Make sure Acquire is running and the server is enabled at the correct port."?

[azurex]

Neuroscan.exe reports "cannot connect to driver/ dongle". This occurs when only BCI2000 is open and the acquisition device is not connected, as well as when the neuroscan device is connected, and the Acquire server is running. Neurogetparams operates as specified however. I have never received an error regarding the port or connection to the acquire server.

I am talking to Neuroscan support at the same time. There have been updates to the Neuroscan.exe file that are not documented in the wiki. Neuroscan is telling me to use the Access SDK to communicate instead of Acquire. The wiki documentation mentions identifying "localhost:3999" for example, but this is no longer a parameter in the source module, instead only the option of device type (Synamp2/Wireless) is offered. It looks like the current version does not attempt to communicate with acquire and additionally has support for the Nuamps system removed entirely. Is there a previous version of the neuroscan.exe file that I could access?

Edit: Also Neuroscan support says that data is transmitted regardless of subject connectivity.

[mellinger]

Ah, you are using the NeuroscanAccessSDK source module rather than the NeuroscanClient module. I did not understand that previously. I guess you cannot run Acquire and the NeuroscanAccessSDK source module at the same time then.
Wiki documentation for the NeuroscanAccessSDK source module is available at:
http://www.bci2000.org/wiki/index.php/C ... nAccessSDK

If you want to use a device that is not supported by the NeuroscanAccessSDK module, you should switch to the NeuroscanClient source module, which connects to Acquire over TCP/IP, and thus connects to any amplifier supported by Acquire. Wiki documentation for the NeuroscanClient source module is available at:
http://www.bci2000.org/wiki/index.php/C ... uroscanADC

[azurex]

It looks like that fixed my issue, thanks.
Had to change Neuroscan.exe to neuroscanclient.exe in my code.

I think the wiki should be changed from
"The BCI2000-compatible Source Module Neuroscan.exe can be used instead of any other source module."
to "The BCI2000-compatible Source Module NeuroscanClient.exe can be used instead of any other source module."

And mention that older versions of neuroscanclient.exe were named neuroscan instead of mentioning that newer verisons instead of making continual reference to neuroscan.exe

[mellinger]

Thanks for pointing me to the remaining references of Neuroscan.exe.

[azurex]

Thanks for helping me get to the bottom of this