I can confirm #2 and #3 don't work on my MCA-C3 (with MDK-C6 keypads) either.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?
Here's the test message I tried to send to the keypad.. no text shows up on the keypad: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.
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 reasonbrettcp 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.
Users browsing this forum: No registered users and 2 guests