JP1 Remotes

[andyross]

I'm trying to add the Comcast Thomson DTA to my 8811. I downloaded both the RM and KM files, and tried both KM and RM to get it into IR. Neither one works. All I can get is the '0' key to work, sometimes. I hope, as it always seems to be, something stupid I did. Any ideas?

The files used are in:
http://www.hifi-remote.com/forums/dload.php?action=file&file_id=8009

The RM and KM files include the originals and my modified (_8811) versions.

[The Robman]

Does the box still respond properly to the original remote?
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!

[andyross]

Yes. The original remote works fine. The 8811 seems to be sending codes as the lights blink, but only the '0' key sends a 0, although I think with one of the files, a few other keys also seemed to be recognized as 0.

[andyross]

I'm still having problems.

I did a test where I factory reset the remote and had it learn the Channel up and down keys. For some reason, BOTH keys were treated as channel down by the DTA. When I looked at the learned codes in IR with version 2.40 of decodeir.dll, the codes were different. They even matched the settings in the RM and KM files.

Any idea what is going on? Is the 8811 incapable of outputting XMP properly?

By me, Comcast just encrypted the expanded digital channels, so I am limited to analog (grainy) for the next 4 months, or need to start using the DTA.

[vickyg2003]

Well I can shed a little light on what is going on.

The Notes section says

xmp-1 62.16 (Even though dev2 says 23, the output is 62.16)

I loaded the IR into my 8811 and shot this at my Widget

Output is coming out as

XMP-2 62.16

I've read enough to know that there are two function areas in XMP (can't really visualize this), depending on where the function appears in the signal its XMP-1 or XMp-2. So apparently this is shooting the incorrect xmp type.

There is a whole long thread about the XMP protocol. If you modify the Jar and the protocols INI you ought to be able to get this up and running. Here are the instructions that were given to me.

Instructions for getting XMP to work.
http://www.hifi-remote.com/forums/viewtopic.php?p=85043#85043

Here is an IR file that shoots this as XMP-1, as the notes suggested.
http://www.hifi-remote.com/forums/dload.php?action=file&file_id=8174

If you need more help, let us know.
_________________
Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.

[andyross]

That worked. Looking at your file and mine, the only change was the 'Fixed data' entry for the device. It changed from 17 0F 44 3E 1F 00 00 to 17 0F 44 3E 1F 00 40. I took my latest version, changed it to 40, and now it works, too.

Playing with KM 9.19, I had to change the XMP type from 1 to 2 to make the change in it. Is something backwards someplace?

[The Robman]

The change to the fixed data isn't what did it, it was the change from XMP-2 style to XMP-1 style. If you were to open your upgrade in RM and keep the "Dreambox" protocol, you could still make it work by transferring your OBCs over to the sub-device column and setting all of the OBCs to zero.
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!

[andyross]

As I mentioned, when I updated my settings in KM 9.19 (I wanted to tweak a few keys), I simply changed the XMP from 1 to 2. I don't know why KM seems to be backwards. Or maybe some of these DTA's are XMP1 and others are XMP2?

[vickyg2003]

Since Andy had enclosed a RDMU file, I used Remote master to change his remote to XMp1

If I select device 62,16 XMP1 from Remotemaster and KM 9.19 you get two different upgrades. Remotemasters Output agrees with Graham's Decode.

Upgrade Code 0 = 38 00 (Cable/0000) XMP 62.16 type-1 (KM v9.19)
6C 00 01 17 0F 44 3E 1F 00 00
End

Upgrade Code 0 = 38 00 (Cable/0000) xmp 62.16 xmp1 (RM v1.98beta7)
6C 00 01 17 0F 44 3E 1F 00 40
End

Both KM and RM provide the same protocol upgrade, so it looks like Mike's KM is backwards. Since I've looked at the output when that last parameter is 40, and it is putting the function codes in the first function byte, while the placing it in the second function byte if that parameter is 00.

I've quoted both protocol upgrades below to make sure I didn't miss any differences.
Upgrade Protocol 0 = 01 6C (S3C8+) XMP (KM v9.19)
43 8B 71 8B 05 00 00 69 01 67 08 0A F0 C0 04 0A
C0 60 C0 0E 04 07 C0 88 C0 B6 C8 08 CF 10 09 6B
05 E4 0A 09 B0 0A C0 C5 F6 FF 4E 6C 08 48 0D C6
F8 13 D7 F6 01 58 49 0D F6 01 0A FB 02 6A F0 46
08 80 08 C8 7B E2 37 5E 3F 46 08 10 00 C0 56 C0
0F 56 07 F0 44 C0 07 6C 03 F6 FF 63 C6 F8 17 F1
F6 01 58 3C 04 F6 FF 73 F6 FF 73 6E 3A F7 1C 12
8D 01 4C F6 FF 6E F1 C6 C7 26 56 C2 0F 6B 09 C6
F8 00 3E F6 01 58 2A F7 AF
End

Upgrade protocol 0 = 01 6C (S3C80) XMP (JP1) (RM v1.98beta7)
43 8B 71 8B 05 00 00 69 01 67 08 0A F0 C0 04 0A
C0 60 C0 0E 04 07 C0 88 C0 B6 C8 08 CF 10 09 6B
05 E4 0A 09 B0 0A C0 C5 F6 FF 4E 6C 08 48 0D C6
F8 13 D7 F6 01 58 49 0D F6 01 0A FB 02 6A F0 46
08 80 08 C8 7B E2 37 5E 3F 46 08 10 00 C0 56 C0
0F 56 07 F0 44 C0 07 6C 03 F6 FF 63 C6 F8 17 F1
F6 01 58 3C 04 F6 FF 73 F6 FF 73 6E 3A F7 1C 12
8D 01 4C F6 FF 6E F1 C6 C7 26 56 C2 0F 6B 09 C6
F8 00 3E F6 01 58 2A F7 AF
End
_________________
Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.