slippyr4 wrote 2011-10-17 15:37: > On 17 October 2011 13:38, Bob Ammerman wrote: > >> >> Are you sending absolutely continously at 57600? IE: With one character >> immediately after the other for many, many characters? >> > > No. My actual data rate is around 6000 bps at the moment. It will go up > later in the project. The code buffers data (e.g. NMEA) for a while, and, > when a packet is ready to go, it blasts it out asap. So the overall duty > cycle is low, but comprises of chunks of ~100 bytes at 57600 saturated, > followed by some sleep. > Do you have any flow-control ? What, more specificaly, does the "garbage" look like ? > >> >> As a test, you could modify your code to send two stop bits (but leave t= he >> windows side programmed for one stop bit) and see if the problem goes aw= ay. >> >> > I'm not sure how to do that. I've read the documentation for the EUSART o= n > the PIC but it doesn't mention a facility for multiple stop bits as far a= s I > can see. > Is it a semi-manual step? (i.e. 9 bit mode, shift my data left one bit, a= nd > set the LSB as a mark?) > > >> >> --=20 http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .