When selecting an interface device to the GRX system consider the
GRX-CI-PRG. This has an astronomic clock (not yet used) and RS232 iterface.
If used in conjunction with smth like moxa or iTach you get more
connections to the lutron system compared to the max of 2 given by the
ethernet only GRX-CI-NWK-E version.
You would also need to log in to the GRX-CI-NWK-E (using the startup
command in system properties)
PRG also offers more commands.
If your client has the GRX 3500 or greater version you can use gauges to
display the intensities. . . smth the 3000 series does not report . . .
EOM for interface: \x0D\x0A
Here is a regex I wrote a while back for displaying the current scene
(there are 16 possible scenes you can program in):
Feedback from hercules:
:ss 000420M0{0D}{0A} (note the starting colon)
Explanation:
1st 2nd, 3rd 6th and 8th controllers are on scene zero (off)
Controller four is on scene 4 and controller five is on scene 2.
Controller 7 is missing from the system. (I have only 7 controllers)
This is not tested properly so please be careful:
.*ss\s[A-F0-9M][A-F0-9M](0)?(1)?(2)?(3)?(4)?(5)?(6)?(7)?(8)?(9)?(A)?(B)?(C)?(D)?(E)?(F)?[A-F0-9M][A-F0-9M][A-F0-9M][A-F0-9M][A-F0-9M].*
Explanation:
We are currently looking at controller 3 out of a possible total of 8 in
the Lutron GRX system system.
The square brackets contain all possible scenes for the controllers we
DO NOT care about. (this might not be the best way of representing this
comments welcome)
If interested in controller 4 one would move the capture indexes.
.*ss\s[A-F0-9M][A-F0-9M][A-F0-9M](0)?(1)?(2)?(3)?(4)?(5)?(6)?(7)?(8)?(9)?(A)?(B)?(C)?(D)?(E)?(F)?[A-F0-9M][A-F0-9M][A-F0-9M][A-F0-9M].*
See attached picture for setting up the feedback groups in Gui Designer.
Not had to use it yet so maybe some comments from Jarrod or fiasco or
fpillet (or anyone) about accuracy of regexes.
In regards to the attached spreadsheet: I copy and paste into notepad
(remove all the tab characters) and paste into your GUI. Remember to
save as ASV file as well.
Fiasco has a smart way of using feedback to limit the number of buttons
and commands used in a system (much more efficient).
Perhaps an example Fiasco?
One last thing:
You need advanced button properties for increasing or reducing the
intensities. (see lutron intensities worksheet/tab on attached spreadsheet)
Hope this helps
Nahshon

To view this discussion on the web visit https://groups.google.com/d/msg/commandfusion/-/0VZnZXUBraQJ.--
You received this message because you are subscribed to the Google Groups "CommandFusion Software" group.
To post to this group, send email to comman...@googlegroups.com.
To unsubscribe from this group, send email to commandfusio...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/commandfusion?hl=en.