JP1 Remotes

I've been following the site fo some time, but this is my first post.

I have an Arcam CR80 remote (Catalyst 48) which I have been using sucessfully with IR. I have created a new RDF for it to rename some of the buttons from the existing Catalyst 48 entries (ZAP, Outlaw) soi that they match what I see on the remote.

I now want to add some new devices using keymap-master, but I'm only offered the Outlaw remote as an option in keymap. It makes allocating buttons tricky as the names are wrong.

Is it possible to get Keymap to use my RDF file, or can I change the button names for the Outlaw remote that keymap offers me?

Thanks

With an RDF file you can use RM. KM is much harder to add a new remote to. Why do you want to use KM rather than RM?

No particular reason. The documentation that I was reading was taking me throught the steps to add new devices to IR.

The documentation was for KM, would RM be better?

alanb wrote:The documentation was for KM, would RM be better?

Yes. Somewhere there is a version of that documentation for RM. But I forget where.

KM and RM do basically the same job. RM is a little easier to learn and to use. In a few special cases KM does something RM can't or RM does something KM can't.

RM requires that you first install Sun Java (which is free). KM requires that you first install Microsoft Excel (which is not free, but most of us already had it installed).

Here's the RM version of the Help doc...
http://www.hifi-remote.com/jp1/help/rm.shtml

I finally got around to reading that document.

To suggest corrections, should I just suggest them in a post, or should I download and edit the file and send it back (to?)

For example, just above Image 5.5 it says

Make sure that when you enter the additional codes you put them in the corrent column, either "OBC" (which stands for "Original Button Code") or "EFC" (which stands for "Extended Function Code", which are also known as "advanced codes")

1) I assume corrent is a typo for correct.

2) We may need a warning about "hex", such as: The hex column is for a OneForAll version of hex encoding. Manufacturers often publish the hex codes for their devices, but those hex codes are very rarely the same encoding that OFA uses. If you have additional codes in the manufacturer's version of hex, do a forum search or post a question for how to convert those codes to OBC numbers.

That's great. I'll give it a try this evening.

johnsfine wrote:To suggest corrections, should I just suggest them in a post, or should I download and edit the file and send it back (to?)

For example, just above Image 5.5 it says
...

Whatever is easier for you. The important thing is to make this a useful document.

If you think it's easier to download and edit yourself, free free to do so.

I'm also willing to make the edits if you'd rather just write them up that way.

If there are changes that you think merit discussion, a new thread is appropriate.

Simple corrections or enhancements can be sent directly to me.

Just keep in mind that this document is just an overview of how to use RM. It isn't the main documentation for RM. That's the Readme.html included with RM, which I also make available at http://controlremote.sourceforge.net/Readme.html.

I've already made the adustments you mentioned.

alanb wrote:I've been following the site fo some time, but this is my first post.

I have an Arcam CR80 remote (Catalyst 48) which I have been using sucessfully with IR. I have created a new RDF for it to rename some of the buttons from the existing Catalyst 48 entries (ZAP, Outlaw) soi that they match what I see on the remote.

I now want to add some new devices using keymap-master, but I'm only offered the Outlaw remote as an option in keymap. It makes allocating buttons tricky as the names are wrong.

Is it possible to get Keymap to use my RDF file, or can I change the button names for the Outlaw remote that keymap offers me?

Thanks

Could you post the RDF and a picture of the remote for me so I can include it in the next round of updates?

No problem.

I will need to test it first, but once thats OK I will post the data.

alanb wrote:No problem.

I will need to test it first, but once thats OK I will post the data.

Thanks

Added details for Arcam CR80, also Remotemaster definitions for Digifusion FVRT200 and Toshiba 220e

alanb wrote:Added details for Arcam CR80, also Remotemaster definitions for Digifusion FVRT200 and Toshiba 220e

Where? Anytime you want someone to look at a file you upload, it is common courtesy to post a link to the file.

I uploaded the files to Nils' Files Section that he referenced in his earlier post.

RDF File : https://www.hifi-remote.com/forums/dload ... le_id=2844

Digifusion FVRT200: https://www.hifi-remote.com/forums/dload ... le_id=2846

Toshiba 220e: https://www.hifi-remote.com/forums/dload ... le_id=2845

I am new to all this, and I am sorry if I didn't follow normal procedures, but "Please supply links to the files" would have got the same reply, and would have been more courteous.

Sorry if I seemed short. It's just that this "normal procedure" is standard web forum etiquette, and is stated clearly in the sticky threads in the beginners forum.

It is also something that we have to ask for on an almost daily basis, which gets old.