Russound CAV 6.6 "Whole House Audio"

pasha · Post by **pasha** » Tue Aug 30, 2005 7:00 am

Please help with protocol upgrade for Russound remote

Pronto link (untested) rus-dis-cav66uno.zip

1. Device: Russound CAV 6.6
2. Type of device: Whole House Audio
3. JP1 Remote model: URC-8811
4. JP1 user? Yes
5. Still have original remote? Yes
6. Checked the file section? Yes
7. Checked Pronto file section (at R/C)? Yes (untested link posted)
8. Partially working setup code? No
9. Learning remote question? few learned codes attached.

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

johnsfine · Post by **johnsfine** » Tue Aug 30, 2005 7:47 am

I edited your post above so the URL to RemoteCentral doesn't make this whole thread too wide to read easily.

I checked and you are right that your learned signals match the corresponding one in that CCF.

I can't recall if anyone has built a Russound protocol executor for JP1 or found one UEI built.

Russound protocol has a four way bit structure, a nasty check nibble, and a changing lead-in that each make writing a protocol executor trickier than typical.

I could rediscover the things I've forgotten for solving those issues. But at the moment I don't have time. Usually when I say I don't have time to construct a Protocol executor, Rob jumps in and proves it was easier than I thought. Hopefully he will this time.

The best description I have of Russound is in my DecodeIr documentation:

http://john.fine.home.comcast.net/ir/De ... l#Russound

Capn Trips · Post by **Capn Trips** » Tue Aug 30, 2005 8:03 am

johnsfine wrote:I can't recall if anyone has built a Russound protocol executor for JP1 or found one UEI built.

Try looking in THIS THREAD wherein Rob created a Russound protocol and device upgrade.

pasha · Post by **pasha** » Tue Aug 30, 2005 8:04 am

I've seen that one... no it's not working for me....

johnsfine · Post by **johnsfine** » Tue Aug 30, 2005 8:29 am

As I noted in that thread the signals there had some similarity to the protocol we previously identified as "Russound" but they weren't the same protocol.

The signals in this thread are exactly the protocol we had previously identified as Russound.

In that thread, Rob attacked the complex structure by breaking the signal into a larger number of smaller "bits" rather than making the executor understand the true bit structure of the protocol. That method tends to require much longer hex commands meaning more work either in setting up a manual upgrade in KM or in defining a protocols.ini entry for RM, plus a much larger resulting device upgrade. But that's usually better than waiting longer for someone to write a more complex executor.

I haven't totalled the details of this one, but I think the real bits would each require two, three or four smaller bits and the 4-bit check nibble would be added to that. So an 8 bit command might take as much as 4*(8+4) = 48 bits of hex command. An upgrade with 6 byte hex commands would be pretty ugly. Probably the distribution of bits makes the true worst cast a lot better, but even 4 or 5 bytes of hex command is quite ugly when 1 should be enough.

pasha · Post by **pasha** » Tue Aug 30, 2005 12:25 pm

It looks like original russound remote is based on the same chip....

I've put manual to
https://www.hifi-remote.com/forums/dload ... le_id=2144

I will try to open it tonight. If there is an eeprom I will post dump... Hopefully it would be helpfull.

-Pasha

johnsfine · Post by **johnsfine** » Tue Aug 30, 2005 12:47 pm

That documentation doesn't leave much doubt that internally the Russound remote is the same as a JP1 remote. And it has learning so it almost certainly has an eeprom.

Usually that would mean the Russound protocol would be included in the eeprom as a factory loaded upgrade. If that's the case then we can easily port it over to a form that KM and RM can make upgrades for your 8811.

Edit: I had assumed someone else already did the simple forum search to see if all this had been done before. So I didn't try that search myself until just now. It sure looks like all this work has already been done:

https://www.hifi-remote.com/forums/viewt ... t=russound

pasha · Post by **pasha** » Tue Aug 30, 2005 1:32 pm

Thanks for the link.... However it looks like there is no protocol upgrades in it.

Post by **The Robman** » Tue Aug 30, 2005 1:51 pm

johnsfine wrote:I checked and you are right that your learned signals match the corresponding one in that CCF.

Except that the learned signals show 40 kHz and the ones in the CCF show 57.6 kHz.

johnsfine wrote:In that thread, Rob attacked the complex structure by breaking the signal into a larger number of smaller "bits" rather than making the executor understand the true bit structure of the protocol. That method tends to require much longer hex commands meaning more work either in setting up a manual upgrade in KM or in defining a protocols.ini entry for RM, plus a much larger resulting device upgrade. But that's usually better than waiting longer for someone to write a more complex executor.

I know what you're getting at and I would normally agre with you, except in that case even with the smaller bits, the signal was still just 7 bits total, and the executor was tiny. If I'd tried to write a 4-burst exec for it, I would still have had to use 1 byte per command and the exec would have been much larger.

In this case, however, I totally agree that this is a 4-burst protocol. I haven't looked at the learned signals, but the ones in the CCF decode quite straight forwardly using 4-bursts.

In Pronto hex...

lead-in (1st) = 0155 0044
lead in (rest) = 00AA 0044
lead out = 0022 06B9

0 pair = 0022 0022
1 pair = 0022 0044
2 pair = 0044 0022
3 pair = 0044 0044

There are eight 2-bit pairs where the first 3 pairs appear to be fixed, leaving 5 variable pairs.

johnsfine · Post by **johnsfine** » Tue Aug 30, 2005 2:17 pm

I can't recall everything I deduced vs. guessed when I added this to DecodeIr. But the documentation I left from that process says there are two bursts of device number, then four bursts of function number then two bursts of check nibble.

pasha · Post by **pasha** » Tue Aug 30, 2005 3:15 pm

Well UNO-LRC1 has JP1 connector
so here is dumo from it.... https://www.hifi-remote.com/forums/dload ... le_id=2145
how I can convert it over for URC-8811

-Pasha

gfb107 · Post by **gfb107** » Tue Aug 30, 2005 3:27 pm

If you use RM, you can import the raw upgrade from IR (Advanced -> Import Raw Upgrade..)
Give it a try.

pasha · Post by **pasha** » Tue Aug 30, 2005 3:42 pm

I'm getting message:

The selected protocol "PID 00 62" (0062) is not compatible with selected remote. This upgrade will NOT function correctly. Please choose a different protocol.

gfb107 · Post by **gfb107** » Tue Aug 30, 2005 3:57 pm

When I look the device upgrade, it has the Protocol > FF box checked. You must check that in RM as well.

The interesting thing here is that the protocol used by this upgrade is PID 01 62, which is the DirecTV protocol!

gfb107 · Post by **gfb107** » Tue Aug 30, 2005 4:22 pm

Which device key are you using to control your Russound Whole House Audio? Is it the DVD key, which is assigned setup code OEM/0079? If not, importing the raw upgrade into RM won't do any good.