JP1 Remotes

The Robman · Posted: Tue Aug 03, 2004 11:54 am Post subject:

Hey Capn,
If you also have a KM file for this, could you load that also please. Remember that while RM can read both RMDU and KM files, KM can only read KM files.

Thanks,
Rob
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!

Capn Trips · Expert Joined: 03 Oct 2003 Posts: 3990

Capn Trips · Expert Joined: 03 Oct 2003 Posts: 3990

Mark Pierson · Posted: Tue Aug 03, 2004 5:41 pm Post subject:

johnsfine · Posted: Tue Aug 03, 2004 5:58 pm Post subject:

My personal design goal for this aspect of RM, was that when the same set of device and OBC etc. information can produce the same final signals out of the remote via two different "protocol executors", they should have the same protocol name in protocols.ini and RM should pick the better one for your model remote and the other should be unavailable.

My hope was that the end user would only need to worry about the set of signals to be reproduced and not about too many details of how that occurs.

With two or more cooks (Mark and Rob and Greg and I, to name a few) at each of two stew pots (KM and RM) you can't expect exactly the same seasoning on every plate.

KM had at least historical and maybe also design philosophy reasons to differ from RM in NEC1 combos.

The Robman · Posted: Tue Aug 03, 2004 6:53 pm Post subject:

I think it was just that at the time we first needed an NEC combo, there wasn't an official exec to do this, so we wrote one and called it "01 40". Since then, obviously, UEI has also decided that they too need a combo exec and they wrote one.

Whenever possible, we will use a built in exec over one we wrote ourselves as it will use alot less EEPROM memory.
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!

Capn Trips · Expert Joined: 03 Oct 2003 Posts: 3990

I roger all of the three explanations about the NEC1 Combo (hacked) {original} protocol vs. the NEC1 Combo (official) {newer} protocol.

My observation (relying on memory only) is/was that using the "known" discretes for video inputs, and a handful of other functions (contrast +-, brightness +-, sharpness +-, etc), when I used the hacked protocol (with KM and 1994) in KM 2 years ago, those functions DID NOT WORK.

When I use the official protocol (with RM and 2117 - which if I read your explanantions correctly, the remote and program are immaterial here, it's only the protocol that is at issue) these functions work correctly.

So my gross conclusion is that the official protocol yields better results - at least for the device 24/24.231 family of signals.

I may get around to testing just for curiosity - build identical upgrades and have each call on a different protocol and test all of the functions for consistency/divergence - or is that a waste of time?

The Robman · Posted: Tue Aug 03, 2004 8:43 pm Post subject:

If the official protocol works and the hacked one doesn't, don't bother messing around with the hacked one.
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!