converting pronto codes into discrete codes

dtitzer · Post by **dtitzer** » Tue Jun 12, 2007 8:10 am

I've been looking for something simple and concise, with no luck, on how to convert discrete pronto codes into functions on my OFA 9910 remote. FYI, I've got a Samsung HP-S5053 and my 9910 does not have the extender loaded/activated. I want to assign codes to L1, 2, 3, and 4 to my HDMI1/DVI, S-Video1, HDMI2, and AV-1 inputs respectively to handle the HD Cable box, Tivo, DVD, and VHS VCR respectively.

I've been using IR for a while and have been able to make macros, switch things around, etc. just fine. But I got a new 50" plasma tv, and I want to to assign discrete codes for the inputs to "L" buttons on the 9910. This sounds like I'm supposed to use keymoves, but I'm lacking info on what to do with the pronto code blocks. I got those codes from remote central. I downloaded IRtool, but I'm not sure I need it.

Just to be clear, I didn't obtain a complete file, I just found a page of discrete codes. I'm uncertain which tool to use to get these into IR and assign to a key.

If there's a cookbook you can point me to, I'd appreciate it.

johnsfine · Post by **johnsfine** » Tue Jun 12, 2007 1:09 pm

You need the correct IrTool (There exist both original and new incorrect varients of IrTool that don't work with DecodeIr. There is one IrTool varient that does work with DecodeIr) and you need DecodeIr.

Remote Central file
or
https://www.hifi-remote.com/forums/dload ... le_id=3886

and
http://john.fine.home.comcast.net/ir/Decode_IR_DLL.zip

With that, you can decode those Pronto Hex strings and get the protocol name, the device number and the OBC and EFC numbers.

The protocol name and the device number should match those built-into your chosen setup code. If you're using an upgrade you can easily check that. If you're using a built-in setup code that works for basic functions of the device, you may find it easier to just assume the protocol and device number of that setup code are correct (unless/until proven otherwise).

The EFC number can then be used to create the KeyMove. In most cases that is redundant with the OBC number. In more difficult cases you need to use RM or KM to create an upgrade (even if you will be using a built-in setup code not that upgrade) so you can use the OBC number instead of EFC number and have RM or KM compute the Hex command that you use instead of an EFC number to set up the keymove.

If you tell us what built-in setup code you're using, someone will tell you whether it uses EFC numbers the simple way (most do) or must be done the hard way.

dtitzer · Post by **dtitzer** » Tue Jun 12, 2007 1:50 pm

I'll ditch the version of IRTool that I have now, and replace it with the one you recommend, with the DLL and give it a whirl. So, when I cut/paste the pronto code block, I should decode it and use the EFC from that in a keymove? Okay. Sounds straightforward. Should the EFC be long (like the pronto code) or short? My first go-round with IRTool, which might not have been with the correct version, output some info that I didn't know how to use.

Just guessing here, but is the replacement DLL (and using an IRTool that uses it) the key to getting OFA codes instead of just regenerating pronto codes?

I'll give it a whirl very soon. I will be "offline" for a little over a week, but will return with good news or more questions. I'm excited about getting this working because it will allow me to further simplify things. I also found some other codes for aspect switching that might prove useful under limited circumstances.

I'm not anywhere near my remote or my own computer right now, or I'd read off the setup codes.

Thanks for the info. I'll be in touch.

johnsfine · Post by **johnsfine** » Tue Jun 12, 2007 2:21 pm

If you have the right IrTool and you have DecodeIr.dll in a place where IrTool can find it, you get a pop up dialog with JP1 decode info when you press Decode.

After you press OK to that dialog (or if you don't have the right version, or if it didn't find decodeir) it will show you decode info from IrTool's built-in decoder, which is not very useful to you.

An EFC number is always a three digit decimal number (it will use leading zeroe(s) if it is less than 100).

dtitzer · Post by **dtitzer** » Tue Jun 12, 2007 2:51 pm

Hmmm. I do recall getting a pop-up box with info, showing it was using NEC1.1 protocol, etc. which seemed completely normal. Are you saying, then, that the EFC number I need will be displayed on that pop-up, and that I can ignore the info in the main window?

johnsfine · Post by **johnsfine** » Tue Jun 12, 2007 4:12 pm

dtitzer wrote: Are you saying, then, that the EFC number I need will be displayed on that pop-up, and that I can ignore the info in the main window?

Yes.

dtitzer · Post by **dtitzer** » Tue Jun 12, 2007 7:34 pm

Okay, it looks like I got IRTool from the same place your link points to. I updated the DecodeIR.dll with the new one, but I get the same results.

The TV (Samsung HP-S5053) shows setup code 2010 when I select it on my remote, FYI. Date of manufacture is late summer/fall of 2006, don't recall the month.

I'll try the codes soon. Thanks loads for your advice, John.

dtitzer · Post by **dtitzer** » Thu Jun 21, 2007 7:34 am

Okay. I'm back. I got to try out the discrete codes, and not all of them are working for me.

I can use the power on/off codes for the Samsung TV (hp-s5053) just fine. The only other code that works right is the one that selects "SVideo-1" for my TiVo box. The others cause the blue power light to flicker (which happens when you send any IR command to the TV that is recognized by the TV), but nothing happens. I'll double check my keymoves. I did zero-pad the front of the code to three digits if it was less than three.

I noticed that the page of pronto codes I got these from isn't model-specific. That page of codes lists more inputs (three S-Video inputs when I only have two, etc.) than I have on my TV. Does anybody have better info on discrete codes for this model and it's set of inputs?

johnsfine · Post by **johnsfine** » Thu Jun 21, 2007 8:43 am

dtitzer wrote:I noticed that the page of pronto codes I got these from isn't model-specific. That page of codes lists more inputs (three S-Video inputs when I only have two, etc.) than I have on my TV. Does anybody have better info on discrete codes for this model and it's set of inputs?

Long ago, when I was paying more detailed attention to threads about Samsung discretes, I concluded that they varied by firmware rev within a model just as much as they varied by model. It was an ugly mess that no one seemed to have a handle on.

I don't know whether any of that has changed.

Given that Samsung discretes are such a difficult question, I think your best chance is to look in past threads (and/or ask new questions) in the forum where it has been discussed the most:
http://www.remotecentral.com/cgi-bin/mb ... e/list.cgi
rather than in JP1 forums.

So for any questions about how to make your JP1 remote send a specific signal, you're in the right place. For any questions about what signals your Samsung device will understand, I think you're in the wrong forum.

dtitzer · Post by **dtitzer** » Sat Jun 23, 2007 9:57 am

Thanks. I ran through a load of stuff from there, and got the codes I needed.

Key to this was use of some Samsung HLS5087 codes posted by PHSJason (post 29) in the Discrete Code Hunter forum.

This link will drop you straight to his listing:
http://www.remotecentral.com/cgi-bin/mb ... samsung#29

I only have one issue, but I brute-forced it: I have a VHS VCR connected to a coax input (cable3/TV), but don't know how to directly address it. I just created a macro to select DVI/HDMI1, then toggle/roll one input. If there's a better way to select "TV" antenna inputs, please let me know.