Cyton+Daisy "Failed to connect to data source..."
Hello,
I just received my very first Cyton+Daisy board but I am not able to get the OpenBCI USB Dongle to connect to Cyton+Daisy board.
By following the steps in https://docs.openbci.com/docs/01GettingStarted/01-Boards/CytonGS
I installed the OpenBCI GUI (v 4.1.5) as standalone app on my Macbook Pro 2017, running on macOS Mojave 10.14.6 with Bluetooth turned on, and I also installed the latest FTDI driver (2.4.2). After I restarted my MacBook, I launched OpenBCI from /Applications/OpenBCI.app.
I checked to make sure the OpenBCI USB Dongle is switched to GPIO_6, then plug it in to my USB type C port (through a USB to type C adaptor), and a solid blue light is turned on. Then I switched on the Cyton+Daisy board to PC, a solid blue light is also turned on.
On OpenBCI GUI, I select data source LIVE from Cyton select Serial (from Dongle). Under SERIAL/COM PORT I got:
- /dev/tty.SOC
- /dev/tty.MALS
- /dev/tty.Bluetooth-Imcoming-Port
- /dev/cu.SOC
- /dev/cu.MALS
- /dev/cu.Bluetooth-Imcoming-Port
I clicked on REFRESH LIST but I am not seeing /dev/tty.usbserial-DB00JLWR or /dev/tty.usbserial-A104JV88.
I cycled through each port, clicked on AUTOSCAN, but only get:
Error connecting to Serial port. Try a different port?
I cycled through each port, clicked on START SESSION, I am getting:
Failed to connect to data source. Check that device is powered on and in range. Also try pressing AUTOSCAN.
My Cyton+Daisy board is less than 1 feet away from Dongle, but I am not able to get it connected…
Can you please help me to resolve the connection issue?
Comments
YChen, hi.
The first suggestion would be to try inserting your dongle into another computer. For example, on Windows, it will appear as a COM port in the Device Manager. When unplugged, it disappears. On Mac, it appears as you expect, as a /dev/tty.usbserial*. It is possible there might be something odd about the usb serial port handling on your particular computer.
The other /dev entries you mention (tty.* and cu.*) are NOT how the dongle is supposed to appear.
IF the dongle is not recognized by a couple tries on other computers, it generally means the dongle flash memory or FTDI chip has failed. In this case you would send an email to contact at openbci.com, and ask how to get a replacement dongle.
Regards, William
On the other hand, if the dongle does get recognized on those other computers, but not your own -- then there may be other things we can try. Please comment here on this thread on what you find.
Hi William,
Thanks for your response. I tried the dongle on two other computers and it works on both. I tried on iMac (2011? macOS Mojave 10.14.6) and another MackBookPro (2017, macOS High Sierra ) and it works on both.
Is there anything else I can try on my own laptop to detect /dev/tty.usbserial*? I removed OpenBCI GIP app from /Applications, reinstalled FTDI driver (2.4.2), reinstalled OpenBCI GUI app, launched OpenBCI GUI, plugged in the dongle on my laptop, but still not able to see any serial/com port...
It's remotely possible that the installation of the FTDI driver on your MacBook, might have wedged something in the OS. I do see from this page that it was released in 2017. That is older than your Mohave, right?
https://www.ftdichip.com/Drivers/VCP.htm
On the iMac and MacBookPro, did you just insert the dongle, or did you install the FTDI 2017 driver there as well? This doc on page 16 has uninstall instructions.
https://www.ftdichip.com/Support/Documents/AppNotes/AN_134_FTDI_Drivers_Installation_Guide_for_MAC_OSX.pdf
After the uninstall, I'm not clear if the original Apple driver is reenabled, or if has been deleted from your hard drive. If the latter is the case, it might be found on the iMac. This command I think would list all the Apple usb drivers:
$ sudo kextstat -l | grep usb
On this High Sierra Mac, I see:
This site implies that a separate VCP driver may not be needed: "For macOS 10.11 “El Capitan” or Later, Starting with macOS 10.11, Apple started providing its own compatible USB VCP driver. You don’t need to install anything."
https://cedrus.com/support/rb_series/tn1557_install_rbx40_macos_x.htm
Compare the folders /System/Library/Extensions on the iMac and your machine. As far as the files / kexts that contain the string 'usb' or 'USB'.
Hi William.
For the other computers (iMac & MacBook Pro-13"), I apply exact the same steps as my laptop (MacBookPro-15"):
1. install FTDI 2017 driver and then
2. install OpenBCI GUI.
I also compared the output of
$ sudo kextstat -i | grep usbandls /System/Library/Extensions | grep -i usbbetween the three computers but I am not sure which drivers could cause the issue... Do you see anything suspicious?Sigh. Is there ONE MORE Mac available that has High Sierra or Mojave, but where you HAVE NOT installed the 2017 FTDI driver? We are trying to determine if the dongle is recognized and runs WITHOUT needing the FTDI driver, on these later macos's. As Apple apparently has their own VCP driver (virtual com port), in recent versions. The older FTDI driver might be interfering with the one on your machine.
Even though all Macs may be on a certain OS level, each Mac machine has a unique upgrade history and driver installation history. Hence there may be something odd about your kext / driver setup, not present on the other machines.
I'm not knowledgeable about how these kexts all are supposed to be setup. Normally the dongle just works in 99.99% of the cases. I suggest (1) try running the FTDI uninstall instructions as previously mentioned. (2) if that fails, reach out to FTDI customer support and ask them for some suggestions. Tell them other vendors claim that Mojave and High Sierra do not NEED the FTDI driver for VCP support. There may be interference between the old FTDI and certain installations of Mojave.
If you are really desperate, this may work: do a complete clean install of Mojave on your machine. Obviously first saving your files, then formatting the internal drive. OR, if you have a spare external drive, you could clean install Mojave onto that, then use that as your boot device.
First see if the dongle is recognized on another Mojave or High Sierra without the FTDI VCP driver. Anyway it's midnight here. Maybe more ideas will surface later. Sorry you are encountering this difficulty. Mac 'appear' to be friendly and uniform. But under the hood, weirdness sometimes awaits. ;-)
This page suggests using a usb hub between the Mac and the dongle.
https://stackoverflow.com/questions/50729781/macos-x-mojave-10-14-beta-ftdi-usb-serial-driver
It also shows that some variation in Mojave usb serial port support seem to exist. Also scan,
https://www.google.com/search?q=mohave+usb+serial+port+driver
Another statement from FTDI that El Capitan and later do not need their VCP driver,
https://forum.arduino.cc/index.php?topic=427825.0
I do have another MacBookPro-15" (High Sierra)
~~ This time I didn't install FTDI VCP driver and the Dongle connects to Cyton+Daisy right away.
I ran
$ sudo kextstat -i | grep usbagain and it contains exactly same drivers as the other High Sierra that I listed above, so I started to look into the two missing drivers 'com.apple.driver.usb.cdc.acm' and 'com.apple.driver.usb.cdc.ecm'. I googled 'com.apple.driver.usb.cdc.acm' and I came across one interesting post (https://discussions.apple.com/thread/8297132) where the user faced a similar issue and there he provided a temporary workaround to resolve his issue.After reading I decide to give it a shot -- reboot with Dongle connected-- and it worked temporary!
This workaround somehow allows the Dongle to show up in the SERIAL/COM PORT (as /dev/tty.usbserial-DM01MW53) for making connection with Cyton+Daisy. If I removed and re-connect the dongle, the port /dev/tty.usbserial-DM01MW53 no longer show. Having said, once the dongle is removed, I have to reboot with dongle connected otherwise it will not show.
Does this temporary workaround ring any bell?
(BTW, I also uninstalled the FTDI driver this time)
When FTDI customer service returns to work on Monday, try contacting them. I'm out of suggestions at this point, may do some more searching.
OK, let me write to FTDI customer services. While asking, is there any specific FTDI product should I mention to them?
The dongle uses the FT231X USB-to-serial converter from FTDI. Support for this chip appears to be available WITHOUT the 2017 FTDI VCP driver, in many recent macos versions.
What you are asking them is: did the install of the 2017 VCP driver, screw up the default Mojave usb serial driver; and how to undo the damage.
Hi William,
Just want to give you an update:
I wrote to FTDI customer support and they suggested me to temporary unload the built-in Apple USB FTDI driver and then run their installer again. I tried that suggestion but unfortunately it didn't help and they are not able to provide further assistance.
Since I am able to use the temporary workaround to connect to Cyton+Daisy, I will just stick with that until I get a chance to reinstall Mojave (or downgrade to High Sierra). Thank you very much for your support, I really appreciated!