Mods4cars Support > Product Support > Knowledgebase

Search help:

Faulty USB driver included in OS X Mavericks, Yosemite and El Capitan prevents proper operation of m4cconnect. *SOLUTION*



When installing m4cconnect on Mac OS beginning with Mavericks, proper operation is not possible. m4cconnect v1.11 will not connect to the module, m4cconnect 1.21 and later will report a warning message when connecting and inform the user about the faulty driver.


Apple decided to include their own, severely broken serial driver for FTDI USB serial chips beginning with Mavericks. That driver simply lacks handshake protocols and is therefore unusable or severely cripples many microcontroller applications. Older versions of m4cconnect included a driver inside the app which now gets blocked, newer versions of m4cconnect use the Apple-forced way of connecting to the USB port and warn the user when detecting Apple's broken driver.


This has been a known issue since late 2013 at which point we filed bug reports with Apple. Unfortunately the driver is still not fixed, so we have developed a compatibility mode in m4cconnect to avoid crashes and the following workaround for manually installing a proper driver.

1) Install the FTDIUSBSerialDriver from the .dmg package supplied on our USB SUPPORT Website

2) Reboot your Mac (important!)

3) Connect the module to the USB port

4) Start m4cconnect

5) Click CONNECT - There should be no warning message


Was this article helpful? yes / no
Related articles USB troubleshooting. What if the module doesn't connect or m4cconnect can't find the module?
MANUAL installation of the USB driver under WINDOWS
When I try to start m4cconnect on Windows I get an error saying that FTD2XX.DLL can not be found.
USB configuration for ALL MODULES with USB port
When trying to run m4cconnect under Windows, an error about a missing MSVCR100.dll is shown
Article details
Article ID: 63
Category: General
Date added: 2013-11-18 21:02:12
Views: 11340
Rating (Votes): Article rated 3.1/5.0 (108)

« Go back