How do I get something like this,

0000 006C 0012 0012 0008 001D 0008 0066 0008 001D 0008 006B 0008 0032 0008 0032 0008 0022 0008 0051 0008 021B 0008 001D 0008 004C 0008 001D 0008 001D 0008 0028 0008 0037 0008 001D 0008 001D 0008 0C20 0008 001D 0008 0066 0008 001D 0008 006B 0008 0032 0008 0032 0008 0022 0008 0051 0008 021B 0008 001D 0008 0022 0008 0047 0008 001D 0008 0028 0008 0037 0008 001D 0008 001D 0008 0C20

Onto my OFA 8811?

Jp1 questions should be asked in the jp1 Forum.

Thanks, but they've got scripting errors which don't allow me to register and therefore can't post.

I don't recognise the signal type encoded in that sample of Pronto Hex. So I can't give any simple answer.

Where is that signal from? Is it one of many similar signals or is it the only one you have?

What are you trying to accomplish? (Why do you want that signal in your 8811?)

Do you have a Pronto or other remote that can use Pronto Hex?

Do you have a JP1 cable for the 8811?

I wouldn't know how to even begin to investigate that, but I have Rob's email address so I just emailed him a link to this thread. I assume he will investigate and/or ask you for more information.

Thanx, for further info, the code is from a Dreambox 7000s, from what I gather a rather nasty machine for IR codes. I've got a JP1 cable, and I've found pronto code ( this hex style ) listings for the Dreambox but I haven't found how to get those into RemoteMaster or IR.exe to get onto the 8811 ( to eventually get onto my MX-500 ).

I did a few forum searches, but I can't tell how much JP1 work has already been done for this. It's complicated by the fact that there seem to be several different related and unrelated devices called "Dreambox".

One of those is the Dreambox device you have. Another is the Dreambox remote that came with that device, that apparently is a JP1 capable remote (so you can use your JP1 cable to read the contents of the Dreambox remote's eeprom).

But in doing the search there seem to be several other devices called "Dreambox" that aren't the above two and don't use this ugly protocol. Also much of the JP1 discussion of "Dreambox" concerns using the Dreambox remote to control other things rather than using other JP1 remotes to control the Dreambox.

If you have the Dreambox remote and if it is JP1 capable, and if you want all this for programming the MX-500, I don't see why you need the 8811 at all.

Are you trying to generate original codes that are included in the Dreambox remote? Or are you trying to generate extra commands that aren't in the original command set?

The Dreambox remote has a massively ugly added protocol executor for this protocol included in the eeprom. With some effort, a JP1 expert (such as myself) could duplicate that in a form that could be used in the KM or RM program to allow it to be used in other JP1 remotes. Maybe someone already did and I just don't know where to look.

The Dreambox remote has two added setup codes SAT/1267 and SAT/1268 and seems to come from the factory with some KeyMoves already set up. If you wanted extra commands beyond what is in the factory Dreambox remote, those seem to be easiest to add as more KeyMoves within the Dreambox (maybe using other device modes if you're out of buttons).

All that can be done using the IR.EXE program communicating via JP1 cable with the Dreambox remote. Hopefully wherever you got that Pronto Hex from includes the JP1 hex command info needed to define that command (which you'd need anyway even if you were doing this as an upgrade in the 8811 rather than as a KeyMove in the Dreambox remote).

Thanks for the info, from what I know there are a number of Dreambox ( linux sat reciever ) models as well as a number of Dreambox remote models as well as a new IR keyboard which is used with the Dreambox. Basically I have a Dreambox 7000s and I believe a Dreambox V3 Remote which I think is JP1 capable as well as an OFA 8811 and JP1 cable. My problem is when I try to get my MX-500 to learn certain commands it says good but the commands don't work. From what I've read this is due to some repetition that gets confused, in any event, I've got to either download those codes ( or preferably edited version which the MX-500 can learn ) and get them into RemoteManager or IR.exe and onto the 8811 or Dreambox remote to teach the MX-500.

There's a bunch of information out there but it all seems to be about pronto codes which I'm to new at this to translate into JP1 hex or EFC for use with IR.exe.

This message was edited by broken on 04/28/05 15:26 ET.

You have that and a JP1 cable? You should try downloading the eeprom image from the Dreambox remote to IR.EXE.


Where did you read that it is due to "some repetition"?

More likely, this is just a hard signal to learn because it needs very precise timing (most IR signals can manage with very approximate timing). IR learning tends to be approximate.


Now I think you mean codes that are already in the Dreambox remote, so getting into RM and from there into the 8811 or back into the Dreambox would just duplicate what you already have.


After further search, I think the Pronto Hex you quoted was the Pronto hex Jon posted in this message:
[Link: remotecentral.com]
and specifically it was the Pronto Hex posted under the label "25 00" by which Jon meant that the JP1 hex command for that same signal is 25 00, which he said earlier in that post is the Dreambox command "Up". But both an earlier post in that thread an the info posted in the JP1 forum says 25 00 is the Dreambox command "OK". Either way it is one you can generate easily with your Dreambox remote.

Ah, a little more knowledge then, I did not know those preceding 4 digit hex codes were JP1, that helps, I guess those are without the extra Dreambox non-sense? Guess I'll try putting those on my 8811 ( don't want to overwrite the Dreambox remote at this point ) and see if the MX-500 will learn those. Basically the purpose of this is to use my MX-500 for the Dreambox, so I ordered the 8811 to mule codes between the PC and the MX-500. Thanks for your help, I'll let you know how it goes, steep learning curve on this stuff but I'm gettin' it.

I'm not convinced there IS a version the MX-500 can learn.

If I remember correctly (don't bet on it) there is some extra cost option to give the MX-500 the same kind of PC programability as the more expensive MX models (or am I totally confused?)

If the code could be inserted in the MX-500 by PC programming then it wouldn't be learned approximately so it should be OK.

For learning an edited version, it's possible that could make the MX-500 learn the signals but we don't know anything yet that indicates what edit might be appropriate.

We have no information (nor are we likely to get any) that indicates the signal generated by the Dreambox remote is imperfect.

Jon posted Pronto Hex to be used by Prontos instead of learning from the Dreambox, not because that Pronto Hex was better than (or even as good as) the original signal sent by the Dreambox remote, but because the Prontos don't learn perfectly and the posted Pronto Hex should be better than a Pronto (especially an NG Pronto) can learn from a perfect original remote.

The 8811 is good at learning. Here is a suggested experiment that I think will help us understand what is going wrong in the MX-500 learning:

1) Learn the problem signal from the Dreambox remote to the 8811.

2) Test that learned signal to see if it works, and tell us, but don't stop there even if it doesn't work.

3) Learn the same signal from the Dreambox to the MX-500. I assume the result doesn't work or we wouldn't be having this discussion.

4) Learn that signal from the MX-500 to the 8811, on a different 8811 button than you used for (1).

5) Use IR.EXE and your JP1 cable to download the eeprom contents of the 8811 and save as a .ir file.

6) Email that file to me (see email address in profile) and/or post the file somewhere (such as the JP1 group's diagnosis folder) and post its URL back here.

Then I (or other interested experts can compare those two learned signals and deduce what the MX-500 is doing wrong in the learning process and maybe deduce what could be done to fix it.

This message was edited by johnsfine on 04/28/05 15:52 ET.

This is the thread I got a bunch of info from that seemed to indicate that some repetition was getting confused, I believe you're on this one as well as a number of other folks,

[Link: remotecentral.com]

Something about a set of 18 hex pairs followed by another set of 18 that repeat, I've read on other posts that simply removing the repetition allows learning and still works.

What do you mean by "extra Dreambox non-sense"?


Won't work. Two big problems:

1) Those Pronto Hex strings are self contained. Each fully describes an IR signal. But JP1 "hex commands" have no global meaning. Each is only meaningful in combination with a JP1 "protocol executor" and a set of "fixed data". The protocol executor and fixed data you need are tied to SAT/1267 and SAT/1268 in your Dreambox remote. They are not present at all in your 8811. Unless someone created the KM or RM file already, a fair amount of expert JP1 effort is required to get SAT/1267 or SAT/1268 into the 8811 in order for those hex commands to mean anything.

2) Once it's all in there, the 8811 should produce the identical signal that the Dreambox remote produced, so if the MX-500 couldn't learn that it still wouldn't.

arg! at least I'm understanding more, about why I wasted my money ;)

Be sure to reread my post 11 which I edited, probably while you were typing post 12.


I thought that might be where you misunderstood the "repetition" issue.

Repetition is a normal part of most IR signals. The Dreambox sends these signals with correct repetition. The NG Prontos have a design flaw in the part of their firmware responsible for learning the repetition pattern. In these signals (and some others) they get confused and learn that wrong. Since the flaw is in the learning process itself (nothing wrong with the original signal they were trying to learn) there is nothing you could do with the original remote (even with extreme JP1 programming) to make them learn this signal correctly. You can only get the correct signal into them via direct PC programming.

There is no reason to believe the MX-500's problem in learning these signals is similar to the NG-Pronto's problem. There are several harder aspects to the signals. The NG Pronto's are particulary stupid about repeat pattern.