New guy here. I've been reading and searching all over the place to see if someone made an upgrade for the URC-9910, but to no avail. I've got a new RCA TV/DVD combo unit model 20F510TD. I am using Decodeir.dll version 2.32, and it still doesn't give a protocol name. I suspect it is just too new of a protocol. The learned codes all work just fine, but there are too many buttons (43) on the original remote to learn all of them at once due to not enough memory on the 9910. I've had to split the TV and DVD functions on two learn passes. The interesting thing about the remote is that it uses the same code for several functions on the TV itself, and the TV decides which function the code will control based on which mode you have placed the TV in using a TV or DVD button. It is like a shift button on a remote, but the shift is done at the TV, so you have to program these two buttons in to get the shift functionality. Once I find the upload location, I will upload the two IR files and see if you guys can identify the protocol so I can do the upgrade on this and have all the buttons working.

You will need an expert to determine whether those Gap decodes are indeed a new protocol or whether they indicate some learning problems. (The fact that the learned signals WORK does not mean that they were learned cleanly enough for decodeIR.dll to decode them.) Are you certain that you have followed all of the recommendations for best learning?

Also, two questions/recommendations:

(1) Why didn't you learn the OEM buttons to the corresponding 9910 buttons? Learning "8" to "TV/VID" and "CH+" to "Pause"
(a) makes no sense, and
(b) makes it very hard to keep track of what function is what;

(2) When you have notes about what function is learned to what button, it's best to put that info in the notes sections of IR. On the Learned Signals Tab, you will notice a "Notes" section at the bottom of the window for EACH learned signal. If you use that, then a person need not try to decypher a cross-reference chart, and is likely to have an easier time helping you.

I noticed that the learned codes basically look like timings of off and on cycles (and I've graphed them in Excel just to see what is what), and they vary slightly off from exacting numbers for whatever time they are, such as 500 us will show up as 492 us or 508 us, etc., so that is a possibility for lack of cleanliness when it comes to learning. Clock timing will never be perfect from device to device on lightwaves unless the clocks are both connected to a synched source.

I did follow all of the best learning practices. I actually found out on my own that if you do not follow them that you will get a single press code and a release code on occasion.

To answer the question, the 9910 doesn't have all the buttons labeled as the OEM remote has, and when learning all buttons, there will be some arbitrary buttons to be used on the learning remote. Since the learning remote is only partially capable of mapping 1:1 to the original remote button labels, it is just as arbitrary to use the correct labels and some incorrect labels as it is to learn them in the sequence that I used; Hence the reason for the map. There would have to be a map no matter what with this remote since it doesn't have the ability to map 1:1 to the original buttons. As with any application when you have a bunch of meaningless, arbitrary codes, you need a map to help you make them into something meaningful, no?

Now that I know the notes window is there (I missed it, quite obviously ), I have re-uploaded the files with the mapped keys noted in each notes section, and also added the mapping to the general notes section on both files.

I noticed that the learned codes basically look like timings of off and on cycles (and I've graphed them in Excel just to see what is what), and they vary slightly off from exacting numbers for whatever time they are, such as 500 us will show up as 492 us or 508 us, etc., so that is a possibility for lack of cleanliness when it comes to learning. Clock timing will never be perfect from device to device on lightwaves unless the clocks are both connected to a synched source.

I'm aware that there will always be some timing variations even in perfectly generated and learned signals, but decodeIR.dll is pretty darned good at smoothing through those. Clearly you have identified some of the things required to build your own protocol. I suggest you download Protocol Builder and read and follow these instructions to try to build your own protocol.

Again, I'm not smart enough to identify whether this protocol is simple enough that the document has sufficient detail to walk you through building a new protocol, but it's certainly a place to start.

M$Guy wrote:

I did follow all of the best learning practices. I actually found out on my own that if you do not follow them that you will get a single press code and a release code on occasion.

OK. I was just throwing it out there as a frequent cause of bad learns. But your learns are all pretty consistent, so I won't question that you learned them properly.

M$Guy wrote:

To answer the question, the 9910 doesn't have all the buttons labeled as the OEM remote has, and when learning all buttons, there will be some arbitrary buttons to be used on the learning remote. Since the learning remote is only partially capable of mapping 1:1 to the original remote button labels, it is just as arbitrary to use the correct labels and some incorrect labels as it is to learn them in the sequence that I used; Hence the reason for the map. There would have to be a map no matter what with this remote since it doesn't have the ability to map 1:1 to the original buttons. As with any application when you have a bunch of meaningless, arbitrary codes, you need a map to help you make them into something meaningful, no?

I understand your point, and see that you are rather fervent about it. I respectfully suggest that it appears that only about three or four functions in each mode really have no analogous button on the 9910 that would be "obvious" to learn to, and a map explaining 3 or 4 is simpler that a map addressing every button. Again, my point is if its all the same for you, fine, but if the goal is to make it as easy as possible for someone to help you, I suggest it's still useful to match as many of the functions as the two remotes would permit for ease of translation, but I will not belabor the point (any more than I already have). We can agree to disagree and it will have no impact on the issue at hand._________________Beginners - Read this thread firstREAD BEFORE POSTING or your post will be DELETED!

I seen that protocol before recently. I didn't get around to doing anything about it and I still don't have time.

I think Rob made an upgrade the last time we saw this, but I'm not certain about that. The last burst before the lead-out burst is tricky. I'm pretty sure PB can't generate that. Lately Rob has done more than I have in making executors for tricky protocols. He knows or remembers more of the ways of sidestepping the rules of simple protocol generation.

This RCA set uses a different device code (ie, the first 8 bits are 00000110 rather than 00000010) so you'll need a new upgrade. I'll try and cook one up for you later today._________________Rob
www.hifi-remote.comPlease don't PM me with remote questions, post them in the forums so all the experts can help!

Looking at the pictures of the remote, it appears that you missed the DISPLAY and PICTURE/SLEEP button.

I followed the link to the PDF of the user manual and it shows a different remote there, do you know why that is by any chance?_________________Rob
www.hifi-remote.comPlease don't PM me with remote questions, post them in the forums so all the experts can help!

Not sure what the deal is with that PDF. The remote I have pictured is the actual remote.

I did determine that the TV and DVD modes on the original remote do output different codes based on their selection (aka, a Shift function), so I have created new files, mapping all buttons to their respective locations as far as possible, then mapping everything else to sequential buttons in order on the 9910. I did this using both TV and DVD modes on the original remote, and learned everything into the TV mode on the 9910. I had to break them up into half the buttons per file due to memory space. The new files are here:

Cool, thanks. I took the info out of the files you created and compiled a new .IR file for myself. The TV portion only controls TV function, the DVD only controls DVD function, and the proper keys work as expected. I only have 4 keys learned, and that's on my DSS, I had to create a learned VOL+ and VOL- and the default code for DSS doesn't support the skip forward and back features of my DVR, so I had to learn those as well.

I see you already uploaded the upgrades to the Upgrades section, so I don't need to do it.