RC5 Protocols.ini -- corrected entry

Discussion forum for JP1 software tools currently in use, or being developed, such as IR, KM, RemoteMaster, and other misc apps/tools.

Moderator: Moderators

Post Reply
jon_armstrong
Expert
Posts: 1238
Joined: Sun Aug 03, 2003 9:14 pm
Location: R.I.P. 3/25/2005
Contact:

RC5 Protocols.ini -- corrected entry

Post by jon_armstrong »

I posted a correction to the RC5 protocol here

I think the RC5Translator is broken. The column width is too narrow in the functions tab to see whether the OBC>63 or not. I also can't get OBC to accept a number greater than 63 because I don't have a place to stash the top bit that really comes from bit 6 of fixed data for whichever device is chosen.
-Jon
johnsfine
Site Admin
Posts: 4766
Joined: Sun Aug 10, 2003 5:00 pm
Location: Bedford, MA
Contact:

Post by johnsfine »

I'm still hoping for some comment from Greg on this topic.

Whether or not a kludge in the protocols.ini entry can cover up some of the symptoms, the RC5Translator code is wrong. (I haven't looked at what Jon did to see how much of the symptoms are covered up).

I reviewed the code, and it appears Greg was fixing a problem in import of KM files when he removed the functionality that I'd like to put back and also made the typo that looses one of the OBC bits.

I don't understand the KM import issue, so if I put back the functionality I want to put back, I'll likely rebreak the import.
gfb107
Expert
Posts: 3411
Joined: Sun Aug 03, 2003 7:18 pm
Location: Cary, NC
Contact:

Post by gfb107 »

I'll have some comments later, when I get a chance to look at it more carefully. I'm a bit busy at the moment.
gfb107
Expert
Posts: 3411
Joined: Sun Aug 03, 2003 7:18 pm
Location: Cary, NC
Contact:

Post by gfb107 »

I'm adding back the code to automatically change the selected device when the user enters an OBC incompatible with the OBC>63 flag for that device.

I'm also fixing the incorrect mask for the OBC.

Look for v1.02 soon.
Post Reply