I see that my upgrade is not working for the user.
I am amazed that UEI can send this signal with such a small protocol although they are using two byte EFC's to accomplish this. They just divided it up into equal timing bits and then each 1 was on, each 0 was off, and just transmitted the whole thing that way. So instead of converting a quad number into a timing pair, they would just use 0011 form -2+2. Very clever.
0011 =-2,+2
0001 = -3,+1
1000 = +1,3
1100 = +2,-2
on the other hand
we translated this to real binary and then did all the calculations.
0 = 00 to -2,+2
1 = 01 to -3,+1
2 = 10 to 1,+3
3 = 11 to +2,-2
I went back and checked and I can see that my upgrade doesn't toggle at the right frame, it should toggle at the first frame, and instead its sending a release frame like the keyboard protocol that I started it from. But for a sling user I wouldn't think that would matter because there is no "hold" so the signal should be releasing the key immediately, you'd only have two frames from the slingboxs, but this would be a problem for a regular remote user. I updated my files to correct the toggle frame to start at the second frame if the button is being held, but this wouldn't matter to the sling user.
Efrez, do the slingbox irblasters have a frequency rating? I believe that the frequency might be a problem. 56K is quite a high frequency.
I wonder if it is intentional for the notes to indicate, "CBL/2889 is the official UEI setup code" yet the setup code in the protocol parameters lists, "1889".
Efrez, most remotes can't handle 2889 as a setup code, but the newer ones can, so we'd need to make it into a lower number to work on 99% of the Jp1 remotes.