JP1 Remotes

All sounds good to me.

Here's something you could address while you are at it. The other day I was trying to create a Device Combiner upgrade with RM and I could not figure out how. I thought it was a selection in the protocol list, like it is in KM, but it wasn't there, so I started digging into readme files and stuff and just couldn't figure it out, so what I did was start one in KM and then open it in RM.

I figured out what the problem was, the remote that I just happened to have selected in RM (which was probably the XML RDF) didn't have the DC set up, so RM didn't offer it.

I think it would be a much better idea to always have the DC in the protocol list and either have it not be selectable if the remote doesn't support it, or better yet, allow it to be selected but have some sort of message that says the remote is not yet supported.

Another thing that has bitten me several times is the fact that different protocols have different columns in the Functions sheet, so if you switch from one protocol to another and then switch back, there is a chance that you will lose all of your code data. Likewise on the Setup tab, if different protocols refer to the device code cells with different names, you might lose that data too. This is one of the things that I've always preferred with KM because, as it's just a spreadsheet, the data in the columns will remain even if the column heading changes, etc.

I also seem to remember that RMIR used to hide the protocol upgrades from the user, is that still the case? If so, how would this be done in the RMIR world...

Supposing we have come up with a custom executor that addresses a particular users needs, so we advise them to create their upgrade in the normal way using KM or RM, then when they copy it over to IR, they should use the custom protocol instead of the one that may or may not be supplied by KM/RM.

Is something like that still possible with RMIR/RM.

gfb107 wrote:There has been some discussion about starting a JP1 wiki hosted here at hifi-remote.com, but it seems to have stalled since no one has any experience setting one up.

I just bumped that thread with a suggestion to get it started, and even volunteered my time to help get it going.

gfb107 wrote:We plan v2.00 to be "RDF Feature Complete," which means supporting everything documented in the RDF Specs and addendums, making RM a complete replacement for both IR and KM for "typical" use.

After that we start adding the bells and whistles and advanced functionality that will truly make IR and KM obsolete.

There will in fact be two bells and whistles already by the time v2.00 comes out. Viewing and (live) editing of the RDF is already there, through a toolbar icon. There will also be a Code Selector, as in IR.exe, but that is not yet done. Code Validation will of course also be there, as that is part of making it "RDF Feature Complete".

mathdon wrote: There will in fact be two bells and whistles already by the time v2.00 comes out. Viewing and (live) editing of the RDF is already there, through a toolbar icon. There will also be a Code Selector, as in IR.exe, but that is not yet done. Code Validation will of course also be there, as that is part of making it "RDF Feature Complete".

I must admit I haven't tried the latest version yet as I have been very busy at work - but is the protocol disassembler in yet/planned?

If my project goes well I should have time to get back to looking into the learned code/upgrade wizard in a couple of weeks..

xnappo

No, the protocol disassembler is not in yet, and I don't think it has been added as a feature request.

I think we've started to stray from the original topic of this thread. Maybe we should start a new thread or move the discussion to the good old RMIR: Prototype IR function in RM

gfb107 wrote:I think we've started to stray from the original topic of this thread. Maybe we should start a new thread or move the discussion to the good old RMIR: Prototype IR function in RM

Agreed, and done.

mdavej, There is something "wrong" with your .ir file, or at least something that RM doesn't like.

First RM parses the hex, and in the process discovers that you have a device upgrade installed for the Multiplex Device, which used PID 01FE. PID 01FE is not a builtin protocol, and is not installed as a protocol upgrade. So the device upgrade must be bad and is discarded.

Then it parses the [Notes] section and sees this note: It attempts to assign this note to device upgrade #8 (that's what the $3008 means). But an upgrade was discarded, and there is no device upgrade #8, and since I didn't allow for that in the code, RM dies.

To get around this, remove the Multiplex Device Upgrade, or install the Multiplex Protocol Upgrade.

This kind of error in the .ir file should not cause RM to die, so a code fix is needed.

Got it. Thanks.

I can see this is kind of a sticky problem. If you ignore the one bad upgrade and import the rest, then you have an orphan device upgrade. It's almost like you have to import it anyway to maintain full compatibility with IR files which allow bad upgrades. In any case I'll definitely remove my bad one first in IR.

I guess the point is that the remote allows bad upgrades to reside in the memory, even if it doesn't let you assign them to a device button. So therefore, RMIR should allow the bad upgrades too.

If the error checking gets too tight, it kind of limits what we can do "outside the box". I have run into several situations where I can sneak stuff past the remote, but IR won't allow me to do what I want without jumping through hoops.

gfb107 wrote:RMIR is taking over. You can get to RM by opening a .rmdu or (KM) .txt file, or by File > New > Device Upgrade

I hate to be a luddite, but this is a backwards step for me. My modus operandi just involves using RM and it is a bit of a pain having to go through RMIR, which I will use VERY infrequently.

Can we not have an additional shortcut to go directly to RM ?

alanrichey wrote:I hate to be a luddite, but this is a backwards step for me. My modus operandi just involves using RM and it is a bit of a pain having to go through RMIR, which I will use VERY infrequently.

Can we not have an additional shortcut to go directly to RM ?

I agree that it would be nice to have a shortcut that goes directly to RM.

However, the new interface doesn't actually require any additional steps.

Old RM steps:
1) Fire up RM
2) Click File > Open
3) Select an upgrade file

New RMIR steps:
1) Fire up RMIR
2) Click File > Open
3) Select an upgrade file

Actually, if the upgrade that you need is a KM file, there's actually one less step, because the old RM always defaulted to RMDU files, so you would always have to change it to look for KM files. The new RMIR looks for "all supported files" so you can see both KM and RM files at the same time, which is great.

Fair point, well made I did say luddite

Quick question guys when I open a IR file it does not show the key Moves this is with a RS 15-134 Extender xshifted V1.10 remote if I open it in IR803 the Key Moves are there?

Thanks,
dolivas

From the first post in this thread

key moves that (1) have the same device type and setup code as their bound device button and (2) the device type and setup code match an installed device upgrade will automatically become part of the device upgrade, and not be shown as a keymove)

dolivas27 wrote:Quick question guys when I open a IR file it does not show the key Moves this is with a RS 15-134 Extender xshifted V1.10 remote if I open it in IR803 the Key Moves are there?

Thanks,
dolivas