OpenVibe acquisition server /dev/ttyUSB0 "could not open"

ayushmhayushmh
edited June 2016 in Software
in OpenVibe SAS (signal acquisition server) after setting everything
according to the tutorial, when I clicked on the connect button it does
nothing and error shown in the terminal is [ ERROR ] Could not open port [/dev/ttyUSB0]
[ ERROR ] Connection failed...
[  INF  ] Disconnecting.

the same problem i was facing with openbcigui processing code
but now I'm able to run OpenBCI_GUI processing
IDK what is this 

Comments

  • wjcroftwjcroft Mount Shasta, CA
    Did you try "chmod 666 /dev/ttyUSB0" ?

    It looks like a permissions problem. This is your own laptop, no need to be concerned about the 666 permissions being a security issue.

  • ayushmhayushmh
    chmod: cannot access ‘/dev/ttyUSB0’: No such file or directory

    this is the outcome whenever i try to do this
  • wjcroftwjcroft Mount Shasta, CA
    Assuming your dongle is plugged in when you do the chmod. Are you sure you have the latest FTDI drivers?
    Try:
    ls -l /dev/tty*
    sudo chmod 666 /dev/ttyUSB0
    [or whatever the dongle shows up as, could be a different number]

    You seem to be able to access /dev/ttyUSB0 with OpenBCI_GUI. What is different with OpenViBE?

  • ayushmhayushmh
    updated FTDI driver
    did what you suggested me to do but still terminal says :
    [  INF  ] Loading plugin: ExternalStimulations (deprecated)
    [  INF  ] Loading plugin: TCP Tagging
    [  INF  ] Loading plugin: LSL Output
    [  INF  ] Connecting to device [OpenBCI]...
    [  INF  ] NO daisy module attached, 11 channels -- 8 EEG and 3 accelerometer -- at 250Hz.
    [ ERROR ] Could not open port [/dev/ttyUSB0]
    [ ERROR ] Connection failed...
    [  INF  ] Disconnecting.
    :/

  • ayushmhayushmh
    @wjcroft Mr.croft I know you''re a busy man but please I've got a deadline to complete please help me to solve this problem so I can take it further to have proper speller working
    Thank you for understanding and helping me out
  • wjcroftwjcroft Mount Shasta, CA
    edited June 2016
    @ayushmh, OpenViBE and our tutorial worked fine for me on Ubuntu 14.04, running under VirtualBox, OS X. You can use the 'dmesg' command to see how the usb device is being attached, my output was:

    $ dmesg
    ...
    [  211.095034] usb 2-1: new full-speed USB device number 2 using ohci-pci
    [  211.773568] usb 2-1: New USB device found, idVendor=0403, idProduct=6015
    [  211.773572] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [  211.773574] usb 2-1: Product: FT231X USB UART
    [  211.773575] usb 2-1: Manufacturer: FTDI
    [  211.773577] usb 2-1: SerialNumber: DN009500
    [  212.294158] usbcore: registered new interface driver usbserial
    [  212.295049] usbcore: registered new interface driver usbserial_generic
    [  212.295326] usbserial: USB Serial support registered for generic
    [  212.309762] usbcore: registered new interface driver ftdi_sio
    [  212.311282] usbserial: USB Serial support registered for FTDI USB Serial Device
    [  212.311413] ftdi_sio 2-1:1.0: FTDI USB Serial Device converter detected
    [  212.311469] usb 2-1: Detected FT-X
    [  212.327602] usb 2-1: FTDI USB Serial Device converter now attached to ttyUSB0
    ...
    [ 2588.252652] usb 2-1: USB disconnect, device number 2
    [ 2588.253094] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
    [ 2588.253119] ftdi_sio 2-1:1.0: device disconnected

    Note that the built-in Ubuntu FTDI driver works fine, no need to use the one on the FTDI site. And you probably should not use that because it is much older than 2014. This program may be helpful for debugging your /dev/ttyUSB0 port. It is a serial terminal port tool. Uses an arcane tty control character based interface, but it works.


  • ayushmhayushmh
    oh thank you very much Mr.croft @wjcroft terminal shows my device is successfully connected now
    do I've to follow Jeremy's blog for electrode placement and which scenario should i select p300 speller or p300 speller xDawn
  • wjcroftwjcroft Mount Shasta, CA
    Jeremy as mentioned in his tutorial used the CoAdapt version. You may need to tweek some of the source code, the Inria page mentions it runs on OpenViBE 0.18. Current release from Inria download page is 1.2.

    http://openvibe.inria.fr/coadapt-p300-stimulator-tutorial/

    http://blog.jfrey.info/2015/02/04/openbci-p300-coadapt/


  • ayushmhayushmh
    I followed jremy's blog till the Calibration but I'm stuck on this step :
    launch dist/openvibe-coadapt-p300-stimulator.sh. When you are ready to proceed, press the s key on the keyboard. Watch for the letters until the session ends.


    I don't know what to do further and I wanted to ask if I should try running this much and if yes then how
    thank you Mr.Croft
    @wjcroft
  • ayushmhayushmh
    ummm....help anyone please
Sign In or Register to comment.

© Vanilla Keystone Theme 2026