dr.frazier
Senior Member
Senior Member
Posts: 230
Joined: Sat Oct 15, 2005 11:27 pm
Contact: Send private message

Re: Russound Driver Released

Sun Dec 15, 2013 1:10 am

An update to the first part. Turned off and reset server as well as cav6.6 network. All keypads pass Controller id correctly but zone id is passed as 1 for all zone keypads. I could have sworn it was passing correctly before but i may be mistaken. May be a bug in driver.

dr.frazier
Senior Member
Senior Member
Posts: 230
Joined: Sat Oct 15, 2005 11:27 pm
Contact: Send private message

Re: Russound Driver Released

Sun Dec 15, 2013 1:25 am

And I answered my second question. I can just assign the button property to call the macro rather than an AV command. Must be late. It sure wasnt that obvious a few minutes ago.
Sorry

User avatar
AllonisDave
Founder
Founder
Posts: 11604
Joined: Fri Feb 07, 2003 8:56 am
Location: Newport Beach, CA
Contact: Send private message

Re: Russound Driver Released

Sun Dec 15, 2013 1:18 pm

>>> All keypads pass Controller id correctly but zone id is passed as 1 for all zone keypads.

Can you show me the Russound event log when you press one of these buttons and it passes the wrong zone #?

dr.frazier
Senior Member
Senior Member
Posts: 230
Joined: Sat Oct 15, 2005 11:27 pm
Contact: Send private message

Re: Russound Driver Released

Sun Dec 15, 2013 1:43 pm

Attached log from mlserver and russound as well as another crash log
Attachments
RussoundError.txt
(2.74 KiB) Downloaded 132 times

dwarfer
New Member
New Member
Posts: 47
Joined: Wed Nov 08, 2006 1:58 pm
Contact: Send private message

Re: Russound Driver Released

Thu Dec 19, 2013 11:03 am

I am also seeing updates as Controller 1 Zone 1 for updates coming from an Uno in Zone 2. Also none of my variables update when pressing the UNO keys or via IR. Variables are only updating when I send commands via MLServer. This is on a CAV 6.6. Log attached.

Thanks
Russound-log.txt
(6.71 KiB) Downloaded 220 times

rileydog
Expert
Expert
Posts: 701
Joined: Wed Jun 02, 2004 1:25 am
Location: Kalamazoo, Michigan
Contact: Send private message

Re: Russound Driver Released

Sun Jan 12, 2014 3:31 pm

I just switched from the legacy to the new driver (not the RIO) - I have (2) MCA-C5's... Device driver sees them and variables are populated.

1) Loudness isn't reported properly - I change it on the keypad and it seems to be ignored - it always shows 0
2) Messages to keypads are not working - I sent the command in ML and I don't see any messages on the keypads
3) I can't get the macros for keypads working - I created a macro russound.keypad.fav1 and have a simple command in there to test - I press that button on the keypads and nothing happens.

I am just starting to test and have only moved a few zones over. I will report more as I uncover issues.

Should I be using the RIO driver?

Thanks,

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

Re: Russound Driver Released

Mon Jan 13, 2014 1:29 pm

rileydog wrote:I just switched from the legacy to the new driver (not the RIO) - I have (2) MCA-C5's... Device driver sees them and variables are populated.

1) Loudness isn't reported properly - I change it on the keypad and it seems to be ignored - it always shows 0
2) Messages to keypads are not working - I sent the command in ML and I don't see any messages on the keypads
3) I can't get the macros for keypads working - I created a macro russound.keypad.fav1 and have a simple command in there to test - I press that button on the keypads and nothing happens.

I am just starting to test and have only moved a few zones over. I will report more as I uncover issues.

Should I be using the RIO driver?

Thanks,
I can confirm #2 and #3 don't work on my MCA-C3 (with MDK-C6 keypads) either.

User avatar
AllonisDave
Founder
Founder
Posts: 11604
Joined: Fri Feb 07, 2003 8:56 am
Location: Newport Beach, CA
Contact: Send private message

Re: Russound Driver Released

Mon Jan 13, 2014 5:53 pm

Can one or both of you perform a careful experiment for me? Turn on event logging to a file in the Russound driver. Clear the log and then issue one loudness change and one message command. Then email me the resulting Russound.log file in the \Logs folder.

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

Re: Russound Driver Released

Mon Jan 13, 2014 6:21 pm

CinemarDave wrote:Can one or both of you perform a careful experiment for me? Turn on event logging to a file in the Russound driver. Clear the log and then issue one loudness change and one message command. Then email me the resulting Russound.log file in the \Logs folder.
Here's the test message I tried to send to the keypad.. no text shows up on the keypad:

1/13/2014 3:19:00 PM ProcessCommand Cmd=[1~Message~1~Hello World] Client=[MyClient1]
1/13/2014 3:19:00 PM TX:1 F0 00 00 00 00 00 70 00 02 01 01 00 00 00 01 00 0F 00 00 00 00 48 65 6C 6C 6F 20 57 6F 72 6C 64 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 45 F7
1/13/2014 3:19:01 PM ProcessResponse Handshake Message [F0 00 00 70 00 00 00 02 02 6D F7]

rileydog
Expert
Expert
Posts: 701
Joined: Wed Jun 02, 2004 1:25 am
Location: Kalamazoo, Michigan
Contact: Send private message

Re: Russound Driver Released

Mon Jan 13, 2014 7:16 pm

I toggled loudness on the keypad and didn't see any messages in the log. Several seconds later, I see the enclosed messages.

What is strange is when I do other things on the keypad, like changing the turn on volume, that instantly shows in the log. So, I don't know if this is just chatter or if it is indeed related to loudness...
Attachments
Screen Shot 2014-01-13 at 6.10.45 PM.png
Screen Shot 2014-01-13 at 6.10.45 PM.png (84.99 KiB) Viewed 2831 times

rileydog
Expert
Expert
Posts: 701
Joined: Wed Jun 02, 2004 1:25 am
Location: Kalamazoo, Michigan
Contact: Send private message

Re: Russound Driver Released

Mon Jan 13, 2014 7:23 pm

Here is the log when I issue a loudness command on and off - so from ML it works, I verified the commands work fine. But, choosing loudness on the keypads isn't updating the ML variables - I think this was reported before, where the keypads get out of synch to the ML variables? Anyhow, I still see unrecognized commands in the log when issuing ML commands. Thanks
Attachments
Screen Shot 2014-01-13 at 6.18.42 PM.png
Screen Shot 2014-01-13 at 6.18.42 PM.png (172.74 KiB) Viewed 2831 times
Screen Shot 2014-01-13 at 6.16.16 PM.png
Screen Shot 2014-01-13 at 6.16.16 PM.png (196.62 KiB) Viewed 2831 times

rileydog
Expert
Expert
Posts: 701
Joined: Wed Jun 02, 2004 1:25 am
Location: Kalamazoo, Michigan
Contact: Send private message

Re: Russound Driver Released

Mon Jan 13, 2014 8:21 pm

I think I know why sending text messages from ML to the MDK keypads won't work - RNET only sends text to the keypads. According to the RIO documentation (which that protocol is only supported on the MCA's), you have to send text in relation to a screen template (there are many screen templates on the MDK to choose from, like a template that has graphics, selectors, etc.). Those MDK keypads are much more sophisticated than the Uno's where they were a single line text display. I suspect the RNET call to that keypad is ignored, similar to it ignoring the RNET command to change the background color of the displays.

The more I read the more it appears that the "new" MCA's need to use the RIO protocol to use a lot of these features. I also suspect key triggers have to happen with the RIO protocol as well. The RIO protocol document has much more capabilities that are not addressed in RNET.

I suspect that the keypad synch issues to ML (where pressing buttons on the keypad don't register in ML), macros firing off key commands and messages to the keypads will have to be done with RIO and not RNET too....

dr.frazier
Senior Member
Senior Member
Posts: 230
Joined: Sat Oct 15, 2005 11:27 pm
Contact: Send private message

Re: Russound Driver Released

Sat Feb 01, 2014 9:24 pm

Any update to the keypads passing incorrect zone id to the driver? Hopefully an easy fix. Needed to configure keypads
Thanks
Randy

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

Re: Russound Driver Released

Mon Feb 17, 2014 2:33 pm

brettcp wrote:I'm using 4.0.4964.18436 and am having an odd issue.. zone 6 doesn't seem to be responding to all off/all on.. Zones 1 through 5 respond just fine, but its as if zone 6 is being ignored. All zones are set to respond to All On Participation in the MCA configuration.

The variable for zone 6 (av_1_zone_6_power) isn't being updated when the All On / All Off command is executed.. all other zones do.

I'm using:

AV|1~Power~All~On
AV|1~Power~All~Off

Any ideas?
This is still an issue.. for now I got around it by writing a script to manually turn off each zone individually.. but All Off still doesn't work on all zones for some reason :(

User avatar
AllonisDave
Founder
Founder
Posts: 11604
Joined: Fri Feb 07, 2003 8:56 am
Location: Newport Beach, CA
Contact: Send private message

Re: Russound Driver Released

Tue Feb 18, 2014 10:30 am

There is an updated protocol document for the MCA that I recently obtained. It it quite different from the old protocol document I had. I have to update the driver to support the newer protocol and this should be fixed. It is high on the list.

Return to “MLServer 4 Device Drivers”

Who is online

Users browsing this forum: No registered users and 2 guests