Manchester encoding

Yes, send 2 bytes.

Ken,

incode=0 'clear 16bit translation WORD vairable

rec_code=0 'clear 8bit translated code BYTE

serin2 portb.0,1646,300,noserin,[wait (qualifier), incode.lowbyte, incode.highbyte]

for rx=0 to 7 'for-next loop 8 times - BYTE vairable

rec_code.0[rx]=~incode.0[rx

send 8 bit packet, you are using it to send a word (16bits), so what is the deal there ? Why does it work with a word size... ken

by the way, I am trying to use an array with picbasicpro

lcdout $FE,$C0, bin encoded1[3]

I thought it would give the 4 th digit of the array in binary, but instead it gives me a 13 bit number... what is going on .

ken

Ken,

Forgive me for too much Xmas cheer.

My application, from memory was a simple remote control. Instead of taking a byte, encoding it each time a button was pressed and then sending it I just used a 16bit already Manchester encoded WORD constant and sent that - in two parts. Lowbyte and then highbyte with a qualifier byte and perhaps a preamble at the start.

Serout or Serout2 sends in user specified values like 8N1, 8bits, no-parity, 1-stop bit. Thats 8bits or one byte at a time so for a WORD vairable it takes two bytes for a WORD - lowbyte and highbyte. If you read the PICBASIC PRO manual you'll see that it drops the preamble, qualifier and other Serout bits. Manchester encoding takes a single byte (8bits) and makes it a WORD through encoding (16bits). Serout2 can't handle that directly so you need to break it down into bytes - lowbyte/highbyte. Hence the encoding/decoding required.

I have dug out the printout that I used to do what I needed and below is the code provided by Greg Yent from the picbasic.com forum archives. Alter it to suit your needs.

TempWord VAR WORD TXData VAR BYTE RXData VAR BYTE

'assign your special data to TXData

ENCODE:

for i = 0 to 7 TempWord.0[i