By lowering the baud rate you're now allowing device B (and SERIN2) twice the time to receive the bits and assemble the byte.
That's probably what's helping a lot more than any line noise issue.
...
Tumbleweed, I had very strong suspicions that the issues were in the communication lines. I changed the Baud rate from 19200 to 9600 and I haven't got anymore wrong data at the receiver. I remember...
Ioannis, yes I'm doing data validation checks all the time. The first byte of the array is always 174. If this condition is not met, then the reading is discarded.
Published on - 27th May 2010 02:01
Number of Views: 8371
This is an effort to help users understand how the I2C command works by comparing it with SHIFTIN/SHIFTOUT. A serial EEPROM, 24FC1025 will be used in the example.
Published on - 1st May 2010 04:59
Number of Views: 4376
With all of the added benefits or the new forum, a useful feature has been lost. This is the "Today's Post" link that was found in the "Quick Links" drop down. Due to compatibility issues with future updates from vBulletin this link can not be brought back.
But there is a couple of ways to do the same thing using the same amount of mouse clicks once it is set up.
...
Re: SERIN2 Receiving Wrong Data
The sending device has the typical 18F4550 USB setup and it is set to "Define OSC 48". The receiving device is set to "DEFINE OSC 16".
rsocor01 Yesterday, 19:56