brettcp
Member
Member
Posts: 71
Joined: Fri Sep 12, 2008 7:13 pm
Location: San Diego, CA
Contact: Send private message AOL

Russound RIO Driver - Power Toggle not working

Wed Feb 08, 2017 7:09 pm

I'm using the Allonis Russound RIO Driver (latest as of today) with my Russound MCA-C5 and can't seem to get the power toggle command to work properly, it seems to only be working one-way:

If a zone is OFF, then the toggle command will turn it on.
If a zone is ON, then the toggle command will *not* turn it off.

AV|1~Power~4~On and AV|1~Power~4~Off work just fine.

Here is a log of what's seen when I issue the command "AV|1~Power~4~Toggle" :

2/8/2017 4:00:13 PM ProcessCommand Cmd=[1~Power~4~Toggle] Client=[MyClient1]
2/8/2017 4:00:13 PM TX:1 event C[1].Z[4]!ZoneOn
2/8/2017 4:00:13 PM ProcessResponse RX:C[1].Z[1].status="ON"
2/8/2017 4:00:13 PM ProcessResponse RX:C[1].Z[1].sharedSource="ON"
2/8/2017 4:00:13 PM ProcessResponse RX:C[1].Z[4].status="ON"
2/8/2017 4:00:13 PM ProcessResponse RX:C[1].Z[4].sharedSource="ON"
2/8/2017 4:00:13 PM ProcessResponse RX:C[1].Z[6].volume="13"
2/8/2017 4:00:13 PM ProcessResponse RX:C[1].Z[1].volume="18"
2/8/2017 4:00:13 PM ProcessResponse RX:C[1].Z[6].sharedSource="ON"
2/8/2017 4:00:13 PM ProcessResponse RX:C[1].Z[6].status="ON"
2/8/2017 4:00:13 PM ProcessResponse RX:C[1].Z[6].volume="20"
2/8/2017 4:00:13 PM ProcessResponse RX:C[1].Z[3].sharedSource="ON"
2/8/2017 4:00:13 PM ProcessResponse RX:C[1].Z[3].status="ON"
2/8/2017 4:00:13 PM ProcessResponse RX:C[1].Z[3].sharedSource="OFF"
2/8/2017 4:00:13 PM ProcessResponse RX:C[1].Z[3].status="OFF"
2/8/2017 4:00:13 PM ProcessResponse RX:C[1].Z[1].sharedSource="OFF"
2/8/2017 4:00:13 PM ProcessResponse RX:C[1].Z[1].status="OFF"
2/8/2017 4:00:13 PM ProcessResponse RX:C[1].Z[1].sharedSource="ON"
2/8/2017 4:00:13 PM ProcessResponse RX:C[1].Z[1].status="ON"
2/8/2017 4:00:13 PM ProcessResponse RX:C[1].Z[1].volume="20"
2/8/2017 4:00:13 PM ProcessResponse RX:C[1].Z[1].sharedSource="OFF"
2/8/2017 4:00:13 PM ProcessResponse RX:C[1].Z[1].status="OFF"
2/8/2017 4:00:13 PM ProcessResponse RX:C[1].Z[4].sharedSource="OFF"
2/8/2017 4:00:13 PM ProcessResponse RX:C[1].Z[6].sharedSource="OFF"
2/8/2017 4:00:13 PM ProcessResponse RX:C[1].Z[6].status="OFF"
2/8/2017 4:00:13 PM ProcessResponse RX:C[1].Z[4].status="OFF"

Here is what I get when I do a "AV|1~Power~4~On"

2/8/2017 4:01:16 PM ProcessCommand Cmd=[1~Power~4~On] Client=[MyClient1]
2/8/2017 4:01:16 PM TX:1 event C[1].Z[4]!ZoneOn
2/8/2017 4:01:16 PM ProcessResponse RX:C[1].Z[1].status="ON"
2/8/2017 4:01:16 PM ProcessResponse RX:C[1].Z[1].sharedSource="ON"
2/8/2017 4:01:16 PM ProcessResponse RX:C[1].Z[4].status="ON"
2/8/2017 4:01:16 PM ProcessResponse RX:C[1].Z[4].sharedSource="ON"
2/8/2017 4:01:16 PM ProcessResponse RX:C[1].Z[6].volume="13"
2/8/2017 4:01:16 PM ProcessResponse RX:C[1].Z[1].volume="18"
2/8/2017 4:01:16 PM ProcessResponse RX:C[1].Z[6].sharedSource="ON"
2/8/2017 4:01:16 PM ProcessResponse RX:C[1].Z[6].status="ON"
2/8/2017 4:01:16 PM ProcessResponse RX:C[1].Z[6].volume="20"
2/8/2017 4:01:16 PM ProcessResponse RX:C[1].Z[3].sharedSource="ON"
2/8/2017 4:01:16 PM ProcessResponse RX:C[1].Z[3].status="ON"
2/8/2017 4:01:16 PM ProcessResponse RX:C[1].Z[3].sharedSource="OFF"
2/8/2017 4:01:16 PM ProcessResponse RX:C[1].Z[3].status="OFF"
2/8/2017 4:01:16 PM ProcessResponse RX:C[1].Z[1].sharedSource="OFF"
2/8/2017 4:01:16 PM ProcessResponse RX:C[1].Z[1].status="OFF"
2/8/2017 4:01:16 PM ProcessResponse RX:C[1].Z[1].sharedSource="ON"
2/8/2017 4:01:16 PM ProcessResponse RX:C[1].Z[1].status="ON"
2/8/2017 4:01:16 PM ProcessResponse RX:C[1].Z[1].volume="20"
2/8/2017 4:01:16 PM ProcessResponse RX:C[1].Z[1].sharedSource="OFF"
2/8/2017 4:01:16 PM ProcessResponse RX:C[1].Z[1].status="OFF"
2/8/2017 4:01:16 PM ProcessResponse RX:C[1].Z[4].sharedSource="OFF"
2/8/2017 4:01:16 PM ProcessResponse RX:C[1].Z[6].sharedSource="OFF"
2/8/2017 4:01:16 PM ProcessResponse RX:C[1].Z[6].status="OFF"
2/8/2017 4:01:16 PM ProcessResponse RX:C[1].Z[4].status="OFF"


...and a "AV|1~Power~4~Off":

2/8/2017 4:02:00 PM ProcessCommand Cmd=[1~Power~4~Off] Client=[MyClient1]
2/8/2017 4:02:00 PM TX:1 event C[1].Z[4]!ZoneOff
2/8/2017 4:02:01 PM ProcessResponse RX:C[1].Z[1].status="ON"
2/8/2017 4:02:01 PM ProcessResponse RX:C[1].Z[1].sharedSource="ON"
2/8/2017 4:02:01 PM ProcessResponse RX:C[1].Z[4].status="ON"
2/8/2017 4:02:01 PM ProcessResponse RX:C[1].Z[4].sharedSource="ON"
2/8/2017 4:02:01 PM ProcessResponse RX:C[1].Z[6].volume="13"
2/8/2017 4:02:01 PM ProcessResponse RX:C[1].Z[1].volume="18"
2/8/2017 4:02:01 PM ProcessResponse RX:C[1].Z[6].sharedSource="ON"
2/8/2017 4:02:01 PM ProcessResponse RX:C[1].Z[6].status="ON"
2/8/2017 4:02:01 PM ProcessResponse RX:C[1].Z[6].volume="20"
2/8/2017 4:02:01 PM ProcessResponse RX:C[1].Z[3].sharedSource="ON"
2/8/2017 4:02:01 PM ProcessResponse RX:C[1].Z[3].status="ON"
2/8/2017 4:02:01 PM ProcessResponse RX:C[1].Z[3].sharedSource="OFF"
2/8/2017 4:02:01 PM ProcessResponse RX:C[1].Z[3].status="OFF"
2/8/2017 4:02:01 PM ProcessResponse RX:C[1].Z[1].sharedSource="OFF"
2/8/2017 4:02:01 PM ProcessResponse RX:C[1].Z[1].status="OFF"
2/8/2017 4:02:01 PM ProcessResponse RX:C[1].Z[1].sharedSource="ON"
2/8/2017 4:02:01 PM ProcessResponse RX:C[1].Z[1].status="ON"
2/8/2017 4:02:01 PM ProcessResponse RX:C[1].Z[1].volume="20"
2/8/2017 4:02:01 PM ProcessResponse RX:C[1].Z[1].sharedSource="OFF"
2/8/2017 4:02:01 PM ProcessResponse RX:C[1].Z[1].status="OFF"
2/8/2017 4:02:01 PM ProcessResponse RX:C[1].Z[4].sharedSource="OFF"
2/8/2017 4:02:01 PM ProcessResponse RX:C[1].Z[6].sharedSource="OFF"
2/8/2017 4:02:01 PM ProcessResponse RX:C[1].Z[6].status="OFF"
2/8/2017 4:02:01 PM ProcessResponse RX:C[1].Z[4].status="OFF"

brettcp
Member
Member
Posts: 71
Joined: Fri Sep 12, 2008 7:13 pm
Location: San Diego, CA
Contact: Send private message AOL

Re: Russound RIO Driver - Power Toggle not working

Fri Feb 10, 2017 6:22 pm

Any word on this?

I can confirm that Toggle *does* work with the Russound serial driver.. so I had to move back to that for now. Would love to eliminate this serial cable and go with RIO. Thanks.

User avatar
AllonisDave
Founder
Founder
Posts: 11164
Joined: Fri Feb 07, 2003 8:56 am
Location: Sedona, AZ
Contact: Send private message

Re: Russound RIO Driver - Power Toggle not working

Tue Feb 14, 2017 4:18 pm

The RIO driver is still a work in progress. I've never had the opportunity to remote into a machine that has a suitable Russound controller for testing. I do have an upcoming job that has two MCA-C5s and I'll be using the RIO driver on that project. So the driver will get updated soon.

brettcp
Member
Member
Posts: 71
Joined: Fri Sep 12, 2008 7:13 pm
Location: San Diego, CA
Contact: Send private message AOL

Re: Russound RIO Driver - Power Toggle not working

Tue Feb 14, 2017 5:00 pm

Thanks, looking forward to seeing this fixed! Also I should mention that when I use a volume slider with the RIO driver, once I move the volume slider, it jumps around for a second before settling on the position I set it to.. with the Russound serial driver, the slider works as expected and does not jump around. Thanks!

User avatar
DavidL
Founder
Founder
Posts: 11373
Joined: Sat Feb 08, 2003 9:39 am
Location: Metamora, Michigan
Contact: Send private message Website

Re: Russound RIO Driver - Power Toggle not working

Mon Jun 19, 2017 7:45 pm

Russound Rio driver is now updated in myInstaller.

Return to “A/V Family Device Drivers”

Who is online

Users browsing this forum: No registered users and 1 guest