Miq1:
Correct. All that happens is: you will get the length byte first as part of the payload.
I even studied the Manchester lib code thoroughly to find if the length would be processed anywhere. No, not at all.
OK, thanks. Maybe you are using an older version.
This was some of the code I was referring to:
// added by caoxp @ https://github.com/caoxp
// compatible with unfixed-length data, with the data length defined by the first byte.
// at a maximum of 255 total data length.
if( (*curByte) == 1)
{
rx_maxBytes = data[0];
}
arduarn:
OK, thanks. Maybe you are using an older version.
This was some of the code I was referring to:
// added by caoxp @ https://github.com/caoxp
// compatible with unfixed-length data, with the data length defined by the first byte.
// at a maximum of 255 total data length.
if( (*curByte) == 1)
{
rx_maxBytes = data[0];
}
I must apologize, I missed that bit. I tried again and you are right, the length byte is used indeed. My fault was not to count that as well when giving the payload length, so instead of 4 bytes I gave only 3. Now doing it correctly, the receiveComplete() works as should be.
So here is the code again, this time using the length byte. I removed my sensor stuff from it, as it does not matter in regards to the RF transmission.