does anyone have a clue about the hdmi code? it is really driving me crazy. how could they have all the codes but this one it doesnt make any sense any help that anyone can giw to come to a solution woulld be greatly apprcietied

John:

Thanks for your post. Interestingly, the two approaches (MakeHex and the excel spreadsheet) give different encodings:

From MakeHex:
Device Code: 07.07 Function: 1B
0000 006D 0000 0022 00AC 00AC 0015 0040 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0040 0015 0015 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0015 0015 0015 0015 0040 0015 0040 0015 0040 0015 0689

From the excel spreadsheet:
0000 006D 0000 0022 00AC 00AC 0015 0040 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0040 0015 0015 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0015 0015 0015 0015 0040 0015 0040 0015 0040 0015 0680

Unfortunately, neither code worked (code 1b; TV (ant) input) on my TSU3000 tring to control my HLP4663.

Btw, the contents of my makehex control file (NecX2.irp) is:
Device=7.7
Function=0..255

Protocol=NECx2
Frequency=38000
Time Base=564
One=1,-3
Zero=1,-1
Prefix=8,-8
Suffix=1,-78
Default S=D
Form=;*,D:8,S:8,F:8,~F:8,_

John, in earlier posts, I've seen people use device code 7; your post recommended device 7.7. What are these codes and how does one go about figuring out the correct one to use (other that sending posts to bboards like this, of course!!)

Thanks for your help. I would still love to find a discrete code for TV input; using the DVI TV/Vid sequence can work, but I don't like the 5 second delay I've had to introduce into my Pronto config....

Thanks,

-- Dave

On 11/08/04 18:31 ET, johnsfine said...

You use one of several tools for generating Pronto
Hex, such as "bmontini's Excel spreadsheet" mentioned
earlier in this thread (and linked to in some
recent thread here) or my MakeHex program.

For MakeHex, you'd need to know that the protocol
is NECx2 and the device is 7.7

You ought to use MakeHex from command prompt with
the -h switch, rather than via the drag/drop method,
ecause that will give you function numbers in
hex rather than decimal, so you won't need to
convert in order to use the list in this thread.

These numbers need a translation before they can
be used with the OFA remote. If you want them
for the OFA remote, I'll explain that translation.
But if you want them for a Pronto, MakeHex is
easier and better.

Dave,

The Pronto hex is very close between both commands. The only difference I see is the gap (the final hex word) between frames 0680 v. 0689 and that minute difference will not matter.

To be hyper-technical the NECx2 protocol per the Samsung data sheet calls for 108 mS total frame lengths. To have MakeHex calculate that you would use these statements in the irp file:

Device=7.7
Function=0..255

Protocol=NECx2
Frequency=38000
Time Base=564
One=1,-3
Zero=1,-1
Prefix=8,-8
Message Time=108m
Default S=D
Form=;*,D:8,S:8,F:8,~F:8,1

The difference being that I removed the suffix= statement and replaced the "_ " at the end of the form statement with a 1. I also added the Message Time=108m and make hex will adjust that final off time so that the frame length will be exactly 108 mS. MakeHex calculates the Pronto hex to be 06E9. Again, this is not the issue here, since all of those gap numbers are close enough to work. 0680, 0689, and 06E9 represent 43, 44, and 47 microseconds respectively. IR accuracy is generally +/-10%

That value will vary slightly when you change the device number. The Default S=D statement will allow you to use Device=7.7 or Device=7 and get the same results. Most other NEC family protocols use Default S=255-D that is the binary complement of device. By convention NEC1:24 means that the subdevice is the binary complement or NEC1:24.231. AFAIK, most if not all NECx variants have S=D, but 7.7 seems easier to reduce confusion.

All these conventions were established largely by John Fine who has also written a number decoding programs for Pronto ccf and hex and RTI TT cml files.

There is a readme file with MakeHex that covers some of these points, but I learned it's features through using it a lot and a similar program written by Barry Gordon that shared their irp syntax initially but both have drifted to some degree as John and Barry added features.

John:

Thanks for the info; I'll try the changes and see if that makes any difference. I'm still very unclear if anyone has had success with a discrete code to set the "TV" (ant) mode on the Samsung HLP-series sets. From the posts, it sounds like some have had success; I'm wondering what is different about my environment.

Since Jon and I tend to post similar things in similar threads, you may want to be clearer about who you're replying to.


I'm sure it won't, and Jon said it wouldn't. He explained some things about MakeHex and IR timing just as general information, not as something that would be useful to change.


The codes are posted in so many places someone must have them working.


There was a lot of discussion quite a while ago about a Samsung device shipped with firmware that didn't have discretes, for which they charged (more than I thought it was worth) for a firmware upgrade that included discretes. Is this that device? Even if it isn't, there is a good chance it is another example of differences between firmware versions.

Anyway, you won't get it to work by tweaking that signal. Maybe there is some entirely different signal that would work. More likely your firmware version doesn't support that discrete.

IIRC, in this case the origin of the "antenna" command is a spreadsheet from Samsung that lists it among the discrete commands for the newer models. Most of the commands listed work but AFAIK, no one has found the "Antenna" command to work.

So, to reinforce John Fine's point (and mine earlier), it is NOT a problem of tweaking the IR command, Samsung apparently forgot to set their firmware in the TV sets to accept the Antenna command.

Jon:

Thanks. The info (and confirmation) is appreciated. Overall, the HLP-series TV has been great, but it really is ashamed Samsung didn't get the codes quite right....

-- Dave

Any updates on the ANT command? I have a HL-P5663W.

Thanks

-Stefan

I've talked with two "tier 2" support tecs from Samsung in the last 24 hours regarding the correct and complete discrete codes for input selection on the HLP XX63W-series DLP TVs. The first tec sent me an excel spreadsheet to convert Samsung hex codes into Pronto IR codes. The sheet appears to be identical to the "bmontini's Excel spreadsheet" described earlier in this thread. It also contains the same hex codes for HLN, HLP, Plasma, and LCD Samsung TVs that have also been posted to this thread.

Needless to say, many these codes, when translated into Pronto form using the supplied spreadsheet do not work. Specifically, the HDMI, DVI, and RF codes do nothing.

When I called back, the second tec swore that there was no new firmware available for the HLP XX63W series. He said he would report my findings back to his boss and have him contact Korea to try to get me some answers (the tier 2 tec was in New Jersey).

I'll report back when I get a response from Samsung. I can post the spreadsheet to this forum, if there is interest, but as the information it contains matches what's already been reported, I'm not sure it's worth the download time (even using broadband....)

-- Dave

Can the Samsung DLP discrete codes work for Samsung SP-46L5H LCD RPTV?

Model SP-46L5HX would also work....



Petri

Has anyone found a code that works for the CATV input. I have an HL-P4663W and an HL-P5063W and none of the codes in this thread or in files for CATV work. I hve tried tons of different variations.

What happens when I push CATV discrete is "CATV" shows up in blue on the TV, but it does not switch the input to the CATV input. Am I missing something? I have even tried to write a macro to go to a discrete and then push *source*, but it is not deterministic from from experience due to the way samsung handles source switch toggle.

Paul

Sorry for the last post. I just went through all the samsung threads I could find and noticed that this issue has already been discussed. I still wish I new how to resolve it.

The following code works for direct access to the Antenna 1 input on my HLP-5674W. I believe I got it from the other thread on the Samsung DLP's.

"Antenna 1"
0000 006d 0000 0022 00ac 00ac 0015 0040 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0040 0015 0015 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0015 0015 0015 0015 0040 0015 0040 0015 0040 0015 0689

Tech reported a strange effect the other day. I have a remote with ONs and OFFs for the Samsung.

I have a page with 2 buttons that code out like this.
On On On delay .1 On
Off Off Off delay .1 Off

From this page the TV works as expected.

Now I have a page that is for System off that includes other codes...
Something like
Sony Recevier Off
Sony DVD Off
Samsung TV Off
Sony CD stop

There are various delays in therre to make sure that everything shuts down.

Here is the fun part. After getting the system shut down the TV will not come back on without unpluggin it.

This is what the field guy reported. Today I am going to see if I can sit with a Samsung and see if there is a IR code conflict that tells the DLP... SHUT OFF TO DEAD. This used to happen in one generation of panasonic DVD players.

Anyone else seen this yet?

I have the Exccel file that Montini posted which has the Samsung TV Discrete Key layout and the Hex to IR code and the IR code to Hex workbooks, but my problem is I am not quite sure what to do with them. Say for instance I am looking for the discrete codes for the DVI input...it shows on that Excel file as being 8A. What can I do with 8A to get that either straight onto my MX-500 or to the URC-8811 so I can teach it to my MX-500. I think I found some of the codes that you are talking about when referring to EFC numbers, like 138 for DVI1 and 255 for DVI2. I tried both of those codes in my URC-8811 and the green light on the front of the TV responded to the signal by flashing the light, but the TV did not change inputs or show any other response. Any help would be greatly appreciated. Thanks!