Difference between revisions of "User Defined Data - UDD"
From Zenitel Wiki
| Line 1: | Line 1: | ||
| − | + | [[Event Handler]] scripts can have variables. The variables are called '''User Defined Data - UDD'''. A UDD is a 32-bit integer value. The content of a UDD survives reset. | |
There are 6000 variables. The Event Handler programmer can use the variables any way they want, but they must keep track of how the 6000 variables are used. It is not possible to give the variables names. | There are 6000 variables. The Event Handler programmer can use the variables any way they want, but they must keep track of how the 6000 variables are used. It is not possible to give the variables names. | ||
Revision as of 11:04, 4 April 2008
Event Handler scripts can have variables. The variables are called User Defined Data - UDD. A UDD is a 32-bit integer value. The content of a UDD survives reset.
There are 6000 variables. The Event Handler programmer can use the variables any way they want, but they must keep track of how the 6000 variables are used. It is not possible to give the variables names.
Write to an UDD variable:
- WUDD index value : Command string action to Write a value to User Defined Data. The value is changed immediately, before the next statement is executed. Can only be used to change values in local exchange.
- $WUDD UINT2 index, UINT2 value : Data Protocol message to Write a value to User Defined Data. Can be used to change variable in remote exchange in AlphaNet. �Example: “@2 $WUDD w 10 w 40” writes the value 40 to variable at index 10 in node 2. ��Note that if $WUDD is sent from the Event Handler, the value is changed when the message is received. Which will be after all statements in the event-action have been executed.
Read an UDD variable
- %UDD(index) : Command string macro to get value of User Defined Data. Text formatting parameters can be added at the end.