JP1 Remotes

[Joe Kane]

The latest IRhelp PDF file is very informative and filled in a lot of missing holes for me. I have been searching for something similar for RDF mod/generation, and can't find that (maybe for good reason).

I have spent a fair amount of time working on this remote and could use a little help. This model was an EOM cable remote that probably saw little to no mass production, so I'm not surprised that it doesn't have a set of files in the RDF distribution.

The remote itself is in a Millenium 4 housing, but was branded as 'Millenium Interactive' by UEI (and I have the manual for it). The remote shares a signature (UMIAUMI0) with a Charter URC-4393 OEM remote, for which Rob made a starter RDF, labeled as a work in progress. The remote itself is in a Millenium 4 housing, but was branded as 'Millenium Interactive' by UEI (and I have the manual for it). I Opened the remote and extracted the model number (URC41xxxB00) from the PCB silkscreen.

I used this (Robs starter RDF) as a base and made some changes to adapt to the remote, and get it load in RM without causing java null exception errors. Knowing that the masses are probably not interested in this remote, I also built my own image map/jpg combo and have that working in RM, so I can assign function keys etc.

Using the macro method, I decoded all the keycodes and named the keys to match the remote in the new RDF 'Millenium Interactive (URC41xxxB00).

Three of the keys that are giving me a little trouble are the 'macro keys', labeled DAY-, LOCK, and Day+. Since the manual calls these out as 'macro keys', it may mean that they are device independent (they don't appear in a device ButtonMap, and attempts to add them in weren't successful. (I know, don't mess with buttonmaps). In the original RAW dump of the remote, these keys had Macro EFCs assigned to them, to generate the equivalent codes for DAY-, LOCK, and DAY+ in GI Protocol.

I am attempting to just directly assign/map the functions to these keys, using a GI device upgrade (also included in my zip file). This doesn't appear to work, but that may be because the keys themselves cannot be assigned to a device via button map. I do have these keys identified in the keycode list in the RDF. (so RM and IR know the total count), but not sure if this is the right move.

In the GI protocol device upgrade, RM seems to recognize that these three keys aren't in a device button map, and when I associate the keys to their respective functions, RM automatically assigns keymoves for these three keys (keycodes $18, $20, and $28).

When I copy the device upgrade over to IR and upload to the remote, all the codes work as expected. However, a few issues:

1) When I looked at the key map in the 'devices' tab in IR, the keynames weren't matching up with the right hex codes, after I got past the grouped keys (number) ,(volume), (channel).

2) And sometimes the last three keys in the IR key map showed 'unassigned' (even though they weren't), which I assumed was due to this issue with the three macro keys being counted (or not counted) properly. All the keynames and functions matched up correctly in RM though. AND, all the keys on the remote were functioning properly, so the final mapping seems to be right.

As I open the files now to point out a few examples (after preparing them for zip and uploading them), this discrepancy has vanished. I did go through the process of copy/pasting the upgrades back in, so maybe there is sync issue or some operator error. I could have sworn I read something similar in an old post, but cannot find that now for the life of me.

Questions:

1) So does that issue ring a bell (key map in IR not in sync in RM)?

2)And is there a way to directly assign a function to the macro keys without a keymove?

3) Can you tell me what the right way to handle the macro keys is in the RDF definition? Anything else I need to fix in the RDF?

4) I'd also like to be able to directly assign functions to the number keys. I realize that right now those keys are driven by a table; but could find nothing in readme or post to decipher the DIGITMAP section. Aside from the "Anatomy of an upgrade' post by Rob, where he mentions that setting the second byte to zero will enable the keymap bitmap for the number keys, I couldn't locate anything to describe how I could effect that change in the RDF



I have included all the files in my upload to the analysis section, at this link:

http://www.hifi-remote.com/forums/dload.php?action=file&file_id=9104

The milleniuminteractive(URC41xxx).zip file contains the RAW dump of the remote before any changes, the jpg and map files, the starter and modified RDF, the millenium interactive upgrade IR file, and the GI protocol device upgrade file that I built.


Thanks,

Joe

[mr_d_p_gumby]

[Joe Kane]

[Joe Kane]

A somewhat related question:

Are the DEVICETYPE mappings in the RDF also hard-coded in the remote?

It would seem that they are. I started with the WIP starter RDF , where all the DEVICEMAP settings were originally set to zero.

[mr_d_p_gumby]