UEI codes - biggest Code Search ever?

underquark · Post by **underquark** » Sat Oct 29, 2005 1:34 pm

Devices.XLS lists many UEI setup codes, their associated protocols, fixed data etc. Some, I believe, are missing and some change over time as old codes are ditched in favour of newer ones. One question also often asked is "what are the values for UEI setup code xxxx?"

I have gone to the European OneForAll site and dowloaded a few WAV files for the URC8060 (a 1st-generation Kameleon). There are thousands of files each with several upgrades but here are just a few that I have extracted so far:

https://www.hifi-remote.com/forums/dload ... le_id=2423

Post by **The Robman** » Sat Oct 29, 2005 2:28 pm

Good work UQ. You can take this a stage further if you like. Did you know that you can open WAV files using IR, which will then convert them into regular raw upgrades. You could then inport those raw upgrades into RM, which will convert them into regular upgrades.

I have a question about your xls, why is the pid column mostly blank?

underquark · Post by **underquark** » Sat Oct 29, 2005 2:48 pm

The Robman wrote:You can take this a stage further if you like.

Have done. Open IR, select "Import from WAV". Look at the Devices tab - just below the "K" of Key Map there is a button which exports the upgrade to the clipboard and from there you can paste it into the growing spreadsheet. Added bonus is that you can save the IR file in much less space (18k) than a WAV file (500-1000K).

Now I'm going back to the site and constructing a list of all the WAV files for all the devices so that I can keep track of which ones have been "done".

The protocol ID column is mostly blank because I missed it out to begin with, then added it in but haven't filled in the blanks yet. This spreadsheet is probably less than 1% finished. I'll work on this a bit more and if folks are interested I'll see if there is a way to let volunteers add little chunks.

underquark · Post by **underquark** » Sun Oct 30, 2005 7:11 am

Update. Combined spreadsheets into one file:

https://www.hifi-remote.com/forums/dload ... le_id=2423

underquark · Post by **underquark** » Thu Nov 10, 2005 9:18 am

During the course of searching out upgrades I have noticed some inconsistencies in DEVICES.XLS. _pid_$002A, for instance often shows Device 127 and Fixed Data 80 but I can't seem to reproduce this in KM. Is DEVICES.XLS wrong, am I wrong (more likely) or can the fixed data vary?

johnsfine · Post by **johnsfine** » Thu Nov 10, 2005 9:31 am

DEVICES.XLS is wrong.

pid 002A should have 5 bit lsb comp translation for the device number. But device.xls uses 8 bit msb comp.

The fixed data can vary. Because only 5 bits are used any fixed data value from 80 through 87 is the same device number 30. But that is a seperate issue from the incompatibility you are commenting on.

Keeping all the tools (devices.xls, KM, RM, DecodeIr, etc.) in sync is very difficult. You have to expect some incompatibilities like this in the more obscure protocols.

Post by **The Robman** » Thu Nov 10, 2005 10:31 am

Just FYI, don't put too much stock in how devices.xls translates protocols that haven't been given names yet (ie, if they still have pid 002A type names) as I probably didn't even try to figure them out yet and just made quick guesses.

If you want to see how devices.xls translates the hex into device codes, look at the devices-dev.xls version.

underquark · Post by **underquark** » Fri Nov 11, 2005 7:48 am

johnsfine wrote:Keeping all the tools (devices.xls, KM, RM, DecodeIr, etc.) in sync is very difficult. You have to expect some incompatibilities like this in the more obscure protocols.

Actually I was just too insecure to say "Hey, the darned spreadsheet's wrong". I appreciate detailed answers such as yours which (hopefully) gives myself and others some insight into WHY these inconsistencies arise rather than just confirming that they do. As I learn more codes I periodically go back over the data and will flag up any other problems that I find. Eventually this might result in a grand unified theory of everything spreadsheet - some sort of HyperDevices.XLS - with setup codes, protocols, data, which remotes they can be found on and upgrade codes for the common buttons.

You don't get trouble like this with commercial software - much! A famous "Auto-route" program, for instance, suggests that I visit my parents' house by taking a short-cut down a road that I know for a fact was closed 30 years ago and neglects to mention that the electrified railway going straight across it might pose a slight impediment to the average driver.

johnsfine · Post by **johnsfine** » Fri Nov 11, 2005 8:27 am

The Robman wrote:If you want to see how devices.xls translates the hex into device codes, look at the devices-dev.xls version.

I don't have time to. But maybe underquark does.

underquark wrote: As I learn more codes I periodically go back over the data and will flag up any other problems that I find.

Maybe you want to go a step further and put the corrections into Rob's spreadsheet yourself.

IIUC, there is a master version of the xls (? probably that devices-dev.xls file Rob mentioned) that includes formulas for info that is determined by general rules. The normal devices.xls is then generated from that. I'm sure you can coordinate with Rob so that you could put a batch of corrections into the file.

underquark · Post by **underquark** » Fri Nov 11, 2005 8:51 am

Time, as Einstein said, is relative

. I'll take a look at the development version of Devices.XLS. Yeah, I'll gather up anything I find and post corrections as a small spreadsheet that the Robman can vet before altering the original. With regards to splicing the Devices info and the UEI upgrade codes data I think I might be heading for too big a spreadsheet as more data accumulates but I'll have a go anyway.