Usb Cdc Drivers For Mac
The Synergy signed USB CDC driver supersedes all previous versions of the Synergy USB CDC drivers. The driver package consists of the catalog (.cat) and installation information (.inf) files along with an application note with instructions to install the Synergy signed USB CDC drivers on the Windows® host PC.
It appears the Mac OS X drivers on Transystem's website for the 860E no longer work with newer versions of MacOS 10.9. I've done some digging, and it appears this device uses a Silicon Labs CP210x USB Bridge chip, but the current VCP drivers on their website do not seem to work for the 860E (I do not see the serial devices in /dev anymore). Has anyone figured out this issue? I've been trying to get support from Transystem, MTK, and Silicon Labs, but I haven't made any progress.
I think the issue is that the new drivers need to be configured with the MT3329's USB 'VID/PID'. SiLab's website has a form where you can get customized drivers , but you need to know the CP210x part number in the form, and I haven't been able to find out that information.
Usb Cdc Driver For Mac
I believe I've found the VID/PID, so that's the last bit if info I think I need. Solution I've discovered the cause of the problem.
Apparently Apple modified their 'USB-CDC-ACM' driver in Mac OS X 10.10 (Yosimite) to remove the modem functionality for non-modem devices like the MT3329. This broke compatibility with bt747 and GPSBabel on the Mac platform.
The creator of mytracks4mac seems to be the one who figured this problem and he has created a replacement driver. I've verified his fix works in Mac OS X 10.12 Sierra. You can find that driver on his website (web archive link, created on 7-Dec-2017). His page is the only one I've found that explains the issue or offers a solution, so I've made sure the archive includes the latest version of the driver as of this date. Hope this finds anyone who's had similar issues.

Mac OS X compatibility: we have confirmed that the Wixel works on Mac OS X and we can assist with advanced technical issues, but most of our tech support staff does not use Macs, so basic support for Mac OS X is limited. The Wixel Configuration Utility running in Mac OS X. You can download the Wixel Configuration Utility and the Wixel command-line utility (wixelcmd) for Mac OS X here:.
(10MB dmg) Double click on the dmg file to open it, and then follow the instructions in README.txt. The virtual COM ports are managed by the AppleUSBCDCACM component of Mac OS X. The of AppleUSBCDCACM is available from Apple. When you connect a Wixel running an app that implements a virtual serial port to the PC, the virtual serial port should appear as a device with a name like /dev/cu.usbmodemfa121 (the number depends on which USB port you use). You can use any terminal program (such as screen) to send and receive bytes on those ports.