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 - 31st May 2010 17:24
Number of Views: 5881
Since this question has come up again, I thought I'd throw this module out to the masses. It is something I worked on a while back, with DT's help. Amid life's other priorities, it got put on the shelf to collect dust.
The basic idea is that by adding the module as an INCLUDE and inserting a couple of commands inside your code, you can have the PIC send timing data to your PC via the hardware serial port. It's made for 18F PICs (although some 16Fs may work too). You also need a timer that is not being used for anything else.
1) Instructions are included, as well as a small example.
2) It worked well for me, and as I recall, DT in testing.
3) Use it however you want.
4) I won't be able to offer much support, but figure there are enough knowledgeable folks around here that can help those who need it.
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