OpenViBE forum

Hi There...
i am using this V3 OpenBCI 32 bit board 8 channels with OpenViBE 1.2.2 which is stable now with the board. but the acquisition server isn't recognizing the board and gives 0 Host Connected. I've done the FTD driver settings described here and on openBCI page but the problem remains the same. I would like to request help on the matter Please.
Following are the errors i receive during acquisition phase...

[ INF ] OpenBCI: Successfully opened port [\\.\COM4]
[ INF ] OpenBCI: Stopping board streaming...
[ INF ] OpenBCI: Soft reseting of the board...
[ INF ] OpenBCI: Starting stream...
[ INF ] OpenBCI: Status ready (initialization took 1681ms)
[ INF ] Connection succeeded !
[WARNING] No response for 1000ms, will try recovery now (Note this may eventuall
y be hopeless as the board may not reply to any command either).
[ INF ] OpenBCI: Stopping board streaming...
[ INF ] OpenBCI: Starting stream...
[ INF ] OpenBCI: Status ready (initialization took 604ms)
[WARNING] No response for 1000ms, will try recovery now (Note this may eventuall
y be hopeless as the board may not reply to any command either).
[ INF ] OpenBCI: Stopping board streaming...
[ INF ] OpenBCI: Starting stream...
[ INF ] OpenBCI: Status ready (initialization took 604ms)
[WARNING] No response for 1000ms, will try recovery now (Note this may eventuall
y be hopeless as the board may not reply to any command either).
[ INF ] OpenBCI: Stopping board streaming...
[ INF ] OpenBCI: Starting stream...
[ INF ] OpenBCI: Status ready (initialization took 604ms)
[WARNING] No response for 1000ms, will try recovery now (Note this may eventuall
y be hopeless as the board may not reply to any command either).
[ INF ] OpenBCI: Stopping board streaming...
[ INF ] OpenBCI: Starting stream...
[ INF ] OpenBCI: Status ready (initialization took 604ms)
[ INF ] Disconnecting.
----------------------------------------------------------------------------------------------------------------------------------
[ INF ] Connecting to device [OpenBCI]...
[ INF ] OpenBCI: Configured 'missing sample delay before reset' to 1000 ; this
can be changed in the openvibe configuration file setting the AcquisitionDriver
_OpenBCI_MissingSampleDelayBeforeReset token
[ INF ] OpenBCI: Configured 'dropped sample count before reset' to 5 ; this ca
n be changed in the openvibe configuration file setting the AcquisitionDriver_Op
enBCI_DroppedSampleSafetyDelayBeforeReset token
[ INF ] OpenBCI: Configured 'dropped sample safety delay before reset' to 1000
; this can be changed in the openvibe configuration file setting the Acquisitio
nDriver_OpenBCI_DroppedSampleSafetyDelayBeforeReset token

hello hassansyed46

we are facing the same problem with OpenBCI Cython Board 32 bit 8 channel.

and we haven't found any solution anywhere and the post was posted by you was seem the only solution. But no reply found yet.

If you had found any solution to overcome then, please help us too.

thanks and regards

Hi, everyone ...

I am using this OpenBCI 32 bit Cyton board 8 channels with OpenViBE 1.3 which is stable now with the board. but the acquisition server isn't recognizing the board and gives 0 Host Connected. I've done the FTD driver settings described here and on the openBCI page but the problem remains the same.
we did all the process described in the documentation of openbci and openvibe

Following are the errors I receive during acquisition phase...




[ INF ] OpenBCI: Successfully opened port [\\.\COM4]
[ INF ] OpenBCI: Stopping board streaming...
[ INF ] OpenBCI: Soft reseting of the board...
[ INF ] OpenBCI: Starting stream...
[ INF ] OpenBCI: Status ready (initialization took 1681ms)
[ INF ] Connection succeeded !
[WARNING] No response for 1000ms, will try recovery now (Note this may eventuall
y be hopeless as the board may not reply to any command either).
[ INF ] OpenBCI: Stopping board streaming...
[ INF ] OpenBCI: Starting stream...
[ INF ] OpenBCI: Status ready (initialization took 604ms)
[WARNING] No response for 1000ms, will try recovery now (Note this may eventuall
y be hopeless as the board may not reply to any command either).
[ INF ] OpenBCI: Stopping board streaming...
[ INF ] OpenBCI: Starting stream...
[ INF ] OpenBCI: Status ready (initialization took 604ms)
[WARNING] No response for 1000ms, will try recovery now (Note this may eventuall
y be hopeless as the board may not reply to any command either).
[ INF ] OpenBCI: Stopping board streaming...
[ INF ] OpenBCI: Starting stream...
[ INF ] OpenBCI: Status ready (initialization took 604ms)
[WARNING] No response for 1000ms, will try recovery now (Note this may eventuall
y be hopeless as the board may not reply to any command either).
[ INF ] OpenBCI: Stopping board streaming...
[ INF ] OpenBCI: Starting stream...
[ INF ] OpenBCI: Status ready (initialization took 604ms)
[ INF ] Disconnecting.
----------------------------------------------------------------------------------------------------------------------------------
[ INF ] Connecting to device [OpenBCI]...
[ INF ] OpenBCI: Configured 'missing sample delay before reset' to 1000 ; this
can be changed in the openvibe configuration file setting the AcquisitionDriver
_OpenBCI_MissingSampleDelayBeforeReset token
[ INF ] OpenBCI: Configured 'dropped sample count before reset' to 5 ; this ca
n be changed in the openvibe configuration file setting the AcquisitionDriver_Op
enBCI_DroppedSampleSafetyDelayBeforeReset token
[ INF ] OpenBCI: Configured 'dropped sample safety delay before reset' to 1000
; this can be changed in the openvibe configuration file setting the Acquisitio
nDriver_OpenBCI_DroppedSampleSafetyDelayBeforeReset token

Seems some users have got the Cyton to work, its mentioned e.g. here,

viewtopic.php?f=13&t=9729&p=15044#p15005

Please see also this suggestion from soultranscender (thanks a lot!),

viewtopic.php?f=5&t=9731#p15035

ps. merged post with a similar topic.

Cheers,
Jussi

hello jussi

We have tried your suggestion but still problem persists.

We have tried in different system as well as in different version of windows but error is same everywhere.

I think we are neglecting an important point which is not discussed in openbci forum as well as in openvibe forum.

I think it'd be a good idea to take the subject up on the OpenBCI forum as well if you haven't done that already; here we know openvibe, but openbci hardware and the driver is probably much better known to the openbci community.


My three cents,
Jussi