OpenBCI 3.3.0 doesn't work (WIndows 10, 64-Bit)
Derek
Berlin
in OpenBCI_GUI
Hi all,
I just downloaded the most recent version 3.3.0 of the GUI and followed the instructions (copied the files into my Programs folder, made them to be run as admin by default and ran the HUB first, then the GUI). It takes quite a while to show the splash screen (methinks a bit longer than in 3.2.0, but that's just a minor detail - just in case it might prompt an idea). The initial menu appears ("System Control Panel"), but no matter which of the four data sources I choose, the program becomes irresponsive. I can wait until the cows come home and nothing will happen; switching back and forth between programs on my computer will have the GUI reduced to a black window. I can still minimize or kill it by clicking on the _ or X, respectively, in the upper right corner, so there is a minor remnant of responsiveness, but that's all there is. Version 3.2.0 keeps working fine.
By the way, is there something like a version history somewhere detailing new features and bug-fixes? So far, I haven't found it and it would be useful for my to know how much I acutally need the update.
Thanks in advance for your time and brain power!
Cheers,
Derek
I just downloaded the most recent version 3.3.0 of the GUI and followed the instructions (copied the files into my Programs folder, made them to be run as admin by default and ran the HUB first, then the GUI). It takes quite a while to show the splash screen (methinks a bit longer than in 3.2.0, but that's just a minor detail - just in case it might prompt an idea). The initial menu appears ("System Control Panel"), but no matter which of the four data sources I choose, the program becomes irresponsive. I can wait until the cows come home and nothing will happen; switching back and forth between programs on my computer will have the GUI reduced to a black window. I can still minimize or kill it by clicking on the _ or X, respectively, in the upper right corner, so there is a minor remnant of responsiveness, but that's all there is. Version 3.2.0 keeps working fine.
By the way, is there something like a version history somewhere detailing new features and bug-fixes? So far, I haven't found it and it would be useful for my to know how much I acutally need the update.
Thanks in advance for your time and brain power!
Cheers,
Derek
Comments
Thanks for your feedback. I downloaded the beta but immediately faced a problem with the hub:
(error message)
A JavaScript error occurred in the main process
Uncaught Exception:
Error: Cannot find module 'openbci-ganglion'
at Module._resolveFilename (module.js:485:15)
at Function.Module._resolveFilename (C:\Program
Files\OpenBCIHub\resources\electron.asar\common\reset-search-paths.js:35:12)
at Function.Module._load (module.js:437:25)
at Module.requier (module.js:513:17)
at require (internal/module.js:11:18)
at C:\Program Files\OpenBCIHub\resources\app.asar\background.js:6:32
at Object.<anonymous> (C:\Program
Files\OpenBCIHub\resources\app.asar\background.js:1798:2)
at Object.<anonymous> (C:\Program
Files\OpenBCIHub\resouces}app.asar\background.js:1800:3)
at Module._compile (module.js:569:30)
at Object.Module._extensions..(module.js.580:10)
(end of error message)
I used the hub that came with version 3.2.0 instead and it seemed to work fine. 3.3.1-beta did open normally, I could choose my source and start the data stream.
One problem I ran into - and I do not know if it is related at all - was that while doing a test run with SD-card saving enabled, it only registered approx. 18 minutes instead of 30 minutes as I had chosen. The file ends on a footer
%Total time mS:001C9E4B%min Write time uS:00000146%max Write time uS: 0000014C%Over:00000000%block, uS
which seems to make sense to me and that writing came to a halt on purpose.
But the very first line of the file starts on FB insteat of 00, so I guess that Cyton didn't start writing right away. More than a third of the file is empty, which would be in accordance with the 18 minutes I'm left with after file conversion. Is this in some way related to the hub or version issue?
And, on a very different note, is there some way to include a time stamp in the SD-raw data file? Since they all have the same time stamp of 01/01/2000, 00:00, it makes it difficult to keep trials apart, especially while trying some bug-fixing. There wouldn't be a way to write the file as bdf straight to the SD?
(sorry if you consider my last questions to be too much of a distractor, feel free to stay focussed on the problem at hand)
Thanks,
Derek