Russound CAV 6.6 "Whole House Audio"

If you have learned signals that don't get decoded when you look at them in IR.exe, post your file to the Diagnosis Area then post your question here (including a link to the file).

Moderator: Moderators

The Robman
Site Owner
Posts: 21886
Joined: Fri Aug 01, 2003 9:37 am
Location: Chicago, IL
Contact:

Post by The Robman »

Just FYI, this is a UEI proprietary protocol, so I guess it could turn up in any remote, not just DirecTV and Russound. They call it "UEI Low Latency". I don't like the idea of using the "DirecTV" name for all of it's variations, when we know that DTV uses just one variation.

My vote is still to create a master entry, using a more generic name, where you have the flexibility to change both the LO and freq. For this master entry, you would be provided the full UEI version of the exec. Then create additional entries, on an "as needed" basis, for any remotes that we discover that use it. These entries should provide the stripped down exec that John wrote, with the freq and LO adjusted accordingly.

As for the possible confusion caused by bad learns, I don't buy that having some learns show up as "DTV 38" and some as "DTV 40" is any less confusing that having them use whatever other names we come up with. After all, the signals are all going to show the same device codes and OBCs. If the user is stumped by it (just like they are when they see NEC2 and NEC mixes, caused by bad learns) they'll ask about it and we'll advise. However, I still think that the amount of support we'll have to give for bad learns will be WAY less than what we would have to give if we forced everybody to look for the freq and lead out times.
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
Post Reply