"Fowler, Paul B." wrote:
>
> Does this mean I need to "clrf RCREG" ???

No, I don't think you can write to RCREG, just read from it.

> Or does the process of "movf RCREG, w" take care of that?

Yes

> How do I empty the buffer?  (Lazy Fowler should go back and read the
> DataSheet again... but no, he asks the piclist instead....)

Such is life as Ned Kelly once said.

        movf RCREG,W    ; flush receive buffer
        movf RCREG,W

Note, that during the "short" time it takes to execute these
instructions, a new byte could be in the process of being received by
the UART, in which case the RCIF flag will be set again once it is fully
received.

If the RCIF flag is set, even disabling the serial port and re-enabling
it will not clear it.

If the receive buffer has 2 bytes in it's RX buffer and the serial port
is disabled, then they must "both" be read out to clear the RCIF flag
before new reception takes place or the OERR flag will be set on the
first received byte after the serial port is re-enabled.

Reading the RCREG while the serial port is disabled will clear the RCIF
flag when the RX buffer is empty.

As a point of interest, if you disable the serial port (SPEN=0)and write
a byte of data to the TXREG, then as soon as you re-enable the serial
port (SPEN=1), that byte of data is immediately sent if TXEN remains
set.

> Most importantly, can this be effecting the encoder to cause it to go so
> slow?

I don't know. I haven't done encoded transmissions before.

I have used RS232 radio links and I noticed that it (my system) took a
short time to begin the transmit, so that sending a byte and ACKing it
back took about 200mS. I don't know if that was because the system was a
spread spectrum unit.


--
Best regards

Tony

mICros
http://www.bubblesoftonline.com
mailto:sales@bubblesoftonline.com

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu