OpenBCI GUI linux64 needs jssc.jar update

edited August 2016 in OpenBCI_GUI
Hi

I just received the 32-bits board, thank you. I'm trying to get it to work for the first time (on Ubuntu 14.04.1, linux64) and followed the tutorial. I already saw that on 32bit, the led should not blink, so that should be ok, but after the step click on « start system » the GUI seems to freeze displaying
« openBCI: openNewLogFile: opened output file: (filename) »
In the tutorial, it is said « During this time, the help line at the bottom of the OpenBCI GUI should be blinking the words: “Initializing communication w/ your OpenBCI board.” »
Does this step « Initializing communication » should happen before or after the logfile creation ?

Thanks in advance.

PS here is the output :

port is open? ... false
-- Init 0 --
Preparing data variables...
-- Init 1 --
a--0
a--1
a--2
a--3
a--4
a--5
a--6
a--7
b
-- Init 2 --
OpenBCI_ADS1299: prefered_datamode = 1, nValuesPerPacket = 8
 a
 b
port is open? ... false
 i
OpenBCI_ADS1299: attempting to open serial port /dev/ttyUSB0
 j
-- Init 3 --
1
2
Buttons: 81, 66
creating channel setting buttons...
3
4
5
6
-- Init 4 --
openBCI: openNewLogFile: opened output file: SavedData\OpenBCI-RAW-2014-12-15_21-32-02.txt
attempting

Comments

  • wjcroftwjcroft Mount Shasta, CA
    edited May 2015
    Gwym, hi.

    Another user, Kevin @keturn , has gotten the board to work with Linux. If you click on his name here, you can then use the [Message] button to send him a private message. Here is the comment when he mentioned Linux is working.

    http://openbci.com/forum/index.php?p=/discussion/comment/1024/#Comment_1024

    William

  • Thank you for your answer, I could finally solve my issue :

    program fails silently at line 5757
    ( catch (RuntimeException e){
          if (e.getMessage().contains("<init>")) {
            System.out.println("port in use, trying again later...");
            portIsOpen = false;
          }
          return 0;
        })
    as other exceptions are not closing the port

    using directly it with processing/eclise, I got an "java.lang.UnsatisfiedLinkError"

    I use the FTDI drivers installed by default in my linux distribution, and it seems something is out of date in the jssc.jar. (cf. https://github.com/processing/processing/issues/2559)
    I downloaded the last version from https://code.google.com/p/java-simple-serial-connector/downloads/list, replaced jssc.jar with the last version and all is working well. :)
  • Glad to hear you've got it going!
  • brainbrain Canada
    edited December 2014
    @Gwym I just encountered the exact issue you describe. However, when I replaced jssc.jar with version 2.6.0 (also tried a few others) from the link you gave, the only difference was that the list of serial/com ports no longer showed anything. Normally /dev/ttyUSB0 appears when I plug in my dongle (along with a list of other ports that don’t change), both when I tried running the stock Linux app and when I’m running the Github master with Processing, but it never starts the data stream. I have the 23bit ChipKIT board.

    Can you provide any more details about your fix?

    Thanks!
  • I had this behaviour too, only the active ports are listed by the jssc driver, instead of the whole list.
    Did you add yourself (i.e. the user who is launching the program) to the dialout group to allow use of serial ports (sudo adduser user dialout) ?

    I can not think of any other idea for now, and I'm not any more using this solution, as I am using my own driver and software I made in javascript to get the data in a webrowser way (using serial api https://developer.chrome.com/apps/serial)
  • brainbrain Canada
    edited December 2014
    @Gwym

    Thanks! I don’t know why I didn’t think of running it as root — it’s like the first rule of photography: take off the lens cap. Adding myself to the dialout group didn’t work, but running it as root isn’t too much trouble.

    BCI.js looks like a great project. I’m watching it on GitHub to keep up with development.

    Omphalosskeptic
  • For anyone else who has this problem, I wrote up the steps that worked for me here:

    http://www.autodidacts.io/getting-started-with-openbci-a-tutorial-on-testing-troubleshooting-and-recording-ekg/#gettingtheopenbcisoftwareworkingonlinux

    Cheers,
    Omphalosskeptic
Sign In or Register to comment.