Multiple 232 commands in succession

vegastech wrote: »

Patient fellow forum'ers: Why doesn't this work? If I look in debugger, I see the string sent out 4 times:

Line      1 (18:46:51)::  FADEDIM,60,[1:1]$0D$0A
Line      2 (18:46:51)::  FADEDIM,70,[1:2]$0D$0A
Line      3 (18:46:51)::  FADEDIM,80,[1:3]$0D$0A
Line      4 (18:46:51)::  FADEDIM,90,[1:4]$0D$0A

Here is the code:

BUTTON_EVENT[dvTPLight,30]  //send lighting preset 1 to all 4 light zones
{
	PUSH:
	{
		local_var integer i
		FOR(i=1;i<=4;i++)
		{
			SEND_STRING dvLight, "'FADEDIM,',itoa(uLightPresets[1].nZone[i].nIntensity),',[1:',itoa(i),']',$0D,$0A"
			SEND_STRING 0, "'FADEDIM,',itoa(uLightPresets[1].nZone[i].nIntensity),',[1:',itoa(i),']',$0D,$0A"

From the Lutron protocol manual:

Each command is made up of fields, separated by commas, and terminated with a carriage return <CR> = $0D Hex.

And:

Some commands allow parameters to be omitted, and a default value will be used. In this case, the delimiting commas must still be used

The FADEDIM command syntax is:

FADEDIM, <intensity>, <fade time>, <delay time>, <address 1>, ..., <address n>

Your output looks like this:

Line      1 (18:46:51)::  FADEDIM,60,[1:1]$0D$0A

You don?t need the $0A and you need the delimiting commas for fade and delay. So your output should really look like this:

Line      1 (18:46:51)::  FADEDIM,60,,,[1:1]$0D

So try changing this:

SEND_STRING dvLight, "'FADEDIM,',itoa(uLightPresets[1].nZone[i].nIntensity),',[1:',itoa(i),']',$0D,$0A"

To this:

SEND_STRING dvLight, "'FADEDIM,',itoa(uLightPresets[1].nZone[i].nIntensity),',[b],,[/b][1:',itoa(i),']',$0D"

And see if that gets you any further.

Lutron should be able to handle 4 commands in succession, however, I would do what Stephen Bolton suggested and build yourself a queue.

Check out this thread: http://amxforums.com/showthread.php?t=5372&highlight=queuing

Jeff

Not really...the wait in the for wouldn't do anything, and the wait after won't help you. You could manually send all four strings with waits, but writing a queue is quite easy. (I've probably written them in 10 or more different ways and most of them very quickly)

Sending Levels

I am working the same problem and having trouble with my Data Event sending a level. Any suggestions appreciated.

DATA_EVENT[dvLights]
{
STRING:
{
IF(FIND_STRING(DATA.TEXT,"'DL'",1)) // DL,[1:4],50,$0D,$0A
{
STACK_VAR CHAR strTemp[24] INTEGER nZone INTEGER nLevel;

strTemp = DATA.TEXT; // hold string in temp
SET_LENGTH_ARRAY(strTemp, LENGTH_STRING(strTemp)-2); // DL,[1:4],50,~~~~$0D,$0A

(******************)
SEND_STRING 0, "'<<<dvLights strTemp= ', strTemp";
(******************)
REMOVE_STRING(strTemp,':',1); // DL,[1:~~~~4],50
nZone = ATOI(GET_BUFFER_CHAR(strTemp)); // 4~~~~],50,
nLevel = ATOI(strTemp); // 50,
SEND_LEVEL dvTP_Lights,nZone,(nLevel/255); // as per example - level bargraph (nZone #4) will go to (nLevel 50%)
(******************)
SEND_STRING 0, "'<<<dvLights nZone= ', ITOA(nZone), ' - nLevel= ', ITOA(nLevel)";
(******************)
}
}
}

Notifications:

Line 1 (18:47:48):: Level Value To [10001:12:1] - Level 9 Value= 112
Line 2 (18:47:48):: Level Value To [10001:12:1] - Level 9 Value= 109
Line 3 (18:47:48):: Level Value To [10001:12:1] - Level 9 Value= 107

Update

The code compiles but is not sending the strings to the program nor are the levels showing up on the TP.

DATA_EVENT[dvLights]
{
STRING:
{
IF(FIND_STRING(DATA.TEXT,"'DL'",1)) // DL,[1:4],50,$0D,$0A
{
STACK_VAR CHAR strTemp[24] INTEGER nZone INTEGER nLevel;

strTemp = DATA.TEXT; // hold string in temp
SET_LENGTH_ARRAY(strTemp, LENGTH_STRING(strTemp)-2); // DL,[1:4],50,~~~~$0D,$0A

(******************)
SEND_STRING 0, "'<<<dvLights strTemp= ', strTemp";
(******************)
REMOVE_STRING(strTemp,':',1); // DL,[1:~~~~4],50
nZone = ATOI(GET_BUFFER_CHAR(strTemp)); // 4~~~~],50,
nLevel = ATOI(strTemp); // 50,
SEND_LEVEL dvTP_Lights,nZone,(nLevel/255); // as per example - level bargraph (nZone #4) will go to (nLevel 50%)
(******************)
SEND_STRING 0, "'<<<dvLights nZone= ', ITOA(nZone), ' - nLevel= ', ITOA(nLevel)";
(******************)
}
}
}