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 - 21st May 2010 14:37
Number of Views: 7176
Hi all,
Few times ago i did this little utility to help in Timer, Usart, Eusart and PWM calc. It have been tested by some user here and there. Thanks to them
'till now, it's seems to be bug free. It assume a minimum of knowledge on your side so far.
I plan to do another version wich will be more complete. It will include more code generation tool. It's still a work in progress but once i'm fixed on the whole idea, i'll post a Trial version.
It will create code for PBP, Swordfish and probably some other compiler.
You have to know it's a tedious job to read all datasheet and be sure everything is correct. For this reason, there's no release date.
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