why does data missing occurs in rf modules
"traxonja" sugessted that
"maui" has given you a nice sample of Manchester.
The detail analysis shows, that the code suggested by "maui" is not a Manchester one, you could rather call it "the maui code".
Furthermore, to get the correct pattern at the receiver side for ALL possible patterns, the "maui code" should also be worked out a bit. (Not all patterns are decoded correctly at present).
To say the true also "real Manchester code" probably will not correct the problem.
Example:
1 1 1 will be converted by "manchester" into 10 10 10 according to "corruption description" will be received as 00 00 00 and ???
I do not know what to do next ?
The string is too short of 1's to convert the string from "two bit manchester" to "single bit data" => death end!
"Munib" presented "coruption rules" as follow:
transmitted 110001
11 ----------->received 10000110
and explain it as :
"if there are more than one consective 1s then only first 1 is converted to 0 and all others are received correctly"
I suspect that the physical transmission is carried out in "reverse" order.
In the presented string
the first "1" is marked
red but the second "1" is marked
blue.
On this base I came to conclusion that the software solution can use the following convertion (code):
1=> 11 and 0=> 00 on transmitter site
and
received
10 OR 11 are converted to 1 ; received 00 is converted to 0 (read all data from
right to
left!)
A few software checking mechanisms can be added:
1.
01 is not a valid bit pair
2. 11 MUST be proceeded by
10
3. bit PAIR sequence
10 11 is not allowed