JP1 Remotes

alanrichey wrote:At the worst, I can 'tweak' the buttons so the correct codes are sent, but that isn't a very professional solution and won't fix what appears to be a (hopefully minor) bug in the new XMP protocol.

It's doubtful that the XMP protocol executor could change OBC 1 into OBC 34, as it simply transmits it as-is (ie, 8-bit MSB, the same interpretation as DecodeIR). It is more likely that OBCs are getting mapped to the wrong buttons, or the wrong OBCs are in use. If you learned the codes from the Harmony, perhaps the learns are corrupted enough that DecodeIR can't correct for the errors.

Hi both

Mike: Thanks for that. I just thought it might be something like the problem pointed out by 'mathdon' in this thread http://www.hifi-remote.com/forums/viewt ... 3&start=90 where he said it could send incorrect OBCs.

(And I can confirm I have changed the entry in my Protocols.ini to DefaultCmd=00 )

Also have to say that the learn using my Harmony looked very clean and very logical, i.e. the OBC s for the numbers were 15,1,2,3,4,5,...

For Rob: I have zipped up 4 ICT files at http://www.hifi-remote.com/forums/dload ... le_id=7990

They are for the 1,2,3 keys which are decoding as OBC 15,1,2 and the LIST button which is decoding as OBC 34. And as we know pressing the '2' button on the final Slingbox remote is sending 34.

I just looked at the ict files and can confirm that Alan got the right OBCs and set up the RMDU file correctly. Maybe I need to take another look at the Slingbox version of the executor.

Zetvoo, could you try more buttons and try and compile a list of what each button really does please.

Alan, if I look at your .rmdu file with a text editor, all the hex codes show as 2-byte ones. Are you absolutely sure you changed DefaultCmd to 00 rather than 00 00 on the XMP (Slingbox) protocols.ini entry before you created the file?
_____________
Graham

Interesting, I see what you mean when I compare it with other RMDU files. But I am certain I changed it. The PROTOCOLS.INI I have amended is in the same folder as the Remotemaster.exe file I am using.

Is it worth manually editing the RMDU to remove the second byte and rebuilding it ?

BTW, this is the entry in my Protocol.ini: (I haven't added the other XMP protocols as I will never use them - is that naughty ?

[XMP (Slingbox)]
PID=01 6C
VariantName=JP1Slingbox
DevParms=Device=62,Subdevice=16,OEM Code=68, Final Frame Toggle:bool, XMP Type=0:XMP-1|XMP-2
DeviceTranslator=Translator(1,4,0,4) \
Translator(1,4,8) \
Translator(2,8,16) \
Translator(0,8,24) \
Translator(1,4,32,4) \
Translator(1,4,44) \
Translator(3,1,48) \
Translator(comp,4,1,49) \
XMPsumCheck(BF00,4) \
XMPsumCheck(00B0,36)
FixedData=10 0F 44 3E 00 00 00
CmdParms=OBC
CmdTranslator=Translator(0,8,0)
DefaultCmd=00
Notes=This version is for use on the Slingbox only.\n\
Device and Subdevice match the values given by DecodeIR. OEM Code defaults to 68\n\
Select XMP1 or XMP-2 for XMP Type as indicated by DecodeIR (default is XMP-1).\n\
If the commands also include a Final Frame, check the Final Frame Toggle checkbox.\n\
The XMP (JP1) protocol will always require a protocol upgrade, but in most cases will\n\
result in a smaller upgrade than the XMP (UEI) protocol. If any of the commands decode as\n\
XMP-1/2 (or have an OBC-2), you must use the XMP (UEI) protocol.
Code.S3C80=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 E6 0D 02 F6 FF 47 C6 F8 9E E5 \
F6 01 58 F6 01 0A 46 08 80 08 C8 7B EC 37 5E 3F 46 08 10 00 C0 56 C0 0F 56 \
07 F0 44 C0 07 6C 03 F6 FF 5C C6 F8 17 F1 F6 01 58 4C 04 F6 FF 6C F6 FF 6C \
6E 4A F7 1C 12 8D 01 4C F6 FF 67 F1 C6 C7 26 56 C2 0F 6B 09 C6 F8 00 3E F6 \
01 58 2A F7 AF

Good catch Graham, I didn't notice the 2-byte hex codes. To fix it, select a the JP1 version of XMP then re-select the Slingbox version and, assuming that you have the right entry in protocols.ini you should get the single hex codes.

Works for me

I've rebuilt the BIN files at http://www.hifi-remote.com/forums/dload ... le_id=7976 I'll PM Zetvoo to re-cehck them.

Cheers

Al

First of all I would like to sorry that I didn't write back but recently I was very busy.
Secondly I would like to set right: I have 2 STBs (5809C i 5810CDX) and I have table code to second. I try get table code of 5809C.
Thirdly I would like to THAKNKS YOU for doing bin file. It works almost perfectly- menu button display channel's options but it's really just a detail

Zetvoo: Thanks for the feedback. No need for the code table now, if the BIN files work we have the codes already.

Do you need a BIN file for the 5810CDX as well ?

Pity about the MENU button. what does the Options Button (Custom 10) do ?

Rob/Graham: Well done for all the work on fixing the XMP protocol. Obviously I can live with the 'double' selection, but do you intend to fix it ?

alanrichey wrote:Obviously I can live with the 'double' selection, but do you intend to fix it ?

IIUC, the reason you needed to do the double section is because when you first created the RMDU file, you had the bad 2-byte entry in protocols.ini but as you've since fixed that, the double selection took care of it. In other words, if you create a fresh upgrade now, you won't need to double select anymore.

zetvoo wrote:Thirdly I would like to THANK YOU for doing bin file. It works almost perfectly- menu button display channel's options but it's really just a detail

Good to hear. Please document all the buttons that are incorrect in anyway so we can fix the source file.

The Robman wrote:IIUC, the reason you needed to do the double section is because when you first created the RMDU file, you had the bad 2-byte entry in protocols.ini but as you've since fixed that, the double selection took care of it. In other words, if you create a fresh upgrade now, you won't need to double select anymore.

Absolutely right I had it in my mind that I had created the RMDU after I changed the Protocols file but now I recall, it was before, and as you say a clean build is fine.

The Robman wrote:

zetvoo wrote:Thirdly I would like to THANK YOU for doing bin file. It works almost perfectly- menu button display channel's options but it's really just a detail

Good to hear. Please document all the buttons that are incorrect in anyway so we can fix the source file.

I suspect that is probably the way the user who created the entry in the Logitech database decided to setup his system, so the Menu button pulled up the Options function. So that is what my Harmony learned. So I just need to work with Zetvoo to determine what the correct code for Menu should be.

alanrichey wrote: Do you need a BIN file for the 5810CDX as well ?

Pity about the MENU button. what does the Options Button (Custom 10) do ?

I need also a BIN file for the 5810CDX If it's not a problem for you I will ask you for do it. code table is here: http://www.hifi-remote.com/forums/dload ... le_id=7997

when I press the MENU button it doesn't display stb's menu but display channel's options: audio, subtitles, display and teletext.

zetvoo wrote:I need also a BIN file for the 5810CDX If it's not a problem for you I will ask you for do it. code table is here: http://www.hifi-remote.com/forums/dload ... le_id=7997

Afraid I can't find an ADB 5810CDX even when I Google it. And it doesn't exist on the Logitech database so I can't load it on my Harmony. And I'm afraid the code table is not enough, we need to figure out the underlying protocol and device numbers. So we are a bit stuck with that.

zetvoo wrote:when I press the MENU button it doesn't display stb's menu but display channel's options: audio, subtitles, display and teletext.

I knew that from your previous post, what I asked was what happens when you select the Custom 10 button, which should display those options. It is possible the original user simply reversed the 2 buttons.

Al

As it sounds like there may be a button or two missing from the codeset that was in the Harmony, I have made a test upgrade that uses a sample of the missing button codes. Use this RMDU file to make a Slingbox bin file and try it out. Most of the buttons won't do anything, but you may find one or two that do something. If that is the case, make a note of which button does what and we'll add them to the main upgrade file.

http://www.hifi-remote.com/forums/dload ... le_id=8000

alanrichey wrote: what I asked was what happens when you select the Custom 10 button, which should display those options. It is possible the original user simply reversed the 2 buttons.
Al

sorry but I don't understand your question. what should I check?
BTW I have also problems with 2 buttons: when I press GUIDE it display INFO, when I press INFO it display GUIDE. I exchanged that codes but after that EXIT button doesn't work. Further more I had to put 2B of code but other codes have only 1B.