If you have a new remote that isn't recognized by RMIR, post the details here so we can help create a new RDF for it. Or, if there is an issue with an existing RDF or map, this is the place.
insaneoctane wrote:When I use ir.exe and choose "download remote" it pops up an error dialog box titled "ir" with the message "list out of bounds (195)".
If you haven't deleted the corrupted CBL/0476 device upgrade discussed above, I think that error has to do with that. After downloading the data from the remote, go to the "Devices" tab and delete that upgrade. Once you upload the data back in to the remote without the upgrade, the error should be gone.
insaneoctane wrote:After I click "OK", I notice in the RAW DATA tab the data goes has data to 19F0...which I think is too far (I think 1400 was max from the test program)?? Also, the raw data now starts at 0600??
Before, IR didn't know where the data started so it just listed from "$0000" on, to end at $1400. Now, since you have the RDF file with data on where the memory starts (at $0600) IR lists the raw data from the starting point, and end $1400 later, which would be $1A00 (which is why the last line you see in raw data tab is $19F0).
You can get the same "list out of bounds" error if you open up the original raw .IR file.
What you should do is make a copy of your raw .IR file and then make the edit suggested by Robman using Notepad. Then open up this modified .IR file in IR7.exe. It should not complain about the "list out of bounds" error. You can then upload this .IR file into your remote. Any future downloads won't have the corrupted device upgrade.
Also, just FYI, if you do do the edit that I suggested, when you open the IR file using IR.exe you will get a pop-up message about a bad checksum. This is OK, the reason that the checksum is bad is because you edited the data without re-calculating the checksum, so just let IR fix the checksum for you.
Rob www.hifi-remote.com Please don't PM me with remote questions, post them in the forums so all the experts can help!
The Robman wrote:As to your question of how this screwy data got into your remote, we have no idea. It was obviously loaded that way at the factory. As to why they even tried loading CBL/0476 into the remote, that's an even better question, as this code is pre-installed in just about every UEI remote, so I would be very surprised if it isn't resident in the ROM of your remote.
Is it possible that they do this as a part of the ID lock function? I have found that the cable cos install their cable box code and "lock" it in so that it cannot inadvertantly be changed or deleted. The remote's instruction manual has a section on the actions to be taken if the remote is to be used with a different cable box.
I made the suggested modifications that Robman made. I then loaded that into IR.exe, which DID complain about the checksum (thanks for mentioning that part- I would've stopped had I not been warned!). Then, I pushed the file to the remote. Now, when I download from the remote, no error! Yea, thanks for that. Now, on to see if I can figure this whole RM and IR.exe thing and control my Philips HTS...
I think all the experts trying to follow this thread would prefer fewer screen shots.
If there is something we ought to see in RM or IR that we could see on our own machines if we had your files, then we would much rather have your files in the diagnosis area and see those things on our own machines.
Screen shots are mostly appropriate for cases where they show something we couldn't get ourselves even if we had copies of your files.
Regarding the problem itself, you have better experts than me in this thread, but my guess from what you've said is that the rdf file does not correctly represent the upgrade area for this model. Maybe that preloaded upgrade would have been correct if we understood how this model stores upgrades.
I think the remote reset the device code because it didn't understand the upgrade area and thus didn't think the setup code given was valid.
Sorry for the image overload and thanks for converting them to just links. What you said makes sense, that the remote doesn't think the upgrade code is valid (I tried it manually, since the upgrade device is supposed to be inside the remote now, and it reacts just like when you type an device it doesn't have...it gives a long blink, not two quick blinks). What files, data, or anything can I provide that will help anyone help me? I'm extremely appreciative of everyone's time and access to your knowledge! Again, sorry for any faux pas with regards to posting etiquette.
I just realized that we never came back to this thread to close it out. It turns out that the device upgrade wasn't corrupted after all, the format of the device upgrades has changed in this remote.
Previously, the first byte of the device upgrade code was the 2nd byte of the protocol id (pid). The first byte of the pid could only be "00" or "01", so they set aside a single bit in the hex code used for the setup code to store this value. This meant that the maximum setup code value was 2047 rather than 4095 (using 3 nibbles of data).
Well, UEI obviously realized that they were running out of both setup codes and protocol ids, so they expanded the pid in the device upgrade code to 2 bytes, which allows them to use pids greater than "01FF". This also means that they don't need to set aside the bit from the setup code hex, which raises the ceiling on setup codes to 4095.
We've moddified IR.exe (v7.01) to look for a new RDF parm which should be set as follows for remotes like this...
2BytePid=Yes
We've also modified RM to look for this parm. When found, it will use a slightly different header for the upgrade code that it generates.
The new header is ...
""Upgrade Code2 = "
compared to the old header, which was...
""Upgrade Code = "
Rob www.hifi-remote.com Please don't PM me with remote questions, post them in the forums so all the experts can help!
For some reason, all of my posts the last 3 days have vanished. I got my hands on 7 Atlas PVR Day remotes yesterday. They are all learning models, with Time warner logo.
The Labels are as follows:
URC11055BCo C054503 JP1
URC11055BC0 C054103 JP1
11055WC0-227-0023-057 C062401 JP1.2
11055WC0-227-0023-057 C061601 JP1.2
11055BA1-XXX-0001-001 A070601 JP1.3
11055BC2-227-0023-1015 C070101 JP1.3
11055BA1 227-0023-0005 A062901 JP1.3
Looks like they are all over the lot as far as age, processor, etc.
Now the sad news. Yesterday at my daughter's I downloaded IR and the RDF files, and was able to talk to all 7 remotes. I also tested learning and inputting device codes. All looked OK. Today when I got home, I tried to talk to them from my computer, and got the same stuff I have been experiencing with the older non learning ones. Can't talk to anything!
Downloaded a new copy of IR, RM and RDFs into a new directory, same result.
I was using the same JP1x cable in both places.
So now I am tired, and totally confused...
My head has cleared a little. I note that in RM, there is only one Atlas..JP1.3 Day, while in the list of rdf there are 2, the 30003000 and the 30333033. I suspect I am getting the wrong one. Can this inconsistency in naming be straightend out??
I think it may work if I can make the upgrades with the 30003000, since I am getting an error message in IR for signatures not matching....
Also those rdf called just 3000 and 3033 don't seem to match anything...
I know this model of remote is confusing because, like all of the other UEI/Cable remotes, there are alot of remotes that look the same on the outside but are different internally. However, you absolutely should let IR.exe chose the RDF for you. You should not pick a different RDF with a different signature and use it to program a remote, as this will lead to all sorts of (predictable) problems.
If you suspect that someone may have already loaded data from an incorrect RDF into a remote, you should do a 981 reset and download again.
If, when you use the correct RDF, there are problems, those problems should be addressed with the RDF that you are using.
Rob www.hifi-remote.com Please don't PM me with remote questions, post them in the forums so all the experts can help!
