JP1 Remotes

jfath · Joined: 16 Feb 2004 Posts: 9 Location: Bloomington, IN

Is there a way to move an upgrade from RM (downloaded by modem)
to RM?

The upgrade is for a Samsung TS160 sat receiver. There is an
upgrade file available that I can load into RM, but it is different in
some way than the one that came from UEI. I don't know enough
to tell what's different, but when I look at the upgrade code produced
by the file in RM and the upgrade code downloaded from the remote
in IR, the codes are very different.

Modem UEI upgrade:
5A 00 BE FE C1 31 6F 6F .....

Upgrade file:
5a 18 3e fe 3e f3 1f 6f 6f .....

The reason it matters to me is that I'm using an IrMan and Girder to
control my home theater. I've taught Girder to recognize the buttons
from the original TS160 remote and Girder recognizes both the original
remote and the UEI upgrade as identical. It does not recognize the
signals from the upgrade file as being the same. If I were to
use the upgrade file, I would have to relearn the buttons in Girder
and then the original TS160 remote wouldn't work with Girder.

Oddly, the receiver will work with the file upgrade or the modem
upgrade, but girder sees a difference in the serial stream IrMan
produces.

The modem upgrade is missing some keys that the upgrade file
includes and I want to mess around with some of the mapping,
which is why I want to get it back into RM.

The upgrade text file uses a device type of cable and I've tried
changing that to sat along with playing with protocols, etc., but
I don't know enough to know what might really be different.

That's the long story that brought me to the qyestion of whether
it's possible to move the modem update data into RM.

Any help is much appreciated.

Jerry

The Robman · Posted: Mon Feb 16, 2004 1:28 pm Post subject: Re: Upgrade from IR to RM

johnsfine · Posted: Mon Feb 16, 2004 1:44 pm Post subject: Re: Upgrade from IR to RM

The Robman · Posted: Mon Feb 16, 2004 1:58 pm Post subject:

And that KM file does indeed use the parm rather than the NECx2 selection! I was trying to figure out the data in the second snippet, especially the "1F" part, so your explanation was useful.
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!

Mark Pierson · Posted: Mon Feb 16, 2004 3:02 pm Post subject:

I just updated the file to use 'NECx2' so the problem doesn't occur in the future. Wink

_________________
Mark

jfath · Joined: 16 Feb 2004 Posts: 9 Location: Bloomington, IN

Thanks for all the replies. I'll try the new file Mark posted (I assume
it's in the Yahoo files section now).

A couple of comments/questions:

Yes, I was using Samsung_SIR-TS160_tuner.txt

I did notice that buttons I learned from the remote showed a protocol
of NECx2 while the file showed NEC2.

I'm using RM v0.86 which I think was current as of a couple of days
ago.

If there was a decimal/hex problem in importing, I wouldn't have
expected the receiver to respond correctly to the remote once
I uploaded that upgrade? The receiver recognized those codes and the
ones from the modem upgrade, but the bit streams were different
enough that Girder didn't match the ones from the file. It did
match bothe the ones from the modem upgrade and the original
Samsung remote.

Finally, I still have to ask, is there a way to move the data from the
modem upgrade into RM so I can work in that environment, or is
it simply not possible?

Thanks again.

Jerry

The Robman · Posted: Mon Feb 16, 2004 3:48 pm Post subject:

jfath · Joined: 16 Feb 2004 Posts: 9 Location: Bloomington, IN

Once again, thanks for the info.

I'm hoping I can skip the whole thing - my concern is that the new
upgrade file will still work with the receiver, but not be recognized
as identical to the original remote when using Girder. The new upgrade
shows fixed data of E0 6F 6F in IR, whereas the modem upgrade
shows fixed data of 31 6F 6F. If the bitstream doesn't match the
one from the original remote, I can't use the OFA and Samsung
remotes interchangeably - not essential, but a plus

Obviously, I don't understand enough about IR bitstreams to know
how/why two different streams can both control the receiver, but
be different enough in pattern that Girder doesn't see a match. I've
read the IR primers, but I'm still learning - thanks for your patience.

Jerry

jfath · Joined: 16 Feb 2004 Posts: 9 Location: Bloomington, IN

It was a little worse than I expected. I downloaded the new upgrade
file from the Yahoo files section. It does show NECX2 protocol when
loaded into RM (v0.88), but when I copy the upgrade into IR and
upload, it doesn't control the TS160. The old upgrade file (which
shows NEC2) does control the receiver OK.

Let me know if I can do anything to help test.

Jerry

The Robman · Posted: Mon Feb 16, 2004 4:41 pm Post subject:

It still sounds like RM is corrupting the data somehow. "E0" is not a valid value for the first byte of fixed data when using the 5A executor. John or Greg will have to comment on what RM might be doing (if anything).

For us to be able to check the data, you would have to post the block of code that you're copying from RM to IR here for us to look at. In the short term you could try editing the data yourself, replacing whatever garbage data gets put in that first position with "31".

To do this, click on EDIT, then look for the "6F 6F" pair, the 1st byte is the one before that pair.
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!

johnsfine · Posted: Mon Feb 16, 2004 5:02 pm Post subject:

It looks like we have several errors in the protocols.ini file entry for NECx2.

It has this:

[NECx2]
PID=00 5A
CmdTranslator=Translator(lsb,comp)
CmdParms=OBC=0
DevParms=Device Number,Sub Device=[0],Parm:$=31
DeviceTranslator=Translator(lsb,comp,0,8,16) Translator(lsb,comp,1,8,8) \
Translator(comp,2,8,0)

If you change the Last two of those lines to
DeviceTranslator=Translator(lsb,comp,0,8,8) Translator(lsb,comp,1,8,16) \
Translator(2,8,0)

then the fixed data will be computed right. The default for subdevice is still displayed wrong and computed differently wrong. Maybe I can figure that out later or maybe Greg will need to. For now, make sure the device and subdevice are both 9 for this upgrade.

jfath · Joined: 16 Feb 2004 Posts: 9 Location: Bloomington, IN

Before I do any mapping - just importing the new TS160 KM file into
RM v0.88 gives:

Upgrade code 0 = 64 88 (Cable/1160)
5a 00 01 e0 6f 6f
END

Jerry

Mark Pierson · Posted: Mon Feb 16, 2004 5:14 pm Post subject:

johnsfine · Posted: Mon Feb 16, 2004 5:26 pm Post subject:

I need to check whether my install of RemoteMaster is healthy, since I'm seeing a bunch of problems and I'm not sure which are really RemoteMaster problems and which are due to my computer being set up for developing RemoteMaster rather than ordinary use.

I try to import that KM upgrade and
1) It tells me "Could not find an exact match for the remote" and offers me a choice of RDFs with the correct one already selected.
2) I click OK, but it ignores the choice of RDF and opens with the wrong remote selected.
3) It translates the Parm value to 1F, so I need to erase that to get the correct value of 31 (which only works because I fixed the protocols.ini as decribed above).
4) None of the buttons have functions assigned, even though in the Km file they did.

jfath · Joined: 16 Feb 2004 Posts: 9 Location: Bloomington, IN

Yep, after changing protocols.ini, I get 1f,6f,6f and the new NECx2
upgrade file does control the receiver correctly.

I still don't understand why the UEI modem upgrade had 31,6f,6f.
I imagine that's a clue as to why the original remote and modem
upgraded OFA don't produce the same bitstreams as the RM upgraded
OFA. That won't matter a bit to most people, though, so I guess I'll
either live with it or try to learn enough to investigate intelligently.

Thanks again for all the help.

Jerry