Lutron Ip Comms

vining

This is basically a repost of other's posted points regarding Lutron IP communications.

1. Unlike RS 232 send strings which require CR ($0D or 13) IP send strings require CRLF ($0D,$0A or 13,10).

2. Login is "'username,password',CRLF". They both must be sent in the same string!.
This must be configure in Illumination software under addressing tap 9 ip/drivers or something. This is where you set the type of feed back you want from HomeWorks as well.

The line feed requirement and the login string requirements took forever to find in the threads last night so I fgure I'd consolidate under one, hopefully easier to find thread.

RicardoSiqueira

Do you use the AMX Lutron Intercative Comm Module or you have your own? I remember while ago that the AMX module wasn't processing correctly the LED feedback when using IP. But it worked fine under RS-232. Any suggestions? Below is how I am handling it with RS-232.

<QUOTE>
//Store info for Physical link phantoms on 1:6:?
VOLATILE INTEGER nHWI_BUTTONS_B[32][15]
VOLATILE CHAR sHWI_KP_B[32] //32 keypads - Max 32 per link
VOLATILE CHAR sHWI_BUT_B[15] //15 buttons - Max 24 per keypad

DATA_EVENT[vdvHWI]
{
STRING:
{
IF(data.text == 'N:1')
{
STACK_VAR INTEGER i

//Keypads to monitor on Physical link 1:6:i
FOR (i = 1; i < 9; i++) //Note: Reduce number if not using all ??? 6/14/07
{
SEND_COMMAND vdvHWI, "'N:K:[1:6:',ITOA(i),']', 13, 10"
}
}
}
}

DATA_EVENT[vdvHWI]
{
STRING:
{
//Process RF link 1:6:? LEDs
IF (FIND_STRING(DATA.TEXT, "'K:L:[1:6:'", 1))
{
REMOVE_STRING(DATA.TEXT, '[1:6:', 1)
sHWI_KP = REMOVE_STRING(DATA.TEXT, ']:',1)
SET_LENGTH_STRING(sHWI_KP, LENGTH_STRING(sHWI_KP)-2)
sHWI_BUT = REMOVE_STRING(DATA.TEXT, ':',1)
SET_LENGTH_STRING(sHWI_BUT, LENGTH_STRING(sHWI_BUT)-1)
nHWI_BUTTONS[ATOI(sHWI_KP)] [ATOI(sHWI_BUT)] = ATOI(DATA.TEXT)
}
}
}

DEFINE_PROGRAM
//LIGTHS FEEDBACK FOR ROOMS (Monitoring OFF State = 1)
[vTP_LUTRON, 501] = (nHWI_BUTTONS[1][2] == 1) //Entry
[vTP_LUTRON, 502] = (nHWI_BUTTONS[2][2] == 1) //Dining
[vTP_LUTRON, 503] = (nHWI_BUTTONS[3][2] == 1) //Kitchen
//....etc
</CODE>

RicardoSiqueira

Sorry, I used the wrong tags. I don't know what I was thinking. Here is the correctly formated message:

Do you use the AMX Lutron Intercative Comm Module or you have your own? I remember while ago that the AMX module wasn't processing correctly the LED feedback when using IP. But it worked fine under RS-232. Any suggestions? Below is how I am handling it with RS-232.

//Store info for Physical link phantoms on 1:6:?
VOLATILE INTEGER nHWI_BUTTONS_B[32][15]
VOLATILE CHAR sHWI_KP_B[32] //32 keypads - Max 32 per link
VOLATILE CHAR sHWI_BUT_B[15] //15 buttons - Max 24 per keypad

DATA_EVENT[vdvHWI]
{
    STRING:
    { 
        IF(data.text == 'N:1')
        {
            STACK_VAR INTEGER i

            //Keypads to monitor on Physical link 1:6:i 
            FOR (i = 1; i < 9; i++) //Note: Reduce number if not using all ??? 6/14/07
            {
                 SEND_COMMAND vdvHWI, "'N:K:[1:6:',ITOA(i),']', 13, 10"
            }
        }
    }
}

DATA_EVENT[vdvHWI]
{
    STRING:
    {
        //Process RF link 1:6:? LEDs
        IF (FIND_STRING(DATA.TEXT, "'K:L:[1:6:'", 1))
        {
            REMOVE_STRING(DATA.TEXT, '[1:6:', 1)
            sHWI_KP = REMOVE_STRING(DATA.TEXT, ']:',1)
            SET_LENGTH_STRING(sHWI_KP, LENGTH_STRING(sHWI_KP)-2)
            sHWI_BUT = REMOVE_STRING(DATA.TEXT, ':',1)
            SET_LENGTH_STRING(sHWI_BUT, LENGTH_STRING(sHWI_BUT)-1)
            nHWI_BUTTONS[ATOI(sHWI_KP)] [ATOI(sHWI_BUT)] = ATOI(DATA.TEXT)
        }
    }
}

DEFINE_PROGRAM
//LIGTHS FEEDBACK FOR ROOMS (Monitoring OFF State = 1)
[vTP_LUTRON, 501] = (nHWI_BUTTONS[1][2] == 1) //Entry
[vTP_LUTRON, 502] = (nHWI_BUTTONS[2][2] == 1) //Dining
[vTP_LUTRON, 503] = (nHWI_BUTTONS[3][2] == 1) //Kitchen
//....etc