@abdan17, can you give us more information about the problem you're having? Are you able to run the OpenBCI 32bit system with our GUI software (or other compatible software)? At what point does the problem arise? If you are getting error codes, please tell us what they are.
i have following all instruction, first i try in windows 8.1 and 7, but both of them can't running OpenBCI_GUI using processing-2.2.1. i try to upload code to OpenBCI 32 bit device using Mpide, but after going to 90% it fail, it tell avrdude: bla bla bla (i assume, chip has conflict address or damage), i have followed instruction in chipkit forum to edit preference.
Then i try to test dongle by uploading code, it work well but it did not work to Device.
now i am working on Ubuntu 15.04, i am trying to run OpenBCI_GUI, but error says: " init timeout Verify your Serial/Com Port Power DOWN/UP your OpenBCI & USB Dongle then rentry initialization ".
I assume:
1. TX and RX don't work 2. i have modified code in dongle, so it don't match with device 3. OpenBCI V3 32 bit damage
could you please tell me what i have to do?
Or in my opinion, how about i send back OpenBCI V3 32 bit to reprograme?
@abdan17 , is it possible that when you uploaded code to the dongle, you did not match the radio channel printed on the anti-static bag that contained the main board? In other words, you need to mod the dongle source to match the channel printed on the bag.
As far as the process being tricky to upload to the main board, this is being refined over time. And the previous link to the thread discussing this has a number of tips. Of course none of those will work without the channels being in agreement.
re: OpenBCI_GUI on Ubuntu. Does a new device show up in /dev when you plug in the dongle?
My suggestion is that before you modify the code in your main board, you try to get a working configuration between the dongle and main board. Do you actually need to modify the code on the dongle or main board, or was that just a last ditch attempt to get something working? Best to test and verify with the default configuration and OpenBCI_GUI, before you start changing things.
Hey @abdan17 just a quick note: I get the same error on Ubuntu 14.04 LTS occasionally, and I have always been able to fix it by a) making sure the batteries are fresh in OpenBCI, and the dongle and board are close to each other, and b) pressing the “reset” button on the OpenBCI board (after trying to connect and it failing with the init timeout error) while everything it plugged in a running, and then trying to connect again.
Comments
i try to upload code to OpenBCI 32 bit device using Mpide, but after going to 90% it fail, it tell avrdude: bla bla bla (i assume, chip has conflict address or damage), i have followed instruction in chipkit forum to edit preference.
Then i try to test dongle by uploading code, it work well but it did not work to Device.
now i am working on Ubuntu 15.04, i am trying to run OpenBCI_GUI, but error says: " init timeout Verify your Serial/Com Port Power DOWN/UP your OpenBCI & USB Dongle then rentry initialization ".
I assume:
1. TX and RX don't work
2. i have modified code in dongle, so it don't match with device
3. OpenBCI V3 32 bit damage
could you please tell me what i have to do?
Or in my opinion, how about i send back OpenBCI V3 32 bit to reprograme?
As far as the process being tricky to upload to the main board, this is being refined over time. And the previous link to the thread discussing this has a number of tips. Of course none of those will work without the channels being in agreement.
re: OpenBCI_GUI on Ubuntu. Does a new device show up in /dev when you plug in the dongle?
My suggestion is that before you modify the code in your main board, you try to get a working configuration between the dongle and main board. Do you actually need to modify the code on the dongle or main board, or was that just a last ditch attempt to get something working? Best to test and verify with the default configuration and OpenBCI_GUI, before you start changing things.
Regards, William
http://openbci.com/forum/index.php?p=/discussion/215/openbci-gui-windows-zip-exe-s-broken-use-processing-source
http://openbci.com/forum/index.php?p=/discussion/224/openbci-gui-linux64-needs-jssc-jar-update
http://www.autodidacts.io/getting-started-with-openbci-a-tutorial-on-testing-troubleshooting-and-recording-ekg/#gettingtheopenbcisoftwareworkingonlinux
Also, I have uploaded the exact version of the OpenBCI GUI that I used when I wrote the tutorial @wjcroft linked to, and some other folks have found it helpful. You can download it here: http://cdn.autodidacts.io/misc/application.linux64.zip
Let me know if this helps,
— Curiositry
i will test OpenBCI V3 with you talk me. but, what will i do with "OpenBCI_GUI" file?
The short form is to unzip application.linux64.zip and then run:
cd application.linux64 && sudo bash OpenBCI_GUI
in terminal.