one thing that burned me is making sure you use the "correct" integration IDs.
I started out just interfacing to the QS processor using phantom keypads for scene control using device integration IDs; that worked fine.
After that was working, I had to control a few individual loads so I used the dimming/switch modules configured with device integration IDs; no feedback or control.
it turns out that you need to use zone integration IDs for controlling individual dimmers/switches and not the device integration IDs; once I made that change, everything works just fine
toggle quoted message
Show quoted text
-----Original Message-----
From: Tray Schaeffer <trayschaeffer@...>
Sent: May 9, 2013 9:00 AM
To: Crestron@...
Subject: Re: [Crestron] Lutron QS designer / QS module r02 / MC3
I¡¯ll keep that in mind. So far, the r02 modules are working for communications and control.
Need to debug the feedback but that is likely an ID issue in code.
Thank you all,
Tray
From: Joseph Vossen
Sent: Thursday, May 09, 2013 8:20 AM
To: Crestron@...
Subject: Re: [Crestron] Lutron QS designer / QS module r02 / MC3
I'm using Lutron's r01 modules running on a MC3 with no issues, I haven't tried the r02 modules yet.
perhaps rollback to the r01 modules unless you need something in the r02 modules.
as an aside, the connection I am using is RS232, not TCP
On May 8, 2013, at 3:21 PM, Tray wrote:
Lutron QS modules r02 with MC3.
Can't login at all to the unit, no commands sent, no reply at all.
Trying to connect IP to port 23. Can telnet via PC but the TCP/IP client in the MC3 does not work at all.
The tech on site does have the Lutron designer software open.
Will that designer connection prevent the MC3 from logging in normally?
Grateful for any help as I am not a Lutron expert.
