PB builder error with Protocol ID

Post by **The Robman** » Sat Jan 03, 2009 2:15 pm

You're very close, so here's my report card.

First off, when you try converting the signal to binary, you need to make a best guess as to which pairs are the logical 1s and 0s, and whether the signal should be read as MSB or LSB. This is a subjective judgment, so there is no correct answer as such, but once you make your selection you do need to be consistent with it.

In my opinion, the 1 pair is "+550 -1600" and the 0 pair is "+550 -550" and the signal is MSB. You appear to agree as the OBCs and device codes that you used in KM match this, and you have MSB selected as the signal style in KM, so so far so good.

The problem is in the PB file because there you have "+550 -550" selected as the 1 pair (rather than the 0 pair). UEI typically gets this backward also, which is why we usually treat their executors as COMP'd. In order for the executor to work with the 1s and 0s backward, you would need to select MSB-COMP in KM.

Also, I notice that you have the leadin selected as "1st frame only" whereas in the learns I see the entire signal repeating while the button is held, so this should be "Same Every Frame". You have 'Repeat Value" set to 1 to force a minimum of 1 repeat, this is redundant as you will always get 1 repeat of the signal, this feature is needed if the device requires 2 or more repeats even with a short press. Entering 1 shouldn't do any harm, but it does waste code. Finally, you have the leadout time entered as 54,650 uS with the "OFF as total" set to YES. As the leadout time is consistent regardless of how many 1s are in the data, this should be set to NO and the correct time entered, which is -25,600.

Regarding the original learns, it looks like you accidentally re-learned the 0 button when you tried to learn the 1 button. The shift-right learn shows us that the 3rd device code is 0 in shifted mode and 16 in normal mode, so you would need a 2nd upgrade if you wanted to include shifted functions. Alternatively, you could treat the variable data as 2 bytes to make it a combined upgrade.

The GUIDE, MUTE and INFO buttons are all the same, so that's either how it is or it's a learning mistake. Likewise for SWAP and CC.

Looking at your codes.txt files shows me that you didn't use the rounding feature in IR, so converting the pairs to binary would have been harder for you. I rounded everything to the nearest 50, which only gave me a couple of 600 times, if I'd have used 550 it would have been even better.

The following zip file contains my attempt at a PB and KM file, plus it also includes my timings text file and the spreadsheet that I used to get the OBCs.

http://www.hifi-remote.com/forums/dload ... le_id=6071

frankstallone · Post by **frankstallone** » Sat Jan 03, 2009 10:19 pm

Wow Rob, We did it! What I dont understand is why yours works and mine didnt. Let me explain. I goofed and gave you a slightly different protocol builder file than my original. In the walkthrough it said sometimes the 1 doesnt have the longer off time so I actually reversed all the numbers (switched 0 to 1s) and changed the off and on times of 1s and 0s. So I had it right, just not on the original one. What I dont understand is why you have a much longer upgrade code than I had. Is that because you mapped all the buttons and I didnt?
I took my original protocol builder file, changed what you suggested that I change, loaded it into the remote, and they didnt work. I imported your settings, loaded it into the remote, and it worked! One other thing I noticed that you did is you posted like 3 different protocols in the notes section of keymap. Is there a reason for that?
My next step is to create a slingbox upgrade file. I am guessing the only thing I have to change is change the remote type to the proper slingbox file instead of the 8820 remote I am using and I should be done?

Rob.... thanks for all the help man... I appreciate it!

Post by **The Robman** » Sat Jan 03, 2009 10:34 pm

Did you go back over your PB file and make all the changes that I listed, including the leadin and leadout changes?

Your KM file only had the arrow buttons programmed, whereas I put all of the buttons in my KM file.

Your KM file only had the HCS08 code, so it would only be good for the limited number of people with HCS08 remotes. If someone with an S3C8 remote, including the Slingbox, were to try using your KM file, it would give them a "protocol unavailable" message, so that's why I included a few other variants.

To use this with the Slingbox, you'll need to open it using RM (as KM doesn't support the Slingbox) and change the selected remote to the correct Slingbox (probably the PL version for you), and then you should export the code as a binary file.

Be sure to name the upgrade correctly and load it up to the file section.

frankstallone · Post by **frankstallone** » Sat Jan 03, 2009 10:45 pm

Rob, I did make the changes but maybe I missed something. The only reason I ask is because I will have to go back and re-learn the dupe codes. So I think I understand what to do with the slingbox but I am stuck in one place. I realized that keymap doesnt support the slingbox so I will have to use remote master. You said I need to open "it" with RM. Can you give me a bit more detail about what I need to open in remote master?

Yes I did confirm that it is PL version. Also, will my 2000 device code still work here?

Thanks again

frankstallone · Post by **frankstallone** » Sun Jan 04, 2009 12:09 am

OK Rob, I think I got it. I used the protocol from protocol builder, and I pasted the Button list from keymap into remote master, exported to .bin and put it in my slingbox folder. I have chosen that .bin as my remote for control in slingbox but it isnt controlling my unit. I know it is outputting because I can see it with my camera, however it isnt outputting the correct codes.

Here is my .rmdu

http://www.hifi-remote.com/forums/dload ... le_id=6074

Any thoughts?

frankstallone · Post by **frankstallone** » Sun Jan 04, 2009 9:04 am

HAH. Rob. I jumped the gun! I got it... I wasnt selecting a dvd player as the device... I selecting "other device" to choose my upgrade file. So it seems to work... But here is a question. Will the slingbox cable box device support play/pause controls? With a DVD player chosen as the device, I wont have guide and info controls but I was thinking a cable box would.

Thanks again for all the help!

Post by **The Robman** » Sun Jan 04, 2009 10:18 am

The "it" in the earlier message was the KM file that we created. If you "cut & pasted" the codes from KM to RM, you made the job a lot harder than it needs to be because RM can open KM files directly.

If your PB file was EXACTLY the same as mine, your signal would work. I pointed out 3 or 4 primary differences. All I can suggest is to open them side-by-side and see which change you're missing. Or, better yet, scape your PB file and try starting again, using the additional knowledge that I gave you earlier and see if you come up with the same PB file as me.

Regarding the BIN file, unlike with remotes where certain buttons are not available in certain modes, all of the buttons are available in all of the modes, so don't worry about the transport buttons.

frankstallone · Post by **frankstallone** » Sun Jan 04, 2009 10:22 am

So I got it all working, but what about the F buttons? There are about 4 extra codes that I need support with, and remote master says it has these F-buttons but when I asign functions to them, I cannot access them within the slingbox software. Is there a way that I can gain access to these buttons?

Post by **The Robman** » Sun Jan 04, 2009 11:16 am

I don't know what an F button is.