Ftdi Sio Drivers For Mac
Hi there, I've been lurking for a while now, and gathering information before going ahead and buying a KHR-1HV kit to get myself into the world of bipedal roboteering. One question I have to ask is whether anyone here has any experience in working with the KHR series using a Mac. All the documentation I have read required a PV with XP for the H2H software, and programming of the boards.
Now, I'm a Mac user, having shed the nightmare of windows a long time ago. I do run Parallels on my mac meaning that I can run XP (and do have it installed).
So has anyone used the H2H on a Mac, running either parallels or bootcamp, or know if there's a Mac version of the SW that can be used? Thanks in advance. Hi there, I've been lurking for a while now, and gathering information before going ahead and buying a KHR-1HV kit to get myself into the world of bipedal roboteering. One question I have to ask is whether anyone here has any experience in working with the KHR series using a Mac. All the documentation I have read required a PV with XP for the H2H software, and programming of the boards. Now, I'm a Mac user, having shed the nightmare of windows a long time ago.
I do run Parallels on my mac meaning that I can run XP (and do have it installed). So has anyone used the H2H on a Mac, running either parallels or bootcamp, or know if there's a Mac version of the SW that can be used? Thanks in advance. Neil offline Robot Builder Posts: 13 Joined: Mon Jul 20, 2009 2:07 pm. Hi there, Me too, I have a mac and I like to control the KHR-2HV from Mac OS X, but I had problems iinstalling the USB Serial Converter Driver does not create the virtual ports (should appear in the / dev) but its´n there. The drivers is here Install Guide Mac OS X is here although I was disappointed to know that there isn´t H2H for mac, do not really need, the idea is to handle it from java but I need the driver installed correctly. Has anyone tried to install the usb driver on Mac OS X?
Offline Robot Builder Posts: 10 Joined: Tue May 12, 2009 9:27 pm. Two solutions: 1) You can use the USB-Serial adapter in Mac with the default FTDI drivers if you remove the EEPROM from it that contains the KONDO device ID's. When you open up the casing on the adapter, it is a 6 pin chip near the connector end, on the same side of the board as the FTDI chip. After removing the EEPROM, the FTDI device will go back to the default ID's and it's driver will register.
Sorry, if I wasn't at work I'd post a picture 2) Modify the driver as this guy did (Japanese): Open up /System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/Info.plist with a text editor or plist editor and add this data to the list of products: Kondo Serial USB Adapter CFBundleIdentifier com.FTDI.driver.FTDIUSBSerialDriver IOClass FTDIUSBSerialDriver IOProviderClass IOUSBInterface bConfigurationValue 1 bInterfaceNumber 0 idProduct 2 idVendor 5724 You should double check these Product/Vendor ID's in the IORegistryExplorer or from within Windows. Of course without H2H, unless you are doing some home grown serial port code on the Mac side, getting the adapter to work there is pointless. (Though this does open the door to using WINE instead of VMWare/Parallels). Two solutions: 1) You can use the USB-Serial adapter in Mac with the default FTDI drivers if you remove the EEPROM from it that contains the KONDO device ID's. When you open up the casing on the adapter, it is a 6 pin chip near the connector end, on the same side of the board as the FTDI chip. After removing the EEPROM, the FTDI device will go back to the default ID's and it's driver will register. Sorry, if I wasn't at work I'd post a picture 2) Modify the driver as this guy did (Japanese): Open up /System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/Info.plist with a text editor or plist editor and add this data to the list of products: Kondo Serial USB Adapter CFBundleIdentifier com.FTDI.driver.FTDIUSBSerialDriver IOClass FTDIUSBSerialDriver IOProviderClass IOUSBInterface bConfigurationValue 1 bInterfaceNumber 0 idProduct 2 idVendor 5724 You should double check these Product/Vendor ID's in the IORegistryExplorer or from within Windows.
Of course without H2H, unless you are doing some home grown serial port code on the Mac side, getting the adapter to work there is pointless. (Though this does open the door to using WINE instead of VMWare/Parallels) offline Savvy Roboteer Posts: 59 Joined: Wed Jul 22, 2009 8:04 am Location: Japan. Sorry about the link. Basically, the EEPROM stores configuration information for the USB-serial adapter including customized vendor/product id numbers which Kondo put in there. You can clear it so that it acts like a 'default' FTDI USB-serial adapter. The easiest way is to use Windows tools to clear it if you have access to a Windows PC: FTDI released a graphical tool called FTPROG which also lets you reprogram the firmware of the device.
Basically look for the VID/PID configuration and clear it out to default. You don't have to mess with any other option. If you MUST use the Mac or Linux, use these steps: 1. Download ftdieeprom 2.
Obtain the VID/PID combination for your USB adapter. On the mac you can find this in the 'System Profiler' which you can get to by going to the Apple menu at the top left-hand side of your desktop and choose 'About this mac.' Then click on 'More info.' And then USB and find out what the VID/PID is. Use that VID/PID information to tell ftdieeprom to erase the EEPROM (just read the instructions for ftdieeprom).
You may have to do it more than once, sometimes it doesn't work the first time. Also, I'm pretty sure build of ftdieeprom on the Mac may not be easy because libftdi requires libusb, which doesn't come on the Mac.
However, libusb, libftdi, and ftdieeprom all compile on the Mac, I have done it before. Sorry about the link. Basically, the EEPROM stores configuration information for the USB-serial adapter including customized vendor/product id numbers which Kondo put in there. You can clear it so that it acts like a 'default' FTDI USB-serial adapter. The easiest way is to use Windows tools to clear it if you have access to a Windows PC: FTDI released a graphical tool called FTPROG which also lets you reprogram the firmware of the device. Basically look for the VID/PID configuration and clear it out to default. You don't have to mess with any other option.
If you MUST use the Mac or Linux, use these steps: 1. Download ftdieeprom 2. Obtain the VID/PID combination for your USB adapter. On the mac you can find this in the 'System Profiler' which you can get to by going to the Apple menu at the top left-hand side of your desktop and choose 'About this mac.'
Then click on 'More info.' And then USB and find out what the VID/PID is.
Use that VID/PID information to tell ftdieeprom to erase the EEPROM (just read the instructions for ftdieeprom). You may have to do it more than once, sometimes it doesn't work the first time. Also, I'm pretty sure build of ftdieeprom on the Mac may not be easy because libftdi requires libusb, which doesn't come on the Mac. However, libusb, libftdi, and ftdieeprom all compile on the Mac, I have done it before. Offline Savvy Roboteer Posts: 132 Joined: Mon Nov 02, 2009 10:24 pm.
Kondo has also posted an official guide for how to connect the USB adapter in Linux: Their approach is to manually load the kernel driver using modprobe, passing in the custom VID/PID combination as parameters. To extend that, you could probably add something in /etc/modprobe.d or /etc/udev to automatically use these parameters when loading the ftdi-sio driver. Note that you only need to use the ftdi-sio kernel driver if you want to access the serial port through /dev/ttyUSB. There is an excellent userland library called libftdi which directly accesses the USB-serial device without the use of the ftdi-sio kernel driver, and a small library called libkondo4 which uses libftdi to provide a high level API that accesses the functionality of RCB4 / ICS3.
Kondo has also posted an official guide for how to connect the USB adapter in Linux: Their approach is to manually load the kernel driver using modprobe, passing in the custom VID/PID combination as parameters. To extend that, you could probably add something in /etc/modprobe.d or /etc/udev to automatically use these parameters when loading the ftdi-sio driver. Note that you only need to use the ftdi-sio kernel driver if you want to access the serial port through /dev/ttyUSB. There is an excellent userland library called libftdi which directly accesses the USB-serial device without the use of the ftdi-sio kernel driver, and a small library called libkondo4 which uses libftdi to provide a high level API that accesses the functionality of RCB4 / ICS3. Offline Savvy Roboteer Posts: 132 Joined: Mon Nov 02, 2009 10:24 pm.
Ftdi Sio Drivers For Mac Download
Ftdi Driver Update
PL2303 Mac OS X Driver Download Download File: Mac OS X Universal Binary Driver v1.6.1 (PKG file format). For Mac OS High Sierra (version 10.13) - see NOTE below.
For Mac OS X Sierra (version 10.12). For Mac OS X El Capitan (version 10.11). For Mac OS X Yosemite (version 10.10).
For Mac OS X Mavericks (version 10.9). For PL2303 H/HX/HXD/EA/RA/SA/TA/TB chip versions. For Prolific USB VID067B&PID2303 Only. Includes Driver Installation Manual NOTE: Mac OS High Sierra 10.13 introduces a new feature that requires user approval before loading new third-party kernel extensions. Go to System Preferences - Security & Privacy and click Allow.