Struggling with first byte received

[HenrikOlsson]

Hi Bert,
No, if you expect 16 bytes you should read RCREG 16 times - one for each byte received. Obviously you have to wait for each byte to actually come in (signalled by the interrupt flag beeing set) but I know you knew that.

As the sending device is sending a byte the USART recevies it by shifting it into the input shiftregister (you can't access this register). Once all bits of the byte are properly received the byte is automatically transfered to the FIFO and the interruptflag is set. When you read RCREG you'll automatically get the byte from the FIFO.

Receiving 16 bytes is no different really, you just need to retreive the bytes one by one and put them in your software buffer/array/whatever.

There should not be any need to throw anything away but apparently there's something strange going on in your case which is why I asked if it is the very first byte after startup or the first byte in every packet that gets read as 0.

Hard to say what's going on really without seeing the code....I'd probably take a step back and just send a single byte and make sure that the it gets received properly.

/Henrik.

[cncmachineguy]

Sorry Henrik,

I Ment to say I wasn't sure if it was only the first byte. I don't think I looked past it last night to see the rest.

I will tinker with it some more tonight.

I am sure if I posted the code, You or someone else would point out the error directly. But that is my fallback position. First I must be sure I have tried all I can to locate the trouble. Just my nature. I like solving these things, and I remember better if I do vs. if someone else points it out to me.

So I start with making sure I fully understand what it should be doing, then I have things to compare it to.

The sending device is a DSM2 Rx, so no stopping the data or sending 1 at a time. I can however, connect another pic and simulate the Rx. that may be worth a go
if I can't get to the bottom of this.

[cncmachineguy]

Well as it turns out, it seems to be just the first byte after startup. Now this I can deal with using a flag or 2.

See, not looking past the first packet is the kind of things I do when it's too leate and I should be sleeping.