Firmware 3.x.x -- where to download? When will guide be updated?

edited July 2017 in Cyton
Hi, I noticed a couple days ago that the cyton trigger tutorial was updated to report that now Firmware 3.x.x incorporates the code needed to receive an external trigger/marker that can be added to the output txt file (this page) . However when I follow the link to 'how to upgrade to Firmware 3.x.x' I only seem to find instructions for updating to Firmware 2.x.x (this page) and I cannot seem to find the new firmware on GitHub. Do you have a general idea when will the firmware will be available (and when will the tutorial be updated)?
cheers (and thank you for implementing this!)
Martin

Comments

  • wjcroftwjcroft Mount Shasta, CA
    Mentioning AJ Keller @pushtheworld, the firmware dev and guru. Also Joel @biomurph.

  • edited July 2017
    thank you @pushtheworld

    I downloaded the library and (I think) I
    successfully uploaded the default_board firmware as said in the guide.
    When I launch the GUI from Processing I can see a response to when I
    type commands like '~5' and ':' in the debug window (even if numeric
    commands like ~5 also power off the connected channel [i.e., #5 in the
    example]..) so I take this to imply I successfully updated to the 3.0.0
    firmware? However, when I type '/0' or any of the other '/' command so
    to change the mode and allow a trigger input nothing happens and the
    debug window doesn't really react, so I am uncertain how to check if it
    is working. I tried connecting my trigger output to pin D17, but nothing
    shows in the output file. How can I check that the external trigger is
    functioning?

    One question, if I launch the stand-alone GUI, do
    the commands above work just the same (in the absence of me getting any
    feedback since I don't have a similar debugging window as Processing
    has)?

    Sorry to sound like I have no idea what I am talking about,
    but I DO have no idea what I'm talking about -- this is all new
    territory to me..!!

    Cheers

     Martin

    PS: re the documentation pages, somehow the "http://" lost a ':' in the first link, and migrated at the end of the other link... if you fix manually both links open  [note by William @wjcroft: I just fixed your bad links, sorry didnt catch that earlier]
  • Martin!

    How's it going? (Other than these setbacks ha)

    Which beta do you have? Please note a new beta was released https://github.com/OpenBCI/OpenBCI_32bit_Library/releases/tag/v3.0.0-beta4 which for sure has these commands.

    Could you try over the air uploading the newest beta4?

    Looking forward to getting board mode changing working with you!
  • Hi @pushtheworld yes, I had installed Beta2. I ran DefaultBoard from the
    Beta4 folder, but when I launch the GUI (from processing) and try
    entering '//' or "/2" (which I assume is what the documentation meant, instead of "~2" which is for the sampling rate?) no response is returned in the debugger (unlike
    what the doumentation says).

    Suggestions?

    Thank you

     Martin
  • @pushtheworld
    Hey AJ, ok so it turns out I also had to update the Processing OpenBCI gui!

    Now that I've both updated to beta4 AND updated the OBCI_GUI for processing it looks like it is recognizing modes. Only thing, unlike what is said in the documentation (See link in my previous post), typing "//" returns "Failure: invalid board mode$$$"
    Typing "/2" or "/0" returns "Success: Board type set$$$ but it does not tell me WHICH board type is set. I know, the docs say "/2" is for analog, and I'm ok with that, but for the future it would be great to get confirmation ;-)

    Cheers
     Martin

    PS: there is no command with which I could, from the keyboard, manually drop a marker in the SavedData is there?
  • @MCube78

    Can you please update Cyton to v3.0.0-beta5?

    You're (valuable) feedback has been patched.

    Re: PS: there is no command with which I could, from the keyboard, manually drop a marker in the SavedData is there?
    Can you please open an issue on the GUI github page to request this feature?

    Thanks,

    AJ


Sign In or Register to comment.