Problem starting OpenBCI_GUI in Ubuntu 18.10

Hi,

I've got a problem that I need help
figuring out a solution to. Whenever I start OpenBCI_GUI in Ubuntu 18.10
I get connection exception, see below. In the team we have seen it on 2
computers of different brands, and haven't been able to solve it for
any of them.

What is working:
- The Gui starts, and shows the Data source menu.
- When selecting Synthetic everything looks good, and I get data in the selected amount of channels

What isn't working as expected:
-
When I select Data source "LIVE (from Ganglion)" I expect a menu to
choose either wifi or bluetooth, the menu doesn't show up. If I try to
start the system nothing happens, neither in the gui nor in the logs.
- When I start OpenBCI_GUI I get logs about ConnectionException, the full log is included below.

What have been tested:
- Start with and without USB dongle
- Start as sudo and without sudo
- 2 computers from different manufacturers
-
Changing to windows on one of the computers worked. However the other
one doesn't have windows, and it haven't been tried on the other
computer

Can you please help me figure out what I'm doing wrong?

sudo ./OpenBCI_GUI 
[sudo] password for krister:
Screen Resolution: 1920 X 1080
Welcome to the Processing-based OpenBCI GUI!
For more information about how to work with this code base, please visit: http://docs.openbci.com/OpenBCI Software/
Launching application from local data dir
OpenBCI_GUI: hubStart: OS Detected: Linux
Local Version: 410, Latest Version: 410
GUI is up to date!
Graphics & GUI Library: ControlP5 2.2.6 infos, comments, questions at http://www.sojamo.de/libraries/controlP5
The
file "SavedData/Settings/UserPlaybackHistory.json" is missing or
inaccessible, make sure the URL is valid or that the file has been added
to your sketch and is readable.
OpenBCI_GUI::Control Panel: Playback history file not found or other error.
attempting to load images for presentation...
DONE loading images!
OpenBCI_GUI::Setup: Is RX mulitcast: false
OpenBCI_GUI::Setup: Has RX joined multicast: false
java.net.ConnectException: Connection refused (Connection refused)
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
    at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
    at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
    at java.net.Socket.connect(Socket.java:589)
    at java.net.Socket.connect(Socket.java:538)
    at java.net.Socket.<init>(Socket.java:434)
    at java.net.Socket.<init>(Socket.java:211)
    at processing.net.Client.<init>(Unknown Source)
    at OpenBCI_GUI$Hub.startTCPClient(OpenBCI_GUI.java:13223)
    at OpenBCI_GUI$Hub.<init>(OpenBCI_GUI.java:13199)
    at OpenBCI_GUI.systemUpdate(OpenBCI_GUI.java:1213)
    at OpenBCI_GUI.draw(OpenBCI_GUI.java:605)
    at processing.core.PApplet.handleDraw(PApplet.java:2429)
    at processing.opengl.PSurfaceJOGL$DrawListener.display(PSurfaceJOGL.java:866)
    at jogamp.opengl.GLDrawableHelper.displayImpl(GLDrawableHelper.java:692)
    at jogamp.opengl.GLDrawableHelper.display(GLDrawableHelper.java:674)
    at jogamp.opengl.GLAutoDrawableBase$2.run(GLAutoDrawableBase.java:443)
    at jogamp.opengl.GLDrawableHelper.invokeGLImpl(GLDrawableHelper.java:1293)
    at jogamp.opengl.GLDrawableHelper.invokeGL(GLDrawableHelper.java:1147)
    at com.jogamp.newt.opengl.GLWindow.display(GLWindow.java:759)
    at com.jogamp.opengl.util.AWTAnimatorImpl.display(AWTAnimatorImpl.java:81)
    at com.jogamp.opengl.util.AnimatorBase.display(AnimatorBase.java:452)
    at com.jogamp.opengl.util.FPSAnimator$MainTask.run(FPSAnimator.java:178)
    at java.util.TimerThread.mainLoop(Timer.java:555)
    at java.util.TimerThread.run(Timer.java:505)
Instantiating hub object...

Comments

  • wjcroftwjcroft Mount Shasta, CA
    Krister, hi.

    You mentioned using with a USB dongle, which one, CSR (old type), or BLED112 (new type). The BLED112 will give best results, it only uses a serial port.

    Have you tried running the GUI from Processing IDE?

  • Hi William,

    I've tried to figure out what
    dongle it is, but I can't manage to figure it out. But I don't think
    it's relevant, I don't get far enough in OpenBCI_GUI to be able to
    choose how to connect.

    I tried to run it through Processing IDE, but with the same result. I can't find any differences in the log.

    I
    also tried to install a virtualbox image with Ubuntu 16.04, when using
    that I can open the OpenBCI_GUI and get the menu to choose how I want to
    connect to the Ganglion.

    I would be happy for any help getting further.
  • wjcroftwjcroft Mount Shasta, CA
    Please verify that you have the BLED112 dongle. The photo in the shop shows what this looks like. In small print on the connector it says BLED112.

    image



    If you do not have this exact dongle, then you have the older CSR dongle, which has been problematic because there are so many variations of the hardware manufacturers. The BLED112 is made by only ONE manufacturer with excellent quality control. BLED112 connects via a serial port, which is also the simplest way to get bluetooth access. The other CSR type dongles connect as bluetooth radio devices. Finally, the built in bluetooth in computers can also be problematic because of manufacturer variations.

    Regards,

  • wjcroftwjcroft Mount Shasta, CA
    If you are in Sweden, then the BLED112 can likely be ordered faster through a distributor in your country, see,

  • I've validate that it's the BLED112 dongle. And I've tried 2 different ones, both gave the same error.

    I checked OpenGL and the graphics as well. It's running "OpenGL version string: 4.6.0 NVIDIA 390.116", which is the latest recommended one if not the absolutely latest.
  • wjcroftwjcroft Mount Shasta, CA
    The base error appears to be:

    "java.net.ConnectException: Connection refused (Connection refused)"

    Where the GUI is trying to start and communicate with the Hub. "Connection refused" implies some kind of permissions problem.

    Have you tried installing separately the Hub and starting it as root?



    The fact that you can run ok on Windows, means that this is some kind of glitch with your Linux setup.
  • The problem was that drivers was missing. Installing arduino solved those problems:
    sudo apt-get install arduino
    This solves the problem for both wifi and USB dongle BLED112.
Sign In or Register to comment.