# Q2686 UART receive buffer size is limit only 56? **URL:** \ **Category:** Legacy AirPrime modules\ **Created:** [May 22, 2010, 7:43am UTC](https://forum.sierrawireless.com/t/q2686-uart-receive-buffer-size-is-limit-only-56/4436 "2010-05-22T07:43:41Z")\ **Posts on this page:** 1\ **Showing post:** 10
**Author:** ![awneil](https://avatars.discourse-cdn.com/v4/letter/a/49beb7/32.png) [@awneil](https://forum.sierrawireless.com/u/awneil)\ **Post date:** [April 18, 2011, 6:28am UTC](https://forum.sierrawireless.com/t/q2686-uart-receive-buffer-size-is-limit-only-56/4436/10 "2011-04-18T06:28:22Z")
Obviously (well, it should be obvious), the first thing you need to determine is whether the external device is actually transmitting the junk, or if there’s a bug in your software that’s causing the junk to appear. > [@raveesa](#): > > Here is the example data I have received at q 26 > MK1CA3001D371C1F+++ÿ++++ > 0AA1001D351C1E0AA2001D381C1F09A4001C391BÁ > 1905KM001D371C1F+++ÿ++++ How, exactly, did you obtain those traces? Is the “junk” always at the end of the “good” data like that? > [@](#): > > since q2686 uart rx buffer can receive maximum of 56 bytes It’s not a limitation of the Q26 buffer - it’s just how FCM works. > [@](#): > > I have implemented the arbitrary-sized “fragments” to receive whole 90 bytes of data Maybe there’s a bug in your software implementation? Maybe there’s a bug or fault in your hardware - eg, are you sure that you have the levels correct…? Are you sure that the external device’s baud rate is absolutely correct? > [@](#): > > How to over come his problem …? FCM just delivers to your application whatever it receives - so, if you get junk, that’s what was received… --- _[View the full topic](https://forum.sierrawireless.com/t/q2686-uart-receive-buffer-size-is-limit-only-56/4436)._