What steps will reproduce the problem?
1a. send many mavlink messages to AC system, eg. 11 byte message at 100 Hz
1b. request data stream(s) with high update rate, eg. at about 100 Hz
What is the expected output? What do you see instead?
- expected: low priority handling of communication (drop, discard), high priority handling of R/C input
- seen: system chokes on the data, armed system will not accept stick thrust, armed system cannot be disarmed (when flooded)
What version of the product are you using? On what operating system?
- AC 2.6, APM1 2560
Please provide any additional information below.
- while testing a custom modification for externally controlling the APM, this issues reappeared
- it was earlier detected in the outgoing direction, i.e. requesting data streams with a high update rate
- the "flood" situation is of course not the intended mode of operation but still the core system should be robust under these conditions
Original issue reported on code.google.com by oswald.b...@gmail.com on 26 Jun 2012 at 10:17
Original issue reported on code.google.com by
oswald.b...@gmail.comon 26 Jun 2012 at 10:17