Can't save a 'pause' function on db-14 button (URC-9910)

[bobn4burton]

I'm guessing I've just overlooked something dumb. I'm fairly new to JP1 programming...so go easy! I am using the URC-9910 with extender 1.1.

OK...so I've been trying to save some special protocol functions in IR. The problem I'm having is that if I program a Pause or LKP function to a button on the db-14 device, it seems to work fine until I save the file, exit IR, restart IR and open my saved file. When I re-open my saved file, the Device button has changed from db-14 to RCVR/AMP. For example, if I program the following:

Device Button -> db-14
Key -> 1
Type -> Pause
Function -> Hex: $99
HexCmd -> $99

Then it seems to stay fine even after I save the file. However, once I close my saved file and IR.exe and then restart IR.exe and open my saved file, it automatcially changes my Special Protocol function from example above to:

Device Button -> RCVR/AMP
Key -> 1
Type -> Pause
Function -> Hex: $99
HexCmd -> $99

Is there something dumb I have missed here? Is it not possible to program a pause or LKP function to a LOGICAL device (db-14, db-13, etc)?

If its just not possible to use a LOGICAL device such as db-14 to program special protocol functions to...then what is the best use of the LOGICAL devices?

TIA for any help!

[Capn Trips]

You cannot assign keymoves or macros to buttons in a logical device db-08 or above.

I don't understand the inner workings, but apparently, there are only 8 devices available for that sort of thing. The logical devices provide a (to some) convenient location to assign/list device upgrades or setup codes that you subsequently reference in OTHER keymoves and/or macros.

I haven't really figured out the utility of THAT, either, for that matter. I mean, you can go into the rdf and change the name from "db-14" to "AV switcher" and assign your AV switcher's setup code to db-14, and when you create other keymoves and macros calling on that device, IR's keymove display will tell you THAT is the setup code/upgrade from which you are calling that particular function, if that makes it easier for you to use IR, but it doesn't help the remote's functionality, imho. For what it's worth, that's my understanding of all those "extra" device indexes offer.

[johnsfine]

Keymoves are shared by pairs of device indexes. Indexes 0 and 8 share a set of keymoves. Indexes 1 and 9 share a set, etc.

Each keymove will work when either of the two indexes is selected.

IR doesn't store which of the two indexes was intended, so when you reopen the file IR will always display the lower of the two indexes. A keymove defined on index 8 would be active in both index 0 and index 8 before IR forgets that it was defined in 8, and it will still be active in both index 0 and index 8 after IR forgets that it was defined in 8.

With an extender or with a special protocol, you can select one of the higher device indexes as the current device. It is just as usable as one of the lower indexes. All the keys defined within the body of the setup code are unique to that index (assuming the setup code is) while all the keymoves are shared with another index.

If you plan to use more than 8 indexes, you should put some thought into which pairs of devices can safely share keymoves. If two different devices both want a keymove on the same button (presumably a different keymove) then you'll lose that if you make those two share. But if you have over 8 devices you probably have a few devices with few if any keymoves, so you ought to be able to work out the sharing.

With an extender, there is no need to associate the indexes directly with the same named device button. You can keep the buttons logically associated with the named devices even if the sharing constraints make you select device indexes that don't logically associate with the true devices.

[bobn4burton]

Thanks for the tips guys! It actually has helped me to understand quite a bit...