Hi Melanie,

Actually, it doesn't seem to make a difference whether the value for STR is variable or constant.

Also, SKIP seems to be generating the same issues...If I:

debugin timeout, error, [wait(msg),_
tmp,tmp,tmp,_
tmp,tmp,tmp,_
tmp,tmp,tmp,_
tmp,tmp,tmp,_
tmp,_
payload[0],_ 'real data starts here
payload[1],_
payload[2],_
payload[3]]

Then I get the expected bytes in payload. But if I do this:

debugin timeout, error, [wait(msg), skip 13,_
payload[0],_
payload[1],_
payload[2],_
payload[3]]

Then I get four completely different bytes in payload. Moveover, they are not bytes that I can identify in the datastream, either before or after my four "target" bytes. But then, they are not random, either.

One thing that I did not mention before, I am running at a heck of a baud rate: 115200. My setup code looks like:

'=====DEFINES===================================== =======
DEFINE OSC 20

'======Outputs==================================== =======
DEFINE DEBUG_PACING 70
DEFINE DEBUG_REG PORTB
DEFINE DEBUG_BIT 6
DEFINE DEBUG_BAUD 115200
define DEBUG_MODE 1 'inverted

'======Inputs===================================== =======
DEFINE DEBUGIN_PACING 70 '(8 / BAUD) * 10^6 us
DEFINE DEBUGIN_REG PORTB
DEFINE DEBUGIN_BIT 7
define DEBUGIN_MODE 1 'inverted

Am I doing something really wrong, or can the Pic just not handle that high of a data rate? I think that it must be me, since I don't notice any other problems (dropped or corrupted data, etc), unless I try to use the STR or SKIP commands (WAIT works fine!).

**shrugs.
**grins.

Any suggestions?

Thanks again,

Ian