SERIN2 – SEROUT2 and Manchester mistake.

[mackrackit]

This is my best guess, but I am not sure as I do not see anything else.

Where you have IBIN16 , try not using the I. This adds an extra character to the 16 digit string. Worth a quick try?

[Kamikaze47]

This should do it:

SERIN2 RECEPTION, 16468, [ManchesterWord.Byte0,ManchesterWord.Byte1]

[RCtech]

This should do it:

SERIN2 RECEPTION, 16468, [ManchesterWord.Byte0,ManchesterWord.Byte1]

Yes, it' s the same code as bruce just posted too.
I just need to modify my serout on TXPIC too.

Nice to saw all your replies.

Lyd.

[Bruce]

IBIN16 is sending % followed by 16 bytes of data. Not just 16-bits. This produces an
ASCII 0 or 1 for each bit in the word.

Try something like;

serout2 TRANSMISSION,16468,[$55,$55,$55,$aa,Manchesterword.LowByte,Manchesterword.HighByte]

On the receiving end, try something like;

SERIN2 RECEPTION, 16468, [WAIT($aa),ManchesterWord.LowByte,ManchesterWord.HighByte]

This way SERIN2 on the receiving end simply ignores your $55 and waits for $aa before the
16-bit data packet.

[RCtech]

IBIN16 is sending % followed by 16 bytes of data. Not just 16-bits. This produces an
ASCII 0 or 1 for each bit in the word.

Try something like .../...

Well, it's fantastic, you just turned my simple remote to remote-control ;O)

Yes, your solution works fine.

Many thanx all for your fast replies.

Lyd.

[RCtech]

Well i've just done a test :

This is what i send: 0110100101100101
This is what i get on the RXPIC input pin named RECEPTION and connected to the RF 433Mhz circuit: 0110100101100101

You can see it's the same datas.

Now, if i do
SERIN2 RECEPTION, 16468, [ManchesterWord]
SEROUT2 INFO, 16468, [BIN16 ManchesterWord,13,10]

This is what i get on the RXPIC pin named INFO : 0000000000100101

So my error is a pure coding mistake, not RF.

Thanx for you help.