search

Owne / ardupilot-mega

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

APM 2.xx XBee packet loss #303

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.Load APM 2.xx 
2.Set XBee data transfer rate to 38400, 57600 and 115200
3.Do an XCTU range test and monitor bad packets
4.Load APM 1.xx and repeat steps 2 and 3 and you will notice....

What is the expected output? What do you see instead?
I expect communications between both XBee modules to be near 100%.  What I find 
is that with APM 2.xx I get that result with a transfer rate of 38400 and 
significant loss of packets with either 57600 or 115200.  Upon reloading my APM 
with 1.xx with the same parameters I get 100% transfer rates with all three 
baud.  Please try and recreate this problem.

What version of the product are you using? On what operating system?
I am using APM 1.xx and 2.xx.  APM 2.xx seems to be bi-directional platform and 
may have a timing issue that prevents transmission where as APM 1.xx seems to 
be uni-directional.

Please provide any additional information below.

Original issue reported on code.google.com by Delorean...@gmail.com on 27 Mar 2011 at 10:15

GoogleCodeExporter commented 8 years ago 
What he means to say, is a range test on all three data transfer rates. I've 
also reproduced the loss on transfer rates above 38400

Original comment by Draconis...@gmail.com on 27 Mar 2011 at 10:22

GoogleCodeExporter commented 8 years ago 
YAY!  I'm not alone!

Original comment by Delorean...@gmail.com on 27 Mar 2011 at 10:23

GoogleCodeExporter commented 8 years ago 
there is a problem with the new fastserial library. i will direct to the 
correct person i tested 2.0x with the older version and it apears to have fixed 
the problem.

Original comment by Meee...@gmail.com on 28 Mar 2011 at 1:03

GoogleCodeExporter commented 8 years ago 
FastSerial.cpp and FastSerial.h are the files

Original comment by Meee...@gmail.com on 28 Mar 2011 at 10:57

GoogleCodeExporter commented 8 years ago

Original comment by Meee...@gmail.com on 29 Mar 2011 at 8:28

GoogleCodeExporter commented 8 years ago 
This problem should now be resolved, problem lied in updated adc library.

Original comment by Meee...@gmail.com on 29 Mar 2011 at 11:18

GoogleCodeExporter commented 8 years ago 
Ok thanks so now I just reload APM 2.xx using the Planner and it should be all 
fixed?

Original comment by Delorean...@gmail.com on 30 Mar 2011 at 8:45

GoogleCodeExporter commented 8 years ago 
Mike - can we "close" this issue?  Just set the status to "Fixed"

Original comment by dewei...@gmail.com on 31 Mar 2011 at 8:00

GoogleCodeExporter commented 8 years ago 
i was just waiting to see what other said, but it looks good.

Original comment by Meee...@gmail.com on 1 Apr 2011 at 12:20