JP1 Remotes

Hello,

I have a SkyPerfectTV remote here the Issue is that it's doesn't seem to fully support this protocol Kaseikyo-162.42.

So I also tried to manage that but still don’t know how to do this.

If you look in my RMDU file for this remote (also in attached zip folder) in Remote Master you will see the next it setup.

Protocol: Kaseikyo

Protocol Parameters:

OEM1: 162
OEM2: 42
Device: 8
Sub Device: 23
E: ????

So “E” parameter should be a constant value in Remote Master but if you look in IR files you will see that for each key it is vary!!!

In old Keymap-master tool I saw the same issue.

Files can be found;
https://www.hifi-remote.com/forums/dload ... e_id=11017

Cheers Phil

While looking at any one of these signals, they appear to be KaKaseikyo-162.42. When you look at the whole group of them you can see that they don't follow the E rule and need to have a custom executor. I can see a pattern in the function part of the code, but I don't understand the "mathmatical" relation necessary to create a code for it. I'd like Rob to have a look and see if he can create an 8bit code. Now that the new remotes can handle a 16 bit code for efc's we don't absolutely need to do it in 8 bits, but it certainly is a good practice.

The 2nd byte is created by XORing the OBC byte with "11101001" and that appears to be an XOR of the 3rd and 4th bytes.

If you want to see how I worked it out, look here:
https://www.hifi-remote.com/forums/dload ... e_id=11018

Columns Q thru X are the OBC binary
Columns Z thru AG are the XSUM binary
Columns AI thru AP are my generated version of the XSUM
Columns AR thru AY tell me if I got it right.

To generate the XSUM I did an XOR of the corresponding OBC bit with the bit in the first row (ie, AI1 thru AP1). I started with all zeroes in the first row, then changed them to 1 if needed to make the generated column correct.

The Robman wrote:The 2nd byte is created by XORing the OBC byte with "11101001" and that appears to be an XOR of the 3rd and 4th bytes.

Thanks Rob I'll take a look.

Cheers Phil

My reply was actually directed to Vicky so she would know how to generate a custom executor for you.

Thanks Rob, I never would have understood the pattern.

Phil,

I've got an upgrade with the protocol, but when I shoot this I'm seeing GAP instead of kasekio, but they look identical to me.


https://www.hifi-remote.com/forums/dload ... e_id=11019

See if this works.

Vicky

The checksum for the Kaseikyo (Panasonic) protocols is always an XOR of some combination of the previous bytes (or nibbles) with the OBC byte, so rather than try to figure out which combination, I just determined what binary value was needed to make it right. Then I looked at the fixed bytes to see if there were any obvious candidates.

Thanks to both of you I will give the file a go and get back to you.

Cheers Phil

Hi Vicky,

So my colleage tested the file you've sent and he couldn't get it to work he's saying.

"I captured signals of binaries which I created from that file which JP1
experts sent us and after comparing signals data from original IR files with what I captured I found difference:

Original files:

Key “1”: {36.4k,436,msb}<1,-1|1,-3>(8,-4,A:48,1,-74.8m)+{A=$455401E808E1}; Alt leadout form: ^136m

Key “2”: {36.4k,436,msb}<1,-1|1,-3>(8,-4,A:48,1,-74.8m)+{A=$455401E88861}; Alt leadout form: ^136m

Key “3”: {36.4k,436,msb}<1,-1|1,-3>(8,-4,A:48,1,-74.8m)+{A=$455401E848A1}; Alt leadout form: ^136m


What I captured:

Key “1”: {36.7k,437,msb}<1,-1|1,-3>(8,-4,A:48,1,-75.0m)+{A=$455410E808E1}; Alt leadout form: ^137m

Key “2”: {36.7k,437,msb}<1,-1|1,-3>(8,-4,A:48,1,-75.0m)+{A=$455410E88861}; Alt leadout form: ^137m

Key “3”: {36.7k,437,msb}<1,-1|1,-3>(8,-4,A:48,1,-75.0m)+{A=$455410E848A1}; Alt leadout form: ^137m


As you can see the difference in constant part of data. And also there is a small difference in carrier frequency

Original is 36.4k and here we have 36.7k, but I don’t know if this really can affect."

Is this a difference a problem that could be stopping the remote from working?

Cheers Phil

455410E808E1
455401E808E1

Yes I see that difference 01/10 difference. Hmm, I wonder what I did, because I had that part down pat, or at least I thought I did. I was seeing the minor frequency difference which was my main concern.

I have to dig out the computer I was using, to check and see where I went wrong. I was dealing with an ancient computer when doing this, because my regular computer was waiting with a replacement video card. I decided to do a memory upgrade as well, so left the cover off. When I got the memory installed and went to put the cover back on, I had my knee on the Widget cable, and when I straigtened the tower back up, I ripped the USB end off the thing. Doh, I'm such a klutz!!! I Anyway Tommy shipped my new Widget, so I should be back in business soon.

Hey Vicky,

That was a bit unlucky USB heads are usually pretty tough, but don't worry there's no hurry.

Cheers Phil

Oops, typo. The third device should have been 128 instead of 8 making the third fixed byte FE instead of EF, and comped 01h instead of 10h.
I updated the file.
https://www.hifi-remote.com/forums/dload ... e_id=11019

Hi Vicky,

thanks I will get my colleage to retest the new file. If you don't get a reply from me today about how it went. Please bear with me until after the 4th of next month as I will be on holiday, and have no access to work emails.

Once again thanks I will replay ASAP.

Phil

Have a nice holiday! And thanks for letting me know that the reply will be delayed. Lack of feedback is one of the biggest pet peeves of most of the posters on the board.