mrAyaz / ardupilot-mega

Automatically exported from code.google.com/p/ardupilot-mega
0 stars 0 forks source link

MP - connect to APM - Click cancel does nothing #519

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?

1. In Mission Planner connect to APM
2. Click Cancel before connection established (or fail-to-connect with 
telemetry before 30 second timeout).
3. Nothing happens, i.e. no cancel - Mission Planner continues to try connect 
until end of timeout.

E.g Clicked cancel after 2 seconds > Terminal screen after 30 seconds:
...
MAVLINK: wait time out btr 0 len 0
MAVLink readpacket read error: Timeout
Mavlink Bad Packet (crc fail) len 0 crc 65535 pkno 0
MAVLINK: wait time out btr 0 len 0
MAVLink readpacket read error: Timeout
Mavlink Bad Packet (crc fail) len 0 crc 65535 pkno 0
MAv Data: len 0 btr 0
941 start
MAVLINK: wait time out btr 0 len 0
MAVLink readpacket read error: Timeout
Mavlink Bad Packet (crc fail) len 0 crc 65535 pkno 0
MAVLINK: wait time out btr 0 len 0
MAVLink readpacket read error: Timeout
Mavlink Bad Packet (crc fail) len 0 crc 65535 pkno 0
MAv Data: len 0 btr 0
785 start
MAVLINK: wait time out btr 0 len 0
MAVLink readpacket read error: Timeout
Mavlink Bad Packet (crc fail) len 0 crc 65535 pkno 0
MAVLINK: wait time out btr 0 len 0
MAVLink readpacket read error: Timeout
Mavlink Bad Packet (crc fail) len 0 crc 65535 pkno 0
MAv Data: len 0 btr 0

---
Using MP 1.1.40, Win XP

Original issue reported on code.google.com by graham.d...@gmail.com on 21 Feb 2012 at 7:54

GoogleCodeExporter commented 8 years ago
this will be fixed in the next version.

Original comment by Meee...@gmail.com on 22 Feb 2012 at 8:04

GoogleCodeExporter commented 8 years ago
The change for this is done now. Thank you.

Original comment by graham.d...@gmail.com on 24 Feb 2012 at 7:11

GoogleCodeExporter commented 8 years ago
Just recived my brand new device.

It did this for the first try.
MP is 1.1.51

Please help.

I was newer able to connect.

Original comment by gabek...@gmail.com on 13 Mar 2012 at 10:05

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
If i use 1.1.51 I can't connect. Only if i go to terminal first, and than to 
mission planner and connectin agin, but will not work the way it should.

If i push the reset button on APM while connecting, than it connects as it 
should.
Srange...

Version 1.1.50 works just fine.

Why is that?

Till it is solved i will use 1.1.50

Original comment by gabek...@gmail.com on 14 Mar 2012 at 2:52