having troblue getting discrete codes for dell 50 inch tv. Hope someone can help

I am having the same issue. Have you had any luck yet?

If you are looking for the Dell W510C then I think we have the info we need.

It has taken an act of congress to get to the right person with the right knowledge and information, however, I believe this is it.

I have downloaded the Makehex program and will be trying to generate the pronto hex format for the codes listed in documents I recieved from Dell.

I may have to enlist the help of johnsfine IR Expert who I noticed in another thread.

I will try to post the codes I generate for on and off tonight.

Is this one of the ones that uses the MCE protocol?
The manufacturer documentation on those is seriously confusing, but I think it is explained well enough in some other threads to use MakeHex for it.

The Dell files I recieved are adobe files titled:

1.
Dell Television Remote Control Codes
For
W3201C, W4201C & W5001C
Plasma TV
Information for Partners
Version 1.1
August 3, 2005

and

2.
IR Code WaveForm
Appendix A - Example of IR transmission to work with Dell TV

I would upload these files to the site if I knew where I should or could.

I have read the Makehex readme.txt and Dell Files and have come to the following:

1. These Dell Models accept infrared remote control codes based on Philips’ RC6 Infrared protocol.
2. The transmissions use a carrier frequency of 36 kHz.
3. I assume I should use the rc6.irp file.
4. I have discrete "Button Discrete (hex)" is in the form 0x23
{example-power on = 0x23)
5. The device should be set to 0 and the function should be set to 23??

With these parameters the makehex program yeilds the following for power on:
Power On:
Device Code: 0 Function: 23
0000 0073 0000 0014 0060 0020 0010 0020 0010 0010 0010 0010 0010 0020 0020 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0020 0020 0020 0010 0010 0010 0010 0BE1

and

Power Off:
Device Code: 0 Function: 24
0000 0073 0000 0015 0060 0020 0010 0020 0010 0010 0010 0010 0010 0020 0020 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0020 0010 0010 0020 0010 0010 0010 0010 0010 0BD1

I don't have the tv to test the codes right now.
haroldzuckier or RO_MSUN give it a try

unless you see a post from Johnsfine first pointing out the obvious.

Johnsfine??

My email is in my profile. You can email them if you don't have web space to store them and post a URL.


Uploading to RemoteCentral is a very slow process. Don't use that for anything for which you're waiting for an answer. It is for sharing files others will need later and for which you don't need answers.


Philips RC6 is both a specific protocol and a family of related protocols. The RC6.irp file in MakeHex is just for the specific protocol. There are other .irp files for other members of that protocol family, including MCE, which is a member of the RC6 protocol family.


That tells you the info that is unique to "power on". But you also need info that is common to all buttons.


If it were RC6 protocol (which I doubt) the only other info you need would be the device number. But you can't just select 0 as the device number. You need the correct one.

If it is MCE (I'm pretty sure it is) you need more than just a device number. But you should be able to find other DELL MCE threads at RemoteCentral to either directly tell you all those details or at least tell you how to read them in the DELL files you have.

I got the email with the files from Dell.

The Waveform.pdf file confirms that the protocol is MCE and that all the details of the way they are using MCE match the Dell.irp file included with MakeHex.

The device number is 0 (shown as "Device Type" in that pdf file).

The other file lists the function numbers in hex. You can either translate those to decimal (see Windowns calculator in view/scientific mode) or use the MakeHex option (see its readme file) for labeling its output in hex.

The "toggle" bit is another factor to consider: Each command has two different forms (created by setting T=0 or T=1 in the .irp file. If you use the same command twice (or more) in row you are supposed to alternate the two forms. So if you want to put the same command twice in a row in a macro, make both versions in MakeHex and alternate them.

But in ordinary (non macro) use alternating two different versions of each command could be quite difficult. That Dell documentation suggests an alternative: Command 00 is a "Dummy" command that can be inserted between two copies of any other command. As a command itself, 00 won't do anything, but it will allow the TV to see the next command as a new command.

In other threads people have discussed including the dummy command as a sequence after each problem command, or (better) editing the .irp file so the dummy command is spliced in after other commands. First find out which commands have problems when used without following the toggle rules. Repeating commands, such as Vol may be very difficult to correctly splice together with a dummy command, but also may not need it. The TV may accept them even if the toggle rules are broken. The Dell documentation seems to imply that only the ten digit commands need to be fixed with a dummy command when they don't follow the toggle rules (but I'm not certain that's what they mean).

the only version of makehex I find is V4.0 updated in feb of 2004

I don't see a dell.irp in the zip

I do see in a post that you uploaded a makehex as quoted in a thread on 7-16-05

[Link: remotecentral.com]

"I just checked the last MakeHex.zip I uploaded, and I see it has DELL.IRP, and MCE.IRP and RC6-M-L.IRP any one of which can produce perfect commands for this device."

I don't see any of these .ipr's in this version of makehex.

Is there a place to download the new or updated version.

[Link: john.fine.home.comcast.net]

I just did a forum search that says I posted that URL here at RC only four previous times in the last three months. I would have guessed it was much more than that. But I think even once a month is often enough that someone doing a forum search for makehex.zip or even just makehex ought to find it.

O.K.

I was thinking I would dowload the makehex.zip from the remote central site, which is where I only found the old version 2004 posted.

I just did the forum search and saw the returns that showed the threads that have the link like the one listed above.

Thanks

Great.

I have been racking my brain on setting up macros for these screens. I am assuming I can insert the .IRP file into the MX-850 Editor to create these buttons. I will try it tomorrow and let you know.

No, you cannot use the .irp file in the MX-850 Editor.

You can:

1) Use the dell.irp file with MakeHex.exe to create Dell.hex

2) Use a text editor (such as Windows Notepad) to select the whole contents of the .hex file and copy to the clipboard

3) Use Irpanels.exe to paste in the clipboard contents and create a CCF file.

4) Use the universal browser of the MX-850 editor to drag IR signals for the numbered buttons of that CCF file into the configuration of your MX-850.

Well do.

I ran into a few issues and have not been able to work on this project. I will be gone for a few days and will be back at it early next week. I will let you know how I make out. Thanks.

Using the Dell.irp I have generated the following codes with toggle set to 0

I can check them in a few days, do you guys have a way to check them, or

as one of you indicated you already have them, if you do for the following model numbers, do these look the same , and can you send them or tell me where they are posted.


Dell Television Remote Control Codes
For
W3201C, W4201C & W5001C

Power On:
Device Code: 0 Function: 23

0000 0073 0000 0022 0060 0020 0010 0010 0010 0010 0010 0020 0010 0020 0030 0020 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0020 0010 0010 0010 0010 0020 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0020 0020 0020 0010 0010 0010 0010 09E0

Power Off:
Device Code: 0 Function: 24

0000 0073 0000 0023 0060 0020 0010 0010 0010 0010 0010 0020 0010 0020 0030 0020 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0020 0010 0010 0010 0010 0020 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0020 0010 0010 0020 0010 0010 0010 0010 0010 09D0

Once I get these working I plan to generate the discrete inputs as well.

I remember typing a response that 0x23 means hex 23, not decimal 23. Hex 23 is decimal 35.

I thought I typed that in this thread, but on rereading, I can't find it.

Anyway, I don't see anything else wrong with the signals you posted, but using command decimal 23 (hex 0x17) when you wanted 0x23, will get you wrong results.

MakeHex can be used in a way that generates hex labels (see its readme) or you can continue to use it the simple way with decimal labels and translated the documented function numbers from hex to decimal (Windows calculator in view/scientific mode can do that).

Edit: Since part of this thread is about use via IrPanels, I should also restate the fact that IrPanels does not work with hex labels. The Pronto Hex is of course in hex, but the labels (device and function numbers) must be in decimal. So you end up with buttons named with decimal function numbers. If you have documentation with hex function numbers, you have to convert each as you select the button.