When the Arduino Software (IDE. MAC OS9: Windows Server 2008 R2 x64: MAC OS8: Support for WinCE FTDI drivers are available for Windows CE 4.2-5.2, 6.0/7.0 and 2013. Support for older versions of Windows Desktop. Get the Arduino drivers. For PC users, go to the Connect menu in mBlock: For Mac users, download the driver. Unfortunately, the latest update for the Mac OSX introduced an issue with this driver. Find out about the solution to this issue. Connect your robot to your computer via USB cable, turn your robot on, and open mBlock.
editNote: the FTDI USB Drivers are from Arduino. But when you install drivers for other Controllers, such as Xadow Main Board, Seeeduino Clio, Seeeduino Lite,
you need to download corresponding driver file and save it. And select the driver file you have downloaded.
You should save these files which you are editing before installing driver with window8,because there will several power off during operating.
Please submit any technical issue into our forum.
Ongoing macOS FTDI driver issues plague many users connecting the Arduino IDE to boards that use an FTDI chip. Since our boards use an FTDI chip for USB-to-serial communication, we have witnessed some of these issues when working with our boards using Mac and macOS.
The symptoms we have observed generally include the spontaneous loss of the USB serial port connection to the board or loss of the port after disconnecting and then reconnecting the board from the USB programming cable.
Rebooting the system can temporarily restore the port, but the problem eventually comes back. Since we’ve seen this issue pop up internally and with many customers, we decided to share what solution has been working for us so far.
The exact cause of this problem is not certain, but it seems to be related to Apple’s support, or lack thereof, for FTDI drivers in the operating system. Earlier versions of Mac OS X did not support FTDI drivers, so users would have to install third-party FTDI drivers. Somewhere around the release of macOS 10.12 Sierra (and maybe earlier), native support for FTDI drivers was included.
So, if you have followed an upgrade path from an older version of the OS without native FTDI support to a new version that has it, there can be contention between the native and third-party drivers. This potentially leads to the mysterious port disappearance issue.
We have found uninstalling the third-party drivers to be a solution. The instructions below have seemed to work for anyone here at Alorium Technology that was observing the FTDI issues.
Join our mailing list to stay in the loop with the latest news regarding Alorium products and other interesting things we are doing. Your email will not be shared, and we won't pester you very often!