Cyton working with old OpenBCI_GUI, but not with recent OpenBCI_GUI (v2.1.2)

After some while of not using Cyton I recently updated the dongle driver (FTDI version 2.12.26.0) and the OpenBCI_GUI (v2.1.2). I followed carefully the instruction (Cyton Getting Started Guide) but Cyton was not connecting. I lost a lot of time searching my error, reinstalling drivers, searching the registry (W7), even learning some git... I tried the "OpenBCI Radio Configuration Utility" (http://openbci.com/community/openbci-radio-configuration-utility/). Here the COM port (#37) is listed, but after selecting it, there is no reaction whether a connection could be established or not.


Finally I remembered that Cyton worked fine with the old GUI. I had to reinstall Processing 2. With the old GUI Cyton connected without problems and transmitted valuable data.
I lost hours and hours and hours. I'm exhausted. I'm interested in clinical applications, I do not want to become a nerd. 

So my questions:

What happens? Did I miss something?
Seems that the new GUI requires some update of the dongle? Or is it Cyton which needs an update? Is there any doc? Where?
What can I do?

Please give the absolute links, if you refer to the docs - there are circular or dead links in the docs, for example the link "http://docs.openbci.com/Hardware/06-Dongle_Programming_Tutorial" is circular. And "https://github.com/OpenBCI/OpenBCI_32bit_Library/blob/dev-3.0.0/UPGRADE_GUIDE" is dead.

Thanks a lot!
Will

ps
I do not see any version number in the old GUI (program title says:  "
//
// GUI for controlling the ADS1299-based OpenBCI
//
// Created: Chip Audette, Oct 2013 - May 2014
// Modified: Conor Russomanno & Joel Murphy, August 2014 - Oct 2014
//"

Comments

  • Same/similar problem here..

    I just got a cyton&daisy, all the updates software etc, and seem to
    be stuck at a no-communication dead end too -- I keep getting a failure
    to poll device/failure: system is down/etc. Like you I tried installing
    the radio config utility and all the other good stuff suggested, but
    didn't change the issue by one bit.

    Not much comfort, but maybe if two people have the same problem we can get some good help?

    cheers

    martin
  • wjcroftwjcroft Mount Shasta, CA
    @will, hi. Can you log your issue at,


    That way it will get in the queue to be examined by the devs.

    @MCube78, not sure you're dealing with the same thing. Will make some suggestions on your other thread.

    Thanks, William

  • edited June 2017
    aj-ptw gave a hint to run OpenBCI_GUI.exe as administrator. It turned out that even the installation path is important:

    My working installation path (under windows 7, running as admin) is : "C:\Program Files\OpenBCI\OpenBCI_GUI.exe".

    This solved the problem. (Perhaps one could mention this in the installation doc?)

    Thanks, wjcroft
Sign In or Register to comment.