Are you using the ERRORS parameter in your #use rs232 directive?  If not,
a simple framing error will hose the whole works.  Also - is the data
coming from the IR receiver inverted, or not?  What's your #use rs232 line
look like?

Dale
--
"Curiosity is the very basis of education and if you tell me that
curiosity killed the cat, I say only the cat died nobly."
          - Arnold Edinborough


On Wed, 5 Dec 2001, Kevin A. Benedict wrote:

> Hi Everyone,
> I am trying to build an IR circuit to TX/RX serial data. I saw the project
> at http://www.rentron.com/Infrared_Communication.htm I built the same circuit
>
> as in figure 6/7. Except, I used a 2N3906 instead of the 2N4403 transistor.
>
> I am using a F628 to send a 40khz carrier wave and then am combining it with
>
> the serial data  out of pin B2. I checked the 40khz carrier on a scope it looks
>
> fine. I checked the serial data on hyper term. That looks fine. When the
> IR Leds xmit they send to a GP1U26X module. This is connected to a F84, like
> in figure 7. ( I know the GP1U26x has a different pin out than fig. 7) Basically
>
> I have the data-out pin going to my rx pin on the pic. and am receiving garbage.
>
> However, if I hook the rx pin to TX from my PC serial port it works fine. I
> can echo the characters back to hyper term and display them on an LCD hooked
> to the
> F84.
> I am using CCS C and basically am just waiting for character in a while loop
>
>  while(1) {
>  j++;
>  if(j>=17) { lcd_putc("\n                 \n");j=0;}
>                                 //clear bottom line at 17 chars
>  c=getc();                     // waits for a char on rx pin
>  lcd_putc(c);                 // puts char out to lcd
>  putc(c);                    // puts char out to PC serial port
>           }
>
> Code works fine when hooked to serial TX pin,  does not work from data-out of
>
> GP1U26x.
> I would greatly appreciate any suggestions.
> Thanks in advance,

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.