Serin serout problem

[skimask]

that is the data, serout going to the input pin of the other circuit


i also tried an f648a, nothing on the lcd
k

Ok, I'm back...the relatives showed up for a bit...had to deal with them...

Your programs:
Transmit side - output is on RB2, correct?
Receive side - input on RB3, correct?

And the big yellow wire is the data wire right?

[lerameur]

yes that sit,
Its hard to belive it works on your end.

thats ok , i was watching mad tv...

[skimask]

yes that sit,
Its hard to belive it works on your end.

Well, do me a favor....
Take that big yellow wire, follow it to the PIC on the right.
Consult your datasheet, and tell me what pin it goes to.

Then take that same big fat yellow wire, follow it to the PIC on the left, consult your datasheet, tell me what pin that goes to....and fix it!

[lerameur]

in the picture I had just finish trying all the B ports., It was in RB6, which was the last of the port I tried
the sending IS on RB2
and Receiving is on RB3

go back to the web site i posted a new picture

[skimask]

in the picture I had just finish trying all the B ports., It was in RB6, which was the last of the port I tried
the sending IS on RB2
and Receiving is on RB3

Then put up a fresh picture and change your receiver to portb.2

[lerameur]

Ok so now both receiver and transmitter are on portb.2
the picture is up

would the problem be in the software, is the pic16f88 special and need extra attention ?

[skimask]

Ok so now both receiver and transmitter are on portb.2
the picture is up

would the problem be in the software, is the pic16f88 special and need extra attention ?

It does...but I think I'm onto something....
On the receiver PIC, it shows:
Waiting...127,22
The 127 is the number of times it's tried to receive data but timed out, the 22 is the number of times it's actually received 4 bytes of data and dropped thru to the display section.
Post your receiver code as it stands again.
Something is amiss. If the serial port wasn't receiving anything (i.e. the serin statement always timed out and went back to loop, the 22 should remain a 0).