Hey guys could really use your help here. Building first quad.
I have the APM 2.5 and had the mission planner installed all working fine, Usb from laptop to APM and would connect. Was simply waiting for my transmitter and receiver (Spektrum DX7, Ar8000) to be able to do anymore. Once I binded the receiver to the transmitter I went back to the laptop to do the rest of the checks but now I can't even connect now?
I get 'No Heartbeat Packets Received' so a little confused whats the problem? It connected fine last night, I had the AR8000 connected to the APM for power when binding.
Was this ever resolved? I am having the same problem
I had / have the identical same problem.
Reverting back to MissionPlanner 1.2.76 solved it, thanks.
Interestingly this problem occurred on system using windows 8.1 and usb 3.0, I also have MissionPlanner latest version installed on an old Netbook running windows XP, which has not shown this problem even with the latest rev of MissionPlanner.
I'm guessing its a USB timing problem associated with one of the USB drivers that's enclosed in each MissionPlanner.msi file.
Update for anyone interested:
Running an older version of MP solved my connection problems (version 1.2.76 worked in my case).
Something seems to have been broken since that version; the MP developers might want to take a closer look into this issue...
If anyone needs the older installer, PM me, and I'll provide a download link.
Thanks a bunch to @Antonio for providing the older installer...
I am new to this, but have been reading some of the discussion. I am also having the same problems with the new MP. Could I possibly get an older version (1.2.76) download link from you also?
Hello, I'm new here...
I'm having almost the exact same problem.
This *appears* to be an issue with Mission Planner and connecting via USB, perhaps one of the recent updates broke something? I know it sounds strange, but here's why I think its due to MP (at least in my case):
Is anyone else experiencing these symptoms?
Since I don't own an official 3DR board, I can't go to them for hardware support.
Still, I really think that this should be a software issue (based on everything I noted above).
If it doesn't end up being fixed, I'll be forced to connect via radio from here on out, or struggle trying to do the brute-force connection via USB.
Oh sorry I never answered this. I got in contact 3dr and they sent me a new one and I returned my old one. Have not tried the new one thou as I am in the middle of moving houses.
Did you ever solve this problem as i am having exactly the same issues.
If i load version 2.91b using MP then i can connect at 115000 on COM11, if i then load version 3.01 i cannot connect using same baud and port. Does 3.01 have something extra in the firmware its waiting for before enabling mavlink?? If i go back to 2.91b then again i can connect.
I had a connection problem like you have and I found that I needed to use a powered USB hub to connect to the APM because the APM was pulling more current than the PC/laptop USB port could supply and the voltage dropped below 4.0 vdc.
I can update the firmware on the APM, and I can connect via the terminal. So maybe there I can do something?