Would it help if i run bootcamp on my mac or VMware or an emulator to run the windows version of APM? Or would i still have the problem that the COM port cant be found? I’m in the same situation as you guys.
[color=#FF0000]APM 2.0.16 + Yosemite (Maverick as well) + HK Mega 2.7 [/color]does not connect to the board (APM cant find the comm port)
…and have no PC available…I enjoyed the blinking LEDs on the board so far. 
My APM2.6 works as expected. Try installing the Arduino Drivers to use the APM2.x HW
from System Information
[code]Arduino Mega 2560:
Product ID: 0x0010
Vendor ID: 0x2341
Version: 0.01
Serial Number: 640323739333514062F0
Speed: Up to 12 Mb/sec
Manufacturer: Arduino (www.arduino.cc)
Location ID: 0x14200000 / 27
Current Available (mA): 500
Current Required (mA): 400[/code]
Yes, it could help if you don’t get it running on OSX. I’m working also with OSX and I had radio-calibration issues with APM-Planner. So I went to mission planner (unfortunately only for Windows) and ran it unter Win7 with VMWare Fusion. It works nicely, I would definitely try APM on Windows before you kick your hardware in the recycle bin 
Now I’m using APM Planner on OSX and I hope billbonney gets this problem with the calibration fixed, then I’m absolutely happy with APM-Planner
[quote=“filoudebruxelles”]Would it help if i run bootcamp on my mac or VMware or an emulator to run the windows version of APM? Or would i still have the problem that the COM port cant be found? I’m in the same situation as you guys.
[color=#FF0000]APM 2.0.16 + Yosemite (Maverick as well) + HK Mega 2.7 [/color]does not connect to the board (APM cant find the comm port)
…and have no PC available…I enjoyed the blinking LEDs on the board so far. [/quote]
Unfonrtunately I was’n able to run APM Planner on VMWare. APM Planner couldn’t start and the program closed. I’m stuck here.
Can you run System Information App with the board plugged in and confirm the board is not showing up as USB connected device. (or create a report for the System Information App and post it here)
Do you have a 3DR Telemetry Radio? Have you tried installing the Arduino IDE and see if that fixes it (it will install the Arduino Device Driver) see arduino.cc/en/Main/Software
[quote=“billbonney”]Can you run System Information App with the board plugged in and confirm the board is not showing up as USB connected device. (or create a report for the System Information App and post it here)
Do you have a 3DR Telemetry Radio? Have you tried installing the Arduino IDE and see if that fixes it (it will install the Arduino Device Driver) see arduino.cc/en/Main/Software[/quote]
Thanks for the hints but installation of the arduino software, nor the 2.0.17 version of APM Planner helped. Here is a screenshot of the system information showing no connection whatsoever with the board.
I have no 3DR telemetry.
What version of Mac are you using? Have you tried powering the board using a battery?
It maybe your board is dead, you could try pugging it into a PC and see if it shows up in device manager.
I have Yosemite installed on an imac and Mavericks on a macbookpro. None of them see the board. I’ll try to connect using a pc later today. Trying to convince my sysadmin at work to give me admin rights on the work laptop so i can install APM. But you know sysadmins…
Keep you updated.
You don’t need admin rights, just need to see in device manager if the USB device is recognized. My feeling here is your board is not working,
i got a pc and installed the APM 2,0 and the board works fine now. Pitty that the APM on mac is such a hassle.
Having similar issues to others in this thread running on a mac with 10.10.3. Had a working copter and 3DR radios. After I installed the latest version I’m unable to connect to my copter via USB or MAVLINK.
Tried installing new drivers. Can see /dev/cu.usbmodema0111 from the terminal when I have the copter connected, but APM is unable to connect. Tried several previous versions of AMP with no change.
Unable to even update firmware firmware on copter. says it can’t open com port.
I have no problems connecting with 10.10.3 and 2.0.17. I am not sure what the issue can be. It does look like you have two flight controllers connected as the port is enumerated to /dev/cu.usbmodem0111
What other devices do you have connected?
Same problem here.
2 Macs, iMac running 10.8.5, Powerbook running 10.6
All worked with genuine 3DR Mavlink until 2.1.4
After that, I can’t get any link at all via radio, crashes 2.1.7 - just hangs…
Installed the FTDI drivers with the 2.1.7 download, tried everything I can think of.
Used to work, now it doesn’t.
Getting very pi$$ed off!!!
I’ve spent most of today trying to sort this out.
Bizarrely, occasionally I will get a connection and everything works.
I disconnect and try reconnecting, nothing for another hour, then suddenly I’m back in.
Tried 2x different computers, 3x different 3DR radios.
Fed up now… 
Try removing the FTDI drivers see for instructions ftdichip.com/Support/Documen … AC_OSX.pdf
You probably need to reinstall afterwards, but it may help.
I don’t have a 10.8 Mac to test on, so cannot verify.
Thank you Bill. It’s bedtime in the UK, but I’ll take some more tablets in the morning and try again…!
Bill
Deleted the FTDI.kext file…
There were no receipts, so ignored that bit…
Reinstalled the FTDI drivers…
IT WORKS!!!
BOTH MACHINES!
I can disconnect and reconnect at will!
All good so far!
I’ll keep you posted…
Thank you!
I also experienced the problem that I plugged the Pixhawk into the Mac with a USB cable, started APM Planner 2.0, and the APM Planner could not recognize a COM port to the Pixhawk. After reinstalling drivers a few times, I went to the cabinet of miscellaneous cables where I found the USB cable and got two more of the same kind. The third cable I tried worked. My Pixhawk didn’t come with a USB cable, and I think the first one may only have been intended to power a device like a small radio, not open up a USB port on a Mac.
I am having this exact same issue, but with a twist. After installing APM on my Mac, I HAD the Pixhawk sending data to APM running on my Mac and I could see the GPS, elevation, and the map was local to where i was, and I WAS receiving the audible disarm alerts, but telemetry was not working. I had red on both sides (ground control and on the craft) So i watched a few YouTube videos on getting telemetry working. The only way it could connect for the radio was to use a DIFFERENT port than what had been used by the computer to connect to the craft. I dont mean a different baud rate, I mean a different serial connection entirely. There had been 4 serial connections displayed. Telemetry started working when I selected the cu bluetooth incoming port at 57600. It reported that connection was a success and populated all of the correct radio parameters and downloaded 417 config settings. But immediately thereafter and until now, despite reinstalling the serial driver and the the APM 2.0 software day build 8-18-18 which was the only one that would install without crashing, the ability to connect from APM on the computer to the craft has disappeared. It only allows me to connect with the radio 57600 connection and the other connection I used previously to connect to from APM to the craft has disappeared, thus I no longer receive any GPS data, nor any other data from the craft, nor any auible alerts. Its just sits in silence. Frustrating…any advice would be GREATLY appreciated.
Forgot to mention, Mac OS version is 10.13. My suspicion is that the xml that’s being read in after start up of the APM app that I believe is saving parameters for the drone and for telemetry settings where the parameters for each are correct (both reported or demonstrated success) MUST be what’s causing this. The driver needs to be device specific somehow. It connects to the computer via the USB when it hasnt been deleted or disabled and it works. Telemetry shows green on both ends even though no data being received by radio is supposedly correct.
I did read about following instructions for removing the conflicting driver. I did not find the D2XXHelper driver. I have reinstalled the FTDI driver 4 times now. It has worked after the first time and after the last install (briefly to connect only) then reports the connection is missing.
what I see in terminal is:
apples-MBP:Extensions apple$ ls
ACS6x.kext FTDIUSBSerialDriver.kext
apples-MBP:Extensions apple$ ls /dev/cu.*
/dev/cu.Bluetooth-Incoming-Port (this connection appears)
apples-MBP:Extensions apple$ ls /dev/tty.*
/dev/tty.Bluetooth-Incoming-Port (this connection appears)
I dont find any USB connections, despite the fact they were used to connect to APM earlier:
apples-MBP:Extensions apple$ ls /dev/usb/
ls: /dev/usb/: No such file or directory
apples-MBP:Extensions apple$ ls /dev/usb.*
ls: /dev/usb.*: No such file or directory
Previously, immediately after installing the FTDI USB serial driver I saw two usb drivers in the connect dropdown in APM Planner 2.
The two I previously saw were labelled as cu.usb and tty.usb. The cu.usb allowed me to connect to the laptop using the USB to microUSB cable. Now there are no drivers labelled as either one.
apples-MBP:Extensions apple$ ls /dev/cu.usb.*
ls: /dev/cu.usb.: No such file or directory
apples-MBP:Extensions apple$ ls /dev/tty.usb.
ls: /dev/tty.usb.*: No such file or directory
apples-MBP:Extensions apple$
I could go along with the theory that the cable wasn’t designed to connect to the drone…IF the drivers were still there. I SAW it working…
Ahhh, you gave me so much hope. Deleted the FTDI drivers from the Library/extensions folder and reinstalled with no luck.