Using a program like OnyX http://www.titanium.free.fr and have it rebuild the kernel extension cache can help if installing the FTDI driver didn't or removal didn't work.
Bill/Chris... Thank you for replying... Just before I gave up for today I reached behind my iMac and noticed the usb plug was slightly out. After pushing it in I was able to see the USBserial port As well as the Bluetooth incoming port. This one bit me for hours... I haven't tried to connect yet.. Tomorrow.
I did go and load 2.3.... funny when checking the Extensions for FTDI.ktext I found none! I did the install as noted on Adrupilot.. Looks good ...now its off to tuning... If I can keep it straight!
That's probably due to the new security in OSX. Try this:
OSX 10.11 has a new feature called “System Integrity Protection” that blocks any kind of third party driver from being used. This is also referred to as “Rootless”. This process will turn that off and allow you to run processes that can modify system files.
Install your USB Serial adapter drivers if you haven’t already done so.
Open a terminal and type sudo nvram boot-args="kext-dev-mode=1 rootless=0"
Reboot.
Open terminal with USB adapter attached and cd to /dev
type ls and your adapter should show up like tty.usbserial.
Replies
Support for APM Planner 2.0 is done here http://discuss.ardupilot.org/c/ground-control-software/apm-planner-2-0
I would not recommend turning of any security features is OSX. You can fix this by one of two methods.
1 Remove the old installed FTDI kext from/Library/Extensions (then reboot)
2. Download and install the new FTDI drivers from FTDI website (current version 2.3)
Also other solutions have listed in section 7.1 of the doc below http://www.ftdichip.com/Support/Documents/AppNotes/AN_134_FTDI_Driv...
Using a program like OnyX http://www.titanium.free.fr and have it rebuild the kernel extension cache can help if installing the FTDI driver didn't or removal didn't work.
Oh dear, the classic, "It plugged plugged it" problem. Awesome that you discovered the issue.
Q: did you install the FTDI driver v2.3 from the website?
I did go and load 2.3.... funny when checking the Extensions for FTDI.ktext I found none! I did the install as noted on Adrupilot.. Looks good ...now its off to tuning... If I can keep it straight!
Thanks Bill
That's probably due to the new security in OSX. Try this:
OSX 10.11 has a new feature called “System Integrity Protection” that blocks any kind of third party driver from being used. This is also referred to as “Rootless”. This process will turn that off and allow you to run processes that can modify system files.
sudo nvram boot-args="kext-dev-mode=1 rootless=0"