Device combiner questions

This is the JP1 beginners forum. There's no such thing as a stupid question in here, so post away, but this forum is just for JP1 users and people considering JP1, non-JP1 users please use the appropriate forum above!

Moderator: Moderators

Post Reply
Juppers
Posts: 52
Joined: Wed Feb 18, 2004 2:54 pm

Device combiner questions

Post by Juppers »

I haven't been able to get the device combiner to work and have a few questions to find out what I'm just not getting.

My remote is a RM-Y809, which I believe is sc38 based. If I use the device combiner for protocols that aren't in the rom, do I have to add those protocols as well as the device combiner protocol? Or do I just add the device combiner?

How do you know if a protocol is 1 byte or two byte?
gfb107
Expert
Posts: 3411
Joined: Sun Aug 03, 2003 7:18 pm
Location: Cary, NC
Contact:

Post by gfb107 »

You must add all the protocols.

You can tell by the length of the hex displayed on the functions sheet in RM/KM.
Juppers
Posts: 52
Joined: Wed Feb 18, 2004 2:54 pm

Post by Juppers »

Thanks. That explains why they didn't work. :)
Mark Pierson
Expert
Posts: 3018
Joined: Sun Aug 03, 2003 12:13 am
Location: Connecticut, USA
Contact:

Re: Device combiner questions

Post by Mark Pierson »

Juppers wrote:If I use the device combiner for protocols that aren't in the rom, do I have to add those protocols as well as the device combiner protocol?
From the Protocol Help sheet and "keymap-master-protocols.txt":
NOTE: On S3C8 remotes, when specifying an upgraded protocol ID, the user MUST ensure that the protocol code is installed on the remote (using IR), as KM has no way to verify this.
How do you know if a protocol is 1 byte or two byte?
If it's a named protocol, you can also look on KM's Protocols sheet.
Mark
Juppers
Posts: 52
Joined: Wed Feb 18, 2004 2:54 pm

Post by Juppers »

Ok. My thinking of what the device combiner is was wrong. I thought it could be used to save upgrade space by combining protocols. Now I see it is for mixing and matching remote codes so you don't have to use a bunch of keymoves and such. Thanks.
Mark Pierson
Expert
Posts: 3018
Joined: Sun Aug 03, 2003 12:13 am
Location: Connecticut, USA
Contact:

Post by Mark Pierson »

Juppers wrote:My thinking of what the device combiner is was wrong. I thought it could be used to save upgrade space by combining protocols.
I see how you thought that, and am surprised nobody's ever brought it up before.
The Device Combiner allows you to combine up to 16 different protocols into one Device Upgrade.
It should probably be changed to something more accurate, like "...combine up to 16 different devices...".

Does anyone have any other suggestions, since even the term devices can be misinterpreted?
Mark
Juppers
Posts: 52
Joined: Wed Feb 18, 2004 2:54 pm

Post by Juppers »

How about "The device combiner is a gateway interface to up to 16 protocols for use by a single or multiple devices."
Teleport
Posts: 15
Joined: Mon Apr 05, 2004 6:02 am

Post by Teleport »

Has anyone written a guide for using the device combiner?

Only I'm a little bit confused by what it does and doesn't do and it's methodology.

Thanks
Mark Pierson
Expert
Posts: 3018
Joined: Sun Aug 03, 2003 12:13 am
Location: Connecticut, USA
Contact:

Post by Mark Pierson »

Teleport wrote:Has anyone written a guide for using the device combiner?
The only guide is what's documented in the readme and on KM's [Protocol Help] sheet.
Mark
ElizabethD
Advanced Member
Posts: 2348
Joined: Mon Feb 09, 2004 12:07 pm

Post by ElizabethD »

Mark Pierson wrote:
Teleport wrote:Has anyone written a guide for using the device combiner?
The only guide is what's documented in the readme and on KM's [Protocol Help] sheet.
Teleport:
Mark once wrote this in answer to my question about combos vs combiner. To me this description clarified perfectly what it can be used for. And sheds light on protocol vs device confusion:
The DC is used to combine multiple dissimilar protocols into one (and they can only be 1-byte commands at that). While it can be used to combine multiple similar protocols, it really has no way to know that they are in fact similar. All it does is say "send command 'A' using protocol #1, command 'B' using protocol #2", etc.

The official Combo's combine similar devices that use the SAME protocol. They say "send all these commands using protocol #1, but command 'A' is sent with dev/sub-dev #1, and command 'B' is sent with dev/sub-dev #2", etc.
Post Reply