Dongle is no longer recognized in GUI or Device Manager
Recently, the GUI and Device manager has ceased to recognize the Bluetooth dongle. Prior to this, I had very few problems, occasionally I would have to restart the GUI because it failed to initialize, but other than that there were not any problems. All of a sudden, the COM Port for the dongle, or any COM port for that matter, was no longer there when trying to start the GUI. Within Device Manager, it says that no COM Port is active, while the dongle is plugged in with the blue light steady and the switch on GPIO_6. The board(32bit) is switched to PC, the blue light on it is steady, and the batteries are fresh. I do not remember making any changes, other than just normal windows updates, but nothing that I would expect could cause something like this. I have restated my computer multiple times, downloaded the Processing GUI again, and uninstalled/reinstalled the FTDI VCP drives, but the port still is not recognized by the GUI or in Device Manager, and I am having a very difficult time trying to figure out why. The computer is running on windows 8 and I downloaded the 2.12.10 executable file from the FTDI chip website, if that information can help at all. I tried to look through the forum, but was not able to find someone else with the same issue or anything that could solve mine, I am sorry if I missed one that did discuss a similar issue. I would greatly appreciate any help anyone could provide.
Comments
(1) does the dongle show up when plugged into another laptop? Either as a COM port on Windows or a /dev on Mac / Linux?
(2) when first plugged in, the red light on the dongle flashes briefly, then the blue light comes on solid. You did say you had the blue light.
As you probably found with the search box, there are some similar cases, but in some of these the blue LED is not coming on at all. If your COM port is not showing up, then reprogramming the dongle flash also seems out of reach. Joel @biomurph will likely comment here.
http://openbci.com/forum/index.php?p=/discussion/554/usb-dongle-stopped-working-suddenly
http://openbci.com/forum/index.php?p=/discussion/429/broken-dongle
http://openbci.com/forum/index.php?p=/discussion/204/getting-started-dongle-drivers
William
Mac-reinstalling ftdi drivers, attempted to connect on Open Bci gui and Neuromore
$ ls /dev/tty.*
/dev/tty.Bluetooth-Incoming-Port
But the lab is also very busy right now with the various engineering tasks from the last Kickstarter. I'd suggest following Joel's advice on the Jan 4 post above. Write to him directly at his email address and include contact at openbci.com. I'll also mention @Conor here. Most likely you'll need to do a swap of your dongle with the fullfillment center.
Regards,
William
Thanks,
device_t role = HOST; // This is the HOST
void setup(){
RFduinoGZLL.channel = 6; // use channels 2-25. 1 is same as 0 and 0-8 in normal GZLL library
RFduinoGZLL.begin(role); // start the GZLL stack
// more stuff here
}
so now i have a new issue.
https://drive.google.com/open?id=0B7epH6R9TdXWbXJYWVlwMV9uN2c
https://drive.google.com/open?id=0B7epH6R9TdXWNDk2UWlvcTVWNjg
This thread discusses workarounds for the plib.h,
http://openbci.com/forum/index.php?p=/discussion/598/openbci-32bit-compile-error-plib-h-no-such-file-or-directory
By "0 microvolts" I meant "close to 0", a few microvolts is ok. Is it possible you are in a high noise EMF area, such as near a wall wart or laptop power supply. Or directly over AC power cords or conduits?
So you had the Ultracortex working ok at one point before the dongle broke.
Can you just try this. (I'm running out of suggestions. And I'm sure you're finding this frustrating as well.) In a small cup or container place a bit of water, maybe a couple tablespoons. Then add a half teaspoon of salt. Dissolve. Then place 3 gold cup electrodes into this solution, connect to channel 1, SRB2, and Bias. All pins closest to board. Then see if you get close to 0 microvolts. If you DON'T get 0, try swapping around the various leads in case there is a bad one. Be sure you are using SRB2, closest to board and not SRB1, farthest from board. Use OpenBCI_GUI to check your signals.
1: I taped one of the smooth spring electrodes to my forehead and attached it to each pin on the board and tested for eye blinking artifacts and for alpha signals. while having all other inactive channels off. All of the pins did fine(showing blinks and alphs).
Leads = electrode leads consisting of a wire with a connector on one end and cup or other electrode at the other end. Lead is a common term used when referring to electronics and test equipment.
You might check with a magnifying glass the surface of your board very carefully, especially around the ADS1299 chip. See if any metal flake particles might have lodged in between the solder connections there. Also look around other parts of the board for any conductive material.
The header pin edge connectors rarely go bad since they are so large and have such large amount of solder connecting to the board.