Hello,
I am trying to capture, decode and then replicate the Rf messages coming from a little remote controlled powerboard/powerstrip (http://www.jaycar.com.au/productView.asp?ID=MS6150).
So far I have been able to capture the messages using a scope (using my PC soundcard) and I have worked the messages out to be the following.
Button 1
0000000010101001011011100010111100
Button 2
0000000010101001011011000010110000
Button 3
0000000010101001011000100010010000
Button 4
0000000010101001011010100010100000
Button 5
0000000010101001011001100010000000
Each of these messages are sent after a long pulse is sent by the remote (about 2-3 times the length of a regular bit).
I am also unsure if I should be inverting these bits.
I am trying to figure out what they mean (they all appear to start with the same first 16 nibbles so I am guessing that would be the unique code for the remote) and then the next bits may be a button code and checksum.
I do however have another remote, made by the same company and I captured its messages too.
Button 1
0011001101100100000011100011100110
Button 2
0011001101100100000011000011101110
Button 3
0011001101100100000000100011001110
Button 4
0011001101100100000010100011110110
Button 5
0011001101100100000001100011010110
There doesn't seem to be anything similar between them so I am getting the impression that the whole message is unique per button, but this doesn't really make sense as I though each remote would have a code and then each button would have the same command code per remote.
They could be encoded somehow but I would have no idea where to start.
What I am trying to do is to be able to use an arduino (or other controller) to send out these messages without having to capture the code of each remote everytime. So if I wanted to add another board I would just tell the arduino to generate a new remote code and off I go.
If anyone can help me figure out how to decode the messages to have a unique remote code and then the individual button codes (which I imagine would be the same across each remote) then it would be much appreciated.
Cheers,
Dean
I am trying to capture, decode and then replicate the Rf messages coming from a little remote controlled powerboard/powerstrip (http://www.jaycar.com.au/productView.asp?ID=MS6150).
So far I have been able to capture the messages using a scope (using my PC soundcard) and I have worked the messages out to be the following.
Button 1
0000000010101001011011100010111100
Button 2
0000000010101001011011000010110000
Button 3
0000000010101001011000100010010000
Button 4
0000000010101001011010100010100000
Button 5
0000000010101001011001100010000000
Each of these messages are sent after a long pulse is sent by the remote (about 2-3 times the length of a regular bit).
I am also unsure if I should be inverting these bits.
I am trying to figure out what they mean (they all appear to start with the same first 16 nibbles so I am guessing that would be the unique code for the remote) and then the next bits may be a button code and checksum.
I do however have another remote, made by the same company and I captured its messages too.
Button 1
0011001101100100000011100011100110
Button 2
0011001101100100000011000011101110
Button 3
0011001101100100000000100011001110
Button 4
0011001101100100000010100011110110
Button 5
0011001101100100000001100011010110
There doesn't seem to be anything similar between them so I am getting the impression that the whole message is unique per button, but this doesn't really make sense as I though each remote would have a code and then each button would have the same command code per remote.
They could be encoded somehow but I would have no idea where to start.
What I am trying to do is to be able to use an arduino (or other controller) to send out these messages without having to capture the code of each remote everytime. So if I wanted to add another board I would just tell the arduino to generate a new remote code and off I go.
If anyone can help me figure out how to decode the messages to have a unique remote code and then the individual button codes (which I imagine would be the same across each remote) then it would be much appreciated.
Cheers,
Dean